Releases: JurajNyiri/HomeAssistant-Tapo-Control
2.3.3
New Features
- Adds support for Home Assistant 2020.12.0
- No longer supports older Home Assistant versions
2.3.2
Fixes
Binary sensor for motion is now shown in Device information in UI
2.3.1
Fixes
Fixes a case when a username / password with special characters were not working
2.3
Version 2.3 📷
Description
This release adds supports for the new Tapo C310 and prepares for any other future camera releases on the same firmware.
The difference between C310 and the old cameras is that the C310 no longer accepts account created via the app for control and only uses "admin" user for control. This user has the same password as the one for your cloud account.
However, it is not needed to provide cloud password for cameras which do not require it (determined automatically by the integration).
Your cloud email is not required and all communication is and always will be fully local. Absolutely no cloud / internet requests are made by this integration.
Breaking changes
None. Your settings will be automatically migrated properly.
New config flow
1 - User is required to create account in advanced settings just like before. He is then prompted to enter this username and password. Integration will test these credentials in 2 ways - does rtsp stream work AND does control work?
2 - A.) If control worked, setup is done.
2 - B.) If control did not work, user is required to enter his cloud password - not email as that is not required.
3 - Setup is finished
During the whole process user is now told exactly what kind of account to enter and where to find it.
It is also possible to change any settings set up while adding the device via integration options with a proper error messages for every possible case or camera.
New Features
- Support for C310
- New service tapo_control.set_day_night_mode
- Night mode is displayed now in attributes of entities
- Checking if device supports ptz, preset etc is now done without determining the camera model
Thank you
I would like to thank Davide Depau for his research and work on pytapo library. Thanks to his research he made this release and a lot of future features possible.
Big thanks also goes to all the testers of C310 who made this release possible.
2.2.3
New Features
Better code handler with log for unexpected errors while using / adding the camera.
2.2.2
2.2.1
Version 2.2.1
Description
This is a small release which updates component to fully work with Home Assistant 0.117.0 following updates for motion detection in home-assistant/core#42020 and home-assistant/core#41949.
2.2
Version 2.2 😎
This release is all about the quality of life improvements.
New features
- Change authentication data and other options via Tapo Integration Options.
- Disable / Enable camera entities via Home Assistant entity manager (make sure not to disable motion sensor via entity, check troubleshooting if you did).
- Disable / Enable motion detection (= the whole onvif connection) via Tapo Integration Options.
No reboot required!
Other minor changes and fixes
- When an error occurs while adding or updating the camera in integration page, the inputs do not lose entered values
- Other minor fixes
Pictures
2.1.1
Fixes
- Fixes compatibility with Home Assistant 0.116.3
2.1
Version 2.1 🏃
New Features
Motion sensor
The first time your camera detects a motion it creates a new binary sensor. This sensor is updated in real time whenever there is a motion to on or off state.
After the next Home Assistant reboot, this sensor is restored with unavailable state until it detects motion again.
Motion sensor should recover from any reboots or disconnects of the camera automatically.
See the new troubleshooting section in readme if you have any questions regarding motion sensor before creating a new issue.
Camera image
Component now also provides an image of the current stream.
It generates it from the current stream on Home Assistant. While this is a common practice in other integrations too, we could do better and get the image directly from the camera instead. See this feature request if you would like to help.
New update coordinator
This release includes a rewrite of how updates are handled, resulting in 2 times reduction of number of requests outgoing camera while not affecting update speed.
Other minor updates
- support for services camera.disable_motion_detection and camera.enable_motion_detection
- support for services camera.turn_on camera.turn_off
Final remarks
If you need help...
Please open a new issue or a feature request, or discuss and ask for help on Home Assistant: Community Forum.
If you would like to help...
Join the discussion or see issues marked with help wanted.
There are already some examples going around with requests for more.
I would love to see what people already created with this camera on lovelace, so please open a PR and let's share!