torbennehmer / hacs-e3dc

Homeassistant E3DC Integration
GNU Affero General Public License v3.0
70 stars 8 forks source link

Error: Setup failed for 'e3dc_rscp' since upgrading to 3.5 #103

Closed Michel1973 closed 10 months ago

Michel1973 commented 10 months ago

System Health details

System Information

version core-2024.1.5
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.11.6
os_name Linux
os_version 6.1.71-haos
arch x86_64
timezone Europe/Berlin
config_dir /config
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1377 Downloaded Repositories | 4
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Discovergy api_endpoint_reachable | ok -- | --
Home Assistant Supervisor host_os | Home Assistant OS 11.4 -- | -- update_channel | stable supervisor_version | supervisor-2023.12.1 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 30.8 GB disk_used | 4.3 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Terminal & SSH (9.8.1), Z-Wave JS (0.4.3), File editor (5.7.0)
Dashboards dashboards | 1 -- | -- resources | 0 views | 0 mode | storage
Recorder oldest_recorder_run | 11. Januar 2024 um 19:34 -- | -- current_recorder_run | 21. Januar 2024 um 20:52 estimated_db_size | 245.37 MiB database_engine | sqlite database_version | 3.41.2

Checklist

Describe the issue

I started the update process from the HACS integration. I get the following error after the system reboot.

Error: Setup failed for 'e3dc_rscp' : Integration not found

Reproduction steps

  1. Go to HACS
  2. Start update process
  3. Reboot system

Debug logs

Sorry couldn't get the debugging logs

2024-01-21 20:52:46.408 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration e3dc_rscp which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-01-21 20:52:46.408 ERROR (SyncWorker_4) [homeassistant.loader] The custom integration 'e3dc_rscp' does not have a valid version key (untagged-a66f76cbe32ae9999176) in the manifest file and was blocked from loading. See https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions for more details
2024-01-21 20:52:46.410 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration awattar_energy_cost which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-01-21 20:52:46.411 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-01-21 20:52:54.037 ERROR (MainThread) [homeassistant.setup] Setup failed for 'e3dc_rscp': Integration not found.

Diagnostics dump

No response

goebelmeier commented 10 months ago

+1, can reproduce

Thomansky commented 10 months ago

+1, can reproduce

Matthias1111 commented 10 months ago

+1, can reproduce

torbennehmer commented 10 months ago

Pleas try if reloading the entire repo helps. I made an error when creating the release. It was fixed quickly, but apparently not quick enough. I beg your pardon here.

Thomansky commented 10 months ago

I completely reloaded the project but unfortunately this didn't help

Michel1973 commented 10 months ago

I have reloaded version 3.5. But this did not help. So I reinstalled the previous version. This is running now.

I will retry the update to 3.5.

torbennehmer commented 10 months ago

I've just repushed 3.5.0. to 3.5.1, i hope that this fixes things, could you check if you can cleanly move to this release?

bmause commented 10 months ago

Ich habe gerade 3.5.0. auf 3.5.1 zurückgeworfen, ich hoffe, dass dies die Dinge behebt, könnten Sie überprüfen, ob Sie sauber zu dieser Version wechseln können?

gerade mit 3.5.1 upgedatet, geht wieder :-)

Thomansky commented 10 months ago

Ja, geht wieder alles

Matthias1111 commented 10 months ago

Confirmed as well. Upgrade from 3.4.3 to 3.5.1 is working now (I rolled back from 3.5.0 to 3.4.3 yesterday.

Michel1973 commented 10 months ago

Confirm that this fix is working. Thank you for your quick support

torbennehmer commented 10 months ago

Thanks for your patience!