hacs-bot[bot]
commented
2 years ago Make sure you have read the issue guidelines and that you filled out the entire template.
Closed jamespreedy closed 2 years ago
hacs-bot[bot]
commented
2 years ago Make sure you have read the issue guidelines and that you filled out the entire template.
ludeeus
commented
2 years ago Your logs do not include the installation/update.
jamespreedy
commented
2 years ago Oh, I'm not quite sure where I went wrong there then. Sorry. I'll try again.
jamespreedy
commented
2 years ago 2022-01-11 09:36:22 DEBUG (MainThread) [custom_components.hacs] Configuration type: ConfigurationType.CONFIG_ENTRY
2022-01-11 09:36:22 INFO (MainThread) [custom_components.hacs] Loaded 12 tasks
2022-01-11 09:36:22 DEBUG (MainThread) [custom_components.hacs] Scheduling HacsTask
jamespreedy
commented
2 years ago @ludeeus - Any better? 🤞🏻🤞🏻🤞🏻
(Literally just had another update come in. Not rebooted to see if it worked yet though ... wanted to make I got you the right logs first.)
ludeeus
commented
2 years ago I do not see an issue in those logs for avanza_stock
jamespreedy
commented
2 years ago OK, great, I'll reboot and see if this one worked. Thank you!!!
ludeeus
commented
2 years ago No need to reboot? You can just look in your config dir
jamespreedy
commented
2 years ago Ah yes, that's true. Well it was in the correct location this time.
Perhaps it was an issue specific to heatmiserneo, I'll reach out to the component creator and see if there's anything I can check the next time they release an update for it.
Thank you for all your help - really appreciate it! 🙏🏻🙏🏻
ludeeus
commented
2 years ago No need, you can just use the downgrade option in HACS for it, restart Home Assistant, and you will be presented with an update. You will get an update button before you restart, but restart before you do it to simulate it properly.
jamespreedy
commented
2 years ago Just updated from heatmiserneo 3d80eb1 to 92126ff. I checked the folder structure and it was correct, hit the update button and checked again before rebooting. I now have the incorrect folder structure again - two nested folders called heatmiserneo. Haven't rebooted yet.
2022-01-11 09:57:02 DEBUG (MainThread) [custom_components.hacs] Configuration type: ConfigurationType.CONFIG_ENTRY
2022-01-11 09:57:03 INFO (MainThread) [custom_components.hacs] Loaded 12 tasks
2022-01-11 09:57:03 DEBUG (MainThread) [custom_components.hacs] Scheduling HacsTask
ludeeus
commented
2 years ago Interesting, seems it has issues since it's a non release repo
jamespreedy
commented
2 years ago Thank you!
System Health details
System Health
Home Assistant Community Store
GitHub API | ok -- | -- Github API Calls Remaining | 4765 Installed Version | 1.19.2 Stage | running Available Repositories | 996 Downloaded Repositories | 13Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | 1 February 2022, 12:00 am relayer_connected | true remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | false remote_server | eu-west-2-0.ui.nabu.casa can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 7.1 -- | -- update_channel | stable supervisor_version | supervisor-2021.12.2 docker_version | 20.10.9 disk_total | 222.8 GB disk_used | 21.0 GB healthy | true supported | true board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | File editor (5.3.3), SSH & Web Terminal (10.0.1), Check Home Assistant configuration (3.9.0), SQLite Web (3.2.0), Duck DNS (1.14.0), Z-Wave JS to MQTT (0.32.2)Lovelace
dashboards | 1 -- | -- resources | 0 views | 11 mode | storageChecklist
Describe the issue
When installing custom_component update, it was installed into the incorrect folder location. Today, I installed a new version of 'heatmiserneo'. https://github.com/MindrustUK/Heatmiser-for-home-assistant
It should have installed into /config/custom_components/heatmiserneo/manifest.json It actually created a new subfolder and installed into /config/custom_components/heatmiserneo/heatmiserneo/manifest.json
This caused the custom_components to fail to load on Home Assistant startup. I was able to move those files into the correct folder manually, and when rebooting it started back up without issue.
I've tried deleting and reinstalling the component just in case, but the issue remained. I've included my debug logs detailing the update this morning below.
Thanks in advance for your help!
Reproduction steps
1 - Update custom_component 2 - Reboot Home Assistant - it will fail to load the component on startup 3 - Move updated component into correct folder structure 4 - Reboot Home Assistant - it will now load the newly updated component correctly.
Debug logs