-
Notifications
You must be signed in to change notification settings - Fork 505
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
Request support for Cleverio CD-200 video doorbell #2295
Comments
Just remembered. |
It installed after many tries, getting same issue as #2288 but all entities are unreachable From log Logger: custom_components.tuya_local.device Failed to fetch device status for Entré-Video-doorbell Tried to take away and reinstall (with upgraded TuyaLocal) and all I get is this and the logg says Logger: custom_components.tuya_local.config_flow Could not find device: xxxxxxxxxxxxx Have restarted HA many times since then but no difference. Very strange behaviour. |
After reinstalling, it works again through the Tuya integration. Now it doesn't autodiscover the IP in the TuyaLocal cloud-add-device. I get both the #2288 error AND "unknown error occurred" when I key in the IP manually. |
Maybe try downgrading to 2024.8.0, as there appears to be a bug in 2024.9.0 config flow |
Ok! Probably both well known and is being worked upon. Have no real hurry here more then doing my bit, confirming the functionality of the config for the cd-200. |
This is strange! |
The fact it is only reporting a single dp in the log above is possibly a sign that this device does not consistently return the same data each time, so cannot be recognised. |
Crap! |
Log message
DPS information
Product ID
tpd76kmnwwsun4iq
Product Name
Cleverio CD-200 Video doorbell
Information about how the device functions
Cleverio CD-200 video doorbell
Has inbuilt PIR that was not reachable from Tuya. Would be extremely nice if that entity was accessible
PDF Manual https://www.kjell.com/globalassets/mediaassets/867160_51768_manual_en_no_sv_20221018.pdf?ref=007B10390E
The text was updated successfully, but these errors were encountered: