Hi, having trouble all of a sudden on my C8 hub, and Radio CT101 zwave thermostat. Everything's been working fine, but randomly everything got very sluggish to respond to apps/commands.
I think the thermostat is stuck in a loop about route changes, but don't know what to do about it. It's a "hardwired" thermostat, with batteries. I tried new batteries in case it was something that easy. Also tried rebooting the hub with no luck.
I've looked at general logs under "past logs" and everything seems ok, but when looking at live zwave logs there must be a problem. I tried turning all logging off under the thermostat preferences tab in case that's clogging it up. Any help is appreciated, thanks!
First screenshot is from the zwave log page. Second two are the zwave device page details (living room thermostat ct101), and the rest are from the logs on the device page next to events.
I had a CT101 and it worked OK if I didn't ask it to do anything interesting It's the very old zwave that doesn't report status unless you poll for it. Bad for automation. You only have 40kbp to it which might be a weak zwave mesh (or maybe that was it's max, I don't remember). That low speed would be issue if lots of message are routed through it.
Yeah it's pretty old as far as smart thermostats go. Had a Honeywell T7 and a few others I wasn't happy with, so I went back to this one. I needed one with a swing temperature setting.
If it matters, it's within 10ft of three zwave plugs/repeaters, and maybe 11ft from.the hub itself.
I'm always afraid to just start pushing buttons, but would hitting refresh or rebuild node in zwave details help? I just don't want to make it worse. It's responding fine to automations, and interacting with it directly from the dashboard fine, just a few seconds slower than usual.
It can be other zwave devices that cause the mesh to weaken and the CT101 is seen as the cause. It's difficult to diagnose that condition. The rules of thumb for those zwave rebuild buttons have changed since I last had a need to understand them. I would not rebuild the entire network. Device refresh probably won't hurt. Probably won't help either. If it's slow because of re-transmitting and re-routing that would show up in the statistics of some or more devices. It could also go away on it's own.
Do you have access t a device with a larger screen?
Really need to see the full zwave details, with refreshed stats (there is a refresh button up top). Should be at least 12 hours after the last hub reboot (please state how long hub has been up).
Are you sending a lot of changes to the stat from the hub? Like adjusting the temp constantly with rules? If not then then it seems like the stat is just spamming stuff out.
Couple things you could try.
Turn on debug logging on the prefs tab for the thermostat, it should run for 30 minutes. See what shows up in logs for that device.
Power off the stat totally (unplugged, no batteries, whatever has to be done) for a good minute so power fully drains. Power back up again. Maybe a "reboot" will get it out of its funk.
Disable the device in the devices list,
This will prevent the driver from running so the hub wont be sending any commands to it. (Also wont process any inbound messages).
THEN, reboot the hub
Check the zwave stats after an hour or so and see if the messages is still going up.
This will tell us if the device is spamming on its own, or is it from the hub commanding it.
Not sure if this is indicative of anything, but after enabling debug logging, it filled up almost immediately. Here's a screenshot from just a few mins of logging.
I've tried removing the batteries and powering the thermostat down for a few mins. Checked zwave logs and its back to spamming that same "routeChanged: true," entry.
I'll try disabling the device in the devices list in a bit as well.
No need, I see your problem.
I vaguely remember there is some sort of refresh setting in the Thermostat scheduler app. However you have it setup, it is refreshing every minute.
You should not need to refresh for Zwave devices at all really, unless it is an old non-plus device.
Tried changing it from one minute, to 10 mins and hit update/save within the thermostat scheduler app. Waited about 10 mins, rebooted the hub, and waited another 10 mins or so but it still is spamming the same thing in the zwave details logs :
Maybe i'll let it just sit for a few hours and check it again. Thanks again for the help, I haven't tried disabling the device yet. I'll also try uninstalling the thermostat scheduler app next.
Seems to be way improved. Noticed if I turn a light or other zwave device on through the dashboard, sometimes the thermostat starts spamming again, but now seems to stop within 10-20 log entries. Just checked again after about 20 mins, and it seems to have settled a lot.
Check the event log again, look for those command-refresh lines. Make sure sure they are going at the interval you set. Do you even need to refresh it?
Looks like the refresh is working at 10 min intervals in the event log. I honestly don't know if it needs to refresh it, there's no toggle to turn that setting off.
You would only need it if you change the thermostat manually on the stat itself AND the devices does not repot changes back to the hub by itself (non plus).
I would push the refresh out to 60 minutes, that will just ensure the hub stays synced up with it, in the chance it misses an event.
