OK - here's my left-field suggestion (as someone who does this kind of stuff for a living).
The Honeywell API service sits on multiple servers behind a load balancer. The latter means that you'll usually stay connected to one particular server via session management. And one of the servers has a configuration ****-up.
That would explain why some are seeing the problem while others aren't. And why reboots (which should establish a new session) sort things out.
Pure guesswork, of course, but it seems likely.
The Honeywell API service sits on multiple servers behind a load balancer. The latter means that you'll usually stay connected to one particular server via session management. And one of the servers has a configuration ****-up.
That would explain why some are seeing the problem while others aren't. And why reboots (which should establish a new session) sort things out.
Pure guesswork, of course, but it seems likely.
Comment