Thanks. I will try that and update.
P.S: That did it 
Thank you! I should have figured out where to check the logs earlier, still getting used to HE.
As an update I still have exceptions in the log file:
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:03.684 [info](http://10.10.10.133/device/edit/202)Living Room TRV - Parsed 'ThermostatSetpointReport(setpointType:1, precision:2, scale:0, size:2, value:[7, 8], scaledValue:18.00)'
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:03.675 [debug](http://10.10.10.133/device/edit/202)on heat
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:03.670 [info](http://10.10.10.133/device/edit/202)Living Room TRV - ThermostatSetpointReport - 'Temperature changed by app to 18.0°C.'
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:03.665 [debug](http://10.10.10.133/device/edit/202)Living Room TRV - setpoint report temps device rep = 18.0 , next = 18.0
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:03.643 [info](http://10.10.10.133/device/edit/202)PARSED zw device: 16, command: 4303, payload: 01 42 07 08 , isMulticast: false
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.853 [info](http://10.10.10.133/device/edit/202)Living Room TRV - Parsed 'WakeUpNotification()'
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.845 [trace](http://10.10.10.133/device/edit/202)Living Room TRV - WakeUp - outbound commands are [4301010112, 430201, 8408], command count is 3
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.826 [error](http://10.10.10.133/device/edit/202)java.lang.NullPointerException: Cannot invoke method toFloat() on null object on line 160 (parse)
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.788 [info](http://10.10.10.133/device/edit/202)Living Room TRV - SensorMultilevelReport(precision:2, scale:0, sensorType:1, sensorValue:[7, 252], size:2, scaledSensorValue:20.44)
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.756 [trace](http://10.10.10.133/device/edit/202)setHeatingSetpointCOMMAND(DD) setting to '18.0'
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.750 [trace](http://10.10.10.133/device/edit/202)WakeUp - Sending new temperature 18.0, curent heating setpoint 19.5
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.678 [info](http://10.10.10.133/device/edit/202)Living Room TRV - Parsed 'ThermostatSetpointReport(setpointType:1, precision:2, scale:0, size:2, value:[7, 158], scaledValue:19.50)'
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.669 [info](http://10.10.10.133/device/edit/202)PARSED zw device: 16, command: 8407, payload: , isMulticast: false
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.645 [debug](http://10.10.10.133/device/edit/202)on heat
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.641 [debug](http://10.10.10.133/device/edit/202)Living Room TRV - setpoint report temps device rep = 19.5 , next = 18.0
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.636 [info](http://10.10.10.133/device/edit/202)PARSED zw device: 16, command: 3105, payload: 01 42 07 FC , isMulticast: false
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.631 [info](http://10.10.10.133/device/edit/202)Living Room TRV - Parsed 'ScheduleOverrideReport(overrideState:null, overrideType:null)'
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.627 [debug](http://10.10.10.133/device/edit/202)Not processed - Schedule Override Report Living Room TRV ScheduleOverrideReport(overrideState:null, overrideType:null)
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.622 [info](http://10.10.10.133/device/edit/202)Living Room TRV - Parsed 'BatteryReport(batteryLevel:70)'
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.618 [info](http://10.10.10.133/device/edit/202)Living Room TRV - BatteryReport(batteryLevel:70)
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.608 [info](http://10.10.10.133/device/edit/202)PARSED zw device: 16, command: 4608, payload: 00 7F , isMulticast: false
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.598 [info](http://10.10.10.133/device/edit/202)PARSED zw device: 16, command: 4303, payload: 01 42 07 9E , isMulticast: false
[dev:202](http://10.10.10.133/logs#dev202)2021-01-18 21:49:02.593 [info](http://10.10.10.133/device/edit/202)PARSED zw device: 16, command: 8003, payload: 46 , isMulticast: falsehas the same error come up twice?
issue was it was trying to do some math with null values as it hasn't cycled all the variables at that point.
I've updated the driver to add some stock values until everything has reported in.
I don’t see it again. The log is clear now.
1 Like
Can someone summarize that are danfoss and popp radiators fully working in hubitat?
I noticed few different topics and some people are buying eurotronic and aeotec trv's. I'm looking for a reliable z wave trv's and found it difficult to decide which one to choose.
They work fine, but are sleeping device which is settable, but commands are stored till device wakes up
I'd go for pop I think as it reports temperature where as the other doesn't
1 Like
Are they all sleepy devices? Why oh why? Is there possibility to change wake up times or are they factory set defaults for example in popp?
My driver you can set the wakeup, think I have it on 10min, gives over a year on the batteries he eutronics is always awake and I get similar battery life
Hi, I'm new.
I like the tado system, but don't like the mandatory cloud functionality.
I'm looking at Hubitat as ZWave Controller and the POPP WIRELESS THERMOSTATIC
VALVE TRV (010101).
But it looks like it is not supported?
Regards,
I use pop, do a search there are some drivers here
1 Like
Hi Mark,
Thank you for sharing your driver. For many years I have Danfoss TVR and I have been very disappointed with them as they never worked as I hoped. After coming across you driver I was excited and hoped it would help.
I have installed driver on my Hubitat with the raw url, but I guess there is something I am missing. In the logs I am getting the following errors and due to this the TVR is not communicating with Hubitat.
dev:3382021-11-22 06:19:49.246 am errorjava.lang.NullPointerException: Cannot invoke method doubleValue() on null object on line 207 (method parse)
dev:3382021-11-22 06:19:49.246 am errorjava.lang.NullPointerException: Cannot invoke method doubleValue() on null object on line 108 (method parse)
Is there some configuration I am missing after installing the driver?
Looking at the driver code I noticed you have 2 lines commented out and replaced with similar lines that include the doubleValue() function. I attempted to switch these comments around and the error then longer occurs but still Hubitat does not communicate correctly with the TVR.
I appreciate it is probably a long time since you looked at this, but if you have any pointers how to resolve my errors I would greatly appreciate it.
Many thanks,
Keith.
Can you send a screenshot of the device details page
add this in configure line 348 it should pre populate the heating setpoint to later functions can do the math on it
sendEvent(name:"heatingSetpoint", value: "10", unit: "°C", displayed: false)
then go to the device and hit configure button
1 Like
Hi Mark,
Thank you so much for the fast reply and suggestion, this has now fixed the errors. Finally the Danfoss TVR appears to be connected and communicating with Hubitat.
Best regards,
Keith
1 Like
Are they working better or as you hoped now?
Hi Mark, yes, they appear to be working much better for me now. The temperatures are changing when I request and I managed to create a few rules to turn on and off different radiators at different times. So far so good. No further errors reported in the logs.
1 Like
Instantly after the inclusion of a Popp thermostat I switched to your driver. But the z-wave connection to the device got lost. I got the errors:
java.lang.NullPointerException: Cannot invoke method doubleValue() on null object on line 206 (method parse)
java.lang.NullPointerException: Cannot invoke method doubleValue() on null object on line 109 (method parse)
To create the "nextHeatingSetpoint" I added as line 349:
sendEvent(name:"nextHeatingSetpoint", value: "10", unit: "°C", displayed: false) //dummy value to allow equations to run later
Now the connection stays and the driver works. Perhaps you can make this or an appropriate modification in your driver to eliminate the problem right from the start?
This was the 2nd Device (of 4 I want to move from VERA). The first works since some weeks. For this first device I started with the generic thermostat driver. This sequence seems to avoid this error.
The driver works for me well with a Popp thermostat. But my preference wakeup intervall (600s) every once a while changes to 1800 s (the zwWakeupInterval in data section and the real behavior). I cannot find a regularity till now.
When I hit "configure", the wakeup intervall switches back to my preference value. I created a daily rule to call configure, but anyway sometimes the wakeup intervall get lost.
Is there a way to find out what happens or to avoid this behavior?
what have you got on line 266, it should set defaults as part of installing.
265 -sendEvent(name: "heatingSetpoint", value: "10")
266 - sendEvent(name: "nextHeatingSetpoint" ,value: "10")
edit latest version wasn't updated in Git.. done now
