Michel Kohanim

@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

@MWareman, we had it inline before and that caused issues. So, it's back to being queued. We'll take another look once we have a little more time. All, there was a big bug with migration which wiped out portal connectivity. You can easily fix this issue by: 1. sudo rm /var/isy/FILES/CONF/PORTALS.PSF 2. suso service isy restart @sjenkins, something is very wrong! Are you certain you are using a good backup from before the PLM failure? With kind regards, Michel

@Goose66, there's no such a thing as Native SmartHome Status Announcements. This is from Benoit: This is basically a proactive notification which allows to say: Your <instance friendly name> is <state> Example: Your vacuum bin is full There's only 5 states possible: Alexa.States.Low Alexa.States.Empty Alexa.States.Full Alexa.States.Done Alexa.States.Stuck This is still far from personalized announcements. I saw another interface that is similar, but targeted to cooking states. They can say: Your <appliance friendlyName> has preheated. Your food in the <appliance friendlyName> has reached target temperature. Your food in the <appliance friendlyName> is ready. Your <appliance friendlyName> is ready to use.\ With kind regards, Michel

@dwengrovitz, The first error is: Failed resetting the PLM. This means that either polisy cannot communicate with the PLM or the PLM is unplugged or, worst case, dead. With kind regards, Michel

@SESamuels, If you need the folder condition to be updated based on the variable, you need to use a state variable. And, you need to make sure you have another program (or manually) changing the variable otherwise, once disabled, the programs will no longer run (the folder is false now). With kind regards, Michel

@mapeter, Unfortunately not. With kind regards, Michel

@theitprofessor, I am certain @InsteonNut will get back you and get everything resolved. I just want to point out two things: 1. Yes, switch between ISY Portal and ML Connect is self service and, as @MrBill noted, it's described here : https://wiki.universal-devices.com/index.php?title=Main_Page#Switch_from_MobiLinc_to_ISY_Portal 2. Since you already have the network module, the switch will not impact it. i.e. when you go back to ML Connect, the Network Module will still be there. With kind regards, Michel

All, it should be fixed. Please click the button on the front once. Clear cache, use the Launcher. Z-Wave migration will not happen soon as we have to do S2 and Certification. With kind regards, Michel

Might be a bug. Will review next year. With kind regards, Michel

@tazman, Java cache works in mysterious ways. If you ever used the direct link before, the jar file is cached and start.jnlp will use the cache. That's why I mentioned that you need to clear Java cache if you have use anything but the Launcher before. With kind regards, Michel

@dwengrovitz, You need to clear the cache. With kind regards, Michel

@tazman, You must use the ISY Launcher. If not, you need to clear cache and then use either: https://<your polisy ip>:8443/admin.jnlp or https://isy.universal-devices.com/polisy/5.3.0/admin.jnlp With kind regards, Michel

At the moment, and from functionality perspective, not much till your PLM dies. And, since I know you don't care about non-functional things such as security, I will not list them. With kind regards, Michel

@Bumbershoot, It moves /FILES/CONF directory and backs it up somewhere. So, you will lose everything. That's why it's best to backup before you restore a 994 backup. With kind regards, Michel

Z-Wave status update is fixed in 5.3.0: With kind regards, Michel

Yes! With kind regards, Michel