can it be an old nearby device which was routing signal?
the other controller for some reason creates the “confusion” ?
Also found from the past this:
Finally, I disable the climate schedule and clock command classes which have
been reported elsewhere to be unstable (although this is apparently not
strictly necessary for correct operation with the THERMOSTAT_SETPOINT command
class, so you may want to ignore that part).
Can this be something causing it?
About the controller I began a network heal on my other network. still getting these random issues with the second device too.
First time laster 5 minutes, second is on 10+ minutes and still going crazy!
If I set a point or update some parameter I suspect it will stop
I saw this on the log:
2018-10-28 22:09:59.840 [DEBUG] [.ZWaveThermostatSetpointCommandClass] - NODE 6: Thermostat Setpoint report Scale = 0
2018-10-28 22:09:59.841 [DEBUG] [.ZWaveThermostatSetpointCommandClass] - NODE 6: Thermostat Setpoint Value = 2E+1
2018-10-28 22:09:59.843 [DEBUG] [.ZWaveThermostatSetpointCommandClass] - NODE 6: Thermostat Setpoint Report, Type Heating (1), value = 20
