Closed Blogshot closed 1 year ago
@Blogshot can you share the log output from HA, in this case I cannot do anything without it.
There is not much more than what I already posted. I hope this helps.
Logger: homeassistant.setup
Source: setup.py:281
First occurred: 16:36:03 (1 occurrences)
Last logged: 16:36:03
Setup failed for custom integration dreame_vacuum: No setup or config entry setup function defined.
From the logfile itself:
[...]
2023-06-13 16:35:34.906 WARNING (SyncWorker_1) [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
2023-06-13 16:35:34.906 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration dreame_vacuum 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
2023-06-13 16:35:34.907 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration xiaomi_cloud_map_extractor 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
[...]
2023-06-13 16:36:03.788 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration dreame_vacuum: No setup or config entry setup function defined.
[...]
Sadly, the integration has seemingly no way to download diagnostic logs. It might be noteworthy that I installed manually because Github has some weird issues with IPv6, so the native installation via HACS was not doable.
Looks like there is a compatibility issue with the lastest version of the HA. I will fix it and release a new version but i don't have time to work on this project right now. I recommend that you downgrade your HA to previous version(if you can) until this issue is fixed.
I just fixed the issue. :)
The problem is that the manual instructions are wrong. I cloned the dreame-vaccum folder into the custom_components folder like described:
Clone the repository to a folder called custom_components in your Home Assistant root directory, e.g. git clone https://github.com/tasshack/dreame-vacuum ~/.homeassistant/custom_components/dreame-vacuum
Using that command will create a new folder for the repository of the integration, so the complete path to the integration is e.g. homeassistant/custom_components/dreame-vacuum/custom_components/dreame_vacuum
- you can see that path is duplicated and therefore the integration is not positioned correctly.
I had to do mv ./dreame-vacuum/custom_components/dreame_vacuum .
to move the integration to the correct position.
After that, I cleaned up by doing rm -r dreame-vacuum
.
The integration now works and I can see the vacuum and all it's attributes.
It might be worth it to add this detail to the documentation. Or at least keep this issue open until you come around to add it.
I was just trying to reproduce the issue but i couldn't. It is glad to know that i don't need to release a new version but just update the documentation. Thanks for your help and sorry for the inconvenience.
Manual installation method is updated.
Describe the bug After filling the configuration dialog, it showed an error that the integration could not be loaded and to try a reboot of HomeAssistant. The integration then shows no entries or devices and seems generally empty.
After rebooting HomeAssistant, the system log shows this:
Setup failed for custom integration dreame_vacuum: No setup or config entry setup function defined.
To Reproduce
Expected behavior The integration should load successfully. And create enteties for the vacuum.
Screenshots
Additional Information (please complete the following information)