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.

Sign up for GitHub

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

Jump to bottom

VeSync integration - Levoit 200S shows as unknown device #127066

Open
bru73f0rc3 opened this issue Sep 30, 2024 · 4 comments · May be fixed by #127616
Open

VeSync integration - Levoit 200S shows as unknown device #127066

bru73f0rc3 opened this issue Sep 30, 2024 · 4 comments · May be fixed by #127616
Labels
integration: vesync

Comments

@bru73f0rc3
Copy link

The problem

The VeSync integration shows my Levoit Vital 200S (LAP-V201S-AUSR) as an Unknown Device Type:
[homeassistant.components.vesync.fan] Office L200S - Unknown device type - LAP-V201S-AUSR

This seems possibly resolved in pyvesync as noted in: webdjoe/pyvesync#197

What version of Home Assistant Core has the issue?

2024.9.3

What was the last working version of Home Assistant Core?

2024.9.3

What type of installation are you running?

Home Assistant Container

Integration causing the issue

VeSync

Link to integration documentation on our website

https://www.home-assistant.io/integrations/vesync

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

[homeassistant.components.vesync.fan] Office L200S - Unknown device type - LAP-V201S-AUSR

Additional information

No response
@home-assistant
Copy link

Hey there @markperdue, @webdjoe, @TheGardenMonkey, @cdnninja, mind taking a look at this issue as it has been labeled with an integration (vesync) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of vesync can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign vesync Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

vesync documentation
vesync source
(message by IssueLinks)

@bru73f0rc3
Copy link
Author

Note, to fix this all you need to do is update ../components/vesync/const.py with
"LAP-V201S-WUS": "Vital200S", # Alt ID Model Vital200S
"LAP-V201-AUSR": "Vital200S", # Alt ID Model Vital200S
"LAP-V201S-AUSR": "Vital200S", # Alt ID Model Vital200S

Been testing it and seems to work just fine.

@cdnninja
Copy link
Contributor

cdnninja commented Oct 5, 2024

Excellent thanks for testing that! Do you want to create a pull request with those additional alt ids or would you like me to?

@bru73f0rc3 bru73f0rc3 linked a pull request Oct 5, 2024 that will close this issue
Open
18 tasks
@bru73f0rc3
Copy link
Author

Done, please let me know if anything else is needed. thanks! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
integration: vesync
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added an additional Alt ID for the Vital200S bru73f0rc3/core
2 participants
@bru73f0rc3 @cdnninja