Error: addMembership EADDRINUSE

[MaurizioB84]

After restart the plugin generate this error and homebridge cannot start.

Homebridge is installed on docker-compose

homebridge_1 | [8/18/2019, 1:40:20 PM] Error: addMembership EADDRINUSE
homebridge_1 | at Socket.addMembership (dgram.js:581:11)
homebridge_1 | at /usr/local/lib/node_modules/homebridge-shelly/node_modules/coap/lib/server.js:233:24
homebridge_1 | at Array.forEach ()
homebridge_1 | at Socket. (/usr/local/lib/node_modules/homebridge-shelly/node_modules/coap/lib/server.js:232:42)
homebridge_1 | at Object.onceWrapper (events.js:286:20)
homebridge_1 | at Socket.emit (events.js:198:13)
homebridge_1 | at startListening (dgram.js:128:10)
homebridge_1 | at state.handle.lookup (dgram.js:249:7)
homebridge_1 | at process._tickCallback (internal/process/next_tick.js:63:19)
homebridge_1 | [8/18/2019, 1:40:21 PM] Got SIGTERM, shutting down Homebridge...

[MaurizioB84]

when I remove the plugin the error not happening.... I'm sure the error is on the plugin

[AlexErl]

I have the same issue. First I added a shelly 2.5 shutter and got this error. I fixed this with the "NetworkInterface" option.
Now, I added a second shelly to the network and the error popped up again.
I have also a Docker Pi-hole container running on the same PI.

I uninstalled the plugin, but the shellys are still discovered. I also deleted the CachedAccessories, but without success.
Do you have a clue why adding a second shelly to the network is bringing up that error again.

[MaurizioB84]

I resolve the issue for now but I think is temporary fix.
I following steps:
1 - remove network manager libraries (apt-get remove)
2 - stop and delete container plus all file in accessories and persist folder
3 - docker prune -all (in order to remove all file related and the image of homebridge) --> maybe not needed but in order to update all I prefer to procede in this way.
4 - docker start with the same configuration and now it's work...

[alexryd]

EADDRINUSE means that another application is already using the address and port that this plugin is trying to use. This usually occurs when another instance of homebridge is running. Try something like $ ps aux | grep homebridge to see if homebridge is already running.

[MaurizioB84]

I'm sure no other app use the same port, in fact when I reinstall all it's work

[alexryd]

Try adding "networkInterface": "<device-ip>" to the config, where <device-ip> is the local IP address of whatever you are running homebridge on.

[AlexErl]

That is what I did when I added my first shelly 2.5 to the homebridge.
The temp. solution for me is that I uninstalled the docker-ce.
Did you already tested it with installed docker-ce?

[Frucoboti]

Try adding "networkInterface": "<device-ip>" to the config, where <device-ip> is the local IP address of whatever you are running homebridge on.

Hello,

Please confirm that is the IP of the Raspberry or the IP of the Shelly.
In my case I have 4 Shelly installed.

Thanks

[alexryd]

The IP address of your Raspberry Pi.

[Frucoboti]

Thanks!, running ok again.

[thechris1992]

Please close it :)