Fix CO/CO2 sensors mixup in Google Assistant

[ryborg]

Breaking change

Proposed change

Not only am I not sure how to ask Google Assistant how to report the level of carbon dioxide in my living room (exposed restful sensor, device_class: carbon_dioxide) but the sensor classes were mixed up here.

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)
• 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
• 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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[homeassistant]

Hi @ryborg,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[probot-home-assistant]

Hey there @home-assistant/cloud, mind taking a look at this pull request as it has been labeled with an integration (google_assistant) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[balloob]

Thanks!

[allenporter]

There appear to be some test failures to resolve

[ryborg]

Also, I'll have to raise as an issue, but I can't confirm that these sensors are working in assistant. So it's hard to label it as a bug fix. It's an obvious coding error is all.

[frenck]

@ryborg Could you please fix the failing test? Thanks! 👍

[ryborg]

All I have been able to do is point out the obvious problem with the code. I can't test.

…

On Sun., Jan. 2, 2022, 10:38 a.m. Franck Nijhof, ***@***.***> wrote: @ryborg <https://github.com/ryborg> Could you please fix the failing test? Thanks! 👍 — Reply to this email directly, view it on GitHub <#63152 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYBFIRPD264NPI2HPD33KTUUBWQ7ANCNFSM5LBV537A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[frenck]

I can't test.

I was not asking for a test with an device, but our automated test suite is failing:

Meaning this code change is incomplete, as the unittest need to be adjusted as well.