+1 from me. Signing up for an Insteon Developer Account takes 2-4 weeks according to Insteon’s web site. And like @GraysonPeddie one reason that I switched to OpenHAB was that I wanted to reduce my dependence on “the cloud” for smart home solutions.
So I can use multiple backends and write a custom component that is based on the light?
I would suppose I could get OpenHAB to turn my LG WebOS TV on by pressing a button in an Insteon KeyPadLinc. And because I use Home Assistant as my primary backend, I could have OpenHAB tell Home Assistant that the TV is on, so it updates the state. If I access the Home Assistant frontend to turn the TV off, Home Assistant can directly talk to the TV to turn off, tell OpenHAB that the TV is off, and then OpenHAB updates the state in a KeyPadLinc.
In my opinion, this whole integration of multiple backends opens up a can of worms. The system of communicating with each other from one backend to another is very complicated, which then comes to a question: why not create a software-based hub in Linux that can act as a central hub for multiple backends regardless of what programming languages each backend is written? I mean, one backend is written in Java, another backend is written in Python, another backend is written in Mono/C#, and so on and so forth. Each of the backend has it’s own REST API, so that the hub can communicate with multiple backends with a central API system.
Wouldn’t that be possible? We could choose which web interface we want to use, be it OpenHAB’s iPhone look-and-feel UI or the material design of Home Assistant.
But then I went completely off-topic in my own thread.
That’s correct. I have chosen to keep it to using OpenHab just for Insteon items to make it simple.
Its not as complicated as OpenHab telling HA anything. Since we are using REST HA just picks up all the info, so if you turn on your LG TV, all that needs to happen is OpenHab turns it on. The state change will be picked up by HA depending on how you write the component.
I’d be happy to get rid of four of my LIFX light bulbs (2 LIFX White 800 and 2 LIFX Color 1000) and go with a discontinued Insteon 2244-224 Starter Kit as I don’t see a need for color changing anymore. If you can get the PLM portion of the 2242 hub to talk to Home Assistant, I will be very happy to test them out, since I got my 4-pack CREE light bulbs that I want to test.
There is a 2244-372 version, but that includes a 2245-222 model. What are the limitations as far as local control through HTTP? It’s not like I can press a button in an Insteon KeyPadLinc, have it send over to Home Assistant, and then have Home Assistant execute a shell script or execute a scene or anything like that. Does it have WebSockets?
Oh, and now that I think about it, I came across this thread about local control in SmartThings forum.
Update: Still, I’m against Insteon Hub 2014 model as it requires a cloud account and I’m not that crazy when it comes to Internet of Threats (err, Things) as I would segregate them in my separate internal network where I won’t give IoT devices Internet access (yes, even Nest and Insteon 2245-222).
My question has already been posted in the Insteon Component thread, but I did not receive an answer about downloading the HA/OH component for controlling Insteon lights. I did not see a link to download in the thread.
I might be interested in porting the openHAB Insteon PLM interface code from Java to Python. However, it’s not a small task. There are over 3000 lines of Java code (and about 1500 lines of XML metadata) in the protocol implementation.
I’m new to Home Assistant and I have a few questions before I invest too much time. The developer documentation says “One Home Assistant rule is that platform logic should never interface directly with devices. Instead, use a third-party Python 3 library”. As far as I know, there is no official third-party library for the Insteon PLM. Does the rule apply in this case?
Steve, pretty sure there is no official library for Insteon PLM- the OpenHAB, and Insteon.py both seem to be the result of reverse engineering, good guesses, and luck, but they also seem to be what there is.
I’m regretting having spent so much money on Insteon, but I’m also wondering what would take you from maybe interested to “that was a lot of work, but well worth it”?
The only other choices that don’t involve ripping and replacing all my Insteon stuff involve spending more money (Insteon hub) or super complicated workarounds (running OpenHAB and having it talk to hass).
For what it’s worth, I’ve started working on this. I’ve got a preliminary python asyncio library going and stubs for a Local Push hass component. Code’s on https://github.com/nugget if anyone wants to assist.
I doubt I’ll have it in good enough shape for 0.38, but maybe within a month or so.