I am using TADO thermostats with the custom driver provided here in the community and generally works fine and I can control my thermostats out of the TADO app or manually change the temperature from within the HE dashboard which then immediately pushes the changes to TADO. I just have to poll the data from the TADO thermostats with a rule machine rule so any changed made in the TADO app are updated to HE and reflected in the HE dashboard, So far so good... Now to my issue...
The TADO app had a pretty cool feature called Auto Assist that automatically turns down the temperature to a preset value when everybody leaves but starts reheating when somebody is returning home so the preset home temperature is already reached when somebody arrives home. For that reason I leave the control of the heating to TADO.
The issue however is that as soon as I either change any temperature settings in HE or for example turn off the heating via HE because a window is opened and then the heating back on went the windows is closed, the Auto Assist mode in the TADO app is set to manual and TADO no longer used auto assist or any preset temperature schedules until I reactivate Auto assist in the TADO app.
The good news is that I have already found a button (End Manual Control) in the driver in HE that forces the TADO app back into the Auto Assist mode but I can’t figure out how to “push” that button via Rule Machine to fix my issue. As you can see after changing the temp in HE tadoMode is set to MANUAL and if I hit the End Manual Control button in the device driver it switches the Auto Assist back on in the TADO app and show either AWAY or HOME as tadoMode.
I’m sure im just too stupid to figure out how to trigger the End Manual Control button in HE, Any ideas? I already tried with Run Custom Action and can select endManualControl but I do wont want to set anything I want to tell TADO to switch out of Manual mode?
Yes I have tried both. First thinking that I just needed to set the endManualContol string to AWAY or HOME. When that didn’t work I thought yeah of course not, it’s not Hubitat sending the String „AWAY“ to TADO it’s Tado pushing its Status (HOME, AWAY) back to HE when whatever that End Manual Control button is sending to TADO Is executed. So I tried setting the values 1 and 0 and on and off for End Manual Control to Tado ... didn’t work either:(
I've looked through the code but I can't see what you're supposed to fill in there. Though I did find there is a separate app which accompanies this device driver. Maybe you can try that and see if you can accomplish your goal with that? Tado-Hubitat/README.md at master · fuzzysb/Tado-Hubitat · GitHub
There is even an tado presence device driver. Maybe that will help?
Is there not a way to see exactly what happens (commands actions are sent) when I hit that EndManualControl button in the Device driver.... Makes me realize that I need to get a grasp on log files etc. too because I always have difficulty finding and understanding them
The TADO presence device driver is something separate that just lets me use the presence status determined by TADQ as a presence Sensor in HE which is indeed helpful for leaving home and coming home routines in HE.
Im not a programmer (so looking at the scripts will confuse me more than it will help
You don't have to know what a device driver sends to a device because you can't issue a command directly to a device from RM. That's were the driver is for. The real question is how to make RM send that button push command to the driver. In the tado app I see the same command used also with a value of the device ID. But since you choose the device in RM I would guess it gets send with the command. But maybe we can ask @bravenel how this works?
@frits your the man... After looking at the driver code and the installation instructions I saw this passage „ also enter the default tado override method, these are Tado-Mode which applies the override only until the next Tado mode change, or manual which will apply the override until cancelled by the User“ I changed the settings in the app and now the manual changes in HE are only valid until the next time somebody arrives or leaves the house. Thanks again @frits
@bravenel it would still be nice to have a way of pushing a button in a driver via RM that would come in handy for lots of people who can’t code.
Have you looked at Custom Action in RM. It exposes every command in the driver. If the command exists, you can use it, and send parameters to it if needed.
End Manual Control is a command that takes no parameters. It's not a button, it's a command. So he was close, but didn't do the obvious step. It's that simple, probably so that he didn't realize he had the answer.
