New Weather Entities Created and Old Entities Orphaned
See original GitHub issueIt appears that v1.1.6 of the BOM integration has created new weather entities and my old entities are orphaned.
I had two entities with entity_id
in the format weather.suburb and weather.suburb_hourly, these are now orphaned and two new entities have been created with the ids weather.home_2 and weather.home_hourly_2. Note, the _2 is somewhat expected as I have other entities from another integration named weather.home.
I also note that the friendly_name
of the new entities is home
and home Hourly
, not using the expected title case.
All of the BOM sensor entities are unaffected.
I’m happy to just rename my entities and remove the old ones, but I thought I would raise an issue as there wasn’t any mention of any breaking changes, and I thought this might not be expected behaviour and could be effecting others.
I’m fairly sure I was running 1.1.5 before without any problems. There are no relevant errors in the Core logs. and restarting Core makes no difference.
Thanks for all your work making this great integration! Let me know if I can provide any more information or help to test.
System Health
version | core-2022.5.4 |
---|---|
installation_type | Home Assistant OS |
dev | false |
hassio | true |
docker | true |
user | root |
virtualenv | false |
python_version | 3.9.9 |
os_name | Linux |
os_version | 5.10.103-v8 |
arch | aarch64 |
timezone | Australia/Sydney |
Home Assistant Community Store
GitHub API | ok |
---|---|
GitHub Content | ok |
GitHub Web | ok |
GitHub API Calls Remaining | 5000 |
Installed Version | 1.24.5 |
Stage | running |
Available Repositories | 1057 |
Downloaded Repositories | 18 |
Home Assistant Cloud
logged_in | true |
---|---|
subscription_expiration | 29 May 2022, 10:00 |
relayer_connected | true |
remote_enabled | true |
remote_connected | true |
alexa_enabled | false |
google_enabled | true |
remote_server | ap-southeast-1-0.ui.nabu.casa |
can_reach_cert_server | ok |
can_reach_cloud_auth | ok |
can_reach_cloud | ok |
Home Assistant Supervisor
host_os | Home Assistant OS 7.6 |
---|---|
update_channel | stable |
supervisor_version | supervisor-2022.05.1 |
docker_version | 20.10.9 |
disk_total | 116.7 GB |
disk_used | 71.0 GB |
healthy | true |
supported | failed to load: Unsupported |
board | rpi4-64 |
supervisor_api | ok |
version_api | ok |
installed_addons | File editor (5.3.3), Samba share (9.6.1), Check Home Assistant configuration (3.10.0), Terminal & SSH (9.4.0), AdGuard Home (4.5.1), Portainer (2.0.0), Home Assistant Google Drive Backup (0.107.2), Studio Code Server (5.0.2), Mosquitto broker (6.1.2), Eufy Security Add-on (0.8.4), RTSP Simple Server Add-on (v0.17.6), Duck DNS (1.14.0), Scrypted (v0.0.177) |
Dashboards
dashboards | 4 |
---|---|
resources | 4 |
views | 19 |
mode | storage |
Spotify
api_endpoint_reachable | ok |
---|
Issue Analytics
- State:
- Created a year ago
- Comments:12 (5 by maintainers)
Closing as 1.1.7 fixes.
Thanks very much for the super quick response and fix. I downgraded to 1.1.5 earlier today and that indeed was a work around, my old entities came back to life. I just updated to 1.1.7 now and all is still working. Great work all!