I just went to a heating-installing company during my lunchbreak and it seems that there is an adapter installed on my valves. This thing is a menace to remove it seems (I will probably wreck it when I get home and try it again…)
The thing I am missing is indeed the K adapter (014G0252) and then they should fit nicely once received and installed.
The ring in the picture isnt the adapter since it has no threads… its just a cosmeting thingy I guess.
So it;’ just like you said it seems:) tnx!
Edit: it took a rediculously large monkey wrench but I can confirm they can be removed (just so other readers know)
As well as checking the menu options, please can someone with the new TRV post a picture of the Vera device settings tab (I’m curious if it is different)
I’ve attached my 2.06fw capabilities and version settings for comparison.
Just got my devices today. They are on firmware 2.50. Couldn’t really mount them to the radiators, need to get RAV adapters first.
But I still added one to the vera. Pairing went just fine, no problems at all. When I change the temperature on the danfoss, it is shows right away as soon as I reload the UI5. When I change it in vera the value is transmitted as soon as I wake up the danfoss. In my opinion this is normal behavior for a battery powered device.
I now have to test how long it takes to get the adjustment transmitted without waking up the device manually. I guess it just wakes up every hour or so, we will see. => Edit: It never takes more then 1-2 minutes to transfer the setpoint from the vera to the danfoss. The vera retries a couple of times, but always sends the new temperature to the danfoss. On the danfoss there is no reaction to be seen, but as soon as you hit any button the new temperature is shown.
Quite possibly… Not having all the models, it’s difficult to be sure which features are based on what firmware. So it’s the power of elimination .
The 2.06fw version which most of us on this forum have, supposedly works with the Danfoss Link, but they do not have those options.
So, if they’re not on the new 2.50 version, then I guess they must either relate to the v3 fw that’s been mentioned and is Danfoss Link only (I think) or the manual is for a non released version…
What I am wondering, is anybody getting the temperature reading from the device on the vera’s UI? In my case it just shows “0”. Also the buttons “Off” and “Heat” are not working for me.
Does anybody know about additional parameters that can be set?
Sadly no, (well certainly not on 2.06fw) it seems Danfoss hides this.
I would have thought it would be very hard to do accurately, especially being so close to a heat source)
I also raised this a while back and as an alternative, there is a post further down in this section of the forum to have a secondary temp sensor report (virtually) on the Living Connect, but that is just for show I believe .
It was one of many enhancements we were hoping for on the new 2.50fw release, but i’m guessing all the set point and temp adjustments are still done internally (and hidden) on the TRV.
Yes, I read in other forums that the device is just not reporting the temperature. So it is not vera’s fault.
Did I get this right, if I want to synchronise a temperature sensor (deviceId: 25) to the danfoss (deviceId: 67) I would have to add the following luup code to the startup functions?
-- sync temp sensor to danfoss
-- list of { temperature_sensor_device_id, { list of Danfoss_LC_device_id } }
devices_to_synchronize = { { 25, { 67 } } }
function synchronize_temp( lul_device, lul_service, lul_variable, lul_value_old, lul_value_new )
for i = 1,#devices_to_synchronize
do
if devices_to_synchronize[ i ][ 1 ] == tonumber( lul_device )
then
for j = 1,#devices_to_synchronize[ i ][ 2 ]
do
luup.variable_set( 'urn:upnp-org:serviceId:TemperatureSensor1', 'CurrentTemperature', lul_value_new, devices_to_synchronize[ i ][ 2 ][ j ] )
end
end
end
end -- synchronize_temp
for i = 1,#devices_to_synchronize
do
luup.variable_watch( 'synchronize_temp', 'urn:upnp-org:serviceId:TemperatureSensor1', 'CurrentTemperature', devices_to_synchronize[ i ][ 1 ] )
end
-- END sync temp sensor to danfoss
There was an explanation from danfoss regarding the temperature reading… they said something like: “we did not design it that way so its not possibe”.
I saw a post dat it was possible to have the reading of another temp transmitter in the danfoss widget but you have to look for that one on this forum (was in the last 3 months if I remember correctly)…
The question that remains for me is whether it still takes 1.5 hours for the thermostat valve to react to a change in setpoint, on this new version of the device. Can anyone verify?
Note that the device will change the valve instantly if you wake it up using the center button. But what happens if you change the setpoint (from a low to a high temperature), and wait for the thermostat to wake up on its own? Does the valve motor run as soon as the new setpoint is programmed, or does it still take 1.5 hours to react?
Well, since all the shops say that the zwave part of the software is 100% identical and I reallyy dont think the danfoss software caused this delay, I will be surprised (happily!) if this would be solved…
chixxi seems to have made the test and it looks promising.
chixxi quote :
I now have to test how long it takes to get the adjustment transmitted without waking up the device manually. I guess it just wakes up every hour or so, we will see. => Edit: It never takes more then 1-2 minutes to transfer the setpoint from the vera to the danfoss. The vera retries a couple of times, but always sends the new temperature to the danfoss. On the danfoss there is no reaction to be seen, but as soon as you hit any button the new temperature is shown.
I’m looking for a Zwave heating solution and was also waiting for the new firmware of the Danfoss Living Connect. If the delay issue is not fixed I will definietly not buy them.
Well the issue is that for this function, there is currently no alternative…
When programming time-triggered scenes it is also quite easy to program around this issue.
I don’t mean the delay between transmitting the setpoint and the device receiving it. That is indeed not a problem with the Danfoss firmware, but a consequence of the way battery powered Z-wave devices operate (intermittently waking up)
I was referring to the delay between receiving a new setpoint on the device, and the actual adjustment of the radiator valve. If the device is woken up manually when the setpoint is being transmitted, the valve is adjusted instantly: you can hear the motor running as soon as the display on the device goes out again. But if you wait until the device wakes up by itself, the valve motor does nothing and it can take up to 1.5 hours for the valve to be adjusted, even though the device already has the new setpoint.
[quote=“intveltr, post:59, topic:173081”]I don’t mean the delay between transmitting the setpoint and the device receiving it. That is indeed not a problem with the Danfoss firmware, but a consequence of the way battery powered Z-wave devices operate (intermittently waking up)
I was referring to the delay between receiving a new setpoint on the device, and the actual adjustment of the radiator valve. If the device is woken up manually when the setpoint is being transmitted, the valve is adjusted instantly: you can hear the motor running as soon as the display on the device goes out again. But if you wait until the device wakes up by itself, the valve motor does nothing and it can take up to 1.5 hours for the valve to be adjusted, even though the device already has the new setpoint.[/quote]
I will test this as soon as I have them mounted and let you know, but I want be able to do this befor the end of the week.
