BigMojo

Exactly, if available! The ZMatter dongle is discontinued so I'm not going to rebuild with either of mine. They've both been through lightning strikes, one had its eISY absolutely smoked, so there's no way I'm devoting any real time to equipment that isn't procurable.

@Stagehand, I'm wondering what firmwares are on the Aeotec dongle you attempted with? Was it deployed straight out of the box or did you go through the SILABS Z-Wave and/or Tera Term Zigbee updates? The Zigbee update process was very problematic due to the bootloader switch. I ended up disassembling the dongle to be able to actuate it reliably during insertion. Pro Tip: Remove the metal shield from the body first, it locks the 2 plastic halves together! During limited initial testing, there was a serious improvement in both speed and reliability with my reincluded 800s (star) in a very challenging and noisy environment. I appreciate you not wanting to reinclude and reprogram for 40 Z-Waves, not a fun endeavor! I'm staring down 85 hard wired and another 50 batts so ya, not fun...

@Stagehand , I'm in a very similar boat with the Aeotec 10 Pro Stick. Which firmware did you test with? Z-Stick 10 Pro Update - Z-Wave (Firmware V2.0 SDK 7.23.2) has two versions 7.23.2 and 7.24.2. I went straight to the 7.24.2 version (being the newest) with the results: ADMIN CONSOLE throws NODEDEF errors and is now useless for programming (picker failures, etc) System Restores, Resets, Clean Starts will not resolve AC errors I was able to apply 7.23.2 over 7.24.2 but have yet to test that FW BOTTOM LINE If you want/need Admin Console to remain functional, DO NOT attempt a dongle topology change on your production system Until YOU have done a proper Hardware Qualification Test !

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.