I have not installed the Insteon2, will I need to do anything special when the 111 release comes out?
I’ve been looking forward to this release, and hope it solves the need to reboot issue I have as it seems to have popped up again.
No, you will not need to do anything special when 0.111 comes out. It will migrate from the previous version.
To give you all a quick update, the thermostat pull request has been approved and so I expect that to be in 0.112. The main solution will be in 0.111 which should come out in the next few days.
I did post two patches to the pyinsteon module so if any of you can download the latest version of the custom component it will install pyinsteon 1.0.2.
Just stumbled across this. Installed in HassOS 0.110.3 on rPi. Working well so far. But I notice several messages like this in the logs, “Light is deprecated, modify InsteonDimmerEntity to extend LightEntity”. Are these expected?
I had just started setting up a new Home Assistant installation, so this new Insteon component’s timing is very fortunate for me. Thanks a bunch!
What exactly does service insteon2.add_default_links do?
Great question. It creates links in the modem (Hub or PLM) and in the device for each button/group as a responder in the modem (and a corresponding controller link in the device) so that all activities in the device are seen by the modem. This is especially important for thermostat devices because they have a specific need for linking otherwise they do not send updates to the modem.
For all Hub users, can you please verify that restarting HA reconnects to the modem? I have another user in a different thread that is indicating the solution fails on restart. I would appreciate the feedback.
Is it run automatically, or should I run it once manually with “all”?
John, per our side discussion, only run insteon.add_default_links if you see a device not updating correctly in HA. There is no harm in running it for any device but it should not be necessary if the device is set up correctly. Also, pyinsteion runs the equivalent command under the hood on initial startup.
Good news, the thermostat PR just got merged into 0.111 so it will be in the next release also!
1 Like
Nice… I’ll be doing the full update
I also just made a small change to insteon2 to use pyinsteon version 1.0.3. If you all can try it and let me know if there are any issues that would be great. We only have a week until 0.111 so I want to make sure we catch as much as possible before the full release.
I’m just getting started with my insteon integration. I’m assuming that when .111 comes out the only thing I’ll have to do is add it to my configuration? If so I’ll just wait at this point. Thanks for all of your work on this. As much as I want to tinker with this stuff, I don’t have time 
1 Like
Quick update. I have made a lot of progress on the control panel element of the upcoming changes. Here is a snapshot. I will be creating a separate thread for that discussion:
2 Likes
very nice… i’ll definetely help test that
Unfortunately it is not easy to enable testing of the frontend like this. However, I am looking for good javascript / typescript people to help. I am not a UI developer 
I just updated to 0.111.0. All went very smoothly migrating my existing Insteon devices.
One question is the “insteon_plm_device_info.dat” file in the config folder still needed ? I noticed the date stamp on the file did not change.
Thanks again for all your efforts
@ brucek1642 great to hear! No, the insteon_plm_devices_imfo.dat file is no longer needed. It has been replaced by insteon_devices.json.
@Bob_Banks not yet but in a few weeks, yes. Once the insteon component has a config flow devices get created. After that, I will be deploying device configuration.
Thanks @teharris1. Coming back to HomeAssistant from HomeSeer and happy to see the .111 release. Should I hold off on configuring names and setting up automations until after your additional changes for config flow?