Problem with turning the fan on or off

AndiT · January 10, 2025, 10:00am

Hi! Fan devices have not been working for a few days after the latest home assistant updates. I use the VeSync integration.

Developer tools/ACTIONS
Fan: Turn off
Choose entity
No matching entities found

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:287
integration: Home Assistant WebSocket API ([documentation](https://www.home-assistant.io/integrations/websocket_api), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%```%3A+websocket_api%22))
First occurred: 10:03:53 (6 occurrences)
Last logged: 11:54:17

* [546500559632] Entity fan.purifier does not support action fan.turn_on
* [546500559632] Entity fan.purifier does not support action fan.turn_off
* [546252993536] Entity fan.purifier does not support action fan.turn_off
* [546435486416] Entity fan.purifier does not support action fan.turn_on
* [546478672912] Entity fan.purifier does not support action fan.turn_on

Do you have this problem too?

Davinatorr · January 10, 2025, 11:46am

Yes, I have that problem too. My automation that turns the air purifier (core200s) off when the window is opened does not work anymore. It states „fan.core200s does not support fan.turn_off“
I use the custom VeSync integration and have set the polling to 120s so VeSync does not block me because of too many pollings per day. Everything else works fine.

lohits.sisodia · January 10, 2025, 1:36pm

Yes… same happening with me as well. Not working with manual switch call.

Mayhem_SWE · January 10, 2025, 1:47pm

Are you using the HASS built-in integration or a third-party custom integration?

Because apparently both types exist, and others are complaining about a third-party custom integration breaking since recent HASS updates:

github.com/home-assistant/core

VESYNC will not load

opened 09:09AM - 07 Jan 25 UTC

biver0

integration: vesync

### The problem VESYNC will not load. I didn't change anything other than upda…te to new Home Assistant release. 2 Logs below. ### What version of Home Assistant Core has the issue? core-2025.1.0 ### 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 _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt 1. First Log: Log details (ERROR) Logger: homeassistant.setup Source: setup.py:334 First occurred: 12:51:08 AM (1 occurrences) Last logged: 12:51:08 AM Setup failed for custom integration 'vesync': Unable to import component: cannot import name 'DEVICE_CLASS_TEMPERATURE' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/loader.py", line 1015, in async_get_component comp = await self.hass.async_add_import_executor_job( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ self._get_component, True ^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run result = self.fn(*self.args, **self.kwargs) File "/usr/src/homeassistant/homeassistant/loader.py", line 1075, in _get_component ComponentProtocol, importlib.import_module(self.pkg_path) ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func return func(*args, **kwargs) File "/usr/local/lib/python3.13/importlib/__init__.py", line 88, in import_module return _bootstrap._gcd_import(name[level:], package, level) ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1387, in _gcd_import File "<frozen importlib._bootstrap>", line 1360, in _find_and_load File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 935, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 1026, in exec_module File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed File "/config/custom_components/vesync/__init__.py", line 13, in <module> from .common import async_process_devices File "/config/custom_components/vesync/common.py", line 10, in <module> from .const import ( ...<12 lines>... ) File "/config/custom_components/vesync/const.py", line 3, in <module> from homeassistant.const import DEVICE_CLASS_TEMPERATURE, TEMP_CELSIUS, TIME_MINUTES ImportError: cannot import name 'DEVICE_CLASS_TEMPERATURE' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 334, in _async_setup_component component = await integration.async_get_component() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/loader.py", line 1035, in async_get_component self._component_future.result() ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/src/homeassistant/homeassistant/loader.py", line 1027, in async_get_component comp = self._get_component() File "/usr/src/homeassistant/homeassistant/loader.py", line 1075, in _get_component ComponentProtocol, importlib.import_module(self.pkg_path) ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func return func(*args, **kwargs) File "/usr/local/lib/python3.13/importlib/__init__.py", line 88, in import_module return _bootstrap._gcd_import(name[level:], package, level) ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1387, in _gcd_import File "<frozen importlib._bootstrap>", line 1360, in _find_and_load File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 935, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 1026, in exec_module File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed File "/config/custom_components/vesync/__init__.py", line 13, in <module> from .common import async_process_devices File "/config/custom_components/vesync/common.py", line 10, in <module> from .const import ( ...<12 lines>... ) File "/config/custom_components/vesync/const.py", line 3, in <module> from homeassistant.const import DEVICE_CLASS_TEMPERATURE, TEMP_CELSIUS, TIME_MINUTES ImportError: cannot import name 'DEVICE_CLASS_TEMPERATURE' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py) 2nd Log: Logger: homeassistant.util.loop Source: util/loop.py:77 First occurred: 12:51:08 AM (1 occurrences) Last logged: 12:51:08 AM Detected blocking call to import_module with args ('custom_components.vesync',) in /usr/src/homeassistant/homeassistant/loader.py, line 1075: ComponentProtocol, importlib.import_module(self.pkg_path) inside the event loop; This is causing stability issues. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#import_module Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 227, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 213, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.13/asyncio/base_events.py", line 707, in run_until_complete self.run_forever() File "/usr/local/lib/python3.13/asyncio/base_events.py", line 678, in run_forever self._run_once() File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2033, in _run_once handle._run() File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component result = await _async_setup_component(hass, domain, config) File "/usr/src/homeassistant/homeassistant/setup.py", line 334, in _async_setup_component component = await integration.async_get_component() File "/usr/src/homeassistant/homeassistant/loader.py", line 1027, in async_get_component comp = self._get_component() File "/usr/src/homeassistant/homeassistant/loader.py", line 1075, in _get_component ComponentProtocol, importlib.import_module(self.pkg_path) ``` ### Additional information _No response_

If you are currently using a custom integration, try the one provided by HASS instead.

AndiT · January 10, 2025, 3:02pm

Thanks for the answers.
I succeeded in the following way:

I deleted the integration from Devices & Services and the folder from custom_components … and I deleted the link from Custom repositories
restart
then I accessed the hacks integration from GitHub - vlebourl/custom_vesync: Custom VeSync component for Home Assistant.
Now it works, but in integration it only shows me the on/off switch and filter lifetime.

vesync591×1280 42.1 KB

Mayhem_SWE · January 10, 2025, 3:13pm

Why not simply use the integration provided by HASS itself then?

AndiT · January 10, 2025, 3:27pm

@Mayhem_SWE
I see it’s the same thing. It works and it looks the same to me, only the switch and filter lifetime

Mayhem_SWE · January 10, 2025, 3:30pm

The HASS provided integration would/should be less likely to break when HASS is updated…

Davinatorr · January 10, 2025, 8:22pm

The official HASS integration unfortunately does not support as much devices as the custom integration. Humidifiers are missing.

RTech73 · January 14, 2025, 2:19am

I’m having the exact same problem with a fan on the Cync integration. I can set speed, but the on/off doesn’t work. It’s our bedroom ceiling fan am my wife is pretty annoyed this stopped working. Any suggestions? I don’t think there’s a built in Cync integration. I need speed settings as well as toggle - which has worked for about 2 years until recently. ANY help would be appreciated! I’ve already tried deleting and re-adding the integration.

stevedavis1234 · January 15, 2025, 7:53am

I have exactly the same with a Ecovent fan integration via HACS.
It’s been working fine forever but since a recent update I get the
'does not support fan.turn_on" /off.
Setting the fan percentage and direction works just fine.
Something seems to have broken Fans!

Davinatorr · January 17, 2025, 10:53pm

I’ve read it somewhere else and it works well for me so I’m gonna share it:

Instead of using fan.turn_off use the following

set_value of the fan speed to 1
Short delay
action fan.decrease_speed

It’s not beautiful but it works.

smenzer · January 26, 2025, 1:46am

I just switched to this fork and it has a fix already…things are working properly now! GitHub - haext/custom_vesync: Custom VeSync component for Home Assistant

Easy to switch to this version if you’re already on the custom vesync - instructions here: Fix to Fan TURN_ON and TURN_OFF features required for HA 2025.1 by elarsson1 · Pull Request #14 · micahqcade/custom_vesync · GitHub

stevedavis1234 · January 27, 2025, 2:07pm

Thanks for the pointer @smenzer
I was able to add
FanEntityFeature.TURN_ON | FanEntityFeature.TURN_OFF
to the Blauberg Ecovents integration and now IT WORKS!!
THANKS