I picked up a bunch of Bosch Raumthermostat II’s during black friday sales, and was able to get them configured and linked up via z2m without any issues.
But i’m running into an issue where the properties exposed via z2m don’t seem to update unless I go into the device in z2m and manually click the little refresh arrow next to the property.
e.g. one of the devices defaulted to the heat being turned on as soon it turned on, so was in that state when it synced with z2m. I re-set the thermostat right after that to turn the heating off, but even the next day z2m was still showing heating state as on. I tried power cycling the thermostat. I tried using z2m’s Reconfigure and Interview commands - but the only way I’ve been able to get that (and other properties) to update is if I manually click the little refresh button.
Since z2m is capable of getting updates without the device being physically interacted with, there must be some sort of command I can use/schedule to force updates?
edit: one other way I was able to force update was by using the thermostat card in a dashboard to change a thermostat setting - i guess if all else fails I could set a script to edit/unedit a property? that seems like an overly complicated workaround though.
I don’t think there’s any need for that.
One of the options on your device page in Z2M is a tab called Configure Reporting. It basically tells Z2M to update when your device changes based on values &/or time
Try playing around with those settings & see how you get on. Unfortunately I don’t own your device so can’t tell you the exact endpoints, clusters & values you should be using.
Thanks for that tip @ShadowFist - I played with the values on a couple of the thermostats and it seems to be helping - will try adjusting the rest today. The initial values appeared to be configured for battery devices, with times up in the 65000 seconds. These thermostats are 220V hard-wired, so that’s not a concern and I’ve reduced the reporting times considerably.
Hang on, I did some digging around and might have found something.
Did you update the thermostat firmware via OTA as soon as you got them by any chance? If so, read this.
Apparently you need to click Interview (the i icon in the picture below) for these devices after a firmware update. According to one post, ideally you should cut/restore power to the thermostat before doing an interview + reconfigure to ensure that it works.
@ShadowFist oh, wow - I totally missed that github thread - thanks!
I had updated all the FW after I noticed the reporting issue (I had also noticed the genOnOff error… but ignored in favor of firmware update…). Anyway, I just power-cycled them all. Reconfigure was failing with the genOnOff error still, but if I did the Interview first, Reconfigure ran without errors. So, fingers-crossed this is all working now!
