This is how esphome works. You change the name of something in the esphome addon and then flash it, it will show up as a new device.
1 Like
Sure, but then it should no longer show as discovered with some old name…
It’s going round in circles
Moreover, this happened after the Esphome update, they were fine before that.
Must be some hidden registry that brought back the old name
Home assistant doesn’t know that old named device is what you renamed, it assumes I the device is alive, just unreachable. Like every other device in HA. This is nothing new. Delete it or disable it.
1 Like
I think you have a miss-understanding on how esphome works with home assistant. Home assistant and Esphome do not talk to each other. Esphome only talks to the devices it manages. Home assistant only searches your network for esphome devices. You don’t even need the esphome addon for home assistant to work with your devices that have esphome flashed on them.
If you make changes in Esphome to your device, home assistant core is unaware of that change because it’s only looking for your devices.
2 Likes
that seems abundantly clear… Still a noob in that department.
as I faintly start to understand that, my name changes we’re done in the ESPhome dashboard, and while I did that, the new name was accepted, but at the same time, the old or maybe original named device was discovered. All still inside the Dashboard.
these devices in the esphome integration, so HA core indeed, have been around for some time now, and weren’t changed:
however, it was not after deleting one of these, and have it re-discovered in the integration during restart, the devices in the Esphome Dashboard were as posted above, 3 online devices, no more old name device discovered.
So it seems HA isnt completely agnostic to Esphome, or vice versa…
well, tbh, this I don’t understand. I would expect any (name) change made in the HA UI, to be propagated throughout the full HA system. Being all Core.
I dont have any other Add-on with devices to compare this with, but as an end-user this is utmost confusing.
And, I repeat, its only inside the ESPHome the issue arises, not in HA Integrations, these were all still fine and reflecting the correct states
1 Like
Will there be a 2022.10.5 with the time zone fix for Tibber which was merged to dev some days ago?
The PR isn’t tagged with 10.5, so it’s likely in the next release.
Ohh. That is probably a misstake, the bug is rendering the implementation more or less useless for automating based on current price as it’s 2h off due to a time zone issue.
Is there a way to add that tag?
That’s up to whoever manages the builds. No clue who does that. Sorry.
Just a quick reminder that between 10.2 and 10.4 - someone broke the ‘health check’ ( [‘HomeAssistantCore.update’ blocked from execution, system is not healthy]) to mark the system as unhealthy when Portainer is installed alongside HA in docker.
A really bad misstep by whomever radically changed the health check to care about other docker containers running alongside HA, and break the update functionality.
A kludge to get around the dev who did this is to stop Portainer and do updates from now on:
docker stop portainer
Alternatively, some have noted that simply renaming the docker container avoid this very poorly designed health check:
docker tag portainer/portainer-ce:latest p0rtainer
I only detailed this because these HA nuisance traps, and documentation are getting worse.
This is by design. You can disable the health check if you like. Portainer is not something that the HA team wants people running on supervised systems.
1 Like
How do we disable the health check?
The Health Check page only speaks of it being enabled by default, and how to enable it if not using default_config:
comes with a disclaimer
Latest release 2022.10.5 broke my plugwise integration…
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/plugwise/gateway.py", line 44, in async_setup_entry_gw
connected = await api.connect()
File "/usr/local/lib/python3.10/site-packages/plugwise/smile.py", line 296, in connect
result = await self._request(DOMAIN_OBJECTS)
File "/usr/local/lib/python3.10/site-packages/plugwise/helper.py", line 304, in _request
return await self._request(command, retry - 1)
File "/usr/local/lib/python3.10/site-packages/plugwise/helper.py", line 304, in _request
return await self._request(command, retry - 1)
File "/usr/local/lib/python3.10/site-packages/plugwise/helper.py", line 304, in _request
return await self._request(command, retry - 1)
File "/usr/local/lib/python3.10/site-packages/plugwise/helper.py", line 301, in _request
raise ConnectionFailedError(
plugwise.exceptions.ConnectionFailedError: Plugwise connection error, check log for more info.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 365, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/plugwise/__init__.py", line 13, in async_setup_entry
return await async_setup_entry_gw(hass, entry)
File "/usr/src/homeassistant/homeassistant/components/plugwise/gateway.py", line 50, in async_setup_entry_gw
f"Error while communicating to device {api.smile_name}"
AttributeError: 'Smile' object has no attribute 'smile_name'
That error says it can’t connect. Check your connection first
1 Like
Hi,
Have problem with the lovelace after restart or opened it in browser. My 2 tablet and on my pc too when boot up or open it the lovelace sometime not load correctly. Mixed the things on the dashboard. Sometimes must do 1 or 2 refresh and after good again.
Before not have this problem. 1-2 months ago see this problem first. What happend after HA update and how can I solve it? Cleared cache, but not solved it.
1 Like
same problem
even made a ticket, but now i suspect the manufacturer
maybe an intentional bug in the firmware, for people who don’t use their ecosystem
Could be, I’ve been waiting for someone else to run into this issue as well. Personally, I really don’t like these V2s and I’ll be avoiding them in the future. Not one change on these devices made them better. All regressions.
1 Like