Still, now that happens every other day, you need to make more tests to see if it doesn’t change when it’s offline for more than a few hours, it could be during three days.
If there was an event that went through the ST Cloud, it would appear in the logs. We’ve made searches on the different days you mentioned and there are no events of routines/scenes, the app (direct commands), the API, or any other service sending those new values.
The team also cleaned all the Groovy stuff in your account directly so, the app you mentioned cannot be executed anymore (if it was we would see the event in the logs as well which doesn’t happen).
The strange part is that we only see those events in the Hub logs and they are events coming from the devices themselves, not originating from the driver that controls them.
When a command to a device is sent through the platform (routine, API command, SmartApp, etc.), we see the event of that command saying which capability it was and the new value. After that, the Z-Wave message is generated and sent to the physical device, it then responds with the Report of the new status confirming the change.
In this case, we’re not seeing that in the logs, only the Report of the new status from the physical device, which generates the capability event for SmartThings.
We don’t know if re-pairing the devices would make a difference, but if you’re willing to try, you can test that.
Thanks @HalD . It is a T6 PRO Zwave Thermostat, these apps are for Wi-Fi thermostats. I would need a driver or app integration for Smartthings. I’ve checked and the only Honeywell has for Smartthings is for the Zwave fans and fan controllers.
It’s good to know you found out what was happening.
If it can be set physically, you could check if after setting it, it sends something to the driver logs. Those can be enabled using the SmartThings CLI, and the command edge:drivers:logcat but it only works if you’re in the LAN or have a way to access that network remotely.
According to the fingerprints in the ST driver, this is the device’s details in the Z-Wave catalog.
I see it has a config parameter about schedules, and in the supported CCs, one is called Clock. So, resetting it will depend on how it is configured in the first place.
In the description of the device I see this feature “Flexible local thermostat scheduling options”…
It is remote. It’s about a 3 1/2 hour drive, so anything I can do remotely is a positive. But now I know what to look for if it happens again and I can probably instruct someone how to fix it.