Improve Airzone climate code

[Noltari]

Proposed change

This makes the code more robust for those cases where the key isn't found on the translation dicts.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[emontnemery]

Please fill in the PR description to explain why this is an improvement

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[emontnemery]

This makes the code more robust for those cases where the key isn't found on the translation dicts.

Does it mean the library may return some unexpected value? Should that be logged?

[Noltari]

This makes the code more robust for those cases where the key isn't found on the translation dicts.

Does it mean the library may return some unexpected value? Should that be logged?

I've only seen it return None when one of my thermostats ran out of battery.
I guess that I need to implement proper availability in the library, but the local API doesn't help since it just stops providing the zone data for offline devices...

[emontnemery]

This makes the code more robust for those cases where the key isn't found on the translation dicts.

Does it mean the library may return some unexpected value? Should that be logged?

I've only seen it return None when one of my thermostats ran out of battery. I guess that I need to implement proper availability in the library, but the local API doesn't help since it just stops providing the zone data for offline devices...

OK, I see. Then I think the code in the PR is OK, but please add some comments explaining the get.

[Noltari]

This makes the code more robust for those cases where the key isn't found on the translation dicts.

Does it mean the library may return some unexpected value? Should that be logged?

I've only seen it return None when one of my thermostats ran out of battery. I guess that I need to implement proper availability in the library, but the local API doesn't help since it just stops providing the zone data for offline devices...

OK, I see. Then I think the code in the PR is OK, but please add some comments explaining the get.

Done in e8b965e

[Noltari]

With the changes done in the library and in the integration in the following PR this is no longer needed:
#93629