Mine did exactly the same as @danabw upon install of 2.2.4.141. Almost every Z-Wave device (I’ve only got about a dozen or so, all Plus except one Somfy ZRTSI non-Plus, and 4 are Ring Extender 2 devices) came up UNKNOWN, previously, all were OK, had run that way for a day since 2.2.4.139. Did not resolve after a few minutes, so I tried a full Z-Wave Repair (only one I have ever done on this C-7 after manual migration from C-5).
Boy was that Z-Wave repair a mistake. System hung after starting:
Stayed that way, no change in Active Log window. Abort did nothing, just sat there. However, the web interface remained active from another machine’s browser. So, I closed all windows, re-visited Settings page, everything seemed operational but no further progress on Repair, which I had aborted, but abort did not dismiss the Repair dialog box.
Here are past logs at that point when I revisited after closing all windows (the hanging Repair is at bottom of screenshot):
On Z-Wave Details page, all devices now showed as OK except the 3 Aeotec Recessed Door Sensor 7 devices, which all showed FAILED. All 3 returned to OK when I opened and closed the doors that they monitored. Have not yet done the wake-up triggers that you instructed - have to move a ladder around to do that.
Hmmm, My Fibaro Smart Implant does not appear to be working normally since 2.2.4.141.
I'm running the HE Driver and it is reporting state changes correctly for my Security contact sensor. The part that isn't working is triggering the relay to open/close the door. I need to look deeper into it but even after power cycling the FSI, the result hasn't changed.
EDIT: Ok, the relay worked directly from the device - so I re-ran the LGK Virtual Garage Door app config and it's working normally again.
Will you clarify what has been repaired? If I access my dashboard on my PC and select a Dashboard Link (I have a button on each page linking to my Home Dashboard), I get an error message "Dashboard Link Tile only work with Legacy Dashboards links", yet on my tablet with the dashboard working in Fully Kiosk Browser, the links work.
I loaded it last night. The only "issue" was a Z-Wave motion detector would not show up, but after looking thru the logs I saw that the battery in the motion detector was crying for help a couple of weeks ago and was most likely completely dead.
So, it was painless for me.
Tonight I will play with the new motion control time window options
My guess (can't confirm from my current location) is that if you use the Legacy link to get to your dashboards it will enable your Dashboard Links, if you use the new links the Dashboard Links will be inactive. Thus, you could create a bookmark for the Legacy Link and always use it to get to your dashboards if you need/want the old functionality. Again just a guess, but...
Thank you so very much for the excellent job you did on the Device Firmware Updater in the 2.2.4 release. What a joy, easy to use, works well. It’s worth the price of the C-7 just for this app.
Now, if Zooz didn’t require the ZEN16 to be excluded, reset to factory defaults, and included again after firmware updates. Grumble.. @agnes.zooz
I believe, though, that the relevant quote is “When the dog sings opera, don’t complain that his pitch isn’t perfect.” I’m thankful that it can be updated. Many manufacturers don’t provide the OTA files to do it.
BTW not all zooz devices require this.. They have some that added new command classes that the original didn’t have.. This causes the device to have a different Node Information Frame
I've just rolled back it back, it's broken AF - RM was the biggest issue as it was reading NULL values for a bunch of things which broke a ton of automation.
Poking around on my dev hub, 142 definitely messed up Maker API. Maker API calls for most (maybe all, not sure yet) number attributes, e.g. level, just return "null".
