Danfoss TRV problems

Wiebe · January 5, 2015, 7:34pm

Two months ago I bought 6 Danfoss TRVs and a VeraLite. I installed everything (on UI7) but got lots of delays and problems like described by several people on this forum. I didn’t have time to fix it back then, so I put everything aside. Last week I installed five TRVs again after finding this script by dunked.

This script seems to work wel for one of the TRVs (the one I keep for testing), but not for the other five. The only difference is that these five were factory reset and again included (after a firmware upgrade to the latest version, 1.7.481). I could link them, but Vera keeps telling me they are not connected. However, when I manually trigger them by pushing a button, I get an entry in the log:

[code]06 01/05/15 20:13:45.500 Device_Variable::m_szValue_set device: 23 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: NodeInfo was: 43,46,72,75,80,81,84,86,8f, now: 43,46,72,75,80,81,84,86,8f, #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2b9f8680>

06 01/05/15 20:13:45.649 Device_Variable::m_szValue_set device: 23 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: TemperatureScale was: 2,0,2 now: 2,0,2 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2b9f8680>
06 01/05/15 20:13:45.650 Device_Variable::m_szValue_set device: 23 service: urn:upnp-org:serviceId:TemperatureSetpoint1 variable: AllSetpoints was: 9,18,18 now: 9,18,18 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2b9f8680>

06 01/05/15 20:13:45.949 Device_Variable::m_szValue_set device: 23 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryDate was: 1420455021 now: 1420485225 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2b9f8680>
06 01/05/15 20:13:45.950 Device_Variable::m_szValue_set device: 23 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryLevel was: 55 now: 55 #hooks: 0 upnp: 0 skip: 0 v:0xe7e408/NONE duplicate:1 <0x2b9f8680>
04 01/05/15 20:13:45.951 <0x2b9f8680>
[/code]

When I compare this to the working TRV, I see that they miss the setting of the CurrentSetpoint. The value in AllSetpoints does reflect the setpoint that I manually set on the TRV. The logs for the working TRV:

[code]06 01/05/15 20:13:10.020 Device_Variable::m_szValue_set device: 6 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: NodeInfo was: 43,46,72,75,80,81,84,86,8f, now: 43,46,72,75,80,81,84,86,8f, #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2b9f8680>

06 01/05/15 20:13:10.149 Device_Variable::m_szValue_set device: 6 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: TemperatureScale was: 2,0,2 now: 2,0,2 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2b9f8680>
06 01/05/15 20:13:10.150 Device_Variable::m_szValue_set device: 6 service: urn:upnp-org:serviceId:TemperatureSetpoint1 variable: CurrentSetpoint was: 5 now: 5 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2b9f8680>
06 01/05/15 20:13:10.150 Device_Variable::m_szValue_set device: 6 service: urn:upnp-org:serviceId:TemperatureSetpoint1_Heat variable: CurrentSetpoint was: 5 now: 5 #hooks: 0 upnp: 0 skip: 0 v:0xeac3f0/NONE duplicate:1 <0x2b9f8680>
06 01/05/15 20:13:10.150 Device_Variable::m_szValue_set device: 6 service: urn:upnp-org:serviceId:TemperatureSetpoint1 variable: AllSetpoints was: 5,5,5 now: 5,5,5 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2b9f8680>

06 01/05/15 20:13:10.390 Device_Variable::m_szValue_set device: 6 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryDate was: 1420484879 now: 1420485190 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2b9f8680>
06 01/05/15 20:13:10.390 Device_Variable::m_szValue_set device: 6 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryLevel was: 61 now: 61 #hooks: 0 upnp: 0 skip: 0 v:0xe7e408/NONE duplicate:1 <0x2b9f8680>
04 01/05/15 20:13:10.391 <0x2b9f8680>
[/code]

If I go to device>advanced, the CurrentSetpoint is listed for device 23 and its friends.

I have no apps installed except for Info Viewer and I have disabled the script by dunked. Furthermore, I have only three more devices: a fibaro switch, a wall socket, and a Horstmann controller.

Some other things of concern: when changing the Wakeup time on any of the TRVs Vera restarts, and I have regular logs of “UserData::TempLogFileSystemFailure start”.

Does anyone have an idea how I can get the other TRVs to work?

slajgaj · January 6, 2015, 11:47am

Hi!
If the Vera say: “Not connected”, then the pairing is not correct.
Try the next method:

unpair the device with Vera
Delete the device from Vera
resetting the valve (factory reset)
Pairing with Vera
The “Not connected” flash is not lua error, it is a Vera internal error. (MCV said: Working this…)

Wiebe · January 7, 2015, 10:43am

I’ve factory reset the Danfoss TRV again. After pairing the messages in the log are now the same for both devices shown above. However, there are still no messages in the log from a wakeup of the TRV. It seems there is still something strange going on with wakeups. I have already deleted all other TRVs that were giving cannot connect errors, so I now only have one working and one troublesome TRV.

There seems to be an issue with (setting) the wakeup time. The working TRV wakes up every 582 s, while it is set to 280 s, and the troublesome one doesn’t wake up at all, or is not logged. Every time I try to change the wakeup time of any of the TRVs (also the working one) I get a lot of info in the log that I interpret as a restart (am I correct? there is also LuaUPnP crash halfway), see txt file.

Does this log make sense to anyone? Is there anything else I can do to figure out what happens?

Wiebe · January 8, 2015, 9:44pm

This is becoming quite frustrating… I now also did a factory reset of the Vera and restored the settings, but this didn’t make a difference.

I read a lot about going to UI5. Do you think that this will make a difference?

Is there a more detailed log available. I would like to know why the Vera keeps missing wakeups. I find it very suspicious that it always misses the second wakeup on the semi-working TRV (and none on the other).

slajgaj · January 11, 2015, 6:43am

Downgrade your Lite to UI5
With UI5 work great all valves