dubocr / homebridge-tahoma

Homebridge plugin for TaHoma, Connexoon, Cozytouch, Energeasy Connect.
Apache License 2.0
138 stars 42 forks source link

Fail to load lang file: connect ENETUNREACH #469

Closed ozzy332131243 closed 1 year ago

ozzy332131243 commented 1 year ago

Since a few days, the plugin delivers the following error, resulting in crashing Homebridge after a while. Any clue whats wrong and how to fix it?

[4/11/2023, 7:49:02 AM] Homebridge v1.6.0 (HAP v0.11.0) (Homebridge 4999) is running on port 51826. [4/11/2023, 7:49:03 AM] [TaHoma] Launched child bridge with PID 7118 [4/11/2023, 7:49:04 AM] Registering platform 'homebridge-tahoma.Tahoma' [4/11/2023, 7:49:04 AM] [TaHoma] Loaded homebridge-tahoma v2.2.54 child bridge successfully [4/11/2023, 7:49:04 AM] Loaded 0 cached accessories from cachedAccessories.0E13527A8AB1. [4/11/2023, 7:49:04 AM] Homebridge v1.6.0 (HAP v0.11.0) (TaHoma) is running on port 48839. [4/11/2023, 7:49:04 AM] [TaHoma] connect ENETUNREACH 178.32.15.131:443 - Local (0.0.0.0:0) [4/11/2023, 7:49:04 AM] [TaHoma] Retry in 60 sec... [4/11/2023, 7:49:04 AM] [TaHoma] Fail to load lang file: connect ENETUNREACH 178.32.15.131:443 - Local (0.0.0.0:0)

...

[4/11/2023, 7:49:57 AM] Error: send ENETUNREACH 224.0.0.251:5353 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) [4/11/2023, 7:49:57 AM] Got SIGTERM, shutting down Homebridge... [4/11/2023, 7:49:57 AM] [TaHoma] Error: send ENETUNREACH 224.0.0.251:5353 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) { errno: -101, code: 'ENETUNREACH', syscall: 'send', address: '224.0.0.251', port: 5353 } [4/11/2023, 7:49:57 AM] Got SIGTERM, shutting down child bridge process... [4/11/2023, 7:50:02 AM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null

tahomauser123 commented 1 year ago

I can confirm this issue. However my log is a bit different: [4/11/2023, 8:44:50 PM] [TaHoma] Launched child bridge with PID 17047 [4/11/2023, 8:44:50 PM] Registering platform 'homebridge-tahoma.Tahoma' [4/11/2023, 8:44:51 PM] [TaHoma] Loaded homebridge-tahoma v2.2.54 child bridge successfully [4/11/2023, 8:44:51 PM] Loaded 32 cached accessories from cachedAccessories.0E3C2B212BD8. [4/11/2023, 8:44:51 PM] Homebridge v1.6.0 (HAP v0.11.0) (TaHoma) is running on port 48957. [4/11/2023, 8:45:11 PM] [TaHoma] getaddrinfo EAI_AGAIN ha101-1.overkiz.com [4/11/2023, 8:45:11 PM] [TaHoma] Retry in 60 sec... [4/11/2023, 8:45:11 PM] [TaHoma] Fail to load lang file: getaddrinfo EAI_AGAIN ha101-1.overkiz.com [4/11/2023, 8:46:11 PM] [TaHoma] getaddrinfo EAI_AGAIN ha101-1.overkiz.com [4/11/2023, 8:46:11 PM] [TaHoma] Retry in 120 sec...

tahomauser123 commented 1 year ago

Today I have restarted the Tahoma Plugin once again and this time it worked fine.

ozzy332131243 commented 1 year ago

Unfortunately, my error is persistent. Another restart didn't solve the issue.

tahomauser123 commented 1 year ago

The error occurred as there was an IP address conflict in my network. Once I habe solved it rebooted the the device everything worked fine again.

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Please make sure to update to the latest Homebridge TaHoma version to see if that solves the issue. This issue will be closed in case of inactivity.

ozzy332131243 commented 1 year ago

My issue still persists. I can't find any IP address conflicts in my network. Most recent versions of homebridge and all plugins are installed. Can anyone advice how to find the root cause for my problem?

dubocr commented 1 year ago

Hi @ozzy332131243,

Which service are you using ? tahoma europe, tahoma us, cozytouch, rexel ... ?

Thanks

ozzy332131243 commented 1 year ago

I'm using Tahoma Europe. Yesterday, I was able to fix the problem by completely setting up homebridge from scratch. The root cause therefore will remain unclear. Nevertheless everything is again working as expected.