Insteon Plugin for HOOBS box locks up the HOOBS box

[greg-e-ctrl]

Hi,

When I have the Insteon plugin running and no activity on the Insteon network that I can see in the log, it randomly lockups the entire HOOBS box from communicating with the Insteon hub although the log says it did. My Insteon Director app still works correctly when the Hoobs is in this state.

Also, when I use some of my Insteon physical switches or another program that sends a command it logs that it cannot find that accessory ID but in fact it is in the device list and i can control it from Hoobs when all is working correctly. Here is the log from that: 1/13/2023, 8:55:38 AM Platform Insteonlocal BridgeInsteon LocalMessage is from keypad, filtering non-keypad devices. 1/13/2023, 8:55:38 AM Platform Insteonlocal BridgeInsteon LocalFound 0 accessories matching 418C4B 1/13/2023, 8:55:38 AM Platform Insteonlocal BridgeInsteon LocalHub command: {"standard":{"type":"50","id":"418C4B","gatewayId":"3429F8","extended":false,"messageType":1,"hopsLeft":2,"maxHops":3,"command1":"32","command2":"02","raw":"0250418C4B3429F82B3202"}}

I debugged this with Zac from Hoobs and he said to contact you. I would love to get on the phone with you and share my screen with you. I am a software engineer and know something about all this home iot stuff with the restful apis used, etc. :)

Thanks!

-- Greg

[zzack01]

@AstonMartin715 Can you also send a screenshot of your dashboard, this will show everything needed

[mightstricky]

Here is what HOOBS support says: Response to ticket "63F3-BEF8-D770-F4EF-3243-B179" Hello, There have been multiple people that have reported this to the plugin developer, please see the below to add to one of these issues or to create a new issue with the plugin developer: https://github.com/kuestess/homebridge-platform-insteonlocal/issues?q=ETIMEDOUT If you have any questions it's OK to reply to this email, and your ticket will be updated. Thank You, HOOBS Support Team

[greg-e-ctrl]

Yep, same problem that I, AstonMartin715, and others are having. The HOOBS folks can't seem to reproduce so they do not know what to do.

@kuestess, @zach: Any fix for this yet? As mightstricky mentions, our HOOBS boxes are just sitting as paperweights now as they do not work!!! :(

You can use my system to debug if you need to. I can provide you remote access, etc. JLMK!

Please fix this or I will be returning the HOOBS box and will not be promoting it positively until so...

This is ridiculous.

-- greg

On 2/28/2023 7:40 AM, mightstricky wrote:

Here is what HOOBS support says: Response to ticket "63F3-BEF8-D770-F4EF-3243-B179" Hello, There have been multiple people that have reported this to the plugin developer, please see the below to add to one of these issues or to create a new issue with the plugin developer: https://github.com/kuestess/homebridge-platform-insteonlocal/issues?q=ETIMEDOUT If you have any questions it's OK to reply to this email, and your ticket will be updated. Thank You, HOOBS Support Team

— Reply to this email directly, view it on GitHub https://github.com/kuestess/homebridge-platform-insteonlocal/issues/288#issuecomment-1448402659, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMOOUEDLJGCUNWS3WP3RY7TWZYL5VANCNFSM6AAAAAAT264J2Y. You are receiving this because you were mentioned.Message ID: @.***>

[kuestess]

@mightstricky @AstonMartin715 @greg-e-ctrl I suppose it could be an issue with the plugin, however it seems odd that the only reports of the issue are with users running HOOBS, and none running vanilla homebridge. The search link provided is a little misleading as it lacks context. At any rate, one sure way to figure out specifically where the issue lies is to have one of you spin up a Homebridge docker container and install the plugin in that to see if the issue persists. If not, then that points to Hoob - if so, it points to the plugin. I'm happy to try and walk you through it if you're willing to give it a shot. You'll just need a machine separate from your hoobs box (and hopefully not Windows :-) [just my personal bias]).

[AstonMartin715]

So I was able to get hold of a spare Insteon hub (still 2245), and set it up as a clean configuration with just switches and plugs (no sensors, no keypads, no cameras), and it's been working for 3 days straight (longest stability I've ever seen). Now what I can't tell is whether or not it's to do with the new hub or the different install. I have also factory reset my old hub and am ready to test it with a simple and clean configuration but I don't want to change any configurations on my main setup right now. If the Hoobs folks want to ship me a different box @zzack01 to test I'm happy to do that. I'll also try the home bridge docker container you mention above @kuestess with that hub when I get a chance. Question for @greg-e-ctrl and @mightstricky - what rev is shown on the bottom of your Insteon hub?

[greg-e-ctrl]

my Insteon hub has a sticker that says:  "rev 1.3 - 1115"

Sorry, I do not have another non-windows machine, but sounds like @AstonMartin715 is able to do so, so thank you both!

On 2/28/2023 3:14 PM, AstonMartin715 wrote:

So I was able to get hold of a spare Insteon hub (still 2245), and set it up as a clean configuration with just switches and plugs (no sensors, no keypads, no cameras), and it's been working for 3 days straight (longest stability I've ever seen). Now what I can't tell is whether or not it's to do with the new hub or the different install. I have also factory reset my old hub and am ready to test it with a simple and clean configuration but I don't want to change any configurations on my main setup right now. If the Hoobs folks want to ship me a different box @zzack01 https://github.com/zzack01 to test I'm happy to do that. I'll also try the home bridge docker container you mention above @kuestess https://github.com/kuestess with that hub when I get a chance. Question for @greg-e-ctrl https://github.com/greg-e-ctrl and @mightstricky https://github.com/mightstricky - what rev is shown on the bottom of your Insteon hub?

— Reply to this email directly, view it on GitHub https://github.com/kuestess/homebridge-platform-insteonlocal/issues/288#issuecomment-1449071476, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMOOUEHUCKAI4B3LZBS72TLWZ2BEBANCNFSM6AAAAAAT264J2Y. You are receiving this because you were mentioned.Message ID: @.***>

[kuestess]

@AstonMartin715 Below is a docker-compose file that will create a home bridge container complete with a GUI on port 8580 of whatever machine you run it on. You'll need to install docker and docker-compose first and then copy the text below into a file named docker-compose.yml. Make sure that you're in the same directory where you saved that file and then type docker-compose up at a command prompt. First time you run that command, it will take a little bit to download the image, but it should eventually indicate that it is listening on port 8580. From there, open http://[ip of machine running docker]:8580 in your browser and you should see a guy similar to hoobs. Documentation for the guy is here: https://github.com/oznu/docker-homebridge but you should just be able to install the plugin and paste in your config from hoobs to get it running.

version: '2'
services:
  homebridge:
    container_name: homebridge
    image: oznu/homebridge:ubuntu
    privileged: true
    restart: always
    network_mode: host
    environment:
      - PGID=1000
      - PUID=1000
      - HOMEBRIDGE_CONFIG_UI=1
      - HOMEBRIDGE_CONFIG_UI_PORT=8580
    volumes:
      - ./:/homebridge

[mightstricky]

.Question for @greg-e-ctrl and @mightstricky - what rev is shown on the bottom of your Insteon hub? Mine is rev 1.4 - 3515

[greg-e-ctrl]

rev 1.3 - 1115

-- greg

On 3/1/2023 4:36 PM, mightstricky wrote:

.Question for @greg-e-ctrl <https://github.com/greg-e-ctrl> and
@mightstricky <https://github.com/mightstricky> - what rev is
shown on the bottom of your Insteon hub?
Mine is rev 1.4 - 3515

— Reply to this email directly, view it on GitHub https://github.com/kuestess/homebridge-platform-insteonlocal/issues/288#issuecomment-1451096988, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMOOUEFQRGIWIBOLYCJLPETWZ7TQDANCNFSM6AAAAAAT264J2Y. You are receiving this because you were mentioned.Message ID: @.***>

[AstonMartin715]

Thanks. Sounds like it’s not isolated to specific Insteon revs (mine is 2.8-4117). @greg-e-ctrl do you ever see the following in your log (which is associated with the keep-alive):

3/2/2023, 5:32:06 PMPlatform Insteonlocal BridgeInsteonLocalClosing connection to Hub... 3/2/2023, 5:32:11 PMPlatform Insteonlocal BridgeInsteonLocalReconnecting to Hub... 3/2/2023, 5:32:11 PMPlatform Insteonlocal BridgeInsteonLocalConnected to Insteon Model 2245 Hub...

I NEVER saw that group of messages with the previous set up, even when I reduced the keep alive time. And now it shows up consistently and predictably on the hour.

[kuestess]

@AstonMartin715 That is the keepAlive functionality - it was inadvertently omitted in the transition to a dynamic platform and re-added in a recent update. You can disable it completely by setting keepAlive to 0 in your config (default is the 1hour that you're seeing).

[greg-e-ctrl]

yep, saw them when playing around with the keeplive setting to see if it would solve our prob...

i now have it set to 0 so i do not see them in the log

e-ctrl

On 3/2/2023 10:08 AM, kuestess wrote:

@AstonMartin715 https://github.com/AstonMartin715 That is the keepAlive functionality - it was inadvertently omitted in the transition to a dynamic platform and re-added in a recent update. You can disable it completely by setting |keepAlive| to 0 in your config (default is the 1hour that you're seeing).

— Reply to this email directly, view it on GitHub https://github.com/kuestess/homebridge-platform-insteonlocal/issues/288#issuecomment-1452312504, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMOOUEAIFXAUI3USODUGMRLW2DOYLANCNFSM6AAAAAAT264J2Y. You are receiving this because you were mentioned.Message ID: @.***>

[mightstricky]

I have been troubleshooting with the Hoobs support from Reddit. I will update there to avoid confusing this thread. See link below. So far after downgrading to 0.5.7 version of plug-in all accessories work from Hoobs. As soon as I added to HomeKit, everything stopped working. I reinstalled the 0.5.7 and restarted Hoobs and everything is work. I am not going touch HomeKit for a while and see if something changes.

https://www.reddit.com/r/HOOBS/comments/10wstqk/im_about_to_throw_this_thing_away/jarojt2/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3

[mightstricky]

I have been troubleshooting with the Hoobs support from Reddit. I will update there to avoid confusing this thread. See link below. So far after downgrading to 0.5.7 version of plug-in all accessories work from Hoobs. As soon as I added to HomeKit, everything stopped working. I reinstalled the 0.5.7 and restarted Hoobs and everything is work. I am not going touch HomeKit for a while and see if something changes.

https://www.reddit.com/r/HOOBS/comments/10wstqk/im_about_to_throw_this_thing_away/jarojt2/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3

Update: Everything stopped working after 7-8 hours. The logs are below and also posted in the above reddit.

3/3/2023, 2:17:31 PMPlatform Insteonlocal BridgeInsteonLocalConnected to Insteon Model 2245 Hub... 3/3/2023, 3:17:25 PMPlatform Insteonlocal BridgeInsteonLocalClosing connection to Hub... 3/3/2023, 3:17:30 PMPlatform Insteonlocal BridgeInsteonLocalReconnecting to Hub... 3/3/2023, 3:17:31 PMPlatform Insteonlocal BridgeInsteonLocalConnected to Insteon Model 2245 Hub... 3/3/2023, 3:19:39 PMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105 3/3/2023, 5:17:25 PMPlatform Insteonlocal BridgeInsteonLocalClosing connection to Hub... 3/3/2023, 5:17:30 PMPlatform Insteonlocal BridgeInsteonLocalReconnecting to Hub... 3/3/2023, 5:19:38 PMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105 3/3/2023, 5:19:43 PMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105 3/3/2023, 6:04:33 PMPlatform Insteonlocal BridgeInsteonLocalSetting level of Dimmer Kitchen to 100% 3/3/2023, 6:04:39 PMPlatform Insteonlocal BridgeInsteonLocalSetting level of Dimmer Dining Room to 100% 3/3/2023, 6:06:44 PMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105 3/3/2023, 6:08:57 PMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105

So then I went into the HOOB and restarted the HOOB's box. Now everything works again! 3/3/2023, 6:18:39 PMWARNINGdevice reboot command received 3/3/2023, 6:18:40 PMPlatform Insteonlocal Bridge stopping 3/3/2023, 6:19:05 PMhub is running on port 80 3/3/2023, 6:19:07 PMPlatform Insteonlocal Bridge starting 3/3/2023, 6:19:18 PMPlatform Insteonlocal BridgeLoaded plugin 'homebridge-platform-insteonlocal' 3/3/2023, 6:19:18 PMPlatform Insteonlocal BridgeLoading 1 platforms... 3/3/2023, 6:19:18 PMPlatform Insteonlocal BridgeInsteonLocalStarted connection watcher... 3/3/2023, 6:19:18 PMPlatform Insteonlocal BridgeInsteonLocalLoading accessory from cache: Dimmer Bedroom

3/3/2023, 6:19:18 PMPlatform Insteonlocal BridgeInsteonLocalFound 15 devices in config 3/3/2023, 6:19:18 PMPlatform Insteonlocal BridgeInsteonLocalRestoring existing accessory from cache: Dimmer Bedroom

3/3/2023, 6:19:19 PMPlatform Insteonlocal BridgeBridge is running on port 51826. 3/3/2023, 6:19:19 PMPlatform Insteonlocal BridgeInsteonLocalConnected to Insteon Model 2245 Hub... 3/3/2023, 6:19:19 PMPlatform Insteonlocal BridgeInsteonLocalGetting status for Dimmer Bedroom

3/3/2023, 6:19:19 PMPlatform Insteonlocal BridgeInsteonLocalInsteon event listener started... 3/3/2023, 6:21:55 PMPlatform Insteonlocal BridgeInsteonLocalSetting level of Dimmer Dining Room to 0% 3/3/2023, 6:21:58 PMPlatform Insteonlocal BridgeInsteonLocalSetting level of Dimmer Dining Room to 100%

[greg-e-ctrl]

yep, same problem, still exists back-rev and current...

e-ctrl

On 3/3/2023 4:18 PM, mightstricky wrote:

I have been troubleshooting with the Hoobs support from Reddit. I
will update there to avoid confusing this thread. See link below.
So far after downgrading to 0.5.7 version of plug-in all
accessories work from Hoobs. As soon as I added to HomeKit,
everything stopped working. I reinstalled the 0.5.7 and restarted
Hoobs and everything is work. I am not going touch HomeKit for a
while and see if something changes.

https://www.reddit.com/r/HOOBS/comments/10wstqk/im_about_to_throw_this_thing_away/jarojt2/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3
<https://www.reddit.com/r/HOOBS/comments/10wstqk/im_about_to_throw_this_thing_away/jarojt2/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3>

Update: Everything stopped working after 7-8 hours. The logs are below and also posted in the above reddit.

3/3/2023, 2:17:31 PMPlatform Insteonlocal BridgeInsteonLocalConnected to Insteon Model 2245 Hub... 3/3/2023, 3:17:25 PMPlatform Insteonlocal BridgeInsteonLocalClosing connection to Hub... 3/3/2023, 3:17:30 PMPlatform Insteonlocal BridgeInsteonLocalReconnecting to Hub... 3/3/2023, 3:17:31 PMPlatform Insteonlocal BridgeInsteonLocalConnected to Insteon Model 2245 Hub... 3/3/2023, 3:19:39 PMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105 3/3/2023, 5:17:25 PMPlatform Insteonlocal BridgeInsteonLocalClosing connection to Hub... 3/3/2023, 5:17:30 PMPlatform Insteonlocal BridgeInsteonLocalReconnecting to Hub... 3/3/2023, 5:19:38 PMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105 3/3/2023, 5:19:43 PMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105 3/3/2023, 6:04:33 PMPlatform Insteonlocal BridgeInsteonLocalSetting level of Dimmer Kitchen to 100% 3/3/2023, 6:04:39 PMPlatform Insteonlocal BridgeInsteonLocalSetting level of Dimmer Dining Room to 100% 3/3/2023, 6:06:44 PMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105 3/3/2023, 6:08:57 PMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105

— Reply to this email directly, view it on GitHub https://github.com/kuestess/homebridge-platform-insteonlocal/issues/288#issuecomment-1454292711, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMOOUEB4CLXQB34NFDU2VE3W2KC4XANCNFSM6AAAAAAT264J2Y. You are receiving this because you were mentioned.Message ID: @.***>

[AstonMartin715]

My brand new installation (same Hoobs box with brand new Insteon 2245 hub) lasted about 6 days (longest ever) but then crashed out with the same messages @mightstricky posted above. So now that's the same problem with 2 different Insteon hubs. A Hoobs reboot has it working again, we'll see for how long. I will set up and test the home bridge docker container as soon as I can set aside the time.

[mightstricky]

Ok, I give up on wasting any more time with Hoobs and this Plugin. After 7 hours (KeepAlive=1200), it is dead again. Thank you it has been nice knowing everyone, and good luck. We can't expect HOOBS to refund the cost of the hub, but I will try.

3/3/2023, 10:13:19 PMWARNINGdevice reboot command received 3/3/2023, 10:13:20 PMPlatform Insteonlocal Bridge stopping 3/3/2023, 10:13:46 PMhub is running on port 80 3/3/2023, 10:13:48 PMPlatform Insteonlocal Bridge starting 3/3/2023, 10:13:58 PMPlatform Insteonlocal BridgeLoaded plugin 'homebridge-platform-insteonlocal'

3/4/2023, 5:14:16 AMPlatform Insteonlocal BridgeInsteonLocalConnected to Insteon Model 2245 Hub... 3/4/2023, 5:34:11 AMPlatform Insteonlocal BridgeInsteonLocalClosing connection to Hub... 3/4/2023, 5:34:16 AMPlatform Insteonlocal BridgeInsteonLocalReconnecting to Hub... 3/4/2023, 5:36:27 AMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105 3/4/2023, 5:54:11 AMPlatform Insteonlocal BridgeInsteonLocalClosing connection to Hub... 3/4/2023, 5:54:16 AMPlatform Insteonlocal BridgeInsteonLocalReconnecting to Hub... 3/4/2023, 5:56:25 AMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105 3/4/2023, 5:56:30 AMPlatform Insteonlocal BridgeWARNINGunhandled rejection: Error: connect ETIMEDOUT 192.168.1.213:25105

[kuestess]

@mightstricky Sorry it didn't work out for you. If you're game to try one other thing, can you try (with a fresh install) 0.5.6? Not saying that this is the cause, but curious if the keepAlive functionality (restored in 0.5.7) might be related. On a separate note, if you do keep your hoobs box, I think it's simply a Raspberry Pi in a nice package that you could re-flash with Debian and run homebridge (which also has a UI, see docker-compose above) on it. This is the setup I have with no issues.

[zzack01]

@kuestess I do not believe it is a HOOBS™ issue, I am running the latest HOOBS™ version 4.3.0, node 16.19.1 homebridge 1.6.0 with no issue with the insteon plugin. If it were a HOOBS™ issue then every HOOBS™ owner that is on the most current version would be having this issue. In the same respect I am also running insteon plugin version 0.5.8 with no issue again if it were a plugin issue everyone with the updated plugin would be having this issue.

So I am not sure if it could be the insteon hub that is causing this or if there are switches/gateways/VPN/firewalls/... between the two causing the issue. Or also not sure if the insteon hub is plugged into a power strip/surgre procter/... as insteon hubs have to be plugged directly into the wall outlet since it "talks" powerline...

I am running the insteon hub and the HOOBS™ box off the main router on my set up and everything works... So I don't believe it is a HOOBS™ issue and I don't believe it is a plugin issue.

For those having the issue:

are you running the HOOBS™ box and the insteon box directly from the main router? do you have any vpn's/firewalls/...? is the insteon hub plugged directly into the wall outlet? if you are running HOOBS™ are you on verison 4.3.0? are you on insteon plugin version 0.5.8? if everything above is good, try to reset the insteon hub and do a reflash on the HOOBS™ box (the current reflash on the site will take you to 4.3.0, just remember to plugin the ethernet cable first then the power cable. If you do reset everything ensure that:

you take down any firewall/vpn/... If using HOOBS™, do a reflash (maybe try a new sd card) on the HOOBS™ box (the current reflash on the site will take you to 4.3.0, just remember to plugin the ethernet cable (to the main router, (no switch/gateway/...)) first then the power cable. then check for updates reset the insteon hub and ensure is connected directly to the main router (no switch/gateway/...), ensure the insteon hub is plugged directly into the wall outlet (no powerstrips/surge protectors/batterybackup/... as outlined in the insteon hub instructions http://cache.insteon.com/documentation/2245-222-en.pdf) then ensure your firmware is updated set up a few devices on the insteon hub then download the latest insteon plugin version currently 0.5.8 test the insteon devices in the HOOBS™ accessory page, then if working correctly you can add to apple home: https://www.youtube.com/watch?v=zYPg9UTY4fM&list=PLao1ak6KCk3oxM4PcU7r9oSGb8ZohxkgC&index=2 @kuestess do you have any other suggestions from the above

[AstonMartin715]

@zzack01 I've done everything you outline above, in some cases multiple times. I've even gone further. For example, I put the Hoobs box and Insteon hub on their own dedicated VLAN so there's no other traffic. There's some combination of factors between the Insteon hub, Hoobs box and plugin that at least 3 of us are experiencing. And I've now obtained and installed a second Insteon hub, which didn't solve it, so I think that eliminates the Insteon hub from being a contributing factor.

[kuestess]

@zzack01 It may not be a hoobs issue, but it is a common factor for the users here. Perhaps that's a red herring, but I haven't seen any troubleshooting from hoobs to rule it out. It is helpful to know that this isn't broader amongst other users.

@AstonMartin715 Let me know if/when you've had a chance to test out vanilla homebridge in docker. Dependent upon outcome from that, it could rule out hoobs and point to a hub/plugin issue that we can try to troubleshoot further.

[zzack01]

@kuestess I agree for some reason there is a common issue with the 3 or so people that are on this thread, monitoring discord there is not any wide spread of this issue...

would be great to hear from @greg-e-ctrl & @mightstricky to see if my above solution works for them...

if not what router are you using? (maybe there is a security setting issue) just thinking of a common issue that could be found...

[greg-e-ctrl]

Hi AstonMartin715,Since you have an isolated volan, can you check with a network sniffer, such as Wireshark, to check if any commands come out of the Hoobs box when it is in the locked up state but thinks it is still sending commands to the Insteon hub correctly?This will confirm if the Insteon hub is receiving any commands from the Hoobs box when the Hoobs   user interface appears to be working when it really is not. Thanks!--GregOn Mar 4, 2023, at 10:25 AM, AstonMartin715 @.***> wrote: @zzack01 I've done everything you outline above, in some cases multiple times. I've even gone further. For example, I put the Hoobs box and Insteon hub on their own dedicated VLAN so there's no other traffic. There's some combination of factors between the Insteon hub, Hoobs box and plugin that at least 3 of us are experiencing. And I've now obtained and installed a second Insteon hub, which didn't solve it, so I think that eliminates the Insteon hub from being a contributing factor.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[hypeitinc]

Hi all!

I have the same or very similar problem as described by you all. I have the same setup in two houses, one is our vacation home so remote access is crucial.

My configuration is a bit different in the way that I use old MacMinis rather than the Hoobs box. (and Hub 2245) Why? because the Raspberry Pi 3 is not reliable enough. As you can see from the universal solution of refreshing the SD card, it can for example get corrupted on power failure. And you can have that happen when you need remote access to something 250 miles away. I had one very early on but sent it back because of these problems. (BTW - This is where I also am having problems with the thermostat controls not working at all on the Insteon plugin)

In this setup everything works fine for about a week. Then the Home App shows "no response” for the different Insteon devices all other wifi devices are working, and a reboot of the Mac Mini resolves the problem. I have the keep alive set to 3600. For the vacation home I also have access through the Insteon iOS App and can still access the devices that way when this happens. (Reason I have it still is because of the thermostat problem…)

Today it happened again, and I had hoped to catch the log here, but messed up. The bridge was constantly stopping and starting and also an error message saying something like "detected memory leak in Insteon Plugin”. Maybe that can help?

At last. @zzack01 I don’t believe that this is a networking issue in terms of router/firewall setup. Why would something work for a week and then suddenly stop and easily recover while resetting the device (Hoobs box, MacMini etc)? Same thing with if the hub is plugged in to a power strip or not. I think most of us here have had their systems working for years before the Insteon debacle lead us to Hoobs...

/Peter

On Mar 4, 2023, at 11:01 AM, zzack01 @.***> wrote:

@kuestess https://github.com/kuestess I agree for some reason there is a common issue with the 3 or so people that are on this thread, monitoring discord there is not any wide spread of this issue...

would be great to hear from @greg-e-ctrl https://github.com/greg-e-ctrl & @mightstricky https://github.com/mightstricky to see if my above solution works for them...

if not what router are you using? (maybe there is a security setting issue) just thinking of a common issue that could be found...

— Reply to this email directly, view it on GitHub https://github.com/kuestess/homebridge-platform-insteonlocal/issues/288#issuecomment-1454842828, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASSOQS2STQCE3233C67NIDW2OGSPANCNFSM6AAAAAAT264J2Y. You are receiving this because you are subscribed to this thread.

[kuestess]

@hypeitinc Which version of the plugin are you using and what is your keepAlive set at in your config?

[greg-e-ctrl]

Agree with you 100% here @Peter!It is NOT the Insteon hub that has an issue. They have been running for years and they still work with the Insteon app when the Hoobs box and app are locked up and do not work!The Hoobs box is just another client app like the Insteon app. So I suggest to sniff the network for how the Insteon app sends commands to the Insteon hub and mimic that in the Hoobs box. And as I asked before, to let us know if the Hoobs box is even sending anything to the ip address of the Insteon hub when it is in the locked up state. @kuestess and @Zach, can you do this exercise and report back to the group on your findings here?Thanks--GregOn Mar 4, 2023, at 1:41 PM, Peter Rexelius @.***> wrote: Hi all!

I have the same or very similar problem as described by you all. I have the same setup in two houses, one is our vacation home so remote access is crucial.

My configuration is a bit different in the way that I use old MacMinis rather than the Hoobs box. (and Hub 2245) Why? because the Raspberry Pi 3 is not reliable enough. As you can see from the universal solution of refreshing the SD card, it can for example get corrupted on power failure. And you can have that happen when you need remote access to something 250 miles away. I had one very early on but sent it back because of these problems. (BTW - This is where I also am having problems with the thermostat controls not working at all on the Insteon plugin)

In this setup everything works fine for about a week. Then the Home App shows "no response” for the different Insteon devices all other wifi devices are working, and a reboot of the Mac Mini resolves the problem. I have the keep alive set to 3600. For the vacation home I also have access through the Insteon iOS App and can still access the devices that way when this happens. (Reason I have it still is because of the thermostat problem…)

Today it happened again, and I had hoped to catch the log here, but messed up. The bridge was constantly stopping and starting and also an error message saying something like "detected memory leak in Insteon Plugin”. Maybe that can help?

At last. @zzack01 I don’t believe that this is a networking issue in terms of router/firewall setup. Why would something work for a week and then suddenly stop and easily recover while resetting the device (Hoobs box, MacMini etc)? Same thing with if the hub is plugged in to a power strip or not. I think most of us here have had their systems working for years before the Insteon debacle lead us to Hoobs...

/Peter

On Mar 4, 2023, at 11:01 AM, zzack01 @.***> wrote:

@kuestess https://github.com/kuestess I agree for some reason there is a common issue with the 3 or so people that are on this thread, monitoring discord there is not any wide spread of this issue...

would be great to hear from @greg-e-ctrl https://github.com/greg-e-ctrl & @mightstricky https://github.com/mightstricky to see if my above solution works for them...

if not what router are you using? (maybe there is a security setting issue) just thinking of a common issue that could be found...

— Reply to this email directly, view it on GitHub https://github.com/kuestess/homebridge-platform-insteonlocal/issues/288#issuecomment-1454842828, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASSOQS2STQCE3233C67NIDW2OGSPANCNFSM6AAAAAAT264J2Y. You are receiving this because you are subscribed to this thread.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[kuestess]

@greg-e-ctrl This is exactly the type of troubleshooting I'd like to see from hoobs. I don't have a hoobs box, but @zzack01 happy to test if you want to send me one.

[hypeitinc]

@kuestess Vacation home: Plugin 0.5.7, keepalive 3600 (don’t want to update until I’m there in person...) SF home: Plugin 0.5.8, keepalive 3600

On Mar 4, 2023, at 1:57 PM, kuestess @.***> wrote:

@hypeitinc https://github.com/hypeitinc Which version of the plugin are you using and what is your keepAlive set at in your config?

— Reply to this email directly, view it on GitHub https://github.com/kuestess/homebridge-platform-insteonlocal/issues/288#issuecomment-1454899877, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASSOQQSQ5U4WZB5PY5UQJTW2O3EVANCNFSM6AAAAAAT264J2Y. You are receiving this because you were mentioned.

[zzack01]

@AstonMartin715 @greg-e-ctrl @mightstricky

Are you running the most up to date software? What versions are you running? (dashboard screen shots would be great)

Have you tried to clear the cache? Under hub settings clear cache, then go into the bridge and click on the insteon bridge and click clear cache.

Also are you having this issue with any other plugin? If so what plugin?

Have you tried to reassign a new IP address to the insteon hub and then update it in the insteon plugin? Have you tried a new IP address for the HOOBS™ box?

@kuestess I have not been able to reproduce the error that these 3 are seeing, thats why I do not think it is a HOOBS™ box issue, also there is a new user that is using a mac mini, also the almost 900 people using the HOOBS™ insteon discord channel would be reporting this as well... Same with the plugin, there are only a handleful of users that have this issue... I still think that there is something to do with these 3 users settings somewhere... Are you able to remote in with them individually and check their plugin settings/ IP addresses/...

[greg-e-ctrl]

Hi Zach,

I have done all of these things multiple times as you asked me a while ago as well as just now...latest versions of everything, cleared caches, only Insteon bridge/plugin running-no other plugins or apps, IP address does not matter, and still same issue; it locked up after a few hours. So now I did a shutdown and its just a paperweight again. :(

e-ctrl

On 3/5/2023 1:19 PM, zzack01 wrote:

@AstonMartin715 https://github.com/AstonMartin715 @greg-e-ctrl https://github.com/greg-e-ctrl @mightstricky https://github.com/mightstricky

Are you running the most up to date software? What versions are you running? (dashboard screen shots would be great)

Have you tried to clear the cache? Under hub settings clear cache, then go into the bridge and click on the insteon bridge and click clear cache.

Also are you having this issue with any other plugin? If so what plugin?

Have you tried to reassign a new IP address to the insteon hub and then update it in the insteon plugin? Have you tried a new IP address for the HOOBS™ box?

@kuestess https://github.com/kuestess I have not been able to reproduce the error that these 3 are seeing, thats why I do not think it is a HOOBS™ box issue, also there is a new user that is using a mac mini, also the almost 900 people using the HOOBS™ insteon discord channel would be reporting this as well... Same with the plugin, there are only a handleful of users that have this issue... I still think that there is something to do with these 3 users settings somewhere... Are you able to remote in with them individually and check their plugin settings/ IP addresses/...

— Reply to this email directly, view it on GitHub https://github.com/kuestess/homebridge-platform-insteonlocal/issues/288#issuecomment-1455209450, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMOOUEAV2RM5WNGXA4FVPZ3W2T7N7ANCNFSM6AAAAAAT264J2Y. You are receiving this because you were mentioned.Message ID: @.***>

[AstonMartin715]

Same here. I've been dealing with this for 9 months so have been up to date on every version since then. We cleared the caches together when we were on our 2nd support call. Per my notes in this thread I installed the Merross plug in which works fine. By definition when I set up the VLAN both devices (Hoobs and Insteon) got new IP addresses, and then they got new ones when I moved them back to the primary network. And for completeness, I have reflashed the Hoobs box twice, and replaced the Insteon hub once.

[kuestess]

@AstonMartin715 @greg-e-ctrl One thing to try is to run node in debug mode - normally you would do this at the command line by running DEBUG=* homebridge -D but I have no idea how to do this in Hoobs. @zzack01 How can users do this in hoobs? The key part is the DEBUG=* prefix (it's not enough to run only homebridge in debug mode). It'll spit out a lot of messages, but may give a better clue as to what's going on.

[AstonMartin715]

@kuestess I was able to create a home bridge container and it says it's running in Docker but I cannot get to it via the IP address of the Mac on which I installed it and port 8580. Any ideas?

[kuestess]

@AstonMartin715 What OS are you running on?

[AstonMartin715]

Ventura 13.1

[AstonMartin715]

Is this the issue with my homebridge installation not working on Docker on the Mac? https://github.com/docker/for-mac/issues/68

[AstonMartin715]

Gave up on Docker. Found my old Raspberry Pi 3.0, installed homebridge and the Insteon plugin. Will see how long it stays up and report back.

[AstonMartin715]

Exact same issue with homebridge. Works great for a while then doesn’t. But according to the log thinks it is still controlling the Insteon. I have now swapped out the hardware (raspberry pi), the controller (homebridge vs hoobs) and the Insteon box. All that’s consistent is the plug-in, my network and the house! Any ideas guys?

[greg-e-ctrl]

Thank you @AstonMartin715 for debugging this for us all!They should be able to pinpoint the issue @. and @kuestess: What are the next steps you will take to resolve this?Thanks all and have a nice weekend!--GregOn Mar 16, 2023, at 9:16 PM, AstonMartin715 @.> wrote: Exact same issue with homebridge. Works great for a while then doesn’t. But according to the log thinks it is still controlling the Insteon. I have now swapped out the hardware (raspberry pi), the controller (homebridge vs hoobs) and the Insteon box. All that’s consistent is the plug-in, my network and the house! Any ideas guys?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[kuestess]

@greg-e-ctrl That depends upon what @AstonMartin715 homebridge debugging tells us.

[AstonMartin715]

[17/03/2023, 15:28:10] [InsteonLocal] Setting level of Master Bed Chandelier to 100% [17/03/2023, 15:28:10] [InsteonLocal] Master Bed Chandelier is on at 100% [17/03/2023, 15:37:34] [InsteonLocal] Received command for 3CE278 [17/03/2023, 15:37:34] [InsteonLocal] Found 1 accessories matching 3CE278 [17/03/2023, 15:37:34] [InsteonLocal] Hub command: {"standard":{"type":"50","id":"3CE278","gatewayId":"000001","extended":false,"messageType":6,"hopsLeft":3,"maxHops":3,"command1":"13","command2":"00","raw":"02503CE278000001CF1300"}} [17/03/2023, 15:37:34] [InsteonLocal] Got event for Master Bed Chandelier (3CE278) [17/03/2023, 15:37:34] [InsteonLocal] Got off event for Master Bed Chandelier [17/03/2023, 15:37:34] [InsteonLocal] Got off event for Master Bed Chandelier [17/03/2023, 15:37:34] [InsteonLocal] No group members defined for Master Bed Chandelier [17/03/2023, 15:37:39] [InsteonLocal] Received command for 3CE278 [17/03/2023, 15:37:39] [InsteonLocal] Message is from keypad, filtering non-keypad devices. [17/03/2023, 15:37:39] [InsteonLocal] Found 0 accessories matching 3CE278 [17/03/2023, 15:37:39] [InsteonLocal] Hub command: {"standard":{"type":"50","id":"3CE278","gatewayId":"4C02B4","extended":false,"messageType":2,"hopsLeft":0,"maxHops":0,"command1":"13","command2":"01","raw":"02503CE2784C02B4401301"}} [17/03/2023, 15:37:39] [InsteonLocal] Received command for 3CE278 [17/03/2023, 15:37:39] [InsteonLocal] Message is from keypad, filtering non-keypad devices. [17/03/2023, 15:37:39] [InsteonLocal] Found 0 accessories matching 3CE278 [17/03/2023, 15:37:39] [InsteonLocal] Hub command: {"standard":{"type":"50","id":"3CE278","gatewayId":"4C02B4","extended":false,"messageType":2,"hopsLeft":0,"maxHops":1,"command1":"13","command2":"01","raw":"02503CE2784C02B4411301"}} [17/03/2023, 15:37:39] [InsteonLocal] Received command for 3CE278 [17/03/2023, 15:37:39] [InsteonLocal] Message is from keypad, filtering non-keypad devices. [17/03/2023, 15:37:39] [InsteonLocal] Found 0 accessories matching 3CE278 [17/03/2023, 15:37:39] [InsteonLocal] Hub command: {"standard":{"type":"50","id":"3CE278","gatewayId":"130201","extended":false,"messageType":6,"hopsLeft":3,"maxHops":3,"command1":"06","command2":"01","raw":"02503CE278130201CF0601"}} [17/03/2023, 16:04:23] [InsteonLocal] Received command for 514D10 [17/03/2023, 16:04:23] [InsteonLocal] Received command for 3DEAB4 [17/03/2023, 16:04:23] [InsteonLocal] Received command for 374DFD [17/03/2023, 16:04:24] [InsteonLocal] Received command for 514D67 [17/03/2023, 18:49:11] [InsteonLocal] Command for Master Bed Chandelier: true, time: 1679092090083, delta: 12061795 [17/03/2023, 18:49:11] [InsteonLocal] Command for Master Bed Chandelier: 100, time: 1679104151878, delta: 4 [17/03/2023, 18:49:12] [InsteonLocal] Setting level of Master Bed Chandelier to 100% [17/03/2023, 18:49:20] [InsteonLocal] Command for Master Bed Chandelier: false, time: 1679104151882, delta: 8793 [17/03/2023, 18:49:20] [InsteonLocal] Discard on for Master Bed Chandelier already at commanded state [17/03/2023, 18:49:22] [InsteonLocal] Master Bed Chandelier is on at 100% [17/03/2023, 18:49:33] [InsteonLocal] Command for Master Bed Chandelier: false, time: 1679104151882, delta: 21877 [17/03/2023, 18:49:34] [InsteonLocal] Setting level of Master Bed Chandelier to 0% [17/03/2023, 18:49:44] [InsteonLocal] Master Bed Chandelier is off at 0%

15:28 is the last time I commanded the light via home bridge and it worked. At 18:49 it did not work.

[kuestess]

@AstonMartin715 It looks like the plugin already thought that the 'Master Bed Chandelier' was already on, so it didn't send an on command. There's logic in the plugin intended to reduce the amount Insteon traffic, ie if it's already on then it won't send the command. This tends to be a bit problematic so I may change this behavior to send the command regardless. Try turning oof then on again (doesn't that fix everything) and it should work.

[AstonMartin715]

Sorry I should have mentioned I tested that. BTW I did notice that when it’s not working and I manually press a switch the homebridge doesn’t receive a signal and there’s no entry in the log. In other words homebridge and Insteon aren’t talking to each other.

[kuestess]

@AstonMartin715 Gotcha. What do you have keepAlive set to in your config?

[greg-e-ctrl]

Hi @zach HOOBS Team and @kuestess Insteon Team,

Would you be willing to let @AstonMartin715 and myself Beta test the new HOOBS Pro box so we can see if this issue exists in it's Insteon implementation?

The question here is: Is the same code running on the same HW and the same embedded OS inside the Pro box as it is with my current Hoobs box? Hopefully, it is not and it will be re-written when ported over so this issue goes away in the new  HOOBS Pro box implementation. Fingers-crossed!

So, @kuestess, are you porting the Insteon plugin to the new HOOBS Pro Box environment or will the existing Insteon plugin code base work "as is" without rebuilding/recompiling for the new Pro box (meaning most likely the issue will also exist in the new Pro box. Arghhh!!!)?

If it works in the Pro Box, then I will migrate to it and use my current HOOBS box as a paperweight as it currently is being used as! :)

Plus we get support for Matter protocol devices as well in the new HOOBS Pro box!

Thanks!

-- greg

On 3/18/2023 6:33 PM, kuestess wrote:

@AstonMartin715 https://github.com/AstonMartin715 Gotcha. What do you have |keepAlive| set to in your config?

— Reply to this email directly, view it on GitHub https://github.com/kuestess/homebridge-platform-insteonlocal/issues/288#issuecomment-1475062764, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMOOUEG5KBR4CCH6DEOOKN3W4ZO65ANCNFSM6AAAAAAT264J2Y. You are receiving this because you were mentioned.Message ID: @.***>

[AstonMartin715]

@AstonMartin715 Gotcha. What do you have keepAlive set to in your config?

Keep alive defaulted to 0 in homebridge. I really don’t think changing that will make any difference as both @greg-e-ctrl and I tested that extensively with the hoobs box right at the beginning of this thread.

[kuestess]

@AstonMartin715 That's what I'm trying to tease out, whether it's an issue specific to HOOBs and reconnecting with the hub, or with both homebridge and hoobs. Try setting to 3600 and see whether that helps.

[AstonMartin715]

Changing the keep alive setting made no difference. Ran some other tests today. Had Homebridge and Hoobs running together for the first time. Both lost connection to Insteon at exactly the same time. This would point to an issue with the Insteon Hub closing itself off to network connections for some reason. Now remember I have tried 2 different Insteon hubs (same version) and this happens to both. And remember, rebooting the homebridge or Hoobs box (not Insteon) solves the problem every time.

See this interesting link https://github.com/home-assistant/core/issues/70808

[AstonMartin715]

Have we thought of bringing the Insteon guys into this? Clearly Insteon has some code that it uses to identify and ignore network noise, and I think it's seeing the traffic from Homebridge and Hoobs as exactly that. The new management team is very focused on customer service (see the webinars) and might be interested in helping out.

[kuestess]

@AstonMartin715 Interesting thread....can you try running homebridge on your Pi with DEBUG=* homebridge -D. It'll spit out a lot of debug messages, but would be very interesting to see what's in the log when a disconnect happens.

I've talked with the Insteon guys (not about this specifically), but they are (rightfully) focused on rebooting the company right now and have very little time for tech support of a non-product.