Michel Kohanim

@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

Hi dinostop, 1. All you have to do is to go to Polyglot Settings and change: ISY Host to localhost ISY Port to 8080 Make sure https is unchecked Enter the username/password for the ISY running on your Polisy There's a bug in factory reset where it does not factory reset ISY (but it does everything else). To factory reset ISY, currently, the only way is to ssh and then: sudo rm -rf /var/isy/FILES/CONF With kind regards, Michel

Hello everyone, We are almost done with our migration utility from ISY994 5x backup to Polisy (not 4x). So, if you don't want to start from scratch, please give us a few more days. With kind regards, Michel

@JDeGeorge, We do not use log4j anywhere: not on ISY and neither on Polisy. With kind regards, Michel

@marc0612, You blacked out the most interesting digits! Please send your UUID to support@Universal-devices.com. With kind regards, Michel

@someguy, Most recent versions of Polisy come with isy service already installed. So, the question is how old is your unit. If you have doubts, click the button behind the little hole on the front only once. This will download and upgrade your Polisy (if not very old). Once you hear the beeps, then isy on polisy can be accessed through the ISY Launcher. To have isy support INSTOEN and/or Z-Wave, please go to the Admin Console | Configuration and check INSTEON/Z-Wave support checkboxes and then click on the reboot button. We are almost done with migration tool from ISY994 5x backup to Polisy. So, if you don't want to start from scratch, please wait till the end of this coming week. With kind regards, Michel

@MWareman, Thank you very much for reporting. We'll take a look asap. With kind regards, Michel

@Techman, Yes, eventually. With kind regards, Michel

Hi All, AWS is down: https://status.aws.amazon.com/ With kind regards, Michel

Thank you very much for all the feedback. I think the issue stems from the fact that isy depends on udx service. It waits for about 20 seconds for udx to respond. I think, in some cases, udx might be too busy (especially after an upgrade). When isy cannot talk to udx, it will not know its UUID, nor does it know the date and available serial ports. If you look at /var/isy/FILES/LOG/debug.log, I am sure you see something like: couldn't communicate with udx ... With kind regards, Michel

Or not ?! With kind regards, Michel