Few minor fixes with improved exception logging from pyezviz

-Bumped pyezviz version. The config flow will now fail if the region is incorrect. You can also run pyezviz (API) to see the correct region url. (The region code is in the url)
-Improved exceptions in api.
-A few other minor fixes to the integration itself.

Camera RTSP creds now also configurable via integration.

-The camera RTSP creds are now imported as separate integration "instances".
-You can now add ezviz integration instances with camera credentials.

Config via yaml is now truly obsolete ;-)

French translation added to integration. (Breaking change reminder: config yaml file needs to change from v0.0.4.0 onwards)

-French translation added.

**PS: In case you missed the previous releases. Your config.yaml file needs to change from v0.0.4.0 onward.

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.

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.

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.

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

Breaking Change : Yaml config needs to change.

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.

Config flow now tests your ezviz cloud login details.

-Config flow now tests your ezviz cloud login details.

bump pyezviz version for empty ip fix on some cameras.

-Added a method to the api to fetch ip info from wifiinfos if empty. The method also checks wifiinfos exists.
if all infos are empty it will return 0.0.0.0
-Alarm sound mode string also now only return the alarm mode. (shorter and only the relevant info)

Improved switch platform setup.

-Improve error correction in switch platform.

Improved switch platform setup.

Rewrote a small piece of the switch entity to make use of a list to find supported switches. (in place of a private __enum method)