-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't figure out how to actually install ha-dyson or ha-dyson-cloud #144
Comments
same here:
|
Same here: Home Assistant Core 2022.6.5 |
I also have no idea what to do when the repo has been added to HACS. i run the latest version, any help would be greatly appreciated |
Maybe related #138 |
Once you have added the repo in HACS, you then add it via the normal 'integrations' screen (the HACS repo makes it available like a normal integration). edit: Clarification. You need to add the integration per device in the normal 'integrations' screen. |
I'm having a similar issue, installed and downloaded Via HACS, and restarted my Pi but nothing shows up in the HA UI Integrations menu. But I must be doing something wrong as it's not just this Dyson integration. I'm having the same issue with a Tapo integration too. |
With hacs you usually have to clear browser cache before things show up in the integration page |
Same here: "This integration does not support configuration via the UI. If you followed this link from the Home Assistant website, make sure you run the latest version of Home Assistant." |
Same problem. Question - what are the next steps to configure? Some stuff
in a text file?
which text file?
can someone please post a template?
Thanks!
…On Fri, Jul 8, 2022 at 6:48 AM catalinbozianu ***@***.***> wrote:
Same here: "This integration does not support configuration via the UI. If
you followed this link from the Home Assistant website, make sure you run
the latest version of Home Assistant."
—
Reply to this email directly, view it on GitHub
<#144 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEH6NWPIYSJ4LURCVZVVC3VTAWTRANCNFSM5YV6RBTA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Same problem here. Any resolution to install Dyson Cloud? |
I would agree with that assessment as I can reproduce amirook error message if I try to install a new integration while libdyson 0.8.7 is installed, although if I forcibly remove the libdyson 0.8.7 and install 0.8.11 and restart and then try to add a new dyson integration, then I get the normal working web pop up asking "setup using wifi or set up using manual" and all that as normal and if I owned a third fan I predict adding the integration would work. I believe the "This integration does not support configuration via the UI." message and so forth is a red herring in the sense thats just a place holder message when the config crashes because libdyson 0.8.7 is installed and the integration requires 0.8.11 so it can't give you the web UI popups to configure the integration because its already crashed out. Certainly I never configured my integrations using file, I used web UI. I can 100% reliably reproduce both working and non-working situations mentioned above in this bug report by forcing the installation of libdyson 0.8.7 or 0.8.11 at HA startup time. 0.8.7 results in problems seen in this bug report and 0.8.11 works perfectly. I am running HA in a docker container on Intel Ubuntu 20.04 server so I am changing/forcing the libdyson version inside my docker container not the dockerhost. You all, as a group, seem to be using a variety of other HA installation methods, I think. #138 has something else going on where something late in the start up process of HA seems to overwrite my fresh install of 0.8.11 with an older 0.8.7 which makes the SECOND restart after a forced installation of 0.8.7 fail. So that aspect of the problem is weird, but probably not related. |
@vincemulhollon I tried force updating
|
i just commented out line 15 in the init file and it seems to work for me, but hope you don't need that model...... |
The repo has been added to HACS. But I can't figure out the next step
The text was updated successfully, but these errors were encountered: