ollo69 / ha-smartthinq-sensors

HomeAssistant custom integration for SmartThinQ LG devices configurable with Lovelace User Interface.
Apache License 2.0
1.13k stars 158 forks source link

Integration won't load after latest update #668

Closed kevmang closed 8 months ago

kevmang commented 8 months ago

Describe the bug The integration won't load after updating to the latest version

Expected behavior Integration loads and entities appear in HA

Screenshots image

Environment details:

Output of HA logs Logger: homeassistant.config_entries Source: config_entries.py:2087 First occurred: 9:53:06 AM (1 occurrences) Last logged: 9:53:06 AM

Error occurred loading flow for integration smartthinq_sensors: No module named 'custom_components.smartthinq_sensors.wideq.const'

Additional context N/A

ollo69 commented 8 months ago

I think there there is a problem in your installation, seems it is not finding a module. I suggest to full reinstall last release. From 0,36.1 to 0,36,2 there is a very little change and nothing to do with the log error than you provide.

kevmang commented 8 months ago

I think there there is a problem in your installation, seems it is not finding a module. I suggest to full reinstall last release. From 0,36.1 to 0,36,2 there is a very little change and nothing to do with the log error than you provide.

Do you have a recommended method to re-install? I can't uninstall and reinstall using the standard method as the interface won't load so HACS won't let me remove it.

ollo69 commented 8 months ago

This really means that integration folder is broken / corrupted. Fully delete the folder smartthinq_sensor under <home assistant configuration folder>/custom_components, reboot HA and that try to install again with HACS.

kevmang commented 8 months ago

This really means that integration folder is broken / corrupted. Fully delete the folder smartthinq_sensor under <home assistant configuration folder>/custom_components, reboot HA and that try to install again with HACS.

Thanks for the advice - I deleted the folder, removed the integration and re-installed. All working again now!