Michel Kohanim

@apostolakisl, Thanks so very much for the update. We have submitted a ticket to Google. Haven't heard back. With kind regards, Michel

@apostolakisl, Do you get Permission Denied errors? We have already opened a support ticket with Google. Something quite screwy is going on there. With kind regards, Michel

@hbskisurf, Please submit a ticket and include your error log. With kind regards, Michel

@KSchex, Thank you. Is it correct to say that the issue is communications related? If so, perhaps adding a range extender is a good idea followed by a heal (especially since the issue seems to revolve around battery operated devices). @rccoleman, unlike INSTEON, Z-Wave commands are short but numerous. So, there will be cases when the queue is large enough so that ISY will have to throttle everything. It's 100% normal as long as the commands in the queue are eventually processed. With kind regards, Michel

Hi Sakiman, What do you get if you use a regular browser and go to https://97.102.166.197? With kind regards, Michel

@carealtor, If Control 'button x' is switched on Then Run whatever program With kind regards, Michel

@hbskisurf, Are you sure you don't have MobiLinc Connect Module (Help | About)? With kind regards, Michel

@buzzhazzard, Please submit a ticket with your UUID. With kind regards, Michel

@KSchex, Please be more specific on the "hung". Error log would be great. With kind regards, Michel

@simplextech, Thank you for asking. We currently don't have any requirements except for energy saving/management/charging vs. discharging. A few folks started working on Tesla Cockpit integration but I am not sure where that is at the moment either. With kind regards, Michel

@buzzhazzard, In 99.9% of the cases, this error indicates that the Google account you are using (linked to ISY) does not have permission to access the Google Home device. The first thing you should do is to use this Google account and see whether or not you can control your Google Home device through the Google Home app. With kind regards, Michel

@bdw72, This is mostly firewall related. With kind regards, Michel

@simplextech, Thanks so very much for the explanation. Two questions: 1. By hardware, what do you mean? Where does the hardware go? How much is it? 2. Do you have anything for Tesla? Such as state of charge, when to charge, nearest charging station, etc.? With kind regards, Michel

@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