Levoit LTF-F422S-WUS not recognised (Levoit Classic 42-Inch Smart Tower Fan) #124123
Comments
|
Hey there @gjohansson-ST, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) systemmonitor documentation |
|
Hey there @markperdue, @webdjoe, @TheGardenMonkey, @cdnninja, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) vesync documentation |
|
This will need support in the underlying library first. |
|
Thanks, I've just marked my PR for pyvesync ready for review, I notice that PR's and Issues in that repo have not been updated for about 6 weeks tho... |
|
I now have the same issue. Is this getting fixed and adding new devices or is it dead and nothing getting done? |
These are now merged once a release is cut, if anyone is interested in contributing their support into home assistant core, feel free! |
|
Underlying API has been updated. #133545 is next to support this. |
|
Could you test 2025.2 and let me know if any issues? |
|
Updates work as expected but state reporting is oddly laggy. It takes about 30s for home assistant to see the fan is on after turning it on. The vesync app correctly sees the stare change immediately. So the api requests are correct. There is also no fan speed percentage reported in the home assistant ui. I’d definitely consider this a good improvement on the road to it working! I’m lacking spare time to help more at the moment, sorry! (New baby). |
|
@mikeyyuen could I get a screenshot of the controls? For a different device this is what mine looks like. You have to click the fan icon to get to it.
As for the state, all vesync switches are impacted by that, we have PRs in the works to fix that. It doesn't reflect until the refresh occurs. |
|
Sure, they appear as follows when on and off
|
|
I can sometimes set a percentage by dragging the bar, the app does respond appropriately, so the requests are going out, but upon turning the fan off then on again it doesn't report the percentage at all. I wonder if when it does read the state from the cloud it interprets the value incorrectly? When I do set it this is how it appears
|
|
That seems accurate depending on mode. The bar is a slider up and down since it has 1-13 speeds from what I can tell, it can't list them all in the space so HA does this instead. It may take a bit to update to reflect the setting though, up to one minute. Same as the on off issue. So try drag to a percentage, let go and wait. It will probably pop back to the old setting for a bit then move. If so it means all is working just not reflecting in realtime. |
|
I believe I found the cause. webdjoe/pyvesync#289 |
|
Is that fix confirmed? I may have been too quick to merge |
Unfortunately I don't have a way to validate without a release. I traced the code and believe should resolve. If it doesn't I can go back to undo it. |
|
2025.2.5 has a fix it in related to this. Could you try it and let us know how it goes? |
|
@home-assistant add-label needs-more-information |
The problem
Home Assistant cannot find it at all. Debug log stays empty. I cannot reopen #122638 which was closed wrongly.
I of course first synced it with Vesync.
What should be controllable and read out state:
Fan On/Off
Speed 0-12
Oscillation (yes/no)
Readout State only:
Temperature
What version of Home Assistant Core has the issue?
core-2024.8.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Vesync
Link to integration documentation on our website
https://www.home-assistant.io/integrations/vesync/
Diagnostics information
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2024.8.2",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.12.4",
"docker": true,
"arch": "aarch64",
"timezone": "Europe/Vienna",
"os_name": "Linux",
"os_version": "6.6.31-haos-raspi",
"supervisor": "2024.08.0",
"host_os": "Home Assistant OS 13.0",
"docker_version": "26.1.4",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"systemmonitor": {
"documentation": "https://www.home-assistant.io/integrations/systemmonitor",
"version": "1.0.0",
"requirements": [
"psutil==5.9.7"
]
}
},
"integration_manifest": {
"domain": "vesync",
"name": "VeSync",
"codeowners": [
"markperdue",
"webdjoe",
"thegardenmonkey",
"cdnninja"
],
"config_flow": true,
"documentation": "https://www.home-assistant.io/integrations/vesync",
"iot_class": "cloud_polling",
"loggers": [
"pyvesync"
],
"requirements": [
"pyvesync==2.1.12"
],
"is_built_in": true
},
"setup_times": {},
"data": {
"vesync": {
"bulb_count": 0,
"fan_count": 0,
"outlets_count": 0,
"switch_count": 0,
"timezone": "Europe/Vienna"
},
"devices": {
"bulbs": [],
"fans": [],
"outlets": [],
"switches": []
}
}
}
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: