[Support] Shelly 1 not discovered in Homebridge

[newbiech]

Want to use a Shelly 1 as a switch to open garage door within HomeKit via Homebridge. Not using it as a garage door opener as there is no need for security (i.e. avoid confirmation within HomeKit).

My environment:

• Homebridge installed on Raspi4, IP 192.168.2.4:8080 (long time running installation without issues), hardwired
• Plugin homebridge-shelly v0.18.0
• Shelly 1 (recent beta FW 20210514-065742/v1.10.5-rc1-gecc99b7), IP 192.168.2.17:80, WIFI

I can access the Shelly via http without issues.

Settings on the Shelly 1:

• ColoT peer set to 192.168.2.4:8080 (also tried with mcast)
• Device discoverable YES
• Authentication disabled
• other settings not of importance I guess?

Homebridge Config: { "name": "Shelly", "admin": { "enabled": true }, "devices": [ { "id": "8CAAB5552E95" } ], "platform": "Shelly" }

Rebooted the Shelly and the Homebridge several times. However, the Shelly is not being discovered. Tried with set "networkInterface": "192.168.2.17" won't work either.

Previously, I have utilized the Shelly with the Mongoose FW (https://github.com/mongoose-os-apps/shelly-homekit/wiki/Garage-Door-Opener-Settings) and utilized it as a GarageDoorOpener. This worked well. However, I wanted to open the garage door automatically once my wife and me come home and such automation required a confirmation - what I want to avoid.

Can anyone guide me through troubleshooting?

[alexryd]

• ColoT peer set to 192.168.2.4:8080 (also tried with mcast)

CoIoT (CoAP) runs on port 5683 so try changing this setting to 192.168.2.4:5683. You can probably also just omit the port number (192.168.2.4).

[chiefcw]

@newbiech You can use a dummy switch to avoid the HomeKit confirmation. Just set your automation to turn on the switch and have the switch set in an automation to open the garage door.

[mflannery]

I opened ports 5683/tcp and 5683/udp on the server that is running homebridge and this allowed the device to connect to homebridge. The button was then “discovered” in the homebridge-shelly admin webpage and the button just showed up in homekit.

I am not sure if you need the /tcp or /udp port to be opened. Opening just 5683/tcp did not do anything so I also opened up 5683/udp. Could have been a time delay or it could be that you need the /udp port opened. Either way, it started working after opening them up.