Levoit classic 300s vesync not showing

brainbudt commented 2 years ago

The problem

I'm getting the following error when trying to install the vesync module

Logger: homeassistant.components.vesync.fan Source: components/vesync/fan.py:105 Integration: VeSync (documentation, issues) First occurred: 3:15:58 PM (2 occurrences) Last logged: 3:26:37 PM

levoit kantoor - Unknown device type - Classic300S

What version of Home Assistant Core has the issue?

2022.5.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

Hey there @markperdue, @webdjoe, @thegardenmonkey, 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! _{^{(message by CodeOwnersMention)}}

vesync documentation vesync source _{^{(message by IssueLinks)}}

brainbudt commented 2 years ago

any update about this issue?

marleyjaffe commented 2 years ago

I'm also experiencing the same issue with the same error in the log. Running v2022.4.7 currently but will report back if anything changes after updating to v2022.7

marleyjaffe commented 2 years ago

Updated to v2022.7 and the issue persists.

MickL commented 2 years ago

I bought the "Dual 200S" in spain and I get the following error:

Humidifier - Unknown device type - LUH-D301S-WEU

I checked the device types that are set within Home Assistant:

https://github.com/home-assistant/core/blob/7c2bd319f1773004d59129ea9a21ca23a24f61df/homeassistant/components/vesync/const.py#L23

And compared them to the ones from Pyvesync:

https://github.com/webdjoe/pyvesync/blob/f50ce620857f8810723039d548b1961ea6bf4cd2/src/pyvesync/vesyncfan.py#L10

And as far as I see there are tons of models missing in Home Assistant including your "Classic300S" and my "LUH-D301S-WEU". So the quick and easy fix would be to add the missing devices to the list.

Kertz1954 commented 2 years ago

I get the following with core 2022.7.3

Logger: homeassistant.components.vesync.fan Source: components/vesync/fan.py:78 Integration: VeSync (documentation, issues) First occurred: 11:32:52 AM (1 occurrences) Last logged: 11:32:52 AM

humber - Unknown device type - Classic300S

It would be better to add this to the supported list of devices, or remove the discovery of it.

As it stands now, the waning message is actualy a bug.

MickL commented 2 years ago

Its not a bug, it has not been added to the list of devices. The list should be updated in general.

MickL commented 2 years ago

I wonder if this integration currently even supports humidifiers that dont have a fan like the Core devices. When checking Pyvesync it has 4 humidifiers (classic, dual and lv devices) and 5 fans (core devices) and I cant find any of the humidfiers in this integration.

I might dig into this more. @epenet @jetpacktuxedo you both made recent changes. Maybe its a quick fix for you compared to me who never even worked with Python?

jetpacktuxedo commented 2 years ago

Probably not a quick fix for me just because I don't have any examples to test against, but I'm happy to lend a hand however I can.

MickL commented 2 years ago

If you make a PR I could test it. My first question would be if im correct and currently no humidifier-only devices are supported, only fan-humidifiers?

jetpacktuxedo commented 2 years ago

My reading of it says that is correct. They might accidentally be supported by the fan.py devices, but it's unlikely. You'd probably want a new humidifier.py file that implements the homeassistant humidifier stuff as defined in this documentation. That's a bigger change than anything I've done, but large parts of it can likely be copied from fan.py.

kernelpanic85 commented 2 years ago

+1 for humidifier support. I just bought a Classic 200S and it doesn't show up in Home Assistant, but is available in the Vesync app. Happy to help test anything.

ChrisRomp commented 1 year ago

Getting error for 300S:

[homeassistant.components.vesync.fan] Kids Humidifier - Unknown device type - Classic300S

PCServices2 commented 1 year ago

Request to add support for the LV600S and the Classic 300S. I have one of each and would love to be able to manage them through HA.🤞👍

gquerbes commented 1 year ago

I am working on getting VeSync humidifiers integrated. I have a Classic300S but if anyone has a Classic200S, Dual200s, or LV600S and want to help test please let me know. So far I have successfully implemented the humidity reading, setting humidity levels, and setting modes. I still want to integrate the night light for models that support is, as well as the empty bucket notification. This would be my first contribution to HomeAssistant so my apologies if it takes me a while to get this completed and submitted.

kernelpanic85 commented 1 year ago

I have a Classic200S and can help test.

gquerbes commented 1 year ago

I finished up for the most part but at the moment only added support for Classic300S, Classic200S, and Dual200S. I've only been able to test the 300S.

Features: -Humidity Control -Changing Modes -Humidity Sensor -Bucket Removed Sensor -Bucket Empty Sensor

Bugs: -Turning power on/off from device or VeSync app do not update back to HASS

Future: -Implement other models -Implement night light control

If anyone knows how to test and would like to give it a try. https://github.com/gquerbes/HomeAssistant_core/tree/feature/VesyncHumidifier

gquerbes commented 1 year ago

Ignore me, looks like someone recently added all the feature I did and more. I'm running it locally and it works great so far https://github.com/vlebourl/custom_vesync

kevin-brown commented 1 year ago

For general awareness, I'm working on implementing humidifiers in the core at https://github.com/home-assistant/core/pull/84025 and would welcome device testing. This doesn't have all of the features of the custom components floating around, this is just trying to get the initial support off the ground in the core.

Ryukenden88 commented 1 year ago

i got a lv600s and receive the message: Levoit Humidifier - Unknown device type - LUH-A602S-WUS

a guy on discord has it working with your integration so im not sure why it doesn't on mine.

KyleStilkey commented 1 year ago

I have the 450S and I'd love to test this out, how would I go about testing this would be much appreciated!

mangp commented 1 year ago

I have the LUH-D301S-WEU and will also be ready for testing

chuckdeal97 commented 1 year ago

It's been at least two years since the first attempts to officially add humidifier support to the vesync integration. Based on reading the comments, each of these attempts appears to be working for a small population that is testing locally as a custom component, with one attempt actually packaging via HACS. I would love for this community to pick a winner - the solution that establishes the baseline support - and get it approved and merged. Here's what I have seen so far:

Issues:

This issue (#72709)
The oldest related issue that was closed due to inactivity (https://github.com/home-assistant/core/issues/44865)

PRs:

This is the oldest solution to the issue (https://github.com/home-assistant/core/pull/62907)
- This appears to have really good coverage of the humidifier device and entities
- lacks any unit tests
It seems to be the basis of a HACS custom_component (https://github.com/vlebourl/custom_vesync)
- Based on PR #62907 and has commits as recent as 3 weeks ago
- It also appears to lack any unit tests
https://github.com/home-assistant/core/pull/84025
- This is similar in implementation to PR #62907, yet I don't think went as far in terms of the related entities
- This solution added unit tests to cover the new work
- I branched from this PR to make a few modifications and improve testing (https://github.com/chuckdeal97/hass-core/tree/vesync-humidifier-kb)

The Ask

I'm hoping to use the collective wisdom of this community to plot a path forward. Which of the above solutions can we get behind to get this integration moving again? What is the best way to do it? Do we promote the existing issue/PR? Or create a new PR and close the other items?

chuckdeal97 commented 1 year ago

As I mention on the PR (https://github.com/home-assistant/core/pull/62907#issuecomment-1445461485) I made an attempt to rebase (and get working) the code from jspayd's branch. Unfortunately, I'm not sure where to go from here.

It's possible that I should just create a new PR based on my branch (https://github.com/chuckdeal97/hass-core/tree/jspayd-vesync-humidifier) and recommend that the original be closed.

KyleStilkey commented 1 year ago

Sorry I read your thread wrong, I see what you are asking, I'd say close the old ones and just make a new PR.

Nafania commented 1 year ago

Just +1 in queue who is waiting for Classic300S support as well.

chiments commented 1 year ago

I'm not sure if I'm doing this right. Please forgive me. I can confirm the Classic 300S does work by using the official VeSync integration and then installing this over it. https://github.com/vlebourl/custom_vesync

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

kernelpanic85 commented 1 year ago

This is still an issue as humidifier support is still missing in the core integration.

drewsteinacher commented 1 year ago

I too am in line waiting for Classic300S support.

@kernelpanic85 -- do you mean that humidifiers are not supported in Home Assistant Core? How does this relate to the Generic Hygrostat and the Humidifier Card?

sid3windr commented 10 months ago

Coming from OpenHAB to HA, with my LUH-O451S-WEU (Levoit OasisMist 450S) I am surprised it's not supported and this issue has persisted for so long...

+1 to the humidifier support (supported by pyvesync)!

Hooverjc commented 10 months ago

same issue here, just got the 300s and while detected in the diags with all the correct settings, it won't show up due to the error noted above. Seems like this should be a relatively trivial fix unless i'm missing somehting.

Piece-OK commented 9 months ago

I woukd love to see an update for Vesync since I can't even use the "custom_VeSync" version. Turns out that I can't setup HACS for the installation because Github marks my account as "spambot" because I just registered and wanted to initialize HACS with the fresh github account (never needed one as a normie user). So +1 from me

Fields717 commented 9 months ago

I am unable to add https://github.com/vlebourl/custom_vesync to my custom repositories in HACS. I click add and nothing happens. Can anyone assist?

ChrisRomp commented 9 months ago

Make sure you don’t have a space in front of the URL.

On Wed, Dec 20, 2023 at 13:00 Fields717 @.***> wrote:

I am unable to add https://github.com/vlebourl/custom_vesync to my custom repositories in HACS. I click add and nothing happens. Can anyone assist? image.png (view on web) https://github.com/home-assistant/core/assets/153452150/41685cb6-da0e-47f2-acca-1171fd891388

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/72709#issuecomment-1865131326 or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM3DMOKAENWV6BITKS75D3YKNGWXBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIYTEOBSHEYDENRSGGSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKBRGI4DQOBZHEZYFJDUPFYGLJLJONZXKZNFOZQWY5LFVIYTENJSG42TIMRQGWBKI5DZOBS2K3DBMJSWZJLWMFWHKZNKGEZDQMRZGAZDMMRRU52HE2LHM5SXFJTDOJSWC5DF . You are receiving this email because you commented on the thread.

Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

Fields717 commented 9 months ago

ChrisRomp commented Dec 21, 2023 via email

No space. I click add, it spins for a couple of seconds then stops and nothing else occurs. no error, nothing.

evirci commented 9 months ago

ChrisRomp commented Dec 21, 2023 via email

No space. I click add, it spins for a couple of seconds then stops and nothing else occurs. no error, nothing.

i have the same problem. i have buy the LEVOIT OasisMist Smart, but the official integration not find the device. i have to try add hacs ropository, but nothing, no error, no add the integration

Fields717 commented 9 months ago

ChrisRomp commented Dec 21, 2023 via email

No space. I click add, it spins for a couple of seconds then stops and nothing else occurs. no error, nothing.

i have the same problem. i have buy the LEVOIT OasisMist Smart, but the official integration not find the device. i have to try add hacs ropository, but nothing, no error, no add the integration

I was able to get mine to work using this url for the custom repository. I hope this helps @evirci !

https://github.com/micahqcade/custom_vesync

Absoblogginlutely commented 7 months ago

same issue here running in a docker container. I downloaded the custom components from https://github.com/micahqcade/custom_vesync and saved to my config/custom-components directory so I have a vesync folder listed (after creating the custom-components directory) Turning on debug and then attempting to get entities I get the following. Note my email address is mainemail+294@gmail.com

2-14 21:11:30.512 WARNING (MainThread) [homeassistant.components.vesync.fan] bedroom humidifier - Unknown device type - Classic300S 2024-02-14 21:12:54.638 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry something+294@gmail.com for light Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 605, in async_unload result = await component.async_unload_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 682, in async_unload_entry return await component.async_unload_entry(entry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 198, in async_unload_entry raise ValueError("Config entry was never loaded!") ValueError: Config entry was never loaded! 2024-02-14 21:12:54.653 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry something+294@gmail.com for switch Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 605, in async_unload result = await component.async_unload_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/switch/__init__.py", line 105, in async_unload_entry return await component.async_unload_entry(entry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 198, in async_unload_entry raise ValueError("Config entry was never loaded!") ValueError: Config entry was never loaded!

blackovercoat commented 6 months ago

have same issue while trying integrate Levoit Core 300s, I'm runing HA on Virtual Machine

2024-04-03 00:26:11.934 DEBUG (SyncWorker_2) [pyvesync.helpers] [post] calling '/cloud/v1/user/login' api
2024-04-03 00:26:12.847 DEBUG (SyncWorker_13) [pyvesync.helpers] [post] calling '/cloud/v1/user/login' api
2024-04-03 00:26:13.700 DEBUG (SyncWorker_13) [pyvesync.helpers] [post] calling '/cloud/v1/deviceManaged/devices' api
2024-04-03 00:26:14.560 DEBUG (SyncWorker_13) [pyvesync.vesync] New device list initialized
2024-04-03 00:26:47.351 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry xxxx@xxx.com for fan
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 672, in async_unload
result = await component.async_unload_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/fan/__init__.py", line 206, in async_unload_entry
return await component.async_unload_entry(entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 198, in async_unload_entry
raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!
2024-04-03 00:26:47.354 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry xxxx@xxx.com for light
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 672, in async_unload
result = await component.async_unload_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 682, in async_unload_entry
return await component.async_unload_entry(entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 198, in async_unload_entry
raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!
2024-04-03 00:26:47.356 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry xxxx@xxx.com for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 672, in async_unload
result = await component.async_unload_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 145, in async_unload_entry
return await component.async_unload_entry(entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 198, in async_unload_entry
raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!
2024-04-03 00:26:47.359 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry xxxx@xxx.com for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 672, in async_unload
result = await component.async_unload_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/switch/__init__.py", line 105, in async_unload_entry
return await component.async_unload_entry(entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 198, in async_unload_entry
raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!

theHacker commented 5 months ago

Just bought a Classic 300s and as foreseen HA does not pick it up, but issues

Classic 300s - Unknown device type - Classic300S

warnings into the log. But I read up front, so no surprise to me.

I tried the custom HACS integration in a staging installation and it's not an option to me. I also own a Core 300s (the air purifier) and this break my existing entities. The HACS integration does not offer the "PM2.5" sensor anymore, but instead a new diagnose entity "Air quality value" (which seems to be the PM value(?), but unit-less).

I would rather see the Classic 300s integration a) in official HA integration and b) without breaking any existing setup.

I have seen multiple tries of PRs but all got closed on their way. I remember in one PR there was mention of PRs being to large.

My question now: What needs to be done to get Classic 300s support merged in HA core? I would very much try to help and get my device working… and the Classic 300s support into HA :smile: However, I am a little afraid of putting effort into this and then get shutdown on PR, because I went a wrong direction.

issue-triage-workflows[bot] commented 2 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

theHacker commented 2 months ago

Issue still applies to 2024.7.4.

MrcoSchrnr commented 1 month ago

+1 at 2024.7.4

Please fix this!

MrGurns commented 4 days ago

There is a fix ready to go for it, it has just been lost in the process.

See: #90455 Further in here: https://github.com/home-assistant/core/pull/104806

Looks like all the changes in HA next have limited this, so they are still trying to get everything working. Keep an eye out, it is likely to make it across the finish line in a release soon, hopefully.

home-assistant / core