Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Router scheduled reboot causes Bond to stop working in HomeKit #192

Open
BobbieVx opened this issue Dec 20, 2021 · 3 comments
Open

Router scheduled reboot causes Bond to stop working in HomeKit #192

BobbieVx opened this issue Dec 20, 2021 · 3 comments

Comments

@BobbieVx
Copy link

My router is scheduled to reboot at 5am a few times a week and recently every time it does the Bond stops responding in HomeKit. This started happening only a week or two ago and was never an issue previously. The Bond app still works just fine after the router is rebooted. It's like homebridge never bothers to check if the Bond is back online after one time of it losing connection.

[12/19/2021, 5:01:01 AM] [homebridge-bond] Child bridge process ended
[12/19/2021, 5:01:01 AM] [homebridge-bond] Process Ended. Code: 1, Signal: null
[12/19/2021, 5:01:08 AM] [homebridge-bond] Restarting Process...
[12/19/2021, 5:01:08 AM] [homebridge-bond] Launched child bridge with PID 5079
[12/19/2021, 5:01:08 AM] Registering platform 'homebridge-bond.Bond'
[12/19/2021, 5:01:08 AM] [homebridge-bond] Loaded homebridge-bond v3.2.9 child bridge successfully
[12/19/2021, 5:01:08 AM] Loaded 1 cached accessories from cachedAccessories.0E3965D89A31.
[12/19/2021, 5:01:08 AM] Homebridge v1.3.8 (HAP v0.9.7) (homebridge-bond) is running on port 44901.
[12/19/2021, 5:02:59 AM] [homebridge-bond] Unable to find Bond for IP Address: 192.168.1.65. Skipping this Bond.
[12/19/2021, 5:02:59 AM] [homebridge-bond] No valid Bonds available.

@davidmjerry
Copy link

davidmjerry commented Sep 12, 2022

I have a similar issue, though I have no idea what is causing it.
For me this happens every night. A reboot of Homebridge resolves the issue usually.

[Tuya] Sending first query to Desk Lights (3.3)
[Tuya] Heard back from Desk Lights with command 10
[Tuya DEBUG] decrementing this._connectionAttempts, currently 2
[Tuya DEBUG] decrementing this._connectionAttempts, currently 1
[Tuya] Disconnected from Desk Lights
[Tuya] Socket had a problem and will reconnect to Desk Lights (Error: ERR_PING_TIMED_OUT)
[Tuya DEBUG] after error setting _connect in 5000ms
[Tuya DEBUG] executing _connect after 5000ms delay
[Tuya DEBUG] reconnect called for Desk Lights
[Tuya] Sending first query to Desk Lights (3.3)
[Tuya] Heard back from Desk Lights with command 10
[Tuya DEBUG] decrementing this._connectionAttempts, currently 2
[Tuya DEBUG] decrementing this._connectionAttempts, currently 1
[9/12/2022, 12:12:35 AM] [Bond] Erorr sending UDP message: Error: send ENETUNREACH 192.168.1.134:30007
[9/12/2022, 12:12:35 AM] Error: send ENETUNREACH 192.168.1.134:30007
    at doSend (node:dgram:705:16)
    at defaultTriggerAsyncIdScope (node:internal/async_hooks:465:18)
    at afterDns (node:dgram:651:5)
    at processTicksAndRejections (node:internal/process/task_queues:84:21)
[9/12/2022, 12:12:35 AM] Got SIGTERM, shutting down Homebridge...
[Tuya] Socket had a problem and will reconnect to Desk Lights (Error: ERR_PING_TIMED_OUT)
[Tuya DEBUG] after error setting _connect in 5000ms
[9/12/2022, 12:12:40 AM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[9/12/2022, 12:12:45 AM] [HB Supervisor] Restarting Homebridge...
[9/12/2022, 12:12:45 AM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution
[9/12/2022, 12:12:45 AM] [HB Supervisor] Started Homebridge v1.5.0 with PID: 6401
[9/12/2022, 12:12:46 AM] Loaded config.json with 0 accessories and 3 platforms.
[9/12/2022, 12:12:46 AM] Loaded 2 cached accessories from cachedAccessories.
[9/12/2022, 12:12:46 AM] ---
[9/12/2022, 12:12:46 AM] Loaded plugin: homebridge-bond@3.2.10
[9/12/2022, 12:12:46 AM] Registering platform 'homebridge-bond.Bond'
[9/12/2022, 12:12:46 AM] ---
[9/12/2022, 12:12:46 AM] Loaded plugin: homebridge-tuya@2.0.1
[9/12/2022, 12:12:46 AM] Registering platform 'homebridge-tuya.TuyaLan'
[9/12/2022, 12:12:46 AM] ---
[9/12/2022, 12:12:46 AM] Loading 3 platforms...
[9/12/2022, 12:12:46 AM] [TuyaLan] Initializing TuyaLan platform...
[9/12/2022, 12:12:46 AM] [Bond] Initializing Bond platform...
[9/12/2022, 12:12:46 AM] [TuyaLan] Marked Desk Lights unreachable by faulting Service.Desk Lights.On
[9/12/2022, 12:12:46 AM] [TuyaLan] Starting discovery...
Setup Payload:
X-HM://0023UNYTBKAS5
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
                       
    ┌────────────┐     
    │ xxx-xx-xxx │     
    └────────────┘     
                       
[TuyaDiscovery] Discovery started on port 6666.
[TuyaDiscovery] Discovery started on port 6667.
[9/12/2022, 12:12:47 AM] Homebridge v1.5.0 (HAP v0.10.2) (Homebridge 3353) is running on port 51273.
[9/12/2022, 12:13:00 AM] [Bond] Unable to find Bond for IP Address: 192.168.1.134. Skipping this Bond.
[9/12/2022, 12:13:00 AM] [Bond] No valid Bonds available.
[9/12/2022, 12:13:26 AM] [TuyaLan] Discovered Desk Lights (eb546bfb7d1ff8ca8e9igs) identified as RGBTWLight (3.3)

@jondthompson
Copy link

I have the same issue. I've put the bond plugin into a child process, so at least I can reboot just the child process, but I haven't automated that reboot...

@mcg
Copy link

mcg commented Jun 27, 2023

I seem to be having this issue as well. Could be a router restart, power blip, etc... Homebridge comes up and cannot find the Bond. Never retries. It could legitimately not be available during a restart due to a power blip as other network equipment or the Bond itself could not yet be back "up". A connect retry with a backoff seems like a fix here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants