Skip to content

Releases: JurajNyiri/HomeAssistant-Tapo-Control

2.0.4

06 Oct 19:53
Compare
Choose a tag to compare

Fixes

Fixes warning "Detected I/O inside the event loop" in config flow

2.0.2

06 Oct 19:37
08d4b38
Compare
Choose a tag to compare

New Features

Camera stream is now available even if user is not using "stream" integration

Fixes

Handles a case when HASS requests camera image

2.0.1

06 Oct 18:43
Compare
Choose a tag to compare

Fixes

Fixes all the warnings of unsafe calls in event loop - "Detected I/O inside the event loop"

2.0

05 Oct 19:03
9a193e3
Compare
Choose a tag to compare
2.0

VERSION 2.0 🎉

It has been a few days since the first release, and I feel its a time for version 2.0 which is packed with a lot of awesome new features.

I would like to say special thank you to everyone who reported bugs or joined discussion on Home Assistant: Community Forum

New Features

  • Completely refactored the whole integration. Code is now a lot easier to read, simpler and up to current HASS standards.
  • Set up via Home Assistant Integrations UI, which also means, setup via configuration.yaml is no longer supported.
  • Automatically creates a new device in Home Assistant with its information like firmware, brand, model etc
  • Each device automatically creates 2 entities - HD and SD streams of camera platform
  • Camera stream is now available
  • Ability to format SD card of a camera
  • Better error handling and validation of service calls before they get executed

Minor updates

  • Integration now has an icon, brand and model
  • Added motion_detection and motion_detection_sensitivity attributes
  • Added privacy_mode attribute
  • Added alarm and alarm_mode attributes
  • Added led attribute
  • Added auto_track attribute

Breaking Changes

  • Integration is now set up via UI. You will need to remove tapo_control from configuration.yaml and set up integration using Home Assistant -> Configuration -> Integrations. Just search for tapo and add the cameras.
  • Entities of platform tapo_control are no longer created, camera platform is used instead.
  • Entity names now include _hd or _sd in the name. This does not affect services.

1.3.1

04 Oct 17:56
Compare
Choose a tag to compare

Fixes

No longer gets presets on C100 in pytapo

1.3

04 Oct 17:19
Compare
Choose a tag to compare
1.3

Fixes

Fix for Tapo C100, no longer requires getting presets on component setup.

New Features

Added new discovered error messages for a few error codes

1.2

04 Oct 15:58
Compare
Choose a tag to compare
1.2

New Features

Better error handling for unexpected errors so that unexpected issues can be debugged more easily.

1.1

04 Oct 14:59
Compare
Choose a tag to compare
1.1

Fixes

  • Fixes a case when component would fail setup if special characters and/or accents were used in camera name

Breaking Changes

  • In some special cases, entity_id of cameras could have changed

1.0

02 Oct 18:14
Compare
Choose a tag to compare
1.0

Initial release of Tapo: Cameras Control

New Features

  • Support for multiple cameras
  • Internal authentication does not expire and works even after reboot of a camera
  • Automatic update of all camera entities
  • Main attributes of camera for every entity, along with preset list
  • Full HACS compatibility

New services

  • tapo_control.ptz
  • tapo_control.set_privacy_mode
  • tapo_control.set_alarm_mode
  • tapo_control.set_led_mode
  • tapo_control.set_motion_detection_mode
  • tapo_control.set_auto_track_mode
  • tapo_control.reboot
  • tapo_control.save_preset
  • tapo_control.delete_preset

Details for services in readme.

Questions? Feedback? Bugs?

If you have any suggestions, questions or bug reports please open a new issue, or discuss on Home Assistant: Community Forum.