Michel Kohanim

@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

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