fasttimes Posted May 30, 2019 Posted May 30, 2019 I’d like to expose devices defined on the ISY Portal to my instance of Home Assistant. Would this be difficult to implement? Quote
rccoleman Posted May 30, 2019 Posted May 30, 2019 (edited) Like what? Home/Away presence? Polyglot cloud? You can use webhooks or the "custom devices" described here to get data from the ISY into Home Assistant or trigger automations. For Alexa, I created programs that run and make REST calls to webhooks in Home Assistant. If you're looking for something new to be exposed, maybe post here or get in touch with OverloadUT here or over there. If you're bought into the Home Assistant ecosystem, Nabu Casa offers much of the same functionality + supports the HA project monetarily. I've moved everything over and have no complaints. Edited May 30, 2019 by rccoleman Quote
Michel Kohanim Posted May 31, 2019 Posted May 31, 2019 @fasttimes, Everything that is available from ISY directly is available through the portal (i.e. portal acts as a proxy to ISY). The only change is the base URL and the credentials. So, what you need is to go to Select Tools menu | ISY Information and then use that given URL as the base and use your ISY Portal credentials. With kind regards, Michel Quote
fasttimes Posted June 2, 2019 Author Posted June 2, 2019 I’m not sure you understand me, or I understand you. What I’d like to do is be able to link Home Assistant to the ISY Portal, not the ISY directly so anything exposed by the portal can be sucked into HA. For some reason controlling devices from HA to the ISY directly is really slow. Google/Alexa is fast. Quote
rccoleman Posted June 2, 2019 Posted June 2, 2019 (edited) 34 minutes ago, fasttimes said: I’m not sure you understand me, or I understand you. What I’d like to do is be able to link Home Assistant to the ISY Portal, not the ISY directly so anything exposed by the portal can be sucked into HA. For some reason controlling devices from HA to the ISY directly is really slow. Google/Alexa is fast. You can't. It only connects to the ISY, so you need to use the ISY as a relay to get events from the ISY Portal into Home Assistant. The only way that you can eliminate the ISY from the communication path between Alexa/GH and Home Assistant is by using Nabu Casa, the cloud service for Home Assistant, instead of the ISY portal. If I understand correctly, you're using voice commands via Alexa/GH to control ISY devices/programs/variables/etc exposed via the ISY Portal, and you want those changes to be reflected in Home Assistant? I found that device state changes like on/off were reflected very quickly in Home Assistant via the isy994 component. Instantly, really. And then you can trigger automations from those state changes in Home Assistant if you like. If you're using Alexa/GH to control an ISY program, you can use a REST command in an ISY network resource to a Home Assistant webhook to get that info into HA. Again, I've found that to be very fast. I recommend turning on debug in the isy994 component in Home Assistant to see what might be slowing it down. You can do that by adding this to configuration.yaml: logger: default: info logs: homeassistant.components.isy994: debug The only issue that I've seen with ISY<->Home Assistant communications is that REST calls into the ISY to control scenes and devices often fail with 404 when many are sent quickly, and that results in delayed or completely missed commands to the ISY. I have an outstanding pull request to PyISY that adds retries to work around that and it's eliminated the uncertainty out of HA->ISY communication. I think it'll only be a problem when controlling Insteon devices because apparently it's an indication that the ISY thinks that the Insteon network is overloaded. Edited June 2, 2019 by rccoleman Quote
fasttimes Posted June 2, 2019 Author Posted June 2, 2019 You hit the nail on the head. The ISY component is super slow. I’ll see what the debug logs say. I know I always get those “took over 10 seconds to load ISY” Quote
rccoleman Posted June 2, 2019 Posted June 2, 2019 Just now, fasttimes said: You hit the nail on the head. The ISY component is super slow. I’ll see what the debug logs say. I know I always get those “took over 10 seconds to load ISY” That's not a big deal - lots of components say that and it really doesn't matter once everything is up and running. I've spent a lot of time poking around in the isy994 component and there's really not a lot of fat there. If it comes from the ISY quickly, you'll get it quickly in Home Assistant. One of the things that has pushed me away from the ISY were weird, unexplained delays in processing device state changes, but that was mostly with local devices and I doubt that it's affecting your use case. You can monitor the ISY side by opening the event viewer, setting it to level 3, and correlating the event viewer content with the error log, which will show the subscription updates to Home Assistant. Quote
fasttimes Posted June 2, 2019 Author Posted June 2, 2019 I’ve a feeling my PLM has gone tango uniform. It’s just so slow, even in the ISY admin. I should have never done that PLM restore yesterday. Nothing works now. Quote
larryllix Posted June 2, 2019 Posted June 2, 2019 5 hours ago, fasttimes said: I’ve a feeling my PLM has gone tango uniform. It’s just so slow, even in the ISY admin. I should have never done that PLM restore yesterday. Nothing works now. You likely have battery Insteon devices waiting to be put into linking mode so that ISY can finish writing updates to them. That can bog ISY down attempting to write updates every time that device has any action. A factory reset of ISY with a follow up Restore may clear things out also. Quote
fasttimes Posted June 4, 2019 Author Posted June 4, 2019 On 6/2/2019 at 6:38 AM, larryllix said: You likely have battery Insteon devices waiting to be put into linking mode so that ISY can finish writing updates to them. That can bog ISY down attempting to write updates every time that device has any action. A factory reset of ISY with a follow up Restore may clear things out also. Is there a way to tell or sure without guessing? Quote
fasttimes Posted June 4, 2019 Author Posted June 4, 2019 On 5/31/2019 at 11:54 AM, Michel Kohanim said: @fasttimes, Everything that is available from ISY directly is available through the portal (i.e. portal acts as a proxy to ISY). The only change is the base URL and the credentials. So, what you need is to go to Select Tools menu | ISY Information and then use that given URL as the base and use your ISY Portal credentials. With kind regards, Michel @Michel Kohanim, if you’re talking about the ISY Component, that is what is painfully slow. I’m not the only person with this issue. In fact it seems to be the norm rather than the exception. Quote
larryllix Posted June 5, 2019 Posted June 5, 2019 1 hour ago, fasttimes said: Is there a way to tell or sure without guessing? Yes! There will be coloured oval cornered rectangles beside each device containing a "1011" code to indicate trying to write binary to the device(s). Quote
Michel Kohanim Posted June 5, 2019 Posted June 5, 2019 @fasttimes, I do not know what ISY Component is. You asked whether or not you can expose ISY Portal to Home Assistant and the answer is an absolute and unqualified yes. i.e. if HASS already talks to ISY directly, it should be able to talk to ISY through the portal with minor modifications of the base url and credentials. With kind regards, Michel Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.