mmb

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.

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.

@Sirmeili I use Fast Off on an Insteon switch to initiate a REST command to my alarm system to arm/disarm. In my case the Rest almost instant. Fyi I did have a problem with my Polisy and Rest after migration from the ISY. The Rest wasn't working at all, but was able to track it down to timeout. Increasing the timeout on the command fixed it. The Event Viewer on level 3 helped sort out the problem.

Hi @Javi question Scene status indicators. I've noticed that when turning on (off) a scene that includes devices from other scenes that those scenes also indicate they are on (off) as well. I noticed this behavior when my Morning Scene program runs it was also indicating on/off status changes for the Evening and Main Floor Lights Scene - they share one device between them. Is this expected behaviour? Thanks, loving the UD Mobile! - - - Morning Scene Off - - - Morning Scene On

Chris Jahn kindly provided the following: Z-Wave Device Initial Naming and Icons Z-Wave functionality is broken up into command classes, and from there we have a fixed setting for which node a status value or command will appear. For example, there are several multisensor types such as air conditioning, air quality, health, movement, weather, etc. all of which can be supported in one device. The weather node, for example, would have temperature, rain rate, barometric pressure, etc. Ignore the light bulb icon. The light bulb is the default icon if there is not specific icon defined for a particular node type. Did Aeotec name their Parameter Setting function Heat Alarm or is this a misassociation in IOX? Of course I can rename to something more appropriate. Battery level and configuration parameters always go to the primary node of the device (i.e. ZY056_1) rather than their own nodes. This is done to reduce the total number of nodes for a device, which can be substantial anyway depending on the device.

Thanks, I installed a new MQTT node figuring I'd just have to live with two nodes with no info. Long story short - I did one last restore form PG2 to PG3 and deleted them again in the AC. That actually got rid of one of them - so I was left with a valid MQTT server and a MQTT no info in the dashboard. I checked Polyglot/PG3/NS and could only see one MQTT registered, so I figured maybe a caching problem. So I rebooted Polisy from the command line and that fixed the problem. All good...

Hi @bpwwer , I have the same issue and followed your instruction. They are removed from the Polisy AC but still persist as unmanaged in PG3 as unmanaged. I did restart PG3 but they remain. These were migrated from my ISY but don't need them anymore. I'm comfortable doing some SSH to investigate. Thanks!

Just curious how the device names and icons are determined in IOX. I installed an Aeotec temperature and humidity sensor and as expected I ended up with 13 devices. One of the devices is called Multisensor and it gives me the temperature and dew point. The icon is a temperature bar graph. Humidity is listed under another device called Weather Sensor with a light bulb icon. The Aeotec device parameters are listed under Heat Alarm with a bell icon. And on and on for 10 more. I know you can rename the devices to something more appropriate. Is there a way to change the icons? Which brings me to my question how the initial names and icons are determined in IOX? Also please excuse any misuse of terminology, new to the world of z-wave. Anybody know? Thanks...

@tlightne but I remember you had to mail the Polisy back which would cost about $50 to $75 from Canada. I'll just use it for Home Assistant when support is done. 🙂