I have included them into my system, but it looks like I’ll have to work on the xml to get them to actually work. I’ve downloaded base xml from the Z-Wave directory, so I’ll give it a go this weekend. I am by no means an expert, so it will be trial and error.
I currently have a ticket logged for Micasaverde support regarding the Danfoss units, and have just submitted a tech query to the UK supplier for the TRV’s. I still have no idea if this is a Danfoss or Micasaverde issue.
After a couple of emails back and forth from my Danfoss supplier, I suspect it is a Micasaverde issue. I only updated my firmware recently and it coincided with adding more items to my mesh. I don’t recall any panic mode issues in firmware 1.5.408.
Does anyone have a link to the released 1.5.408 version, so I can try rolling back one of my vera’s to test my theory?
Sounds like a firmware issue from what i heard. So they could resolve the problem if they are willing to spend resources on it… and with the development of UI7 i am not so sure they will…
Anyway I am returning the Danfoss and chaniging to the ugly StellaZ…
No updates from MCV yet in regards to my support ticket…
@mikee123 Micasaverde released an app a while back called MIOS Utility which allows them to update our Veras with new products/z-wave class configuration etc without the need to push a new firmware.
Looking on the App Store it was last updated at the beginning of Oct, so they have ways to push out fixes… (Assuming they are responsible and they know what it is)
Thanks for that. I think i’ll wait for a few more reviews before i’ll give that a go. Especially as i’ve never restored from a backup which i might need to do if things do not work out.
I’m not sure how many extra reviews it’ll get (most plugins have very few)
Personally I don’t think you’ll be an issue, (famous last words;) ) plus worse back ups and restores (system and zwave network) are actually quite straight forward.
All three veralites have been reset to factory defaults (including zwave chip). I have rolled one unit back to firmware 1.5.408 and installed six Danfoss 014G0012 units (all firmware 2.51) to this unit. All valves are within 7m of the unit, three within a clear line of sight. I have done this configuration to be sure that there is no firmware conflict between the two different TRV firmware versions I have. There are no other zwave products hung of this vera.
I have relocated on of the other veralites (running 1.5.622), and spread control of the other TRV’s across these units, just to retain some heating control. No vera’s are bridged, and they are acting as standalone units. (I am not using these as test units).
I have also attempted to include the two StellaZ’s into my non test system. One successfully, one does not want to know. (I can exclude it no problems, I just can include it!
I have successfully exluded my Danfoss, and its on its way back… So i am not a Danfoss owner any more. And i dont think i will miss them. Loosing connection every 2 max 3 days is just not good enough, firmware issue or something else, i cant live with that.
Two StellaZ (the ugly one) successfully included. I will probably start a new thread about them when i have time as this does not really belong in this thread i think.
Yes, Definitely spin off a new thread for the StellaZ TRVs, as I may be joining you soon. I was going to do one myself to start gathering feedback in advance UPDAtE - I’ve just seen this → http://forum.micasaverde.com/index.php/topic,16889.0.html
Back the the LCs, I’ve found too that popping out a battery for a few seconds seems to give me some rest bite, but that can’t be a long term solution. I do feel the fix is with Vera, I’ve also had issues with the EZmotion sensors in the past where the Vera wake up time was not long enough to complete a full transaction, so variable updates were often incomplete (especially on long routes) … So it’s possible that the LCs are seeing that too and the reason why they go into panic mode and feel disconnected…
If long routes contribute to this issue… how about forcing the route to go straight from Vera to the Danfoss unit. I’m not sure how to configure this, but I am pretty sure that my Vera can talk to all of my Danfoss units without any hops.
I did actually look into manual routing (especially as one of mine does not have node 1 in it’s neighbours list) but the others all do and they still go into panic mode.
From what I read, I can’t work out how to set it so that it can only talk to Vera (node 1). - plus as you know that defeats the benefits of a mesh system but I fully agree, it would be good to do, if only as a test…
OK, just checked this morning. Five TRV’s OK, one in panic mode. The unit that is in panic mode faces into a stud wall, however it does face the vera unit. I am going to pair a TKB socket switch to the test vera and position this at socket at close proximity to the panic mode TRV.
@mikee123 you can use the mios utility its safe. the less safe thing about it is the new implementation file that could mess up old gear. there’s some post mentioning a z-wave thermostate not working correctly after this update of the z-wave sys file. you won’t see the plugin anywhere but in the installed plugin section of vera. this is by design.
@benp did you get any new device(s) with the stella-z or non at all ?
Only one device with the StellaZ I have managed to included. The second will not include (with either of my two non test vera’s), however it will exclude multiple times if requested. I suspect this unit will be going back.
I should add that the unit I have included does not appear to respond to setpoint changes. I’ll try again tonight.
As for the Danfoss test unit setup. I incorporated an additional relay into the system and placed it adjacent to the TRV that went into panic mode. Currently (remotely) all six valves are reporting comms error. The only difference with the TRV that I have been having issues with is that it reports CurrentSetpoint and SetpointTarget as 1deg difference (Current 19degC, Target 18degC).
Last night I checked a few of the valves on my non test setup and multiple valves were in panic mode. I’ve just checked a couple of these valves remotely and the valves are both indicating differences between the Current and Target setpoints. Could this be an issue?
UPDAtE - I’ve just seen this →