Just a quick message that I have decided to replace my Tado thermostat by a different heating solution. Since I don't have any way to properly test or validate any changes I make I will cease my development activities on this hardware. In its current form the plugin is quite usable and bug free and ...

Just make sure to use libssl1.0-dev when building. Domoticz seems to have some issues when used with libssl-dev.

Working fine here too. Has anything changed in your installation? OS updates, Domoticz updates, ... anything?

Can I use Tado hardware with this plugin without letting the Tado hardware connect to internet? Nope. Tado hardware only talks to the Tado servers. If you want to get something done on Tado devices you'll have to do it via the Tado servers. Local device is not able to do anything meaningful. Even ...

You can try opening the debug console of your browser and see if any javascript errors show up.

If they do there's possibly some caching-related issue. Maybe you can try doing the same in private browsing mode, bypassing the cache?

Not too sure about the behavior of the mobile API. Chances are that one does not enforce rate limiting since it's not an official API anyway and Nest never bothered to implement rate limiting? But to be frank: I just don't know. The polling interval is currently not user configurable. But in the ...

Happy to hear if they work correctly. As I do not have the luxury of a Tado-controlled cooling system I'm curious how it will work in practice

Nest throwing a 307 redirect either means: There is some maintenance happening at their side. That should be transient and resolve itself. You hit some rate limit. This can be fixed by polling less frequently. The latter case which is something that needs to be changed in the plugin. Unfortunately ...

@Onrust: I agree. In some cases the scheduling mode that is currently hardcoded in the plugin is not desirable. The difficulty is that I cannot just say "leave it as is". When setting a new setpoint I am required to specify one of the modes (schedule/until manually ended/timer). For the initial ...

Since you got the environment data from My Tado it shows that your Domoticz installation is able to access the internet. Getting this error either means that Tado has an issue or authentication is failing. Can you please double check that your username/password is correct (no spaces or line feeds ...

I'm not entirely sure what defines a beta release. I was referring to the git development branch (which may very well be the same thing).

Thank you, this is helpful. I'll take a look at it when I get the chance.

Also in the works is implementing a setting where the override mode when changing the setpoint for a zone (schedule/timer/ until manually ended) can be configured.

really appreciate your effort and work on this. I 'turned it on' yesterday and working well. In looking to replace my PHP script, wondered if you would consider the following enhancements: Away indicator - change from switch to alert. Also with additional parameter for proximity (currently I have ...

As of recently Tado support is available in the development versions of Domoticz. In order to keep the feedback a bit channeled I created this topic to collect issues and suggestions. This plugin is based on the my.tado.com web application. Unfortunately Tado does not offer an official API so all ...

Above is correct. In the development a c++11 feature was used, even though not explicitly specified in the build scripts. Most compilers will compile it anyway. Problem is that the gcc compiler that comes with Ubuntu 16.04 is rather old and does not handle this gracefully as you discovered. A fix to ...

As mentioned earlier, camera support is not a priority for me right now for a number of reasons: - I don't have a camera, never had one either - I have no idea what its uses are and what useful information for these things would be - My time is limited and I want the current plugin to be confirmed ...

Been doing some cross-compilation because compiling on a rpi is unbearably slow. Running into some compilation errors on Linux that I don't get when building on Windows, probably some non-portable code. Will look into it later. For now, compiling it via MS Visual Studio should work. Other platforms ...

That's what I'm currently doing. On my Windows desktop build is done in like 1-2 minutes, on my Raspberry it's more like half a day.

Yes. I don’t want to go through the trouble of putting in pull requests (and bothering gizmocuz) to the development domoticz repository while it’s still in feature testing (consider it alpha). It is synced up to the development branch though.

I did some additional work, restructuring and troubleshooting. I'll be uploading the changed code to my github shortly, and will be doing a test compile on a Linux machine tonight. Please help me in testing this and pointing out if things break! Things fixed Away mode in case of multiple homes ...