Insteon stopped working after last 2 updates

After the most recent update, the Insteon integration seems to have stopped working… Also, the web interface stops functioning.

I am currently using version 0.110.5

If I remove (comment out or delete) the configuration.yaml entries, the home assistant interface works again after a host reboot / core restart.

My yaml config…

# Hub 2242 configuration variables
insteon:
  host: 123.45.67.89
  hub_version: 1
  username: xxxxx
  password: xxxxxxxxxx

Any suggestions? Other entries in the configuration.yaml seem to work fine.

I am a bit confused by your configuration. Are you a Hub Version 1 or 2? Hub version 1 does not need a username or password.

I am using version 1. When I first put the configuration in, it would not connect without the username and password. Once I put them in It appeared to connect without error. I tried again without the username and password, and the same issue occurs. Also tried the config using hub_version: 2, same results.

Thanks. What was the last release you know to be working? Also, are you able to produce any logs? To put the Insteon component into debug mode you would do the following:

logger:
  default: info
  logs:
    insteonplm: debug
    homeassistant.components.insteon: debug

Pardon the “noob” question… I assume the logger settings go in to the configuration file. I added them there and uncommented my insteon settings. The web interface became unresponsive as expected after restarting through the web interface. I commented the insteon settings out once again, leaving the logger settings as is, then performed a host restart. I noticed that core restarts fail immediately with an error with the insteon config enabled.

The web interface is back but I am not sure where to retrieve the logs from. At the moment I have been looking through the web interface (dev tools logs). I do not see the logs when browsing through a samba connection.

Edit: The last time I recall this working it was 2 updates back. Sorry, I do not recall the number.

What I am looking for is the log file when it hangs. Do you know how to get to your configuration directory (the directory where your configuration.yaml file is) without HA running? If so, I would like you to add the insteon configuration back in and restart HA. After a minute or two, shut down HA and open the log file.

I thought I knew but probably not. At the moment, I am running home assistant using the vbox .vdi file. I plan to move to another system or pi after I get the hang of using setting up home assistant.

Long story short, I cannot get to the logs…

Have a look at these instructions:

Thank you for the link… Using the command “core logs” I was able to see the last bit of the log through the vbox console. I noticed that it appears to be attempting to connect to the default port “9761”. I had changed the port some time ago to “25105” for remote access.so I don’t think “9761” will work.

The hub current settings
Current Network Settings

PLM Version: 9D
Firmware Version: 4.8A Build Feb 08 2013
Insteon ID: 2C.C0.8C
MAC Address: 00:0E:F3:2C:C0:8C
Port: 25105
Mask: 255.255.255.0
DHCP: Enabled
GateWay: 192.168.xx.x
IP: 192.168.xx.xx

I tweaked the insteon settings again to add the port.

# Hub 2242 configuration variables
insteon:
  host: 192.168.xx.xx
  ip_port: 25105
  hub_version: 1
  username: xxxxx
  password: xxxxxxxx

It appears to be connecting now and the web interface for home assistant remains available after restarting the host. (Might have typo’d the host when I re-added during my testing) I am getting new errors in the dev-tools section now: “Lost connection to Insteon Modem: read failed: socket disconnected” is repeating. Not sure if this is related or not.

Thank you for your help!

Glad to hear you got it working. By the way, there is a major upgrade to the insteon component coming out in 0.111. If you have any issues with that version I would really like to hear about it as soon as possible. Also, you will want to be able to roll back to 0.110 if needed. You are one of the few hub version 1 users that I know about and I do not have one of those devices to check if it works.