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

С200 - invalid continuation byte #489

Closed
tariya-garker opened this issue Dec 21, 2023 · 8 comments
Closed

С200 - invalid continuation byte #489

tariya-garker opened this issue Dec 21, 2023 · 8 comments
Labels
Help wanted Extra attention is needed

Comments

@tariya-garker
Copy link

tariya-garker commented Dec 21, 2023

Description

Faced with the same error:
'utf-8' codec can't decode byte 0xd0 in position 4003: invalid continuation byte
appears on the already added camera and if it is removed, with reboot, and add again

Reproduction Steps

probably update the camera software to 1.3.11 (the offer, since I did not notice exactly when it started)

Expected behavior

a stably working camera with its options

If applicable, add error logs.

home-assistant_tapo_control_2023-12-21T09-10-09.445Z.log
Screenshot_117

Device Firmware

1.3.11

Integration Version

5.4.12

Using stream component

Yes

Does camera work via official integrations?

N/A

Camera has all attributes filled out in developer tools

No

HASS Environment

HAOS on Proxmox (on miniPC)

Search for similar issues

Yes

Additional information

I didn’t notice exactly when it started, for some time I didn’t follow the updates, then I read in the integration description that there were errors at 1.3.9 - I decided to update, but I didn’t know that the camera already had 1.3.11 - actually from one mistake, another came out as I suppose.
I tried to remove the camera and add it again - with no result
I tried to delete the integration and install it again - with no result
there are no restrictions for the camera on the router, it works stably in the native application, the stream also gives out in the Surveillance Station, the error appeared BEFORE adding the Surveillance Station

@rark-ha
Copy link

rark-ha commented Jan 10, 2024

I get the same error showing up.

image

If I trigger something on the C200 camera (like auto-track etc) in an automation, the automation will abort itself quoting the
"'utf-8' codec can't decode byte 0xd0 in position 4003: invalid continuation byte" error.

@foxnewmen
Copy link

foxnewmen commented Mar 2, 2024

After setting up the IP address, login and password, the integration does not find any devices or objects. The mistaken comment is: 'utf-8' codec can't decode byte 0xd0 in position 4112: invalid continuation byte
Please help me solve the problem!
Integration version: 5.4.15, Camera software version 1.3.11

@JurajNyiri
Copy link
Owner

JurajNyiri commented Mar 2, 2024

In the logs of @rark-ha I see also camera being unavailable - host is unreachable. It is possible that the camera is overloaded or your network (wifi) is unstable for camera. Try removing everything using the camera except Home Assistant, restart the camera and try again.

If the issue persists with only HA being the only client, I will need access to the camera to debug further.

@JurajNyiri JurajNyiri added the Help wanted Extra attention is needed label Mar 2, 2024
@rark-ha
Copy link

rark-ha commented Mar 5, 2024

If the issue persists with only HA being the only client, I will need access to the camera to debug further.

Noting your comment, I looked to see if anything else was using the camera (nothing was). Looking inside of HA I had a couple of old automations that would take a snapshot and save the image on an event (e.g. when door opened, pan to door, take picture). Turning these couple of automations off, restarting HA, and monitoring the logs over the last couple of days I don't get the error message anymore.

The automation was pre the ability to access Tapo recordings from the HA Media setup.

@infinitytec
Copy link

I seem to be having this issue as well. If I do not move the camera at all (or, sometimes, allow auto-track) the camera seems stable, but if I tell it to move I will often see the camera reboot.

@foxnewmen
Copy link

Today I connected a new camera TAPO C100. Everything is connected and working perfectly in the integration. The problem persists only with the TAPO C200 camera. I already tried to reset it to factory settings, configured it again - all to no avail. Everything in the TAPO application works flawlessly.

@JurajNyiri
Copy link
Owner

JurajNyiri commented Oct 17, 2024

Closing due to inactivity. If the issue persists with the latest version of cameras and integration let me know and we can reopen.

@SDimou
Copy link

SDimou commented Jan 16, 2025

I have the exact same issue for a long time with model C210 and I have been waiting for a solution but nothing so far... Camera software is 1.3.14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

6 participants