[DEPRECATED] Tado Heating Integration

@Fuzzyligic
I have tested your app since a couple of days. You did a great job at all! - Tank you very much :slight_smile:
One little bug is in my version (the last one from 3th of Dezember). The button for set heating point down doesnt work. Upper perfectly and the other buttons too. It synrchronize with Tado very well.
If I set down the setpoint via Tado-App it minimize it in your devicehandler too.
If I press the down button for setpoint in you app…nothing will happen. Even not in your app.

Creating a new device again did not solve the problem.

Hope you can help. I would be happy for every comment :slight_smile:

@tobias.freyer thanks for picking up that bug. its been resolved in the latest versions which are on github now

you will need to update the Tado (Connect) Smartapp, and the Tado Heating and Hot Water Device Types.

once done and published just go into your devices in your ST app and click on the settings button and then hit done, this will correctly set the state data for the devices. after this all the set point changes should work.

Hi @Fuzzyligic.
Really sorry about this dumb question but I do get confused with github.
Do you have the details that I need to set up in github?
i.e. Owner, Name and Branch.
I have setup the following but it doesn’t seem to update.
Owner - fuzzysb.
Name - SmartThings.
Branch - master.

Thanks.

Hit it by posting only the code.
You have to click that also named button before :slight_smile:

It will fill in author and the rest automatically.

Thank you @Fuzzyligic for your message and your work. I will send you money in PayPal the next days for your great work after I updated my code and if it will work:-)

UPDATE: It didn’t fixed the problem for me.
I created a ā€œnewā€ SmartApp with your last code v1.2 and create a new ā€œheating deviceā€. This device got the same problems as before with the setpoint down. :frowning:
I can’t explain, because your code looks exactly the ā€œset point upper buttonā€ :-/
Found out, that my used code before was allready v1.2. Im using your App for only a few days and not since release 3th Dez and the v1.2 release.
Any ideas?

LIVE LOGGING ERROR:
"cannot increase heat setpoint, its already at the maximum level of null "

I’m sorry, but I’m unsure of what you mean.

my SmartApps > + new SmartApp > ā€œFrom Codeā€ and not the standard settings ā€œFrom Formā€

Then paste in the full code you have copied before :wink:

Ah ha. Gotcha. Never looked in there before.

@bobbles yes sorry only just seen your message. Unfortunately it’s in the UK don’t have github.com integration, so its just a simple copy and paste job of the code overwriting the exiting code with the new version

Hi Stuart.
We actually have github integration now. I’ve always done the copy/cut/overwrite method but have managed to integrate some DTH’s and Smartapps.
I have tried with your code but it shows as green italic which I believe means not found in any repository. I am at a bit of a loss.
I have used:-
Owner - fuzzysb.
Name - SmartThings.
Branch - master.

Wow OK I know I was away for a while. Totally missed that it was in the UK. As for using it I will look later and see if I can figure it out

OK I know why is not working because my reps aren’t named correctly. Will look to see about changing them…but will need to change a lot of links etc…

That’s OK. No problem.
I was beginning to think I was going mad 'cos everything looked right but it just wasn’t, if you know what I mean.

@bobbles

I have updated the Smartapp and moved it to a new dedicated repository you should now be able to get github integration working Ok with the repository details

Namespace: fuzzysb
Repository: Tado
Branch: master

Hi Stuart,

what’s about my problem with the setpoint down?
@Fuzzyligic

LIVE LOGGING ERROR:
"cannot increase heat setpoint, its already at the maximum level of null "

Do you have any Ideas? The App is installed with TADO-MODE and not as" manuall"
Maybe this is a mistake, but only the down button doesn’t work. The upper is fine.
It makes no sense :smiley:

@tobias.freyer

I have fixed that already in v1.2 of the app. did you install the new version and update all the device types? if so and its still not working just go into the device in the ST app on your phone and select the settings (gear) icon and then click done. after this the setpoint down should work. I have tested it here and its now working fine

if your still having issues please grab the logs from live logging for both the device and smartapp and DM me.

Regards

Stuart Buchanan

@Fuzzyligic

Dude as simple as fuck… my misstake :smiley:
I used your newest SmartApp Version but devicehandler v2 and not the newest v2.2 !
I’m such a fool :slight_smile:

Now Im the happiest guy in Germany…it is like a little chirstmas present :smiley:
So I’ll give something back to you…at PayPal :wink:

No problems I’m glad it’s working for you. Thanks for the donation much appreciated.

Hey @Fuzzyligic, did tado ever sort out their authentication model? oAuth auth method is a big requirement for getting the device ported directly into Stringify, until then they can’t support the devices created by this SmartApp, because they’re ā€œnot on the hubā€???

Which is wierd, because I have simulated switches that are imported into Stringify just fine, and they’re not technically on a hub either.

@NOITAIDAR they have oauth for the mobile phone presence connection from the Tado app, but i don’t think they have an oauth model for user auth, but im not 100% sure, but without a published API who can really know, but i did sniff the packets from the windows app to check and no oauth is not used until you tick the enable presence option.

but they must have it working in some manner as they have an alexa skill in which oauth is a requirement. but i will still no closer to figuring it out.but im probably not the most qaulified person to figure it out 100% as im still pretty new to oauth flow.

Thanks for the quick response @Fuzzyligic. Was hoping for an easy way to port through to Stringify (screw IFTTT and their 1 hour delay. lol) Come to think of it, IFTTT must use oAuth too.

So far, I’ve managed to create a simulated Presense Sensor for the Tado MODE, and use CoRE to update it’s value, but not sure how I could do that with temperatures ans SetPoints… for three separate zones. lol