Add energy management for efergy

[tkdrob]

Breaking change

Unit of measurement now uses an ISO standard currency code. Periods are now separate from the currency specified by the user, in the entity unit of measurement. Users are advised to adjust the currency configuration item, if set, to be a valid ISO standard currency code and also any automations, scripts, or templates that handle the entity unit of measurement.

Proposed change

Follow-up to: #54210
Should be merged after: #56890

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 Efergy sensors not showing up in new Energy Consumption sensor list #54005, fixes Efergy integration not usable in Energy Management HA 2021.8.3 #54219, fixes Efergy Intergration #54687
• 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.

[MartinHjelmare]

This will be a breaking change. Is just the currency accurate as unit of measurement for this measurement?

If we're going to keep the device class as monetary for this sensor we need to validate that the currency config is an ISO-standard currency code.

core/homeassistant/helpers/config_validation.py

Line 1287 in b1f4ccf

currency = vol.In(

[tkdrob]

The user can specify the period in the yaml and it defaults to yearly.

[tkdrob]

So I just tested these changes further. Adding one of the two sensors for consumption is breaking the energy dashboard:

2021-09-25 05:04:01 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [4873682656] Error handling message: Unknown error
Traceback (most recent call last):
  File "/Users/tkdrob/core/homeassistant/components/websocket_api/decorators.py", line 25, in _handle_async_response
    await func(hass, connection, msg)
  File "/Users/tkdrob/core/homeassistant/components/energy/websocket_api.py", line 167, in ws_validate
    connection.send_result(msg["id"], (await async_validate(hass)).as_dict())
  File "/Users/tkdrob/core/homeassistant/components/energy/validate.py", line 283, in async_validate
    hass.data[DOMAIN]["cost_sensors"][flow["stat_energy_from"]],
KeyError: 'sensor.energy_consumed'

[tkdrob]

Marked as draft to block merge until issue is resolved.

[tkdrob]

I've now tested this on my production machine and everything works fine. This has to do with the current dev build or just my dev environment being screwy.

[MartinHjelmare]

Thanks!

[MartinHjelmare]

Please link a docs PR where we update the currency config item description and example.

https://www.home-assistant.io/integrations/efergy/#configuration

[MartinHjelmare]

Changing to draft to avoid merging accidentally. We, author and me, decided to hold this until next release to give some time to add a config flow to avoid more than one breaking change release. The config flow is in the works.

[tkdrob]

Closing as merger went wrong.