Since migrating to OH3, I have not been able to have a stable connection to my Insteon Hub (2245-222). I’m wondering if anybody else is experiencing the same thing.
With the last version of OH2 I was running (2.5?), the connection between OH2 and the hub was very stable and reliable. I would go for months without touching the system. Now, I can only expect 2 to 3 days of service before I have to restart the hub.
The curious thing is that when this happens, I drop back to using the Insteon app on my iPhone. The app correctly tracks the status of the items and I can send commands and have the devices react correctly. However, if I use curl commands at the command line of the host RPi, I also don’t get a response back from the hub. The last time this happened, I issued similar commands from other computers on the home network and also did not see a response. If I stop and restart OH3, the log will show that the Insteon binding was not able to connect (login?) to the hub. Only way to fix it is to restart (unplug/plug) the hub and then restart OH3.
I use the default connection string “/hub2/my_user_name:firstname.lastname@example.org:25105,poll_time=1000”. I’m wondering if the poll_time of 1 second is too fast and if that should be changed to 2000 or even 3000? The DEBUG log for the binding shows that at some point, the binding is issuing commands and waiting for responses; instead of raising an error message, it just keeps waiting and re-queuing the messages indefinitely. I would think that at some point if the hub has not responded to any message for a certain period of time, the binding would go into an error state. As it is now, OH3/Insteon binding continues to operate, still accepting command and the binding keeps sending them out to the non responding hub.
This is my 3rd try using OH3. The first one was using the official docker image on a RPi4 but that proved problematic (problem with the hub and could not get SONOS to work). I then moved to using OH3 directly under Raspian OS on the same machine as was hosting the docker image (experiencer the hub issue). Finally I moved back to a dedicated RPi3 using the official Openhahian image. Other that the Insteon binding, the rest of the OH3 works as expected. I’m using the Insteon, Z-Wave, SONOS, Astro, HTTP, MQTT, Network, NTP, OpenGarage, OWM and Unifi bindings.
Again, other than migrating from OH2 to OH3, I did not change anything else in my home network. Although it is not impossible that the hub is defective, the fact that it keeps running with the official Insteon app tells me the problem is somewhere else.
Would appreciate any suggestion.
PS. Can we still downloads the 2.x version of OH? I might try going back to it to see if I can reproduce the problem. I just wish I could export the OH3 database to text files!!