BigMojo

It may be an NTP issue (12 hrs & 41 sec indicated difference)

@vbPhil SSH sudo pkg info isy will give you the full version (et.al.) info

Installed smoothly, seems to have fixed up my 5.6.3 zWave glitch. I did go through and re-interview all my ZYs, a handful of devices want re-inclusion but everything else is running MUCH better! Thanks to the entire UDI team for all your efforts !!!

@landolfi, I can't speak to the root cause, that's best left to the team. I can say that my issue was communications related evident in a corruption of my zWave device definition file(s). Without putting a timeline on when the new package will be released, I can tell you I'm fully backed up (2x) and ready to go on the upgrade. Read into that what you will 😉

@TexMike, I have the same issue and @Michel Kohanim, @Chris Jahn & the team have been busting butt on this issue. It's my understanding that the fix is in final testing and the solution should be here very soon.

@TheA2Z ^^ Excellent ! I just did over 100 Zooz FW updates (no bricks) and would also suggest: Disable what you can on IoX to reduce network and log traffic (programs, node servers, etc). Make sure the battery > 80% before inclusion 1' - 10' unobstructed view of zWave antenna. This speeds things along greatly during interview If you have SSH access: sudo tail -f -n 500 /var/isy/FILES/LOG/ZWAY.LOG I found this helpful because: It's a lot easier to observe what's actually happening on the zWave network The device can still be actively communicating with IoX but the blue indicator may not always be flashing. Once the zWave interview timeout reaches ~200-150, triple click the sensor to reawaken it. This gives the unit more time to interview without getting (too) bogged down by spamming wakeups. Repeat until the interview completes or the unit stops actively sending info other than wakeups. You will quickly recognize what a good vs. bad inclusion looks like in the ZWay log and can respond appropriately. Hope this helps

GLASSY Smooth Update ! Well done and thanks to @Michel Kohanim @bmercier & @bpwwer for all your efforts!

@dbwarner5, I can tell you I’ll be looking at my router’s logs (Syslog’d to NAS) to see if/when anything is getting recorded for the IOX’s MAC/IP. A quickie test would be to modify your router DHCP lease time to as low a value as you can and see if that changes your failure frequency. If so, raise the lease time to a large value to correlate a greatly reduced fail frequency. I’m tied up with the holiday weekend but I’ll take a deeper look in the next few days to see if I can replicate your condition. Happy Memorial Day everyone!

I’ve been seeing the same behavior also. Would it be possible to insert a connection drop timer variable before the notification triggers? This may also be a DHCP renewal but I haven’t had a chance to look at that yet.

The current distro ( v3.1.21_1 ) installs and operates properly, thanks @bpwwer

Installs and operates properly, thanks @bpwwer

@Techmanyou should be good to go with ZRTSI on Eisy with z-Matter from what I can see. It's a lateral move but it looks good.

Hi Guys! First my apologies this took so long, life got busy and I wanted to focus properly on this. ZRTSI works on the Eisy as well as it does on the Polisy. It should be noted: My application is UP/DOWN storm shutters so I couldn't test interim positioning via Motor Control Scene control doesn't currently work with the scene responders but at least it's there (not on Polisy) Scene control works with the switches BUT you will command flood. The ZRTSI likes to be spoon fed commands about every 2 seconds or more You CAN NOT query position! You eat 17 (or however many nodes you enable +1 for the controller) device addresses so there's a heavy hit to your pool versus the hoped for multichannel. The RTS radio in the ZRTSI has better range than the URTSI I'm leaving this install in place for now so if anyone would like further info, please ask. eisy zrtsi ch01-scene node object.txt eisy zrtsi ch01-scene node info.txt eisy zrtsi ch01-scene node def.txt eisy zrtsi ch01-switch node object.txt eisy zrtsi ch01-switch node info.txt eisy zrtsi ch01-switch node def.txt eisy zrtsi ch01-motor node object.txt eisy zrtsi ch01-motor node info.txt eisy zrtsi ch01-motor node def.txt eisy zrtsi controller node object.txt eisy zrtsi controller node info.txt eisy zrtsi controller node def.txt eisy zrtsi cmd flood.txt eisy zrtsi inclusion base and 16 nodes.txt

Worked like a champ, issue resolved, thank you @bpwwer !

Upgrade went fine, all seems operational but: Could some people check to see if their polyglot and pg3 log timestamps are offset by -2 hours? System time shows correctly through SSH. Let's just say that my box has some interesting challenges so YMMV but thought this was worth noting