For custom naming purposes (in section “customize:”), what are the sensor types of the battery and light sensors of the Insteon motion sensors?
binary_sensor.1a2b3c_2 = light sensor
binary_sensor.1a2b3c_3 = battery sensor
where 1a2b3c is the Insteon device address of your motion sensor.
FYI on a breaking change to both
insteonlocal. Please see this thread and give your input:
I have recently moved over from openhab, because the integration you have done with insteon. It is amazing, thank you for the work!! I have all 29 of my various devices working flawless. I was able to monitor the door sensor battery in hidden door sensor in openhab. Can you explain how to get it going in homeassistant? I have a motion sensor and it is reporting the battery on group 3 just like this post suggests. I have tried different groups to get the battery for the door sensors “address: 1a2b3c_2” etc. and it is not reporting back anything. Are these battery devices different?
Thanks again on the work! You made it worth the hassle to move over.
Battery sensor for the door sensor is not enabled yet. It is in the to do list but not sure when.
Wow, thanks for the quick reply, it’s all good. That and the “fast-off” option are the only features I miss from Openhab. But the door sensor and keypads being responsive enough to trigger devices and automations is worth the switch! I appreciate the work put into this component, it shows. This component is why I switched.
On a side note, the “fast-off” would be a good future feature as well. I used “fast-off” to control under cabinet lights. The kitchen switch kicked the lights on. And an automation also kicked on mqtt under cabinet lights. Turning off the switch would leave them on (ambience lighting). Double taping the switch “fast-off” would turn the under cabinet lights off too, with an automation. Useful for having two switches in one.
This topic is admittedly pretty old, but I’m new to HA. I’m a long-time Insteon user looking to ditch my hub and most of its associated devices in favor of HA running on RPi. In fact I would’ve fully walked away from Insteon by now except that I’ve not found anything in the [ z-wave | zigbee ] world to match the design, feel, and responsiveness of the Insteon mini-remotes.
So my device needs are quite slim at this point: I want Insteon on/off mini remotes to trigger HA automations.
Q: is it the case that once I get an Insteon 2448A7 USB dongle into my RPi, the remaining work is:
- add relevant lines to my
- join my mini remotes to the USB dongle and vice versa
- set up new automations with event handlers listening for
If so, is Insteon missing from my manifest of configurable HA integrations simply because I don’t have the USB dongle installed yet?
I’ve successfully integrated an Insteon LampLinc-style dimmer, via HA’s native support for my 2245 Hub, such that I can control the dimmer via HA and work it into automations.
However I can’t seem to trap events from my mini remotes. I can hear them chirp when I put them in linking mode and then call the HA
insteon.add_all_link service, as if they’re responding to the link request. But that’s the limit of my progress.
Is that only possible via (a) using a PLM instead of a hub, and/or (b) running HA on something other than hass.io on a Raspberry Pi (so that I can install certain Python libraries)?
Mini remotes do not appear as Entities in HA, they only trigger automations. For example,
- id: '1552262250942' alias: Mini Remote Lock Front Door trigger: - event_data: address: 1a2b3c button: b event_type: insteon.button_on platform: event condition:  action: - data: entity_id: lock.front_door_lock service: lock.lock
The example above will listen for mini-remote
1a2b3c button b.
I’ve not seen anything come across the HA event stream of the type
insteon.button_on, even after attempts at pairing. So I can’t set up automations as you recommend.
I suspect I need more progress on the pairing side before mini remote events will pass through HA via the 2245 hub.
Put insteon in debug mode by using the following somewhere in your configuration.yaml file:
logger: default: info logs: insteonplm: debug homeassistant.components.insteon: debug
Then update the logs so I can see what devices the Hub knows about.
Also, with the insteon component in debug mode, if you press the buttons on the remote, the log with catch them. This will confirm the Hub can see the remote’s buttons.
OK, log sent to you via direct message.
The mini-remote is a battery operated device and so it does not reply to
device id requests. In order for HA to see the device you need to setup
device override configuration as follows:
insteon: host: !secret hub_ip username: !secret hub_username password: !secret hub_password ip_port: 25105 device_override: - address: 44899f # 8 button mini remote cat: 0x00 subcat: 0x1b - address: 449b4e # 1 botton mini remote cat: 0x00 subcat: 0x1c
Hopefully you saw this in the documentation for the Insteon component.
As you mentioned, this is a case of not “RTFM”-ing. I didn’t get down to that section of the documentation because I assumed I was still stuck on the pairing process.
Having now added overrides to my
configuration.yaml I can trap and act on events generated by the mini remote. Thanks a bunch for the help, and for writing the module in the first place.
Glad you figured it out.
I have just released a significant update to the insteon component as a beta. It is available through a custom component to allow people to test without disrupting current implementations. The details are in this thread:
I am working on migrating my HA insteon integration from Hub to PLM. I have the USB PLM connected and recognized by my test instance of HA running on a PI 3b+
I am stuck on how to get the PLM linked as controller/responder.
Some older posts refer to having to do this for every device but then I see mentions of plans to eliminate this step.
What is the current best practice. I have 20+ insteon devices
I have my ISY currently controlling all my Insteon devices. I, too, would like to move everything to HA + PLM (or USB) but can’t figure out how to link in HA. Help would be appreciated!
I got an Insteon USB PLM working, much of what I learned is on this thread. Hard part was linking each device one by one.
Using USB PLM on Hassio on a raspberry PI3b, it has been very stable for about 3 weeks.
I just barely decided to pay the $5 a month for HA cloud service to get Alexa working. Working on moving off of the Insteon HUB that is handling all my Alexa integrations now.
The problem with having an Insteon HUB and PLLM via HA at the same time is that if the HUB controls a device the PLM never knows about it.