Michel Kohanim

@asbril, I don't think you're doing it correctly. Please see @mmb's image above, note the dropdown with Default. For each device in a scene, you will see at least Default and Command. Now, click on the switches within the scene, in the picture above ZW_024. You will see the same dropdown. Now, if the switch supports Z-Wave scenes, you will see Z-Wave Scene in the drop down (but this is rare). If the device supports it, you will also see Z-Wave Association (much more prevalent). In short, if and only if your device supports it, you should use either Z-Wave Scene or Z-Wave Association. If your device does not support it, you will not see those options. With regard to On but not Off, most probably the reason is that the switch is only sending On. You can check that on the Event Viewer by looking for DON (on) and DOF (off). With kind regards, Michel

Hi @brians, Regardless of what you do, once you restore your backup to Polisy, your Z-Wave devices are removed. So, what you want to do is this: 1. Backup 994 2. Print Tools | Topology 3. Restore backup on Polisy 4. Use the topology and Exclude then include your Z-Wave devices in that order. This way, whatever programs you already have will continue to work and whatever Alexa spokens you have will point to the same devices 5. Last step is migrating your ISY Portal accounts (do this last): https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY With kind regards, Michel

Hi @brians, Those URLs are 100% normal. There's no default page. With kind regards, Michel

@Techman, Do you have any other Z-Wave devices to test with and, more specifically, powered ones? With kind regards, Michel

@lilyoyo1, I feel you ... I was in Philly last weekend. Quite a freezing experience .... With kind regards, Michel

Thank you @io_guy, Is the error NOT-FOUND or Forbidden? With kind regards, Michel

@lilyoyo1, Thank you. There was a bug with udx ... please do the following: sudo pkg update && sudo pkg upgrade sudo service udx restart sudo service isy restart Reload your backup. With kind regards, Michel

There was definitely a bug with udx. Please: 1. sudo pkg upgrade udx 2. cat /usr/local/etc/udx.d/static/update13.sh | sudo bash With kind regards, Michel

It says "send to host is down" ... network connectivity? With kind regards, Michel

@io_guy, Good to hear from you! Polisy has identical APIs as 994. Anything that works on 994 should work on Polisy. The only thing that's different is case sensitivity ... in short, whatever you have in nodedefs are now case sensitive. With kind regards, Michel

@asbril, That means udx is not running: sudo service udx restart With kind regards, Michel

@lilyoyo1, What's the output of: uname -a pkg info udx pkg info isy With kind regards, Michel

@smileyw, There is not. You should just use ISY Launcher. With kind regards, Michel

Hello everyone, 1. The update availability has been removed from PG ... making it streamlined for the future UI 2. Haven't had time to work on the error log With kind regards, Michel

@Techman, unfortunately not. Our priority is to get S2 working. Once that's done, migration, certification, and then OTA. With kind regards, Michel

@dakall, Is the 4th one still in ISY | Node Servers? If so, Node Servers | Configure | <name> | Delete. With kind regards, Michel

@stevehoyt, did you adjust latitude and longitude? With kind regards, Michel

All, As mentioned, we just cannot support ELK as native; it breaks so very many things that we have cleaned up and streamlined. We'll work with the developer and provide as much help and support to move important features into the node server. With kind regards, Michel

@hart2hart, You must have gotten the latest UDX ... it means that it's updating the firmware. With kind regards, Michel

@xlurkr, Exporting ELK lighting is a UI thing which we can support. We cannot support ELK in the firmware when there's already a full featured node server for it. With kind regards, Michel

@Whitehambone, Yes, please and include your UUID. With kind regards, Michel

@MWareman and those with NR issues, just pushed a fix ... it seems that, for some, the queue is not picking up the elements and they just stay there not being processed. Please do either: 1. Click on the button on the front only once, OR 2. sudo pkg ugprade isy With kind regards, Michel

@sjenkins, Please submit a ticket. We could not reproduce. With kind regards, Michel

@larryllix, Will check the date. But, what's the purpose of the program stopping itself? Make no sense. @MWareman, When queued, the variables are substituted when sent which has always been a bug. We removed the queue but that caused other issues. With regard to the NR not being executed while it works using the Test button, can you do one more experimentation? Can you please change the NR such that it does not use substitution variables? In short, is this the case with all your NRs or just this one? With kind regards, Michel

@sjenkins, Looking into these issues. Please stay tuned. With kind regards, Michel