No act of kindness will go unrewarded.
We're rewarding you with many reasons to dig. 
3 Likes
Can you turn on debugging and do a couple of set point changes so that I can see what is being set?
I get this on a change.
dev:8942022-09-30 11:06:47.460errorgroovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.math.BigDecimal#. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class [C] [class java.lang.String] on line 591 (method setHeatingSetpoint)
dev:8942022-09-30 11:06:47.400debugsetHeatingSetpoint(null) called
If you turn the debugging on we should get a debug log entry immediately prior to the error.
There's part of the issue. If we do it from the device page do we get the same error?
This is all I get:
dev:8942022-09-30 11:11:09.836debugGot thermostat setpoint report: ThermostatSetpointReport(value:[0, 185])
dev:8942022-09-30 11:11:09.800debugparse:zw device: 47, command: 4303, payload: 01 22 00 B9 , isMulticast: false
dev:8942022-09-30 11:11:09.503debugsetHeatingSetpoint(18.5) called
Value 185?
Don't know if it helps, but I did a thermostat setpoint change at the thermostat (rather than from the hub GUI) and logged how it was received at the hub.
2022-09-30 01:30:53.994 pmdebugGot thermostat setpoint report: ThermostatSetpointReport(value:[2, 208])
dev:40652022-09-30 01:30:53.992 pmdebugparse:zw device: 5F, command: 4303, payload: 01 2A 02 D0 , isMulticast: false
dev:40652022-09-30 01:30:53.911 pmdebugGot thermostat setpoint report: ThermostatSetpointReport(value:[2, 208])
dev:40652022-09-30 01:30:53.908 pmdebugparse:zw device: 5F, command: 4303, payload: 01 2A 02 D0 , isMulticast: false
dev:40652022-09-30 01:30:53.821 pmdebugGot thermostat setpoint report: ThermostatSetpointReport(value:[2, 208])
dev:40652022-09-30 01:30:53.818 pmdebugparse:zw device: 5F, command: 4303, payload: 01 2A 02 D0 , isMulticast: false
dev:40652022-09-30 01:30:53.759 pmdebugGot thermostat setpoint report: ThermostatSetpointReport(value:[2, 208])
dev:40652022-09-30 01:30:53.757 pmdebugparse:zw device: 5F, command: 4303, payload: 01 2A 02 D0 , isMulticast: false
dev:40652022-09-30 01:30:53.542 pmdebugGot thermostat setpoint report: ThermostatSetpointReport(value:[2, 208])
dev:40652022-09-30 01:30:53.540 pmdebugparse:zw device: 5F, command: 4303, payload: 01 2A 02 D0 , isMulticast: false
May have found it. v1.2.8 should be out there now.
Just downloaded. Looks like it is working. I'm getting numbers again for my setpoints.
1 Like
So far so good 
1 Like
Ut Oh. It's still outputting temperatures in degrees C, even though the control Apps are expecting degrees F. It's putting my furnaces into heat mode (which I'm manually overriding)
Can you check that one?
Still having problem. After about 5 minute the temperatures do go back to Farenheit, but then after that when I make a setpoint change (via the dashboard) temperatures go back to Centigrade and heat kicks back on.
I'll look to see if I can change that for when updated. Makes some sense when new as you have to pick one or the other before the preference is known.
The dashboard still thinks the thermostat is in Centigrade, but now with a 73C reading
(second row are my actual thermostats...first row are the HE controllers that I use)
But Celcius is what the whole world uses except the USA, it's fine. 
2 Likes
Right! There's the problem. 
I rebooted the hub and units came back to Farenheit and seem to be staying Farenheit now when I change setpoints. Sounds like something might have been cached that kept converting units when setpoints were changed.
I'll keep an eye on it.
Okay, thanks for your help.
Happy to help. I sure would have loved to know what was cached in hub memory to cause that units change....and if there could be a way to prevent it in the driver initial configuration.
I imagine I can probably get it to repeat that behavior again if I reinstall the driver. I might try tomorrow and see what happens. It's getting close to Happy Hour now! 
1 Like
