Every so often (not frequently) I will come home to a dark house. It always is because the Insteon plugin cannot communicate with the hub. I can almost always correct this almost immediately by disabling and re-enabling the Insteon plugin. In this case, i can see from the log that the problem started around 7:15am. I successfully reset the plugin and re-established communications with the hub at 5:20 pm. So whatever was going on with the hub, it had plenty of time to reset itself or timeout or whatever.
I can see that the plugin tried to restart the interface 8 times at a 15 seconds interval, and then gave up. Is this perhaps not long enough for the hub to recover? Should it try longer?
My next question is how can I detect and fix this situation with events?
First off, I'd like to be notified when it happens. I noticed that there's an Insteon special trigger for "Interface Stops Responding" I just wanted to confirm that this is what will trigger when the plugin stops communicating with the hub. How is this different from "Interface crashes"
I also see that there are Insteon actions for enable and disable interface. do these correspond with the same actions that the plugin does on it's own?
I can see that the plugin tried to restart the interface 8 times at a 15 seconds interval, and then gave up. Is this perhaps not long enough for the hub to recover? Should it try longer?
My next question is how can I detect and fix this situation with events?
First off, I'd like to be notified when it happens. I noticed that there's an Insteon special trigger for "Interface Stops Responding" I just wanted to confirm that this is what will trigger when the plugin stops communicating with the hub. How is this different from "Interface crashes"
I also see that there are Insteon actions for enable and disable interface. do these correspond with the same actions that the plugin does on it's own?
Comment