@guybrushmr80 No, Hue emulation doesn’t expose thermostats. Openhab use their own Alexa skill: https://github.com/openhab/openhab-alexa
This might be a good template for pimatic, though. If one doesn’t mind to open pimatic to the internet.
-
Alexa / Amazon Echo: Easy way to control MAX! Thermostats
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
@michbeck100 said in Alexa / Amazon Echo: Easy way to control MAX! Thermostats:
@guybrushmr80 No, Hue emulation doesn’t expose thermostats. …
But as mentioned above, at least you could control the MAX Thermostats as if they were light bulbs. I‘m using ha-bridge and get basically 3 different functions:
- Schalte Heizung aus -> set temperature to 16 degrees
- Schalte Heizung ein -> set temperature to 21 degrees
- Schalte Heizung auf < number> -> set temperature to <number>
-
@googlyeyz @GuybrushMR80 Just raise a feature request on github or better, create a pull request
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
@googlyeyz can you share your exact setup how you accomplished this? Sounds really interesting. I wouldn’t really need to set the exact temperature, turning the heaters on and off would be enough.
-
xCite86 posted detailed instructions a while ago here:
-
Shouldn’t it be possible to set up
a dummy switch that can be controlled with Alexa and have a rule that changes the temperature whenever that switch is triggered? I tried that yesterday but I’m struggling with setting the Max! Thermostat to “comfy” - “mode” seems only to support “manu” and “auto”. -
Which plugin do you use … pimatic-max or pimatic-maxcul ?
I have implemented the max support for the pimatic-maxcul. For me it works well.
currently i make the changes for the “normal” heating devices. ( DummyHeating/ pimatic-max )But maxcul is ready. Maybe someone can test the changes too?
The on/off temperature is comfort and eco temperature.
After this test i would create the pull request.
Just download the changed version of the echo plugin.# **stop pimatic first** cd /**pimatic-folder**/node_modules/ rm -rf pimatic-echo git clone https://github.com/treban/pimatic-echo.git cd pimatic-echo npm install # **start pimatic again**
-
I’m using pimatic-max - pimatic-maxcul is requiring additional hardware, replacing the cube, right?
-
not necessarily. i have flashed my cube with the cul-firmware. but this is a other topic.
I think this evening i will have implemented the other thermostats also.currently i dont now to which temperature i should translate the on/off commands.
-
I think the easiest way to turn the heater on/off would be to set them to comfy/eco. But I’m not sure how to set this in a rule… probably super simple but I just don’t get it.
-
The normal heating devices and also the max-devices (it extends the build-in heating device)
don’t have a comfy/eco temperature.
Only the max-cul plugin provides this settings.I think the best way would be to implement this values in the pimatic core heating device template,
instead to make this in the echo-plugin. -
but I can see and toggle the comfy/eco setting in the UI!?
-
nice. I overlooked that.
The comfy/eco values come from the config directly into the GUI without being present in the devices as an attribute.I’ll make the changes and let you know.
-
@GuybrushMR80
The changes are done. The plugin now supports the Dummy Heatingthermostat and both Max-Plugins.
Please check the changes. install-guide see post #14After that I will create the pull request.
@michbeck100 is currently preparing a new version for dot2 support. -
awesome! I have it a try and I think we’re almost there. Unfortunately whenever I ask Alexa to turn the heater on/off, pimatic seems to freeze. At least I get an “Could not connect (xhr poll error), retrying…”-error in the GUI. I setup the devices with the following parameters:
- hueType: Switch
- active: Yes
- additional names: Wohnzimmerheizung, Heizung im Wohnzimmer
Alexa finds two devices, based on the names above.
-
might also be an issue with my Max! setup - when I toggle to eco/comfy it also doesn’t work. The error is “error [pimatic]: Command was rejected”. Not sure if it worked before your changes.
EDIT: Setting the temperature also doesn’t work, same error message. Reading the temperature from the wall thermostats seems to work fine.
EDIT2: OK, for some thermostats it seems to work - from time to time. So the error occurs for some all the time for others not. I was thinking an unstable connection could be the issue but the one that doesn’t work is next to the cube… regardless of the issue I have I think the echo plugin needs to handle the error to avoid crashing pimatic. -
@guybrushmr80
the max system should work without the echo. If you have also problems with the max plug-in
your problems are based on that.The echo plugin only sets temperature like over the GUI.
EDIT:
MAX Commands over the GUI are reliable?! -
I used the OS X Max! software and everything works fine with this one. In pimatic I keep getting these “command rejected” errors…
As I said: Even if this is not a Echo specific issue, the plugin shouldn’t cause a crash of pimatic if this problem occurs.
EDIT: Opened a new thread on the Max! error: https://forum.pimatic.org/topic/3902/command-refused-error-with-max-plugin -
You are right. Can you post the last log messages and the exception before pimatic freeze please.
-
debug [pimatic-max]: Response: { accepted: false, duty_cycle: 51, free_memory_slots: 50 }
13:48:02debug [pimatic-echo]: setting state of Wohnzimmerheizung to false
13:48:02debug [pimatic-echo]: changing state for Wohnzimmerheizung: {"{“on”: false}":""}