-
Notifications
You must be signed in to change notification settings - Fork 92
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
D230 privacy mode (switch.doorbell_privacy) missing in HA (available in Tapo app) #629
Comments
Hello try to remove the camera and add it back again |
thanks for such a fast reply! Doing it now. The already better news is that I was able to remove it this time (without switching the hub off). Will update in a few... |
|
I did update HA from 2024.7.2 to 2024.7.3 - I can downgrade if you';d like me to try that? I restarted after removing the hub/doorbell, so here are the logs since then...
|
should I now raise a separate issue for selecting |
Yes please, make sure to document what you see in the app for that option as well please and we can take it from there. |
great - thanks |
…or some cameras
* changes * tapo-siren-fix * getMost-list-breaking-change * siren-and-select * comments * fixes-and-comments * numbers * siren * unneded-mapings * cleanup * testing-fixes * cleanup * Fix: PR does not work with C200 1.0 1.3.6 * fix-siren * Update README.md to add instructions in case the cloud password does not work. * Update README.md * Update README.md * Update README.md * Implement color mode Reference: https://developers.home-assistant.io/docs/core/entity/light#color-modes > New integrations must implement both color_mode and supported_color_modes. > If an integration is upgraded to support color mode, both color_mode and > supported_color_modes should be implemented. This also fixes this warning at startup: ``` WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.tapo_control.light.TapoWhitelight'>) does not set supported color modes, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/issues ``` * Create ru.json * Update README.md * Update README.md * Update README.md * Update README.md * Fix #568: IP address is not a supported Tapo device * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml * Update issues.yml Temporarily disable cloud password close bot * Update issues.yml * Update README.md * Update README.md * Update README.md * Update README.md * Update README.md * Update README.md * changes * tapo-siren-fix * getMost-list-breaking-change * siren-and-select * comments * fixes-and-comments * numbers * siren * unneded-mapings * cleanup * testing-fixes * cleanup * fix-siren * Handle cleanup of config entry * Fix: PR does not work with C200 1.0 1.3.6 * alarm-status-false-default * Fix #616: Warning for async_forward_entry_setup * Fix #612, #615, #530, #525 * Fix: Blocking call when copying file from cold to hot storage * Add: Binary sensor with details about media sync setup * Fix #572: ffmpeg for sound detection doesn't terminate on Home Assistant restart * Fix #561: Unexpected error fetching Tapo resource status data * Fix #571: Incorrect device_class for D230 doorbell battery sensor * Fix: Descalate "Recording is currently in progress." warning to info on media sync * Add: HDR switch * Add: Experimental optimization for battery cameras * Fix: Update interval is now based on whether the device has a battery or not * Update: Automatically determine whether the device is currently running on battery or not and adjust update interval * Fix: Camera entities ignoring update threshold * Update README.md * Update README.md * Create add_camera_with_new_firmware.md * Update README.md * Update add_camera_with_new_firmware.md * Update add_camera_with_new_firmware.md * Fix #629, #621: Setup for switch entities fails for some cameras * Add #457: Battery optimization for solar cameras * Update: Migrate update interval to config entry storage * Add: Configurable update interval * Update: Bump version * Update: Guides for new firmwares workaround * Update: Readme instructions about stopping use of tapo app not required * Update: Readme formatting * Update README.md * Update add_camera_with_new_firmware.md * Update README.md * Fix: Removal of disabled device results in error and warning, time sync debug log * Fix #450: Config entry name resets on reconfiguration * Update: Bump version * Fix: stopManualAlarm instead of start on siren off * Fix: Mute error on siren on/off * Update: Revert result_has_error changes * Update: Ensure compatibility with #632 --------- Co-authored-by: marcosngomezi <[email protected]> Co-authored-by: Antoine Buchser <[email protected]> Co-authored-by: L. López <[email protected]> Co-authored-by: Virenbar <[email protected]> Co-authored-by: Nathan Spencer <[email protected]>
Description
I had power outage resulting in most of my doorbell entities being permanently
unavailabel
- I was unable to remove the device so pulled the plug on the hub, restarted HA and re-added the hub - all good.However, the doorbell camera privacy mode no longer exists in HA (and the doorbell night vision is unable to be set to
auto
but this ticket is about the privacy mode).Reproduction Steps
Expected behavior
I expect doorbell privacy mode switch to exist (it exists in mu phone's Tapo app).
The privacy mode switch was available in HA prior to my outage.
If applicable, add error logs.
Not sure is this log entry is relevant:
Device Firmware
1.1.16 build 20240617 rel. 65780
Integration Version
5.4.26
Using stream component
No
Does camera work via official integrations?
Yes
Camera has all attributes filled out in developer tools
Yes
HASS Environment
Docker on RPi-4
Search for similar issues
Yes
Additional information
I wasn't sure if #540 is related or not. It has an
invalid
label.I also mentioned my issue with being unable to select
auto
for night vision as not sure if it is relevant or not. Selectingon
oroff
works. This ticket is not about that though (keeping it to one topic). However, for info, When I select 'auto' oroff
in the UI, I get the following error:The text was updated successfully, but these errors were encountered: