The integration does not load (TAPO C420). #621
Labels
Fixed
Bug has been fixed.
Comments
|
Did this start happening after an update? If so, which one? I do not have these hub cameras so I cannot verify them myself. |
Yes, it most likely happened after the latest updates (O.S. and Core updates, if I remember correctly, but probably Supervisor too).
|
|
Did it happen after integration version update? Could you rollback and note down the versions where it worked? |
|
5.4.25 works and 5.4.26 works not. |
|
Podemos volver a la versión anterior 5.4.25? Gracias |
|
Could you please manually remove following parts from your installed code on the latest version one by one and after each time see if it helps: First remove this green part in switch.py 
Then remove these: 
Finally if it still does not work, replace these greens with red: 
|
JurajNyiri
added a commit
that referenced
this issue
Jul 20, 2024
marcosngomezi
pushed a commit
to marcosngomezi/HomeAssistant-Tapo-Control
that referenced
this issue
Jul 20, 2024
…or some cameras
JurajNyiri
added a commit
that referenced
this issue
Jul 20, 2024
* 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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When Home Assistant starts, the integration struggles to load, showing "initializing" for a certain period of time (indefinitely long).
Also, if the startup is successful, you can see that many camera and hub entities are no longer available.
Reproduction Steps
=/=
Expected behavior
=/=
If applicable, add error logs.
home-assistant_tapo_control_2024-07-07T15-09-15.196Z.log
Device Firmware
1.2.17 Build 20240305 rel.75572 (cameras) - 1.3.3 Build 20240604 rel.61598 (hub)
Integration Version
5.4.26
Using stream component
No
Does camera work via official integrations?
N/A
Camera has all attributes filled out in developer tools
No
HASS Environment
Hassio on Raspberry Pi4
Search for similar issues
Yes
Additional information
No response
The text was updated successfully, but these errors were encountered: