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

Sadly no, I run 13 ZCombo units and they don't act as repeaters. I've kept an eye out and searched for hardwired but I haven't found any. When I first deployed zWave I had success buying some Leviton plug in switches and dimmers and that got all my smokes communicating solidly. Side Note: Our building code started out with Battery Smokes (before hardwiring was available), then to hardwired and finally back to battery units. It turned out the hardwired units would sometimes take lightning damage and brick with no indication so they reversed the requirement. Don't know about your codes but it's something to consider.

@Techman I'm running the zooz-700 on 7.17 FW IIRC. I do have a new EISY w zMatter in house that I'm about to begin bench testing my different device types on. Happy to do the ZRTSI first but I'm probably a couple days away from that if you can wait. Re: Somfy it's ironic, they were super early to the zwave party and now that demand should be on the rise.... I'll reach out to Somfy and express interest in the ZRTSI, I'd encourage any other Somfy RTS users to do the same.

I've run a ZRTSI for a couple of years on my Polisy. A few things to be aware of: It's a 300 series device, solid but slow It will include as 17 devices (1 controller and 16 nodes) I just reached out to @Michel Kohanim& @Chris Jahntwo days ago to see if I could reclaim some device pool space, it's a Somfy issue. I'll be submitting a request to them but I wouldn't hold your breath. If you've got the headroom, I would definitely recommend it vs the URTSI, no net resources to wrangle and a cleaner hardware package if it needs to be positioned in a public area to extend your RTS signal reach!

No update for Polisy, eISY = yup

@larryllixI had a similar issue when commissioning a new desktop. What resolved my issue was to: Disable Norton (both auto protect and firewall) Remove Java Reboot Disable Norton (both auto protect and firewall) Download and Reinstall Java Add universal-devices and your IOX to the security exceptions list in the java control panel Add -Xmx1g (or whatever you require size wise) to the runtime parameter in the java control panel Download a new start.jnlp Unblock the start.jnlp in your downloads (Right Click / Properties / Unblock) Run start.jnlp If all works as expected: reboot and try Finder again without disabling Norton I suspect there's a norton vs. oracle installer issue...

Same error, same fix, same result ! Thank you gentlemen and the very happiest of holidays !

I can confirm that firmware 7.17 is definitely needed. As a funny side note and cautionary tale: I was using a wifi antenna dock as my USB extender and wasn't seeing anything on DMESG so I tested the stick and extender using Simplicity Studio and discovered that the shells of both the dock and the stick were combining to prevent full insertion/reliable connection (nothing or DMESG spamming as the stick came in/out). Since you need to upgrade the firmware anyway, I suggest you: Insert your stick directly into your PC and update the FW as instructed above. I wouldn't recommend updating firmware using an extender, if yours is iffy because your cat was chewing on it, things might not go so well ? Remove the stick and reinstall it using the extender. Go into settings for Simplicity Studio Hit REFRESH, if the stick doesn't appear, troubleshoot your extender or get one that's RELIABLE Select the stick and press OK At this point we know the extender is working. Go into Network Management and confirm that your FW is at 7.17 (just to be double dog sure) Remove the stick/extender from your PC and install it on the POLISY. Shutdown the POLISY Cold boot the POLISY (this was crucial for me) Open the AC on your POLISY and confirm that the z-wave menu is now populated. I want to thank the community for all the great content and support, it's much appreciated.

Hey @Michel ! After the odd result from importing the file, I also tried the clipboard import(s) to see if the result changed, it didn’t. I'm more than happy to provide or try anything you’d like to see, Topo files, backups, logs, remote access, etc. On a side note, THANK YOU to you and your team for the evolutionary corporate vision and execution you’ve shown. I know it’s been a hard road but UDI is kicking *** and we all owe you a great deal of gratitude for the astounding results you’ve accomplished in the 2 years since we last spoke. All my best, Tom

I was attempting to compress my programs folder to see how many I had available for my next roll-out and saw some very strange (or loose nut behind the keyboard) behavior. Specifically: Backup ISY Export All Programs Export All Programs to Clipboard Delete All Programs Save Changes - 430 Programs Deleted Reboot Import All Programs from Clipboard Save Changes Screenshot “Import from Clipboard Result” - INCORRECT – former directory structure Delete All Programs Save Changes – 128 Programs Deleted, expected 430 Import Saved Programs Save Changes Screenshot “Import Result” - INCORRECT – former directory structure Delete All Programs Save Changes – 128 Programs Deleted Reboot Restore ISY Screenshot “Restore Result” - CORRECT – current directory structure Delete All YELLOW programs Save Changes - 24 Programs Deleted Reboot Export All Programs (Includes 18 "Red" programs with run references to deleted "Yellows" Delete All Programs Save Changes - 407 Programs Deleted, expected 430-24=406 Reboot Import Programs Save Changes Screenshot “Import Result No Yellows” - INCORRECT – former directory structure Delete All Programs Save Changes – 111 Programs Deleted Reboot Restore ISY Delete All "Yellow" programs Save Changes – 24 Programs Deleted Reboot Delete subsequent "Red" programs Save Changes - 19 Programs Deleted Reboot Delete subsequent "Red" programs Save Changes - 4 Programs Deleted Reboot Export Programs Delete All Programs Save Changes - 386 Programs Deleted, expected 430-24-19=387 Reboot Import Programs Save Changes Screenshot “Import Result No Yellows or Reds” - INCORRECT – former directory structure Delete All Programs Save Changes – 111 Programs Deleted Reboot Can anyone confirm this behavior? Possible factors could be: Inadvertent use of Reserved Keywords in File/Folder names Duplicate File/Folder names located in different parent folders (Different Operating Modes & Archives) Existence of "Yellow" or "Red" programs. I've been messing with the Z-Wave side and my SMOKES programs currently point at non-existent devices OLD (7 years) SD card I know this looks like the typical user error resulting from restoring the wrong save file but I've repeatedly verified that I'm pointing at the right source and destination files. Not sure if this is a known issue, only thing I found was the discussion about programs being re-enabled after an import. Thanks !