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

Siren entity doesn't work anymore - Tapo C210/C310 #850

Closed
jymorel opened this issue Jan 31, 2025 · 3 comments
Closed

Siren entity doesn't work anymore - Tapo C210/C310 #850

jymorel opened this issue Jan 31, 2025 · 3 comments

Comments

@jymorel
Copy link

jymorel commented Jan 31, 2025

Description

My alarm automations are crashing because the siren entity is no longer functional for my Tapo C310 and C210 cameras.
I tried a workaround using the manual alarm start button entity, but the alarm sound is only activated for 3 seconds and I can't find a way to make it permanent...
Any help or explanation would be appreciated. Thanks

Reproduction Steps

in the Tapo camera control integration, click on "siren"

Expected behavior

siren entity working again

If applicable, add error logs.

No response

Device Firmware

C210 : 1.4.4 Build 241211 Rel.42339n / C310 : 1.4.4 Build 241211 Rel.42339n and 1.4.1 Build 241204 Rel.58421n

Integration Version

6.0.9

Using stream component

Yes

Does camera work via official integrations?

Yes

Camera has all attributes filled out in developer tools

Yes

HASS Environment

HAOS / RPI4

Search for similar issues

Yes

Additional information

No response

@JurajNyiri
Copy link
Owner

Please post debug logs and what you see when you turn on siren.

Additionally, when did the issue start occurring, what changed?

@jymorel
Copy link
Author

jymorel commented Feb 1, 2025

I don't know exactly when this started occuring, but I noticed this issue this afternoon when my alarm went off and the alarm process stopped strangely. No change for a while except updates maybe

Image

Image

Error log when clicking on the C210 siren entity :

Enregistreur: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:245
intégration: Home Assistant WebSocket API (documentation, problèmes)
S'est produit pour la première fois: 31 janvier 2025 à 21:10:29 (7 occurrences)
Dernier enregistrement: 01:58:52

[547926023408] Unexpected exception
[547295824912] Unexpected exception
[547162646864] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<7 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/core.py", line 2795, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2838, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1006, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
hass, entity, func, data, call.context
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1078, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/siren/init.py", line 113, in async_handle_turn_on_service
await siren.async_turn_on(
**process_turn_on_params(siren, cast(SirenTurnOnServiceParameters, data))
)
File "/config/custom_components/tapo_control/siren.py", line 113, in async_turn_on
raise Exception("Camera does not support triggering the siren.")
Exception: Camera does not support triggering the siren.

@JurajNyiri
Copy link
Owner

JurajNyiri commented Feb 1, 2025

Unfortunately this works as expected, unless there is a new way how siren is reported. Some cameras report siren state, some do not (and there is no way how to see the capability, before triggering the siren). You will need to use button entities to start/stop siren. If it worked in the past, they probably changed it via a firmware update.

If you find a way how siren state is reported via an app, or a way to turn on the siren via the app indefinitely, let me know and we can reopen.

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

2 participants