Well, part of that feature exists but only at the command line level of pyinsteon. You can replace a device’s ALDB with a set of ALDB records from a json file. It is not a 5 minute job since you have to prep the json file but that will get the ALDB updated. Then you have the properties and operating flags which there is currently no current tool in pyinsteon for. Let me know if you want more details.
@rarroyo I checked the Momentary (or non-toggle as Insteon defines it) issue and I don’t see it on my side. When I have my “H” button set as non-Toggle OFF only, it sends a on_event which is available to automations. I setup an automation which is triggered on the event type insteon.button_on and pressing the H button triggered the automation.
Also, re-reading the issue with a dimmable KPL, the main light of a dimmable KPL needs to be triggered with light.turn_on or light.turn_off since it is a light not a switch. All the other buttons are switches.
Thanks, I’ll have to re-try that. I tried this a while back when I was setting up some automations, and I couldn’t see any events in the developer tools.
@teharris1 is there any intention pyinsteon to support the ‘insteon wireless thermostat 2441ZTH’ in the near future?
or its operating flags in the ALDB?
pyinsteon finds it and insert it to the ALDB but cant get it working.
my guess that the 2441TH (wired) is working properly?
thanks!
Insteon thermostats are difficult and the battery operated one is even tougher. There are very specific ALDB requirements for the thermostat. Have you tried to set the default links? Keep in mind for a wireless device you need to wake it up before it will talk to the modem.
I have both a 2441TH and a 2441ZTH and they both work for me with the HA integration
@teharris1 Thanks for the quick reply.
I have the wireless thermostat connected to external power source so its always on.
what do you mean by set the default links? are you refer to the operating flags?
btw, my thermostat looks like this in the ‘insteon_devices.json’:
{
"address": "394144",
"cat": 5,
"subcat": 10,
"firmware": 0,
"engine_version": 2,
"aldb_status": 4,
"aldb": {
"8191": {
"memory": 8191,
"in_use": true,
"controller": true,
"high_water_mark": true,
"bit5": false,
"bit4": false,
"group": 0,
"target": "000000",
"data1": 0,
"data2": 0,
"data3": 0
}
},
"operating_flags": {},
"properties": {
"program_lock_on": false,
"key_beep_on": false,
"button_lock_on": false,
"celsius": true,
"time_24_hour_format": true,
"led_on": false,
"temp_offset": 0,
"humidity_offset": 0,
"backlight": 0,
"change_delay": 1000
}
my only change here was to change the celsius from ‘false’ to ‘true’.
Thanks!
Never Mind, for some reason, the router started assigning dynamic IP. Not HA issue
as from version 2021.5.1 my Insteon stopped working !!! , I changed nothing in the configuration.
Alexa skill is working. insteone iOS app still working
```
Logger: homeassistant.components.insteon
Source: components/insteon/init.py:96
Integration: Insteon (documentation, issues)
First occurred: 12:32:02 PM (4 occurrences)
Last logged: 12:35:59 PM
Could not connect to Insteon modem
```
Found this other error in log
```
Logger: pyinsteon.protocol.http_reader_writer
Source: /usr/local/lib/python3.8/site-packages/pyinsteon/protocol/http_reader_writer.py:58
First occurred: 4:22:14 PM (3 occurrences)
Last logged: 4:24:53 PM
An client error occurred: Cannot connect to host 192.168.x.xx:25105 ssl:default [Connect call failed (‘192.168.x.xx’, 25105)]
```
@teharris1 hello! i was wondering if you can help me how to change the back light level of a KPL?
Thanks!
@OferPRTZ In HA, navigate to: Developer tools and click on the Services tab. From the service drop down select insteon.add_default_links. In the Service Data field enter the entity_id in the following format:
entity_id: climate.a1b2c3
@Alfonsolsl This can be done from the OS level by running the command insteon_tools. There is not a lot of documentation around this but try typing help for a list of commands or help <command> for command specific help. In general you are going to do the following:
insteon_tools
connect <connection info>
load_devices <path to insteon_devices.yaml file> 0 0
manage_config
The manage_config command brings you to the menu where you can set operating flags and properties. Use the following:
print_config <device address>
set_config_value <device address> <property name> <property value>
write_config <device address>
In your case it would look like this:
print_config 1a2b3c
set_config_value 1a2b3c led_dimming 10
write_config 1a2b3c
thanks!! i can see you have something in the oven related to this… good luck!
just testing 2021.7.0b0 and insteOn not working anymore… I was getting an error, that modem did not respond to ID request. I removed the integration and trying to install it, I get “Failed to connect” …
1 Like
Did you try restarting your hub?
not with 0b0. but I tried upgrade again with 0b3 and the same problem. tried restarting hub. remove integration and re-add after restart … and many other combinations … always fail to connect.
anybody has hub v2 running with 2021.7.xx ?
update:
all previous tries are on raspberry pi 3b+
I tried 0b4 on virtual machine (oracle) and still no luck… error: failed to connect to modem when I try to add the insteon integration
Updated to 2021.7.0 just now and have same issue as above – cannot connect to v2 hub.
It looks like the issue is in the pyinsteon library, so I opened an issue for it:
2 Likes
Hooping to find a solution here. Was driving me crazy for a few days trying to figure out why me Insteon integration was not working.
by the looks of it the fix might be coming in 2021.7.3