Support Thread for IoX 5.6.4

[Chris Jahn]

This is the support thread for IoX 5.6.4:

 

 

>>Could you expand on the OTA support in 5.6.4. i.e., what works and what doesn't.  How does one use OTA, I couldn't find the option in any of the tabs.

The process begins with making sure you have the correct firmware file, starting OTA firmware upgrade in the Admin Console, uploading the firmware file to IoX which then uploads it to the device itself.  Once complete, the device applies the firmware file, or returns an error if it detected something went wrong. 

The process of uploading the firmware to the Z-Wave device takes roughly 20 minutes and depends entirely on communications and the size of the firmware file.  The file is broken down into small fragments and each fragment is sent individually in a Z-Wave message.

For example, the ZW4009 Enbrighten Smart Switch takes about 20 minutes and requires sending about 4500 fragments to the device

The first thing to do is get the firmware file from the manufacturer and make sure you are getting it for the correct device/model and version.  This will be a .otz, .gbl, .bin, or other type of file.  For now we are not allowing binary files like .gbl because we have bricked at least one device (a Zooz 5 button keypad) when using it.

To start OTA Firmware upgrade, right+click on the primary node of the device and select Z-Wave.  You will see "OTA Firmware Upgrade" in the menu if the device supports it.

 

[BigMojo]

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 !!!

[Techman]

Apparently the Aeotec Zwave devices are currently not supported by the OTA updates as the option menu is not there. Aeotec uses the RAR compression format for their firmware update files. Is there a timeframe when they will supported?  

I noticed a new option, power management, is that only for ADR?

For those doing a firmware update, it's probably best to have your device on USB power rather than batteries, in order to prevent a timeout.

Edited August 12, 2023 by Techman

[Chris Jahn]

1 hour ago, Techman said:

Apparently the Aeotec Zwave devices are currently not supported by the OTA updates as the option menu is not there. Aeotec uses the RAR compression format for their firmware update files. Is there a timeframe when they will supported?  

Hopefully in the next build or two. 

 

1 hour ago, Techman said:

I noticed a new option, power management, is that only for ADR?

Yes, this is just for ADR.  Most of the dashboard functionality was brought into the Admin Console in this build.

[hart2hart]

Installed and running. Thanks!

[landolfi]

1 hour ago, Techman said:

Apparently the Aeotec Zwave devices are currently not supported by the OTA updates as the option menu is not there.

Does Zwave X-Ray give a way to determine the device firmware version? I've looked for it on my Aeotec Multisensor 6 but can't find it so far. Aeotec says some versions of the Multisensor 6 firmware shouldn't be updated to the latest.

[Techman]

@landolfi

For the Multisensor 6, Aeotec states: Do not update V1.08 (or previous versions) to V1.09 or later, this will brick older MultiSensor 6 units.

Currently, Aeotec states that you have to use the Zensys tool and Zstick to verify firmware version. This requires unlinking the device from the ISY and linking it to the Zstick. Not the most desirable option.

It's possible that the Xray tool can show the firmware version under Command Class but I'm not sure where you would find it

[Geddy]

Updated and installed almost okay. Had to perform a full power cycle to get the Z-wave portion to become responsive again. 

There was not an alert to reboot, but eisy did seem to reboot in the process based on notifications to UD Mobile. However, z-wave was "unresponsive". Used the "reboot" button to try again, and same alerts came through UD Mobile. But not until a full 6 button press and power cycle did the z-wave work. 

 

[Techman]

@Geddy

The first time I clicked on Upgrade I didn't get a reboot notice, I clicked on Upgrade a second time and the reboot window popped up after a short while. All my Zwave devices are working normally after the 2nd upgrade. 

[giomania]

I am still stuck on 5.6.2 and unable to upgrade. Were we expecting this release to fix this type of issue?

[RRalston]

For ZooZ devices, I have found the Firmware version information using X-Ray and the "DH Device" query. it is listed like this:

Integer  DATA devices.8.data.applicationMajor = 1 (0x00000001)

Integer  DATA devices.8.data.applicationMinor = 30 (0x0000001e)

 

 

I have checked 5 devices and this info is consistent with the version info provided on the device when received.

 

 

[gviliunas]

Upgraded from 5.6.3 to 5.6.4 without any problems or abnormal behavior. Thank you to the UDI team!!

[DennisC]

@Javi

Upgrade to v5.6.4 0n Polisy appears to have broken my ability to view cameras that were previously added to UD Mobile v1.1.23. I was able to connect to the same cameras this morning running v5.6.3.

I checked the Play Store, but there doesn't appear to be any updates available.

When attempting to view a camera, the display continually cycles through: Loading, Buffering, Stopped, and then the display freezes and you can not back out of the page. Sometimes, the app then crashes, sometimes it continues and repeats the same cycle.

I can still view cameras on an eisy running v5.6.3.

[Javi]

50 minutes ago, DennisC said:

@Javi

Upgrade to v5.6.4 0n Polisy appears to have broken my ability to view cameras that were previously added to UD Mobile v1.1.23. I was able to connect to the same cameras this morning running v5.6.3.

I checked the Play Store, but there doesn't appear to be any updates available.

When attempting to view a camera, the display continually cycles through: Loading, Buffering, Stopped, and then the display freezes and you can not back out of the page. Sometimes, the app then crashes, sometimes it continues and repeats the same cycle.

I can still view cameras on an eisy running v5.6.3.

Cameras are independent of UD equipment, there is no connection whatsoever.  So there must be something else causing the crash. 

What is the brand and model of the Android device?

[DennisC]

12 minutes ago, Javi said:

Cameras are independent of UD equipment, there is no connection whatsoever.  So there must be something else causing the crash. 

What is the brand and model of the Android device?

Samsung Galaxy S20+

Since it worked just before I upgraded and it's still working on my other system running v5.6.3, I thought they were connected.

[Javi]

20 minutes ago, DennisC said:

Samsung Galaxy S20+

Since it worked just before I upgraded and it's still working on my other system running v5.6.3, I thought they were connected.

Cameras are still beta and there will be issues, but it should not cause crash, failure to load may be expected. Please first reboot your Android device and UD equipment which may be having issues before trying anything else.

I don't see anything in crash reports which sticks out but I'm still a little confused. Cameras are independent of UD Equipment so I'm not sure what you mean by it is still working on your other system.  The following questions will help me narrow the issue to UD Equipment, Camera Equipment and/or UDM/

Do you mean cameras are working at one location and not the other?   

Is it Favorites Tab which is crashing?  If so does the same happen on the Home Tab when trying to view UD equipment or Cameras?   

Can you try disabling the system which was upgraded in UDM (Settings Tab > Systems > System Name > System Status).  Does the issue persist if the system is disabled? 

[DennisC]

11 minutes ago, Javi said:

Cameras are still beta and there will be issues, but it should not cause crash, failure to load may be expected. 

I understand this.

13 minutes ago, Javi said:

Do you mean cameras are working at one location and not the other?  

Correct, the system that was updated to v5.6.4 stopped working. The system at another location running v5.6.3 still works.

15 minutes ago, Javi said:

Is it Favorites Tab which is crashing?  If so does the same happen on the Home Tab when trying to view UD equipment or Cameras?   

Favorites and Home respond the same way, neither will display the camera feeds.

17 minutes ago, Javi said:

Can you try disabling the system which was upgraded in UDM (Settings Tab > Systems > System Name > System Status).  Does the issue persist if the system is disabled? 

Yes

20 minutes ago, Javi said:

 Please first reboot your Android device and UD equipment which may be having issues before trying anything else. 

Done prior to posting my problem here.

 

If you feel this issue has nothing to do with the upgrade, I will look in to other causes 

[TheA2Z]

Went from 5.6.3 to 5.6.4.  Everything seems to be working fine. 

Note: I, like @Geddy always after upgrading, power down (6 clicks of power button), then unplug the eisy for about 30s, then plug back in.  Had a problem in past where that fixed a problem, so now I just do it.

Thanks UD devices team for your dedication to making the product better everyday.

 

[Javi]

17 hours ago, DennisC said:

If you feel this issue has nothing to do with the upgrade, I will look in to other causes 

Yes. The UDM cameras integration has no relation to UD Equipment. The only connection is from UDM app to the Camera.

I replicated the failure to restart feeds on Android, but not the crash.   If possible send me a copy of the backup file and let me know which camera system is having issues and I can take a look.

[Athlon]

Updated to 5.64 without any issues.

It will be nice to be able to update my z-wave stuff without having to remove my Zooz S2 Stick 700 from my Polisy and put it into my Rpi HA setup. (It uses a .gpl file.)

[landolfi]

Updated successfully to 5.6.4 from 5.6.2. The only issue was that after the 5 (not 4) beeps, I had to disconnect power to get AC to recognize 5.6.4, IoX kept reporting 5.6.2 even after I cleared cache and re-downloaded IoX launcher. Upon startup, Zwave responded immediately after a brief refresh and AC immediately recognized and added on/off and color nodes for a Zigbee Sengled LED bulb.

Thanks to UD guys for all the hard work!

[DennisC]

5 hours ago, Javi said:

I replicated the failure to restart feeds on Android, but not the crash.   If possible send me a copy of the backup file and let me know which camera system is having issues and I can take a look.

I sent the requested backup file. However, I am starting to believe this has something to do with Android security certificate. If I lease the premises or turn WIFI off, the camera image appears.

[Javi]

4 minutes ago, DennisC said:

I sent the requested backup file. However, I am starting to believe this has something to do with Android security certificate. If I lease the premises or turn WIFI off, the camera image appears.

Could be the router does not support NAT Loopback.

[DennisC]

16 minutes ago, Javi said:

Could be the router does not support NAT Loopback.

Not sure about that, it has been working all week until late yesterday morning.

[EJones01]

The update was fine but.... I was hoping the Zigbee Tuya Human Presence sensor that connected as an on/Off device would become more useful. Instead it finds it but then says unavailable now?