Domoticz

Hello everybody,

since a couple of months the Nest plugin (FilipDem) seems to behave differently. In the past I would only have to change Token and Cookie perhaps once or twice a year. At the moment it will only be 'remembered' less then an hour. I already logged out of anything Google Home or Nest releated but it won't 'stick' anymore.
Is there something I can try to solve this or do perhaps others experience this as well?

And more urgent, is there perhaps another way of reliable controlling my Nest thermostat with Domoticz (with or without third party bridge software)?

Hi,

I'm using the same plugin on 2 locations each with a Domoticz and NEST setup.
As far as I know it still works.

As I understand it, you have login manually to your NEST thermostat and then you copy the cookie from that session to your Domoticz setup. Normally the Domoticz will then keep using that cookie.
The important part here is to never log out of that session because then the cookie will become invalid.

I did not check lately but there aren´t much changes lately on the plugin.
I even saw that it was cloned by someone who wanted to take over the maintenance...

What version of the plugin are you running?

Tom

Hi Tom,

You've got me triggered: I am using this plugin for ages (previously the one from Roland Breedveld) and only checked the version number (2.3.0). But apparently some minor changes have been made. So after a full blown update of Linux, I recopied the files (removed the complete folder first) and set it up like first time use again. For now the plugin seems to work (but that is the same behaviour as before the update). Fingers crossed to see if it will work after a couple of hours.....

OK, so that didn't work, but it set me onto the right track.

Long story short: if I use my W11 worklaptop to gather Token and Cookie, then after an roughly an hour it doesn't work anymore. Sidenote, yes I did clear cache, logged out of all Google account related devices, etc.

However, if I use my private Linux laptop to gather the Token and Cookie, then all seems OK. Until now, roughly 48 hours later, I still see the updates of the devices as expected. So it's probably W11/company policy induced. I tend to remember that the problems occured around the same time I had to migrate from W10 to W11.

Solved? Yes, but not sure why it became a problem in the first place. Anyway, it's working again and in the end that's all that really matters to me....

well,
incidently I had to renew my cookie also this evening.
I used Chrome on Windows10.
so far it's working...