sjenkins

I think I calculate 9hrs until you succumbed & updated. I can relate

As others here I required an extra reboot on both my Polisy & Eisy to make PG3 come up. Did not need to ssh & run update script. most node servers started in their own which is great except backup/restore and openweather . They both required a restart to get going. I’ll try to remember to cross post there nothing new on zwave devices so far.

Sorry Dennis, didn’t read up the screen. I actually had the same issue with YoLink as you & worked with Bob on it day before last. I was describing the other NS issue which resolved the way I described.

I had this not being able to write with a few of mine. One resolved after “a while” the others might have but I did sync with man’s without replace they made it through the gauntlet. Interesting is the one which resolved itself also completed interview. I actually went backwards in this update for my “completed interview” score but all my z-wave are working pretty fast. Just not all features yet. Thanks @Chris Jahnkeep slogging, bit by bit we are getting there!

Have you tried stopping & restarting the node server. There is a bug currently they are working on where the node server shows running but is not. Happens for me in a number of servers usually indicated in the admin where the server node does not indicate running.

I have the power failure alarm device if you are looking for another tester.

I appreciate that UD is giving us one more knob to tryout as we all figure these devices out.

I will PM you my main pg3x log @bpwwer also asked for it right after a pg3x reboot. Also, I checked in the EISY folder log files and they end at the point of upgrade. Nothing after.

No log available ; I understand not the same thing. Last log file for the NS ends at point of upgrade.

No log available for the YoLink on its own. PM'ing you a copy of my general log. At the bottom will be a restart of the YoLink server.

Sorry I didn’t state that. Yes a few complete power downs and pg3x restart along with the ns cycling. only this ns; all others, about 10, came back and even started up with eisy boot post update. enjoy your w/e we will survive just fine.

It actually sets a delay between commands as opposed to truly speed. The release notes say it may be useful for older devices or those struggling to be interviewed properly. I am thinking of trying it on a device or two which are not completing interview. I would likely try to move it back to default after that though as all my devices are talking ok outside of interview.

Thought I'd start a thread here ; It is in the 5.5.5 support thread by a few of us. Will not start or restart. No log file will start. Also tried a re-install.

On a very positive note my GE switch with motion is now reporting motion. Still does not report interview complete after a couple sync-update-interview. I didn't do a replace. My zooz 77 's which I have two ; still has one which will not bring in the associations. I am wondering whether one is behind in its firmware. They are both in the same gang box but have always seemed to act a bit different. I am looking forward to doing updates OTA with EISY as I am in an OSX/Linux house and cannot use the regular tools. My ZSE44 is next but since I need to open it up and hit the button a lot I am scheduling for the weekend.

Didn't mention. Same as above here. Also cannot get a log to get going for the Yo-Link.

Tried all my tricks but only the YoLink will not start. Did stop / start. stop / restart. Re-install. unplug EISY again. All other Node servers came on. Even my Sonos is back (thank you!).

minor point but wanted to bring to your attention.

Yes they are working fully for my programs. I am not currently using association or basic controls with these devices though. I am finding to complete the interviews with the z-wave devices I have in some cases had to redo it many times. My zen77 devices have not completed interview but after many times one has associations and the other I can't get them. The log files show a TONNE of data passing by but no joy at the end. Next update perhaps.

So with this release I got a few more of my z-wave devices to complete their interview: Homeseer HS-LS100+ Zooz ZSE42 water leak XS sensor Zooz ZEN 31 RGBW dimmer Not able to complete interview with the following (still get limited usage) GE Jasco 26931 switch with motion sensor (switch ok but no motion update on ISY, shows up in log) zooz Temp/Humidity XS ZSE44 (getting temp/humidity but battery showing zero) ZEN77 S2 Dimmer 700 only getting switch and scene 1/2 but no associations Hard to say if some of my z-wave need an update (I am linux/Mac only) so I am looking forward to the ability to update from the ISY. Anyway wanted to get this out there as feedback for @Chris Jahn and the team. We are making progress. Let me know if there is further data which will help.

did you need to do a sync with replace to get this working?

Thanks, now I know that is needed for zooz (and maybe others). I did that with a few of my z-waves and it helped with a few. Good to know its not a UD/isy issue.

At first all my servers showed green with nodes. I had to stop each of them and start or restart. Did it with the log tab selected for each node & you can be sure it started. That got all my servers going again. They only came up with this manual intervention and not a eisy or pg3x reboot.

Haven’t done the 5.5.4 update but last night did the *.20 update for pg3x and even though my servers showed green with nodes I had to stop each of them and start or restart. Do it with the log tab selected for each node & you can be sure it started. That got all my servers going again. They only came up with this manual intervention and not a eisy reboot.

I am getting these same nodes (I have about 7 of these sensors). Having the same where the Leak Detected Alarm does not turn off. I am using the main node which does come on/off for my programs right now.

I have been finding the battery devices have needed a few interviews to complete. It's as if the device goes back asleep. I have found by either hitting buttons on the device or activating it (moisture, motion) that sometimes keeps the interview going. mostly through just another interview seems to eventually get it all done. also in one case I went onto something else and the data/nodes showed up later. just with battery. dong this I have got all of my z-wave working with all nodes. Now I am really looking forward to being able to do OTA updates for my z-wave. I am in an OSX / Linux house so need this to get my devices up to date.