Breaking Change : Yaml config needs to change.

Just repeating in case you missed the previous update.

From v0.0.4.0

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.

You'll need to remove the integration. (Hopefully the last time you'll need to do this)
Move your config to the "original integration" location under the Camera platform. (I'll update the readme with example)
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.

Issues fixed (from v0.0.4.0):
-Small error on new defence mode service. (2nd attempt, Now it works.)
-Removed the ezviz switch service. The hass one works. (If you find the toggle switches causing issues)
-Changed default timeout to 25 seconds.