Chris Jahn

Yes, we are no longer backing up the node status history database (the database used by UD Mobile to show charts for the ongoing activity of your devices). This database can grow to a significant size so we're deciding on the best direction for pruning it and backing it up.

Not that I'm aware of. Yes, we've moved the bulk of the work from the Admin Console to the eisy and it sped things up quite a bit! I'll see why we are missing the completion notification.

Hello all, This release contains minor enhancements and bug fixes. Important Note: Please do not unplug your unit from power. Instructions: 1. Backup your unit. 2. Please click on the using the Upgrade Packages button in the Configuration section of the Admin Console. Fixes: - Insteon I3 Paddle and I3 Keypad buttons default links - Show Unix Time status values as Timestamps - Faster IoX Backup - Some characters not displayed correctly in Admin Console For Developers: - Allow node servers to define their own status names in nodedefs - Fill in device type field for Zigbee (so a UI can properly identify devices) - Query Zigbee devices after they are added - added <rpnode> to Zigbee nodes - added <NodePropertyHistory> to system options - Initial support for posting events to MQTT - Fix ISO8601 Timestamps for node property history and events

Hello all, This release contains minor enhancements and bug fixes. Important Note: Please do not unplug your unit from power. Instructions: 1. Backup your unit. 2. Please click on the using the Upgrade Packages button in the Configuration section of the Admin Console. Fixes: - Remove default time events from event viewer - Occasional issues when restarting IoX Features: - Better support for Philips Hue (including support for enhanced hue) - Support Zigbee Color XY / Temperature - Allow user to manually specify Zigbee radio channel (for Securifi devices)

The thing that may have actually fixed it was the first step of removing the existing /var/isy/FILES/CONF/ENABLED.D2D file (well, actually moving it so essentially deleting it), then restarting IoX, and then re-enabling the programs again.

The reboot won't create new nodes, but if the same node with same address was recreated with the same functionality being used in the programs then you should see them again in programs. (Which may not currently be the case because as you mentioned, the interviews probably didn't succeed).

The nodes were likely recreated so the best bet is to restart IoX and they should re-appear in the programs again. We have a feature request to fix this so that a restart is not required (wasn't possible due to memory constraints in Isy-994 but we should be able to do it in Polisy/Eisy)

Hi Rob, First off, I believe the device was successfully upgraded. One of the interesting things about OTA firmware upgrade is that it is primarily driven by the device being upgraded. Its something like this: 1) The ISY tells device X it wants to apply an OTA firmware upgrade, providing it with the number fragments in the upgrade (and a few other things) 2) Device X sends a message back to ISY agreeing with the upgrade 3) Device X sends a request to ISY for each fragment (possibly multiple times) and ISY sends the requested fragment to Device X 4) When Device X recognizes it has all the fragments, it assembles them into one file and applies it to itself 5) It sends out a success/fail status message to ISY (although some devices incorrectly skip this step) At this point though, the ISY still thinks Device X is at the old version because it hasn't been interviewed since the upgrade. Therefore, you have to either right+click | Z-Wave | Synchronize | Update with Interview (Making sure the device is awake and stays awake), or, remove the device and add it back again. We are going to help automate this in an upcoming build to avoid any confusion and to close the loop on the firmware upgrade.

The interview failed possibly because the device may have factory reset itself as part of the upgrade (and thus the empty DH X-Ray). Did you try removing and adding the device back? edit: One more possibility, was the device awake when you tried to interview it? From Zooz website (for OTA Firmware upgrades) You may need to exclude and re-include the device after the update is complete for best performance. Please consider you may need to rebuild all of your automations and settings for the device.

I'll add a prompt at the end indicating whats needed along with option of doing an interview right away.

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.

Hello, This was tested on the current I3 Keypad and I3 Paddle and all the flags ands LEDs should be working and visible as status (and thus usable in programs etc.). Have you tried querying the Keypad Flags node? Is it possible you have an earlier version of the I3 Keypad that doesn't have the most recent firmware?

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.