I just noticed, my Danfoss has lost connection again. This time it had lasted only a day. And i have plenty of zwave devices around which work fine. It is going back. Have ordered 2 ugly StellaZ’s instead. See how i get on with those. But apparently they have same functionality on Vera, you just cannot use the ‘modes’, but you can change setpoing, and it even reports temperature.
So lets see… will report back once i have them installed
Hi @mikee123
I have 3 x Danfoss Living, I’ll need to check if they have lost connection (antennae and bell flashing) tomorrow, but I wanted to share this with you, and wondered if you could share yours.
I’m curious if there is still some communication going on…
There’s also a CommFailure entry in the list too (not shown) which for this one is showing 0 (zero)
according to versioninfo you have a firmware 2.51 device (last 3 digits) and the batterylevel seems to work also… 87%
if the communication would fail the commfailure or pollnoreply would indicate this and show a number of how many fails it had.
[quote=“parkerc, post:22, topic:177061”]Hi @mikee123
I have 3 x Danfoss Living, I’ll need to check if they have lost connection (antennae and bell flashing) tomorrow, but I wanted to share this with you, and wondered if you could share yours.
I’m curious if there is still some communication going on…
There’s also a CommFailure entry in the list too (not shown) which for this one is showing 0 (zero)[/quote]
I’ve just gone through all my 20 valves and can confirm that two (2) are showing comms failure = 1. All the rest are 0. I can also confirm that only one of the two valves shows panic mode, the other does not. I am even more confused now…
What is strange is Vera reports the right setpoint, but the change is not getting through. I have to double check when i get back home, but at the moment it should be at 16 degrees, but is showing 21, which is where it was last night when i checked comms on the thermostat. I will try to change it now and see what happens. Here is what mine is showing:
[quote=“benp, post:24, topic:177061”][quote=“parkerc, post:22, topic:177061”]Hi @mikee123
I have 3 x Danfoss Living, I’ll need to check if they have lost connection (antennae and bell flashing) tomorrow, but I wanted to share this with you, and wondered if you could share yours.
I’m curious if there is still some communication going on…
There’s also a CommFailure entry in the list too (not shown) which for this one is showing 0 (zero)[/quote]
I’ve just gone through all my 20 valves and can confirm that two (2) are showing comms failure = 1. All the rest are 0. I can also confirm that only one of the two valves shows panic mode, the other does not. I am even more confused now…[/quote]
I’ve had a look at all the valves Advanced settings and tabulated some of the details. From this mornings look, it appears that two additional valves are now showing CommsFailure.
One highlight is it appears I have three(3) 2.50 firmware rather than the one (1) I though I had. I’ll have to check the labels tonight. Multiple differences in SetpointTarget and CurrentSetpoint details. I’ll add in which rooms are showing panic mode tonight.
mine is version 2.51 i have sent a command to it to change setpoint to 19 degrees (it was at 21 degrees). It looked as if it had accepted it as it had changed in my Device to 19, but had a look now (about 1 hour later) and it is back at 21 degrees. So it looks at the moment it is not accepting setpoint changes, but might still be communicating with Vera
I do wonder if there is something more deep-seated at play here - have a look at the thread I posted a while back > http://forum.micasaverde.com/index.php/topic,16565.0.html and go to the google link in the first post.
If we can confirm symptoms are consistent across the Connect Z then we can log a call/bug with MCV after all they are supposed to guarantee they can support all z-wave products,
Just got home and checked the status of all my valves.
19 out of 20 all showing panic mode. 1 unresponsive requiring battery out to reset.
I think I am going to un-pair all TRV’s this weekend, reset all my three Veralite’s to factory defaults and start again one last time. If the problem persists I’ll contact Tech Support.
I continue to wonder if the COMMAND_CLASS_CLIMATE_CONTROL_SCHEDULE has anything to do with it.?
Within the LC you have the ability to set the set points against a schedule, the google post I linked to looked to disable this. Does anyone know how I can get Vera to show me what schedule settings are being used for this command class?
See page 229 of ftp://act-solutions.com/Megaworld/Devkits/Old%20Dev%20Kits/DevKit4.24/data/SW_DOC/SDS10242-11%20-%20Z-Wave%20Device%20Class%20Specification.pdf
Update - found this post, just not sure I have the skills/confidence to follow it. > http://forum.micasaverde.com/index.php/topic,8596.msg55250.html#msg55250
After checking the status of my valves this evening, I reset each unit. Default 21degC.
End result, three hours later. All (read all) valves displaying panic mode…
Sent from my iPhone using Tapatalk - now Free
from what i can “translate to normal language” the thread speaks of setting the setpoint for all weekdays at the same time and it needs stuff like setpoint -5 for setting the setpoint from 21 degrees to 16
perhaps you can try to make the setpoint say like -2 and see if it drops the current temp by 2 degrees ? not sure wether the vera takes minus values , could also try 2 and see if it goes up by 2 to be safe (and warm lol)
I have the antenna and bell too, with winter coming I’m going to need mine to work, I think we should all log calls to ensure this gets on MCVs radar
A side piece of info for you, by using the Info viewer plugin, I can see this for my LCs
PollOk PollTxFail PollNoReply
17 Radiator 1 9 ---- 3953
171 Main Bedroom Radiator 275 ---- 14
172 Radiator 2 364 ---- ----
17 = fw 2.06
171/2 = fw 2.51
Radiator 1 looks to be having some other issues, but Radiator 2 is also flashing as well , even though it shows no ‘Poll No Replies’. Something does not feel right.
It could be the 1.5.622 version were running, as I’m sure it was more stable before, but then again during the summer months I’m not thinking about heat …
You may have hit the nail on the head. I had been running 8 valves successfully before I updated the firmware (to cater for a few Fibaro units I purchased)…
Sent from my iPhone using Tapatalk - now Free
yeah the older then 2.51 firmware seem to be a bit worthless from what i read. the 2.51 should be bugless, but i seriously doubt the thing. perhaps it needs other steering then the vera provides, which means the danfoss is using its own z-wave implementation which differs from the standards in use.
All 20 valves now reporting comms failure after resetting last night (and performing a heal overnight)!
To get anything done to address this, we will each need to log a support call with MCV, so it is on their radar (the more support tickets = the more attention it should get). After all they do guarantee compatibility → http://wiki.micasaverde.com/index.php/Guaranteed_Compatibility
I’m surprised I’ve not privately heard from @Ap15e as i recall he has some too.
Also the wiki does not confirm if they work ‘error free’ with the latest firmware → http://wiki.micasaverde.com/index.php/Danfoss_Thermostat_LC
Maybe it’s the heal… I know it affects some other units (like the older Duewi in-wall switches)
Just an FYI -
I tried a number of things today, poll now, configure node, update neighbours etc. each with various degrees of success. The bottom line is they still fall off the network and return to panic mode.
So, to get some help, I’ve logged a called with MCV and also flagged it with the company I bought them from to the hope they can hep influence matters with both Danfoss and MCV (otherwise they have to go back)
Hopefully those of you experiencing the same issue will log a call too …
I have with the place i bought them from, and they are investigating