I have a custom device handler for my CT100's, which worked well in ST and it's working well now on Hubitat. But I have noticed in the logs these occasional messages output as part of the zwaveEvent(hubitat.zwave.Command cmd) catch-all function:
Unexpected zwave command ThermostatOperatingStateReport(operatingState:0)
The DH does have a zwaveEvent(hubitat.zwave.commands.thermostatoperatingstatev1.ThermostatOperatingStateReport cmd) function, which gets usually invoked when the devices report their operating state.
Any idea about why occasionally the message ends up in the catch-all function - even if it seems to know that the command is a operating state report?