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

Tapo c200 control number - tons of warning in logs #801

Closed
fate8383 opened this issue Jan 1, 2025 · 1 comment
Closed

Tapo c200 control number - tons of warning in logs #801

fate8383 opened this issue Jan 1, 2025 · 1 comment

Comments

@fate8383
Copy link

fate8383 commented Jan 1, 2025

Description

2025-01-01 13:08:00.657 WARNING (MainThread) [homeassistant.compo
nents.number] Updating tapo_control number took longer than the s
cheduled update interval 0:00:30

I have tons of them…which entity can I disable? Or any other way?

Reproduction Steps

Default add tapo c200, all defaults…check logs

Expected behavior

Not to have tons of warning if something takes longer than usual.

If applicable, add error logs.

No response

Device Firmware

Firmware: 1.3.14 Build 240716 Rel.41863n(4555)

Integration Version

Latest stable

Using stream component

No

Does camera work via official integrations?

N/A

Camera has all attributes filled out in developer tools

Yes

HASS Environment

Docker but host network on rpi4

Search for similar issues

Yes

Additional information

No response

@fate8383 fate8383 changed the title Tap control number - tons of warning in logs Tapo c200 control number - tons of warning in logs Jan 1, 2025
@JurajNyiri
Copy link
Owner

This warning is coming out of ha for every integration if it takes longer than 30 seconds to update. There is nothing to fix here.
I recommend fixing the root cause of slow delays - probably camera being overloaded, ha or slow network. Alternatively you can disable warning logs.

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