Docker, addMembership EADDRINUSE

[Frucoboti]

Hello,

Last week I added the plugin to my local homebridge on the RPI3 and worked fine.
I have recently installed docker to test hass.io. Worked ok too. But I think that I didn't reboot RPi.
Today I have updated and upgraded Raspbian, so the RPi has been reseted. I started to receive addMembership EADDRINUSE error, and entered in infinite loop.
I have decided to delete local installation of Homebridge and install it on docker.
First instance worked fine with homebridge-shelly plugin. When added started with same addMembership EADDRINUSE error.
So I decided to create a second instance of Homebridge on docker, to don't shut down the first one.
The error still appear. This is part of the log:

---

homebridge-shelly_1 | Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
homebridge-shelly_1 |
homebridge-shelly_1 | ┌────────────┐
homebridge-shelly_1 | │ 292-25-059 │
homebridge-shelly_1 | └────────────┘
homebridge-shelly_1 |
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] [Shelly] 0 devices loaded from cache
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] Homebridge is running on port 52724.
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] [Shelly] New device discovered: SHSW-PM E677F4 at 192.168.1.114
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] [Shelly] New device discovered: SHSW-PM E5DEA3 at 192.168.1.115
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] [Shelly] New device discovered: SHSW-25 688491 at 192.168.1.116
homebridge-shelly_1 | [9/2/2019, 11:49:45 PM] [Shelly] New device discovered: SHSW-PM E67B9C at 192.168.1.113
homebridge-shelly_1 | [9/2/2019, 11:49:46 PM] Error: addMembership EADDRINUSE
homebridge-shelly_1 | at Socket.addMembership (dgram.js:581:11)
homebridge-shelly_1 | at /homebridge/node_modules/homebridge-shelly/node_modules/coap/lib/server.js:233:24
homebridge-shelly_1 | at Array.forEach ()
homebridge-shelly_1 | at Socket. (/homebridge/node_modules/homebridge-shelly/node_modules/coap/lib/server.js:232:42)
homebridge-shelly_1 | at Object.onceWrapper (events.js:286:20)
homebridge-shelly_1 | at Socket.emit (events.js:198:13)
homebridge-shelly_1 | at startListening (dgram.js:128:10)
homebridge-shelly_1 | at state.handle.lookup (dgram.js:249:7)
homebridge-shelly_1 | at process._tickCallback (internal/process/next_tick.js:63:19)
homebridge-shelly_1 | [9/2/2019, 11:49:46 PM] Got SIGTERM, shutting down Homebridge...
homebridge-shelly_1 | [9/2/2019, 11:49:46 PM] [Config] Homebridge Config UI X v4.6.1 is listening on :: port 8081
homebridge-shelly_1 | -U /homebridge -P /homebridge/node_modules -C

And this is th docker-compose.yml created:

---

version: '2'
services:
homebridge:
image: oznu/homebridge:raspberry-pi
restart: always
network_mode: host
volumes:
- ./config:/homebridge
environment:
- PGID=1000
- PUID=1000
- HOMEBRIDGE_CONFIG_UI=1
- HOMEBRIDGE_CONFIG_UI_PORT=8080
homebridge-shelly:
image: oznu/homebridge:raspberry-pi
restart: always
network_mode: host
volumes:
- ./config-shelly:/homebridge
environment:
- PGID=1000
- PUID=1000
- HOMEBRIDGE_CONFIG_UI=1
- HOMEBRIDGE_CONFIG_UI_PORT=8081

I have removed Hassio from docker, checked that anything still remain in Raspbian, without luck.

Maybe you can help me. The plugin worked flawlessly until the reboot.

Lot of thanks.

[Frucoboti]

working again with "networkInterface" value.

thanks.