Michel Kohanim

@simplextech, Sounds quite interesting. Quick questions: is this a hardware solution or software? Where does it run? What does it offer that Locative doesn't? With kind regards, Michel

@Jamison_IO, Mist of the recent errors are DNS related. Cannot troubleshoot logs from 7 months ago. With kind regards, Michel

Thank you. But, that's incorrect. In my.isy.io, click on Select Tools | ISY Information and then copy/paste the URL for your ISY (not the Admin Console). With kind regards, Michel

@Javi, What URL are you using? With kind regards, Michel

@kclenden, THANK YOU. Very helpful. #659. With kind regards, Michel

@dbuss, I greatly appreciate your appreciation @bmercier(Benoit) fixed the issue in the ISY Portal. So, please give it a try. It'll be included in the next build for the local version of UDAjax. With kind regards, Michel

@buzzhazzard, My pleasure. No, I don't think this has anything to do with power supply. Either someone tried factory reset OR the SD Card is also getting corrupt. I strongly suggest doing a backup immediately and have an SD Card on hand. With kind regards, Michel

@dbuss, Thanks to help from @simplextech, we found a workaround till we find a permanent fix for this issue. The issue is that the thermostat is reporting nonsensical unit of measure and UDAjax (and Alexa) throw an error while the Admin Console simply uses the UOM from ISY and sends it through the REST interface. So, it should be fixed in the next release. With kind regards, Michel

@buzzhazzard, Yes, that's correct. Anything between 5 to 30 volts center positive with minimum 500mA should work. With kind regards, Michel

@BigMojo, Thank you for the accolades! @kclenden, thanks SO very much for trying to reproduce. I appreciate it very much. We have not been able to reproduce. Are you certain that you saved the programs before export? With kind regards, Michel

@Javi, Unfortunately not yet but definitely something important on our requirements list. With kind regards, Michel

@dbuss, The issue with this thermostat is that it does not report the unit of measure properly. Can you please try going back to Celsius and then to Fahrenheit? With kind regards, Michel

@BigMojo Why are you restoring from the clipboard? You should restore from the export file. With kind regards, Michel

@Pascal, It should bring in all the sites you have as nodes. If you don't get them, please try the site_id parameter. If not please submit a ticket with your Polyglot Cloud logs for this node. With kind regards, Michel

Hi @dasFuuf, Please follow the instructions here. With kind regards, Michel

@Robert Messenger, The only explanation is that ISY is still using the address for the last PLM. Are you sure you rebooted ISY with the new PLM and then did File | Restore Modem? With kind regards, Michel

@MWareman, @bmercier mentioned that he would enhance our GH implementation to support this. With kind regards, Michel

@kartman_canada, Alexa groups are not identical to ISY groups/scenes. So, you are not going to see valid devices in the ISY scenes in the Alexa app. With kind regards, Michel

@jkraus, Yes, it'll take the values from the top level scene and copies them into each and every member of that controller. With kind regards, Michel

@dogla, Do you have any programs? If not, these are all coming from another device. Unfortunately it's very difficult to figure out where they are coming from. With kind regards, Michel

@ZManInNY, Please submit a ticket. With kind regards, Michel

@vdenis3399, What's your Admin Console version? With kind regards, Michel

@blueman2, Something is wrong with that dongle. Please send your invoice to sales@universal-devices.com and request for a replacement. With kind regards, Michel

@canuckcam, 1. Click on the red x next to the username 2. Delete and add the user 3. Delete from one add to the other 4. Revoke in the Admin Console, delete from one account, add to the other, Approve in the Admin Console. Alternatively, ISY can be in multiple sub accounts Unfortunately not for general questions. With kind regards, Michel

@david-4, The reason for sensors is that Alexa routines can get triggered based on them. Have you reviewed all the supported commands? With kind regards, Michel