Charmed Quark Systems, Ltd. - Support Forums and Community
Next V2 driver problem - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (http://www.charmedquark.com/vb_forum)
+-- Forum: General Discussion (http://www.charmedquark.com/vb_forum/forumdisplay.php?fid=3)
+--- Forum: CQC Support (http://www.charmedquark.com/vb_forum/forumdisplay.php?fid=9)
+--- Thread: Next V2 driver problem (/showthread.php?tid=10382)



Next V2 driver problem - kjaerligkatt - 09-05-2017

In the past week I've noticed the Nest driver dropping offline, with what appeared to be convention problems.  I think the problem coincided with me upgrading from 4.8.  Nest cloud driver is v1.5

Initially it looked like the problem was connecting to the Nest cloud, as requests were being rejected.  Digging deeper revealed that the rejections were due to the CQC connection being locked out, due to too many requests being sent.

Nest Error. Op=Query All Info, Code=429, Msg=blocked

Beyond that I was struggling to see why this might be, not least of all because my logs were being flooded with this message because every reconnect attempt was generating the same message (so every few seconds).

After more troubleshooting, I manged to trap the errors shortly after an initial fail, and discovered that the originating cause is due to the following message :

Device setup failed. Error=Value 'Eco' exceeds the limits for field Thermo_Entrway_Mode

This eventually leads to CQC being blocked, presumably due to too many re-attempts that exceed the Nest timed query limit.

I don't ever remember seeing this with 4.8, and guess that maybe the Nest driver was also updated when I moved to 5.1?


RE: Next V2 driver problem - Dean Roddey - 09-05-2017

What version are you on? The driver was updated, but it, was to add support for the eco mode stuff that the nest added. So if you haven't bot that updated driver, that may be it. If you already have the updated driver, maybe there's so far unseen issue with it.


RE: Next V2 driver problem - kjaerligkatt - 09-05-2017

I'm currently on v5.1.904


RE: Next V2 driver problem - Dean Roddey - 09-05-2017

Is this a heat-only or cool-only thermostat, i.e. just one set point, not two?


RE: Next V2 driver problem - kjaerligkatt - 09-05-2017

Yes, it's a heat only configuration.


RE: Next V2 driver problem - Dean Roddey - 09-05-2017

OK. I didn't think that they had Eco mode, since I thought that was an automatically 'keep it in this range' type thing. So I didn't add that to the limits for those.  Try the attached driver pack. So import and then do a reconfigure on the driver to pick up the changes.


RE: Next V2 driver problem - kjaerligkatt - 09-05-2017

Should that have increased the version number of the Nest driver, as it's still showing v1.5 and still fails. I've imported, and tried reconfiguring, restarting the service and rebooting the PC. 

Also, the Manifest didn't have a path - see attached. Is that correct?

Eco is just a temperature that is configured to use when in Away mode, rather than the scheduled temp, to save heating an empty house unnecessarily.  it can also be selected manually.


RE: Next V2 driver problem - Dean Roddey - 09-05-2017

I didn't bump the version for this quick test. Let me try it against the Nest simulator. I think I had issues with the simulator working right in heat/cool only mode and so I may not have been able to test it as well as the standard scheme. I'll try it again.

The manifests don't have a path, because where they go is implied and it's always to the same place. The CML files do because they go to specific places based on their class path.


RE: Next V2 driver problem - Dean Roddey - 09-05-2017

My bad. I added it to the wrong limit string. Try this guy.


RE: Next V2 driver problem - kjaerligkatt - 09-05-2017

That fixes it. Thanks Dean.