Skip to content

Commit 014bfad

Browse files
bieniuthecodebdraco
authored
Add Shelly push update troubleshooting list (home-assistant#28470)
Co-authored-by: Shay Levy <levyshay1@gmail.com> Co-authored-by: J. Nick Koston <nick@koston.org>
1 parent 6cdda3d commit 014bfad

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

source/_integrations/shelly.markdown

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,17 @@ Generation 1 devices use the `CoIoT` protocol to communicate with the integratio
5151

5252
We recommend using `unicast` for communication. To enable this, enter the local IP address of the Home Assistant server and port `5683` into the **CoIoT peer** field and push **SAVE** button. **This is mandatory for battery operated devices**. After changing the **CoIoT peer**, the Shelly device needs to be manually restarted.
5353

54+
Home Assistant will display a repair issue for the Shelly device if push updates from this device do not reach the Home Assistant server.
55+
56+
The list below will help you diagnose and fix the problem:
57+
58+
- Check if your Shelly devices have a properly configured `CoIoT peer`.
59+
- If you can't find the `CoIoT peer` settings in the device's web panel, it's probably using an ancient firmware version, and you should update it to the current one.
60+
- If Shelly devices are in a different subnet than the Home Assistant server, you should ensure communication on `UDP` port `5683` between these subnets.
61+
- If Home Assistant is running as a virtual machine or service on an operating system other than Home Assistant OS, you should open `UDP` port `5683` on the device's firewall and/or ensure that communication from this port is redirected to the Home Assistant service.
62+
- The missing push updates may be related to the WiFi network range. If using a WiFi network with several access points, enable **Internet & Security** >> **WiFi Client AP Roaming** option. Consider moving Shelly device closer to the WiFi access point. Consider adding another WiFi access point, which will improve the connection quality with the device.
63+
- If you think your Shelly devices are working correctly and don't want to change your network/configuration, you can ignore the repair issue. Still, you must know you are giving up the best experience of using first-generation Shelly devices with Home Assistant.
64+
5465
## Shelly device configuration (generation 2)
5566

5667
Generation 2 devices use the `RPC` protocol to communicate with the integration. Battery powered devices need manual outbound WebSocket configuration, Navigate to the local IP address of your Shelly device, **Settings** >> **Connectivity** >> **Outbound WebSocket** and check the box **Enable Outbound WebSocket**, under server enter the following address:

0 commit comments

Comments
 (0)