Multiple shelly devices in Home Assistant pointing to one physical device

dejanpan · November 19, 2024, 1:13pm

Hi there, I would like to cross post this topic because I do not know if it is a HA or a Shelly problem: multiple shelly devices in Home Assistant pointing to one physical device - Shelly 2PM Gen3 - Shelly community.

Please advise if I should’ve not done that. This is my first post in this community.

RonnieLast · November 19, 2024, 1:21pm

Hi. I’d set static IP’s on the Shelly devices and also create a static entry for the specific MAC address within the DHCP lease table. I do this by issuing a dynamic IP first and then converting that entry into a static IP in my router software (eliminates MAC address typos).
Also are you setting the RPC correctly on each Shelly?

I’d specifically use the IP address of HA here and not the .local address. You may then have to delete the Shelly devices from HA and reconfigure them again once the IP’s change, but I have found that they normally work ok without being removed if the RPC is configured properly.

andrejpan · November 19, 2024, 4:12pm

There is an open ticket about this problem from a few days ago.

github.com/home-assistant/core

Shelly Integration requires static/fixed IP for devices

opened 11:46AM - 15 Nov 24 UTC

zapster

integration: shelly

### The problem Due to a router restart, some of my Shelly devices got differen…t IP addresses. This resulted in quite a mess. For some devices, I got a `DeviceConnectionError` because the IP known to HA was no longer in use. Others got an IP that was previously used by a different Shelly device, which resulted in two HA devices controlling the same physical Shelly device, duplication of entities for these devices, and quite some confusion. This is not ideal. Browsing through issues and threads, I often read "static IP or fixed DHCP IP is recommended". I argue that this is not only recommended but a strict requirement and it should be stated prominently under the "Configuration" section of https://www.home-assistant.io/integrations/shelly/. So my suggested short-term fix is to update the documentation accordingly. What it not clear to me is why the Shelly Integration needs to store the device IP to begin with. I'd assume that it identifies the devices by a unique identifier, e.g., the MAC address. Since Shelly devices anyways initiate connection to HA (e.g. via WebSocket), HA could easily wait for this connection and update the internally stored IP address accordingly. However, I'm not familiar with the code so I probably miss something. FWIW, I've had the problem with Shelly Gen3 PM1 and 1 mini devices which use WebSockets. Not sure if Gen1 devices are also affected. ### What version of Home Assistant Core has the issue? core-2024.11.1 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Shelly ### Link to integration documentation on our website https://www.home-assistant.io/integrations/shelly/ ### Diagnostics information _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

@RonnieLast, what did you notice if RPC was not set up? So far, we have not set RPC on Shelly devices.

Sir_Goodenough · November 19, 2024, 4:48pm

Hello Dejan Pangercic,
Welcome to the forum. Let’s see if I can be of any assistance.

Your first post was excellent. You did find an issue that someone has helped you identify.
Don’t be afraid of us, we try not to bite our new friends.
Looking forward to seeing your next post.

RonnieLast · November 19, 2024, 7:55pm

When CoIoT wasn’t configured on Gen-1 Shelly devices you would see latency and slow updates when states changed. I only have two Gen-3 devices so far and have not seen any issues when RPC isn’t configured - so far anyway.