Michel Kohanim

All, Amongst other fixes, long awaited backup/restore is now ready! Happy New Year! With kind regards, Michel

OUTDATED - This version has been updated and is obsolete. Please see the current release found in the Current Release area of the forums. Fixes: - Fixed status reporting of Z-Wave devices (such as motion sensors, etc.) - Network Resources actions are queued when run from programs rather than run inline - Fixed NLS strings for formatted values in ISY events for all node servers - Fixed NLS strings for formatted values in ISY events for nodes using encoded editors - Fixed XML crash when doing variable substitution in Network Resources - IPv6 not allowing regular connection - Invalid UUID sent to the portal Enhancements: - Backup from 994 and Restore on Polisy! WARNING: - Everything is migrated except for Z-Wave - If you're also changing PLMs, please make sure you also Restore the PLM - Test binary network resources Bugs: - USB connected dongles (such as the PLM or Z-Wave Zooz Stick), cannot be unplugged and then plugged back in while ISY service is running. If, for any reason, you need to unplug, please use the Admin Console | Configuration tab | Reboot button to restart the service How To Install: - First, backup please! - If on 5.2.0, Admin Console | Help | Automatically Upgrade. Once the Admin Console closes, wait 30 seconds before trying again. If Polisy does not show up in the ISY Launcher, please wait 60 seconds and reboot - Click the button on the front only once - Otherwise, ssh and do: sudo pkg update && sudo pkg upgrade How to use Z-Wave: - Plugin your Zooz Stick in one of the USB ports on ISY - Go to Admin Console | Configuration, check Z-Wave Support checkbox. Save and then click on the Reboot button - From that point, Z-Wave works as it does on the ISY-994 with the following exceptions --- Backup/Restore of the Z-Wave dongle is not yet available --- Z-Wave | Z-Wave Version is likely to be blank - Note: for now, S2 is not yet supported With kind regards, Michel

@waffles, with Alexa, you need to rediscover everything. @asbril, migration does not care about online status. With kind regards, Michel

@waffles, Your hope is our command. @bmercier developed migration for all of those yesterday. Should be available later today. With kind regards, Michel

Unfortunately, that's the case and I went through it myself last night. With kind regards, Michel

@smileyw, You should be able to get to it via https://<ip>:8443/ ... With kind regards, Michel

@mmb, That is very slow. Please use the Event Viewer, on Level 3, and post the traffic. It might be that it's using a less optimal route. With kind regards, Michel

@mmb Did you manually add Polisy to ISY Launcher? With kind regards, Michel

@ase, First of all, I do value your input especially when clarifying how Polisy works. This said, I have a few comments some technical and some as a 15 year old veteran of this forum: Non technical first: 1. In this forum, most of us have strong opinions including me. As @Teken can tell you (the infamous antagonist), we always recover because, at the end of the day, we are here to share/have fun/learn and not destroy each other, increase our blood pressure, and get disgusted. 2. For me, everything starts/ends with liberty. It's up to the individual to heed any advice. Very Technical and Geeky parts that you will appreciate: 1. If you unplug the TPM board, Polisy will not boot. Also, the firmware is signed so, if you flash the ROM, and if the ROM has been locked, then you will brick Polisy 2. The latest version of firmware is UEFI based with TPM backed OS verification. This means that you cannot simply install another OS. It will not boot. This firmware is ready but we have not yet deployed it since the commissioning process is rather cumbersome (adds 3 minutes per unit) and the migration of the firmware to UEFI at runtime has not been thoroughly tested 3. You cannot add an SSD unless it's through USB. There's only one mSATA connection. The other two are mPCIe 4. Although VM may work now, sensitive information/configuration will be stored in ROM and encrypted by TPM. It might be a little difficult doing that with a VM without first creating abstractions for those. Hope we can get back to calm! With kind regards, Michel

@sjenkins, thank you SO very much. But, it's not fair. Would you please send your UUID to sales@universal-devices.com with a link to this post? With kind regards, Michel

@DennisC, Please send your uuid to sales@universal-devices.com and request for the extension. With kind regards, Michel

@sjenkins, That's precisely why we applied and currently under review. With kind regards, Michel

@matapan, In order to be part of Lutron partner network, we will have to manage everything in house. With kind regards, Michel

This is NOT true. WiFi is supported. @mmb, Please check /etc/wpa_supplicant.conf and make sure the password is saved properly. With kind regards, Michel

Precisely. We only write to the SD when we have to flush the log or save configuration, or save init values for variables. Regardless, it's always best to follow what's been tested and we know works. With kind regards, Michel

@MWareman, Unfortunately not. These were minor fixes: 1. Factory reset didn't reset the ISY's configuration 2. Reset credentials didn't reset ISY's credentials 3. UDX gave up as soon as it could not connect with MQ broke Migration took a little longer. But, we should be done this week. With kind regards, Michel

@ase, thank you very very much! @matapan, first if all, thank you very much for the compliments. There are products for which we have to manage their lifecycle for a variety of reasons such as certification (Z-Wave, Zigbee, OpenADR,..) and licensing. This said, and as @ase suggested, there is absolutely no way we can support 1000s of devices out there on our own and in house. So the question for you would be: what do you want to use and which controller gives you the reliability and extensibility? Once the equation is changed from what UD has to do, to what you need, then you will be free to make the best decision for you. With kind regards, Michel

@Wes Westhaver, The whole purpose of the procedure is to make sure bad sectors and files are not burned into the new SD Card. Not sure why following the manufacturer instructions should not be followed and, instead, use a method that may make things worse? With kind regards, Michel

@bpwwer, PG3 is still not being installed by default. With kind regards, Michel

@someguy, I responded to your ticket. I think your Polisy OS is too old and does not have the packaged kernel (i.e. you cannot upgrade the OS with the button on the front). So, if you do know how to use ssh, you need to do two things: curl -s https://pkg.isy.io/script/update121.sh | sudo bash sudo shutdown -r now Wait for the unit to reboot, then: cat /usr/local/etc/udx.d/static/update13.sh | sudo bash sudo shutdown -r now This should do it. With kind regards, Michel

@DennisC, We are contacting all the developers for all the node servers. In case we cannot get a hold of them, or if they give us permission, we'll take over. With kind regards, Michel

@kccustom, What's your preferred ISY (under My Profile)? With kind regards, Michel

@mbking, 1. Yes, backup/restore will also restore node servers 2. Yes, we should have a migration path from PG to PG3 With kind regards, Michel

@dinostop, it's cleaner if you restart till we finish the backup/restore (from ISY994). With kind regards, Michel

@someguy, Most probably you have VPN or Firewall software on your computer that's why Polisy is not found. Also, it's either http://192.168.1.105:8080/desc OR https://192.168.1.105:8443/desc You never told us how old is the unit. With kind regards, Michel