Releases: JurajNyiri/HomeAssistant-Tapo-Control
Releases · JurajNyiri/HomeAssistant-Tapo-Control
4.2.2
New Features
- Add #261: Support for Tapo C225 Camera and possibly other cameras using the new authentication rejection method. Thank you @yayitazale for help with debugging the issue.
4.2.1
New Features
- Requests are now retried twice instead of once when device responds with invalid authentication
- Ability to update cameras using hub
- Night mode support for cameras using hub
- Battery sensor for cameras that have battery
- Cache capabilities of the camera, significantly reducing startup time
- Other small microoptimizations
Fixes
- Fix an edge case where updates were not reflected on entities
4.2.0
Version 4.2.0
This release has a significant rewrite of pytapo and this integration in support of new types of battery cameras which are using Hub to communicate. Only control is added for now, and no battery, or any other sensors for the new cameras yet. Motion sensor and streams are also not supported until someone figures out the stream protocols on the camera.
Since Home Assistant will now query the battery powered camera every 30s for updates, you might notice higher battery usage. In case of higher battery usage, please report it through a new issue and I will address the issue.
New Features
- Add #243: Support for cameras powered by batteries through a Hub like Tapo C420S2
Fixes
- Fix #257: Update entity does not have a unique ID and was not visible under device
Breaking Changes
None
Thank you
Thank you @bebo-dot-dev for documenting the new communication API calls in a feature request issue.
Media
4.1.7
4.1.6
4.1.5
Fixes
- Hot fix for C310 motion sensor select
4.1.4
4.1.3
Updates
- Improve update process time by reducing number of requests going to camera from N to 1 on each update request
4.1.2
Fixes
- Fixes slow state update of switch and select entities on changing state. State is now updated as soon as camera acknowledges the command and does not wait for the next refresh cycle. This fixes most of the cases where switches / selects would revert to old values. There is still a case when this can happen which will be fixed in next release.