Info: 1/ New API rate limit 2/ 868MHz interference

[ChrisWallwork]

I hope that this information might be of use to others.
Background: My 10 year old Evohome heating control system recently stopped working. The controller lost contact with most of the other devices (HR92s, BDR91s, RFG100) but intermittently reconnected. If I moved the controller near to another device, it was able to reconnect. Most of the rooms showed a temperature of 0 Celsius on Domoticz. In the process of sorting it out, I discovered two things that may be of value to others:
1/ The API for Honeywell Evohome now appears to have a much stricter rate limit. The Domoticz Hardware setup page for Evohome via Web API advises (re the poll interval) "If you set this to less than 60 seconds you may be in violation of Honeywell's usage terms". But, despite having set it at 101 seconds, I noticed repeated errors in the Domoticz log that the rate interval had been exceeded. Checking online, I found info at https://developer.honeywellhome.com/faq-page that says "Our limit is designed to allow you to poll device status every 5 minutes for up to 20 devices per hour, with a little cushion to make changes. If you need a higher rate limit, please contact us: [email protected]". I've not had any errors in the log since increasing my poll interval to a little over 300s
2/ I discovered that the reason my controller had lost contact with other devices was that an old DTS92 room thermostat was causing interference on 868MHz once its batteries had run low. It was left over from my previous setup, not linked with the current system but kept as a room temperature display. The batteries had apparently died; the display had gone blank but, once I removed the old batteries, all the problems with my Evohome system ceased. It's now got new batteries and isn't causing any problems.

[sidepipe]

Yep, on your point 2 I've had DT92s go haywire many times... they just don't seem to be well designed. I used to use rechargeables in them, but every so often one would start spewing traffic causing not only EvoHome to randomly have comms errors but also ZWave to stop working and also my garage door opener and car fob. Mind you, any radio protocol that doesn't need any sort of authentication is by definition badly designed....