Open daJuels opened 1 year ago
I had the same problem until I figured out that a container on the Raspberry Pi was causing the trouble. Do you happen to have other containers running at the same time? I turned off the affected container and then everything worked. The only problem I had was that the plugin didn't work for me and the Homebridge expired. I just can't explain why a container produces the error. Ports are different.
I solved the problem by entering the IP address of the Raspberry Pi in the Advanced Settings under Network Interface. Described on the Github page.
My error was slightly different:
Error: addMembership EADDRINUSE
at Socket.addMembership (node:dgram:861:11)
at /homebridge/node_modules/homebridge-shelly/node_modules/coap/lib/server.ts:266:34
at Array.forEach (<anonymous>)
at Socket.<anonymous> (/homebridge/node_modules/homebridge-shelly/node_modules/coap/lib/server.ts:263:58)
at Socket.onListening (node:dgram:257:7)
at Socket.emit (node:events:518:28)
at startListening (node:dgram:183:10)
at node:dgram:371:7
at processTicksAndRejections (node:internal/process/task_queues:83:21)
I'm running HomeBridge as a container with network_mode: host
. Setting IP of the system in Plugin Config -> Advanced Settings -> Network Interface
fixed it. Thanks @bo-2221!
After a Server Restart the plugin is not working anymore. Homebridge keeps restarting.
Homebridge Version: v1.5.0 Plugin Version: v0.19.1
This is the error I get - cannot find anything about this error online.. any clue?
Error: addMembership ENOBUFS at Socket.addMembership (node:dgram:841:11) at /homebridge/node_modules/homebridge-shelly/node_modules/coap/lib/server.ts:266:34 at Array.forEach ()
at Socket. (/homebridge/node_modules/homebridge-shelly/node_modules/coap/lib/server.ts:263:58)
at Socket.onListening (node:dgram:244:7)
at Socket.emit (node:events:527:28)
at startListening (node:dgram:173:10)
at node:dgram:358:7
at processTicksAndRejections (node:internal/process/task_queues:84:21)
Got SIGTERM, shutting down Homebridge...