I’m finding the Insteon integration painfully slow. I used the UI version (not custom-component) on the latest version of HASS and while it found all my devices (yay!) controlling those devices is pretty much unusable.
Coming from my old Home Automation, the Insteon time was nearly instant, but under this integration it can take 1-5 seconds to turn on a device and about 50% of the time it doesn’t work at all, the switch in HA just returns back to where it was (i.e., I turn it on, nothing happens and the toggle goes back off).
My CPU and memory usage is nearly zero, so my Py is not overloaded, so I’m wondering if there is anything I can do to speed things up. This represents about 50% of my devices (the other being Z-Wave) so having this kind of performance makes HASS almost completely unusable for me.
Depending of how many devices you have the first discovery can last a lot. You can expect 1 minute per device.
When this is happening the devices will act like you described before, unresponsive, laggy. You have to wait. In my installation the entire process last 2 hours with more than 50 devices.
If you’re getting issues after this time try to factory reset your Insteon Modem and your devices, I found issues when a device has broken links from a older setup, this will populate your com spectrum with trash.
It does seem to have settled a bit, only a couple of devices now are doing that regularly. Hopefully a factory reset of the modem won’t be needed, that’s such a painful process to re-sync everything. I’ve had to do it a couple times over the years and hate it.
Thanks @Alfonsolsl, Just completed the insteon sensor integration.
Say, you know if the insteon wireless thermostat (2441ZTH) is working with the module?
can get this thermostat working…
After I left Indigo for HA and implemented this solution for Insteon, I noticed that too until everything settled down. At the same time I had a switchlink fail that was causing a lot of bad traffic on the power line. That took while to sort out, but finally found it and replaced it. Today, many months later I find that Insteon response is no different than it was in Indigo. I have stopped buying Insteon though, I’m slowly replacing it with WiFi Tasmota device as there is MUCH more capability, they’re faster, and I can eliminate talking through a specific interface like the PLM.
Hang in there, and welcome to the group! I loved your additions to Indigo, one of the few reasons I held on as long as I did.
Oh wow, I’m flattered! I really like Indigo well enough, but when it came time for my Mac mini to be replaced I made the decision to explore new options, particularly with the $80 renewal coming in a few weeks from then. HA is certainly a bit shaky at times but overall I’m pretty happy with the capabilities. Like you, I’ve been phasing Insteon out for Z-Wave, although I still like the KeyPadLincs so I’ll probably continue to have some kind of Insteon in my system.
checking latest logs, found the entry below occuring multiple times. I hope @teharris1 will have time to look at these before they become a breaking issue.
/usr/local/lib/python3.8/site-packages/pyinsteon/protocol/http_transport.py:167: DeprecationWarning: 'with await lock' is deprecated use 'async with lock' instead
await self._read_write_lock
I have several KPLs installed and when the buttons are programmed as “Momentary” they do not produce an event in HA, so they can’t be used to trigger automations. If I program the buttons as “Toggle” then they do trigger on and off events, but I need them to trigger the automation on each press, that’s why the “Momentary” event is important.
I opened up a request topic here.
Also, on a separate issue, the switch.turn_on and switch.turn_off work fine to turn on/off the leds on the relay version of the KPL, but it doesn’t work on the dimmer version of the KPL. The main button on the dimmer version is defined as a light in HA, but the other buttons are defined as switches.
I know that this has been moved into the main branch for HA.
I didn’t know where to post this question so I decided to post it here but please let me know if I need to post somewhere else.
Is there any way to enable 2 instances of the Insteon integration? I have 2 Insteon Hubs and I can only connect to 1.
I was able to do this in openHAB however I prefer Home Assistant but it seems it is limited to a single instance in Home Assistant.
@jastorino Currently the integration only allows for a single modem to be connected. Can you help me understand the use case for multiple modems? I have been asked for this feature before but I don’t understand why you would not want all devices connected to the same modem or why you would want multiple modems to control devices.
@rarroyo I will look into the issue with momentary. I am surprised this would be an issue.
Also switch.turn_on and switch.turn_off should work the same on the dimmable and the non-dimmable KPL. And you are correct, the other buttons are switches since they are only on/off entities like any other switch. I will look at this as well.
@Haddood Thanks for the heads up. It will be supported until 3.10 which comes out this year. I will definitely have a fix in before that. The change is in my current dev branch so on my next update of pyinsteon it will be addressed. Thanks again.
@teharris1 I have a feature request for the next release (let me know if you would rather this be a ticket on Git):
Ability to migrate a device from one to another. I got spoiled with Indigo that did an amazing job of Insteon management and when (because it is when, not if with in this case) a keypadlinc goes south it would be nice to just migrate all the settings from the dead KPL to the new one. I’ve been putting off replacing one of my dead KPL’s because the whole method of moving to a new one is painful and I have considered spinning up old Indigo for this change since I’ve had to do that many times over the years and it’s a 5 minute process in Indigo.
