Skip to content
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

Odd Dyson local not supported entries. #35

Closed
GitPetri opened this issue Jun 28, 2023 · 1 comment
Closed

Odd Dyson local not supported entries. #35

GitPetri opened this issue Jun 28, 2023 · 1 comment

Comments

@GitPetri
Copy link

I have 3 Dyson fans. 2 were integrated back in time with the previous Dyson local integration and migrated via the 'Experimental no-reconfiguration swap' -method described in #3 (comment)

Before I added the 3rd device, I also installed the new Dyson cloud integration via HACS. Setting up the new device, everything worked a-ok, got the fan visible via auto-discovery.

The odd thing now is that for the 2 earlier fans, neither entries 'Volatile Organic Compounds' nor 'Nitrogen Dioxide' work. From an entities-card clicking either of them on either of the 2 fans, the notification statement is
This entity is no longer being provided by the dyson_local integration. If the entity is no longer in use, delete it in settings.
For the 3rd fan added lately both the entities work so I can see the values for the parameter.

I assume that regardless that the Dyson local integration was updated to the libdyson-wg -version, there is some legacy conflict with the 2 fans.

Any ideas on how I should re-generate the 2 fans so that they actually use updated Dyson local and would (probably) show the VC and NO₂ entries?

@GitPetri
Copy link
Author

Nevermind, looks there are some ghost entries:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant