mmb
-
Posts
629 -
Joined
-
Last visited
Posts posted by mmb
-
-
7 hours ago, DesertRat said:
I may say uploading firmware to device .... or get to reading firmware on device ...... but it never completes.
Has anybody had any success applying the latest ZSE42 *.gbl? Can UD confirm it is supposed to work. Do I need to use a ZWave stick and Simplicity Studio on my laptop to update the ZSE42 firmware outside of the eisy?
@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.
-
2 hours ago, Chris Jahn said:
On clarification on this .. to see the changes to the device in IoX after the OTA Firmware upgrade completes, you must either do:
right+click | Z-Wave | Synchronize | Update with Interview
or
Remove and add the device again.
Thanks @Chris Jahn, why wouldn't IOX capture these changes as part of the update process?
Like close the loop...
-
6 hours ago, peterathans said:
However when I went to select the file (in my Downloads folder), the file selection box is empty (doesn't show any files). The original .zip file is in the same folder and doesn't show up either.
Am I missing something?
@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.
-
2
-
-
21 minutes ago, Chris Jahn said:
I also upgraded a Zen17 (1.04 -> 1.30) which worked except that the device did not send out a completion message so the status window just stayed up. I waited for quite awhile before I closed the window and started using the device.
If this happens when doing any OTA Firmware upgrade, I would recommend you wait at least 10 minutes after you see the last fragment being sent. Its probably overkill but it gives the device the time to apply the firmware and do a software reboot without being interrupted.
To get the new features from the device you can right+click Z-Wave | Synchronize | Update with Interview
If that doesn't work you may need to remove /add the device again.
Thanks Chris, this has been quite a learning experience, but that's a good thing. 👍
-
1
-
-
1 hour ago, Chris Jahn said:
Its saying "Reading firmware file" .. did it send any of the fragments?
@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
-
1 hour ago, Chris Jahn said:
There is one clarification to that. Some people have reported that they have devices that support OTA but it still doesn't show. We haven't tested it here, but if you right+click Z-Wave | Synchronize | Update (Not Update with Interview) then it will recreate the ISY nodes and then you should be able to see OTA if the device supports it (again, only for the root node e.g. address of form "ZY005_1")
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!
-
23 hours ago, mmb said:
Lastly does anyone know where the Z-Wave OTA update utility is located?
I must be blind 😬
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.
-
1 hour ago, Geddy said:
This is normal and not a concern. ISY Finder is listing both the local IP address and local domain address when auto discovered.
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?
-
4 hours ago, Bumbershoot said:
Right click on one of your Z-Wave devices, then you'll see the Z-Wave | OTA Firmware Upgrade menu items.
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.
-
2 minutes ago, Techman said:
@mmb
You need to clear your java cache and then download the IoX Launcher, that will correct the "not found" issue. Apparently, the launcher has been updated You may have used an older version.
https://isy.universal-devices.com/start.jnlp
@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 😬
-
48 minutes ago, Tom Carmody said:
Should I be more patient? How long should it take for a ZSE29 to be included and written into Admin Console?
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.
-
-
1 hour ago, dpierre said:
Does anybody know or heard of, if there is an integration for Wyze Cameras within UD mobile? Thanks
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.
-
On 8/2/2023 at 3:35 PM, mmb said:
I’ll submit a ticket for PG2 leftover in the launcher.
Thanks.
@Geddy fyi Michel says the leftover "PG2 Deprecated" will be removed in the future.
-
2
-
-
59 minutes ago, MrBill said:
it sounds like you have not rebooted.
@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 timesPG3x/MQTT is running fine now.
I’ll submit a ticket for PG2 leftover in the launcher.
Thanks.
-
1 hour ago, Geddy said:
Yes @Geddy deleted old link icon, cleared cache and downloaded a new start link.
But still have the old launcher with PG2 Dep.
-
1 hour ago, Geddy said:
@mmb Great! Glad it's working. Make sure you reinstall all node servers!
While I kind of miss the beeps of the Polisy...
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?
-
8 minutes ago, Geddy said:
Marched right into PG3x!
That seems more like a power cycle will fix it or a forced web refresh.
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.
-
1
-
-
28 minutes ago, Athlon said:
Just go past that - it's safe to do so. (The message is normal and just a warning - not a fatal stop.)
@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.
-
55 minutes ago, Geddy said:
If you're on 3.1.21 are you on Polisy and still on PG3 (not PG3x)?
Based on current release area 3.1.21 was the last mentioned release for Polisy PG3 - https://forum.universal-devices.com/topic/41246-pg3-version-3121-polisy-may-22nd-2023/
To get beyond that you would need to update to PG3x (please note that doing so will remove PG2 from the Polisy.
To move to PG3x on the Polisy the process is in the wiki - Polisy User Guide.
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.
-
That works quite well, thanks!
I have My Lighting setup with estimated and turned it off for the other scenes. So it flags me if I left something on at the end of the day.
@Javi I imagine you thought of this but have you considered a Select All / Deselect All calculator button at the top of each scene? One of my scenes has a lot of devices so a deselect and confirm takes a bit of clicking.
Anyway nice feature.
Support Thread for IoX 5.7.0
in IoX Support
Posted
@Chris Jahn that would be helpful, thanks!