I’ve been playing with home assistant for a while testing / trialing out items. Today I made the decision that all of the shelly1’s and other items should be on static ip addresses so I can better manage/handle routing etc.
However in doing that, removes their functionality from HA.
I might be blind, but I can’t for the life of me find where you can edit a device/integration to update the associated IP address of the item. Is this not actually possible?
Do you instead have to delete/re-add the deivce and then reassociated/redo the automations/scripts etc?
Surely theres a location where you can edit / modify an item to update its IP address?
Thanking everyone in advance, hopefully theres a way… thought I had to ask before doing it the manual method and re-adding everything.
Hi there, I think it would best to just delete the device and add it again. Even then the shellys should retain their original entity_id and so you wont have to resync any automations or so. Make sure that you restart the device after you delete the shellys before re-adding. I advise you to try this with one device first than deleting all the devices at once.
I do also whish there should be an option to change the ip addres in esphome integration in homeassistant!
Due to the nature of the original desgin (mDNS) most people running esphome on the same subnet as homeassistant have no issue with ip address changes though…
Me, running esphome devices on a separate ssid and disabling mdns… I whish it was possible to change ip addresses without the hassle of deleting integrations and re-adding them.
i am having the same issue. i am moving my iot devices to a separate vlan and ssid, so they’ll get new ip addresses. I’d like to avoid readding the devices to HA, so changing their IP in the config files would be great. i did try the approach suggested by @avonthur but for me the device remains unaivailable, even when updating the ip address in core.config_entiries
Install and run the Terminal addon.
From the Terminal:
Change directory to /config/.storage: cd /config/.storage
Then edit the core.config_entries file: nano core.config_entries
Make changes to this file as you see fit, then use ctrl + x to exit the program, and press y when asked to save and then enter to confirm you want to keep the same filename.
Reboot Home Assisant, and it should work.
If not, there are probably more changes required than you think, and the best solution would just be to delete the integration and start over.
What if the file /config/.storage/core.config_entries doesn’t exist?
Will creating it do anything? what format should it be? json or yaml ?
ok it seems like this is something to do with the studio code server addon. all dotfiles are hidde and the usual vscode tricks to show hidden files are not working.
./frustrating
Ok it’s a "helpful" preconfiguration done by the studio code server addon due to addon authors personally nuanced view of the world.
Thanks @andrix - worked for me. I fixed a changed IP address of a Sony Bravia Android TV. I had changed its IP by adding a DHCP reservation on my DHCP server for the TV. Unlike other integrations, core.config_entries did not update the Sony TV section and still had the old IP.
With core.config_entries updated to new IP, Now Home Assistant can detect again whether the TV is turned on or not and all the other fun stuff.