Skip to content

Breaking Change : Yaml config needs to change.

Compare
Choose a tag to compare
@RenierM26 RenierM26 released this 21 Feb 09:29
· 200 commits to main since this release

I'm making progress on the official component pull request and had to change the config structure to match the original. The component now imports the config from the "original" camera platform and makes use of unique ids for config flow.

  1. You'll need to remove the integration. (Hopefully the last time you'll need to do this)
  2. Move your config to the "original integration" location under the Camera platform. (I'll update the readme with example)
  3. Fix the structure of your config to be similar to the "original ezviz" component (I'll update the readme)

Just remember that the domain should be "ezviz_cloud" instead of "ezviz".

Basically this integration (hacs version) is close to a drop in replacement for the original. (except for the domain name difference)

PS: also added new services in this release.