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

Entity fan.air_purifier does not support action fan.turn_on #29

Closed
aarnaegg opened this issue Jan 4, 2025 · 4 comments
Closed

Entity fan.air_purifier does not support action fan.turn_on #29

aarnaegg opened this issue Jan 4, 2025 · 4 comments
Assignees
Milestone

Comments

@aarnaegg
Copy link

aarnaegg commented Jan 4, 2025

The problem

After updating to HAOS 2025.1.0, HA now gives the error
2025-01-03 17:24:15.865 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140406162783632] Entity fan.main_bedroom_air_purifier does not support action fan.turn_off
2025-01-03 17:24:20.980 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140406162783632] Entity fan.living_room_air_purifier does not support action fan.turn_on

What version of this integration has the issue?

1.3.3

What version of Home Assistant Core has the issue?

2025.1.0

Diagnostics

"integration_manifest": {
"domain": "vesync",
"name": "VeSync",
"codeowners": [
"markperdue",
"webdjoe",
"thegardenmonkey",
"vlebourl",
"tv4you2016",
"gdgib"
],
"config_flow": true,
"dhcp": [
{
"hostname": "levoit-",
"macaddress": "
"
}
],
"documentation": "https://github.com/haext/custom_vesync",
"iot_class": "cloud_polling",
"issue_tracker": "https://github.com/haext/custom_vesync/issues",
"loggers": [
"pyvesync"
],
"requirements": [
"pyvesync==2.1.12"
],
"version": "1.3.3",
"is_built_in": false,
"overwrites_built_in": true
},
"setup_times": {},
"data": {}

Home Assistant log

2025-01-03 17:20:40.434 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ states('sensor.living_room_air_purifier_filter_life') | int < 10 }}) renders=3>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 643, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2745, in _render_with_context
return template.render(**kwargs)
~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1295, in render
self.environment.handle_exception()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2383, in forgiving_int_filter
raise_no_default("int", value)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1921, in raise_no_default
raise ValueError(
...<2 lines>...
)
ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('sensor.living_room_air_purifier_filter_life') | int < 10 }}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 760, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
variables, strict=strict, log_fn=log_fn, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 645, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('sensor.living_room_air_purifier_filter_life') | int < 10 }}' but no default was specified
2025-01-03 17:20:40.438 WARNING (MainThread) [homeassistant.components.template.trigger] Error initializing 'template' trigger for 'Notifications': ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('sensor.main_bedroom_air_purifier_filter_life') | int < 10 }}' but no default was specified
2025-01-03 17:20:40.438 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ states('sensor.main_bedroom_air_purifier_filter_life') | int < 10 }}) renders=3>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 643, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2745, in _render_with_context
return template.render(**kwargs)
~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1295, in render
self.environment.handle_exception()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2383, in forgiving_int_filter
raise_no_default("int", value)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1921, in raise_no_default
raise ValueError(
...<2 lines>...
)
ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('sensor.main_bedroom_air_purifier_filter_life') | int < 10 }}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 760, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
variables, strict=strict, log_fn=log_fn, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 645, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ states('sensor.main_bedroom_air_purifier_filter_life') | int < 10 }}' but no default was specified
2025-01-03 17:20:40.486 ERROR (MainThread) [homeassistant.components.homekit] HomeKit HASS Bridge IT cannot startup: entity not available: {'exclude_domains': [], 'exclude_entities': [], 'include_domains': [], 'include_entities': ['humidifier.main_bedroom_humidifier'], 'exclude_entity_globs': [], 'include_entity_globs': []}
2025-01-03 17:21:18.792 WARNING (MainThread) [homeassistant.components.govee_light_local.coordinator] Device H6840 is not supported. Only power control is available. Please open an issue at 'https://github.com/Galorhallen/govee-local-api/issues'
2025-01-03 17:22:12.497 WARNING (ImportExecutor_0) [homeassistant.components.light] ATTR_COLOR_TEMP was used from vesync, this is a deprecated constant which will be removed in HA Core 2026.1. Use kelvin equivalent (ATTR_COLOR_TEMP_KELVIN) instead, please report it to the author of the 'vesync' custom integration
2025-01-03 17:22:12.499 WARNING (ImportExecutor_0) [homeassistant.components.light] COLOR_MODE_BRIGHTNESS was used from vesync, this is a deprecated constant which will be removed in HA Core 2026.1. Use ColorMode.BRIGHTNESS instead, please report it to the author of the 'vesync' custom integration
2025-01-03 17:22:12.500 WARNING (ImportExecutor_0) [homeassistant.components.light] COLOR_MODE_COLOR_TEMP was used from vesync, this is a deprecated constant which will be removed in HA Core 2026.1. Use ColorMode.COLOR_TEMP instead, please report it to the author of the 'vesync' custom integration
2025-01-03 17:22:12.501 WARNING (ImportExecutor_0) [homeassistant.components.light] ATTR_COLOR_TEMP was used from vesync, this is a deprecated constant which will be removed in HA Core 2026.1. Use kelvin equivalent (ATTR_COLOR_TEMP_KELVIN) instead, please report it to the author of the 'vesync' custom integration
2025-01-03 17:22:12.503 WARNING (ImportExecutor_0) [homeassistant.components.light] COLOR_MODE_BRIGHTNESS was used from vesync, this is a deprecated constant which will be removed in HA Core 2026.1. Use ColorMode.BRIGHTNESS instead, please report it to the author of the 'vesync' custom integration
2025-01-03 17:22:12.504 WARNING (ImportExecutor_0) [homeassistant.components.light] COLOR_MODE_COLOR_TEMP was used from vesync, this is a deprecated constant which will be removed in HA Core 2026.1. Use ColorMode.COLOR_TEMP instead, please report it to the author of the 'vesync' custom integration
2025-01-03 17:22:24.197 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140406162783632] Entity fan.main_bedroom_air_purifier does not support action fan.turn_off
2025-01-03 17:24:15.190 DEBUG (MainThread) [custom_components.vesync] Finished fetching vesync data in 1.131 seconds (success: True)
2025-01-03 17:24:15.865 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140406162783632] Entity fan.main_bedroom_air_purifier does not support action fan.turn_off
2025-01-03 17:24:20.980 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140406162783632] Entity fan.living_room_air_purifier does not support action fan.turn_on

Additional information

No response

@ewelin34
Copy link

ewelin34 commented Jan 5, 2025

I think this was solved here:
micahqcade#14

@gdgib
Copy link
Collaborator

gdgib commented Jan 6, 2025

Quite right. I'll get this merged in here and a release today.

@gdgib gdgib added this to the v1.3.3 milestone Jan 6, 2025
@gdgib gdgib self-assigned this Jan 6, 2025
@gdgib
Copy link
Collaborator

gdgib commented Jan 6, 2025

Opened #33

@gdgib
Copy link
Collaborator

gdgib commented Jan 6, 2025

Fixing in #35

@gdgib gdgib closed this as completed Jan 6, 2025
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

3 participants