According to Danfoss you cant upgrade the firmware. There may however exist a hack!
Summarization:
Danfoss 2.06 / Vera 3 : 1.5.459 : no issues
Danfoss 2.06 / Vera Lite 1.5.408 : no issues
Danfoss 2.50z / Vera Lite 1.5.408 : no issues
Danfoss 2.5.3 / Vera Lite 1.5.408: no issues
Danfoss 1.06 / Vera ? : Delay issue…
I think we found the problem issue firmware… anyone else? (not many responses till now…)
I do not believe software van be upgraded Im affraid, even by Danfoss themselves…
Thanks for all the contributions
Focussing on the new Danfoss Connect Z - are we saying there are two potential firmwares in circulation?
Danfoss 2.50
Danfoss 2.5.3
It would be helpful if each of these relate to a Danfoss product number such as 014G0012, which I understood the 2.50 to be ? That way people can be more specific in their purchase?
There was also some discussion earlier about there being some extra functions in certain Living Connect fw release, such as sizing and orientation of the valve ?
[quote=“parkerc, post:83, topic:173081”]Thanks for all the contributions
Focussing on the new Danfoss Connect Z - are we saying there are two potential firmwares in circulation?
Danfoss 2.50
Danfoss 2.5.3
It would be helpful if each of these relate to a Danfoss product number such as 014G0012, which I understood the 2.50 to be ? That way people can be more specific in their purchase?[/quote]
2.5.3 also relates to 014G0012!
its the same valve…
the issue is that the same valve has different fws…
140G009 was the “old one” (which I received) and they had allready changed the fw from 1.06 to 2.06.
Then they changed the typenumber to 14G0012 and brought it out with this software (which they named 2.5) and shortly afther this they removed the Danfoss software from it making it fw 2.5.3
I believe this is how it went… and why we dont understand anymore which one is which…
Therefore I started to “poll” to see where the issues are but it seems its only the 1.06 version (untill someone shows otherwise…)
OK, in the spirit of auditing the models out there and sharing that info - here’s a photo of my unit.
Part No. Firmware
014G0009. 1.06
014G0002. 2.06. - photo confirmation…
014G0012. 2.50
014G0012. 2.5.3
Any others? (Photos would be good)
I can than also update the first post in this thread, to save others trawling through…
to my recollection, the 14G0002 wasnt a compatible zwave device… only a Danfoss LC with Danfoss controller (this is the part of the software which is removed from the newer ones)… right?
The photo and feedback on this thread suggests that 014G0002 fw 2.06 works with Vera (although some report delays) - my own thoughts are that the fw 2.06 was an attempt by Danfoss to have their device work with BOTH their Danfoss Link and other HA controllers.
To help Ap15e, has a wiki page on this, so if we compile more feedback and compatibility results here on this forum, the wiki page can be updated to reflect this.
http://wiki.micasaverde.com/index.php/Danfoss_Thermostat_LC#HW_revisions
Vera 2 with Firmware 1.5.408
014G0012 danfoss Firmware 2.51
No issues
The comparison would be more usefull if people were more specific about the outcome. No issues can mean a lot.
What matters is the reported delay in physical response. Typical example that I would like to see tested is if there is a nigth/ day schedule of e.g. 16 to 21 Centigrade, how long it takes for the radiator to change its temperature. With other software (Zwave.me) I do see a 1.5-2 hour delay as well (014G0001 2.06).
Actually, the only test I trust is:
- Switch off radiator (Danfoss to 4 degrees Celsius). Let it cool down.
- A couple of hours later: Use Vera UI5 user interface to increase temp to highest setting (28 degrees Celsius)
- Do NOT touch the Danfoss. This is important because when you press a key on the Danfoss, even to check the temp on the display, it takes this as a reason to open the valve.
- Feel with max 15 minutes intervals if the radiator’s temp increases. Post the time it takes until the radiator starts heating up in this forum.
Thanks!
I have the LC Z (014G0012) SW 2.50 + Vera Lite 1.5.408 (UI5). The LC keeps disconnecting after some time (flashing antenna + alarm) and I have to do a “connection test” to get it to talk to Vera again. So to all of the previous “no issue” posters, did you have to do anything special (other than include + configure) with the LC to keep it communicating with Vera?
AFAIK, these devices need SUC, which was stripped in the latest Z-Wave firmware, and therefore won’t be compatible with Vera in it’s current form.
Thanks!
mgb
Your symptoms could suggest that the LC is at the limit of range of Vera or other z-wave nodes in your mesh network. Did you include it next to Vera or in its final location? Have you updated Neigbor nodes or done a full system heal to see if that improves things?
Another idea is to move the LC back next to Vera, do an update again and then see if it keeps disconnecting, if it does then it could be a faulty unit
I get the flashing antenna on most units after a while though it doesn’t seem to affect operation. I’m still on 1.5.401 though
[quote=“parkerc, post:94, topic:173081”]Your symptoms could suggest that the LC is at the limit of range of Vera or other z-wave nodes in your mesh network. Did you include it next to Vera or in its final location? Have you updated Neigbor nodes or done a full system heal to see if that improves things?
Another idea is to move the LC back next to Vera, do an update again and then see if it keeps disconnecting, if it does then it could be a faulty unit[/quote]
@parkerc: I have a Vera Lite so I included the LC in it’s final location (Vera was in low power mode). After inclusion, I did “Configure now” setting the wakeup interval to 900 - I manually wokeup the LC when I did this so the config would take. I not quite sure what a “full system heal” is. Could you elaborate?
Now I did (just) move the Vera nearby the LCs and did an update neighbors. I will report back if the connection issues persist.
@[quote=“intveltr, post:95, topic:173081”]I get the flashing antenna on most units after a while though it doesn’t seem to affect operation. I’m still on 1.5.401 though[/quote]
@intveltr: At first I thought this was the case, and it 50% is. I tried this and Vera → LC communication worked: I changed the set point of the LC in UI5, wokeup the LC and the set point took even with the Antenna + Alarm flash! Then, I set the heat point again in UI5 but this time I let it timeout and say “Failed, waiting to retry when the node wakes up” before I wokeup the LC. Result: the set point did NOT take 
I tried this again after moving the Vera closer (as I said above) and achieved the same results ??? This leads me to believe the LC does connect to Vera when it wakes up as the set point is not taking.
I’m at a loss
I have about 11 LC valves on 2.51, set to wake-up every 5 minutes and switch the temperatures in the am and pm in rooms via schedule.
I find most of the time the new set-points take within about 10 minutes and you can hear the valve motors activating when they’ve taken but about 5% of the time they seem to miss the cmd and so I get the odd radiator that doesn’t take the set-point.
I don’t usually do anything special and it sorts itself out at the next schedule, I was half tempted to write a plugin that monitored the valve and kept attempting to bring it to the target set-point so if it missed a cmd it would correct it quicker but my valves don’t do it often enough to worry me.
I must have about 40-50 z-wave dimmers and switches in the walls now so I can’t believe it’s coverage related, I assumed it was an LC/Vera firmware interaction.
Well I said I would report back and I’m happy to say that moving the Vera closer to the LCs appears to have fixed the connection issue - both LCs have stayed connected all day. 
Changing the temp in Vera updates the LCs after they wakeup so everything seems ok.
Tomorrow I will test moving the Vera back to it’s original location (maybe this time do a proper “update neighbors” + system heal) and see if the connection will hold. There are plenty of the Fibaro in wall switches between the Vera’s original location and the LCs so maybe I didn’t update the neighbors properly. If this doesn’t work, I’m thinking I might purchase another Vera Lite and run it in a master-slave / primary-secondary with my existing controller.
Will report back tomorrow!
I allso have the fw 1.06
I’we found out that the LC controls the heat depending on time, temp, and real temp (room temp).
it “changes” the temp in steps, depending on how last time’s “change” came out …
it’s a little bit tricky to explain. But works like this.
to control LC the way Danfoss would like the unit needs to know the time and weekday, it needs to know the “comfort temp” AND the “saving temp” (alternative / low temp).
then You program the unit to heat up the room from ex 07.00 AM to 09.00 AM and ex 04.00 PM to 10.00 PM.
The LC then aut. begins x-minutes before 07.00 AM to ramp up heating. At 07.00 the unit checks the temp. if the temp is lower than the “Comfort temp’s target” the unit remembers this and corrects the time and ramp < for the next “comfort temp”. Continiusly trying to improove the heating / saving result.
You could say that the problem isen’t the way the fw works on the LC, it’s the way Vera controls the LC.
so how do we get Vera to change this ?
I’m Sory for my bad English, but I hope it make’s sense …
Allan
That is all probably correct, but… most of us just need a means to switch the heating on or off. This simply takes up to 2 hours before the valve moves on the old firmware.
Personally, I am not interested in a time based schedule. I want the heating to switch on at the time I decide to drive home, which is not predictable.