mmb

How long did you leave the sensor when eisy reached Reading? Chris says it should take about 10 minutes.

@Chris Jahn that would be helpful, thanks!

@DesertRat I went through exactly this with my Zen17, it uploads the fragments properly but gets stuck on the Reading and never seems to finish. I just killed the window and with Chris Jahn's help I was able to confirm that it had indeed completed successfully. Chris tested the same Zen17 and had the same result - stuck on Reading. Techman shows how to confirm the version. I believe Chris says to do a Synchronize and Update with interview before checking version.

Thanks @Chris Jahn, why wouldn't IOX capture these changes as part of the update process? Like close the loop...

@peterathans try moving the gbl file to the Desktop or Documents folder.

@Chris Jahn passed along how to confirm z-wave firmware version information for a device. right+click | X-Ray | DH Command Classes and look for the Version command class (134) and you will see the application/library/etc. versions for the device In this case version 1.30.

Thanks Chris, this has been quite a learning experience, but that's a good thing. 👍

@Chris Jahn the process started with Sending 8400 fragments then followed with the Reading message where it’s been for the last several hours. Fyi the Zen17 was on the initial firmware release and there’s been 5 or 6 updates since. 1.03 -> 1.30

Good information @Chris Jahn Also, I'm in the process of updating my Zen17 relay and it's so slow. Is there anyway to know if the update froze? I've been at "Reading firmware file for device 3" for several hours. The update file was large at 8400 fragments. Thanks again for the help!

Chris got back to me. The OTA function is located on the root node of the z-wave device. If OTA isn't there the device isn't capable.

I'm ok with it @Geddy but this is new in my use of ISY/Polisy over the last 15 yrs. Wouldn't I have seen this prior to this specific upgrade?

Thanks @Bumbershoot I expected it should be straight forward. This is what I see for all my z-wave devices. I'm updated to 5.7 on both UI and Firmware.

@Techman I'm up to date on the start.jnlp and the cache was cleared but the not found is gone on my latest try. Still stuck with two launcher rows. Thx!

I upgraded from 5.6.4 and all good. No disabled programs. As someone else reported I cleared the java cache as well and 5.7.0 now shows up in the launcher, however when I clicked on the 5.7.0 I got a popup window that said "Not Found" I clicked OK in the box and the admin console loaded. The launcher also presents two lines one the local IP of Polisy and the other just "polisy". I cleared the java cache a couple of times with the same result. Lastly does anyone know where the Z-Wave OTA update utility is located? I must be blind 😬

There isn't a lot of feedback to let you know anything is happening, so I use the Diagonstics/Event Viewer to reassure me something is actually happening.

I run BI, Polisy and UD Mobile, just curious what is your end goal?

My understanding is UD Mobile supports RTSP and MP4 urls per the wiki. So the alternate Wyze cam firmware that supports RTSP should do the job. However from Wyze: RTSP was considered a beta feature and we are currently assessing the path forward as the firmware versions have aged quite a bit. We have removed the firmware files for these versions for now and we’ll update the pages when plans are finalized. Please note that firmware files take a while to work on and test so you may not see an update in the near future. We apologize for the inconvenience.

@Geddy fyi Michel says the leftover "PG2 Deprecated" will be removed in the future.

@MrBill I never installed PG2 on Polisy, it was running on a VMware server. It also migrated to PG3 on Polisy just fine. Upgrading to PG3x was quite bumpy. I have literally rebooted about 10 times at this point. - from the AC console several times - from the ssh command line several times - powered down and up several times PG3x/MQTT is running fine now. I’ll submit a ticket for PG2 leftover in the launcher. Thanks.

Yes @Geddy deleted old link icon, cleared cache and downloaded a new start link. But still have the old launcher with PG2 Dep.

I did remember thanks @Geddy, I wish these changes came with expectation of estimated time. As noted I may have rebooted before the process wasn't finished. Does the new EISY have no sounds? Last question, should I still be seeing PG2 Deprecated?

Ok @Geddy got it running finally. Another two power cycles, one fixed the ISY discovery, the second fixed the PG3x version. Maybe I didn't allow enough time between previous reboots but I was waiting long enough to get the beeps.

@Geddy @Athlon Thanks it seems Firefox gives you a dead stop whereas Chrome allows you to proceed. Onto the next problem. After reinstall all nodes, I'm stuck here. I did a reboot, ssh reboot, power down restart. My only node MQTT server is running but the interface seems messed up.

Thanks @Geddy I'm not on PG3x. I fail on a cert error on the first line of the wiki. Is this a known issue?

Is PG 3.1.36 generally available? I have tried Upgrade Packages in the AC with no change, still on 3.1.21. I also tried ssh command line sudo pkg update && sudo pkg upgrade && sudo service isy restart - and no change.