Shelly integration replaces hostnames with IP addresses

[IngmarStein]

The problem

I'd like to configure my shellies using host names to make the integration more resilient against IP address changes. I've configured fixed IP reservations in the DHCP server, but I'd like to remove those and be able to, for example, move the devices from one VLAN to another without manually adjusting all IP addresses in the HA integration.

To that end, I've re-configured each integration to use a local hostname and these appear to stick for a while, but they are eventually replaced again with IP addresses. Is there a way to prevent replacement of the hostname or is that even unnecessary because auto-discovery would pick up new IP addresses anyway and match them with existing devices?

What version of Home Assistant Core has the issue?

2024.7.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

No response

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

[rrooggiieerr]

Looking at the Shelly integration source code (config_flow.py) the integration will take care of IP changes

[IngmarStein]

Excellent. Matching by MAC address or some other unique identifier provides the stability for the use case I mentioned.
If replacing the user-specified hostname is working as intended, please feel free to close this issue. If not, it's essentially just a cosmetic issue.

[home-assistant]

Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of shelly can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign shelly Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

shelly documentation
shelly source
_{^{(message by IssueLinks)}}

[thecode]

To that end, I've re-configured each integration to use a local hostname and these appear to stick for a while, but they are eventually replaced again with IP addresses.

This is by design, we translate the hostname to IP and store the IP.

Is there a way to prevent replacement of the hostname or is that even unnecessary because auto-discovery would pick up new IP addresses anyway and match them with existing devices?

Currently there is no way to prevent replacing the hostname, the integration will update the IP according to mDNS advertisements from the device (based on MAC). This should also work if you move the device into another VLAN (may take some time or device reboot)

[IngmarStein]

Alright, thanks for clarifying.