v0.10.0

What's Changed

• v0.10.0 Updates by @magico13 in #311
• Bumped version to 0.10.0.
• Updated sensor names to more closely follow Home Assistant's
  recommended naming conventions. Only changes them if they're still set
  to the default, you can still rename them.
• Addressed Home Assistant warnings about deprecated functionality and
  also numerous linter recommendations.
• Bumped PyEmVue to 0.18.6, which includes improvements to the
  authentication flow and supports bidirectional circuits.

Full Changelog: v0.9.3...v0.10.0pre

v0.9.3 Fix missing data due to partial updates

• Bumps PyEmVue to 0.18.4 to fix #261.

Note: Startup will take longer on this version if you have devices that are offline but it should complete within about a minute. The time can be reduced by removing the offline devices from your Emporia account if they are no longer available, or bringing the devices online (eg plugging in any unplugged smart plugs). A future update will handle these offline devices better.

Full Changelog: v0.9.2...v0.9.3

v0.9.2 Bump PyEmVue to v0.18.3

• Bump PyEmVue to v0.18.3

Full Changelog: v0.9.1...v0.9.2

v0.9.1 - Variety of Updates and Fixes

• Uses v0.18.2 of PyEmVue, which has improved retry and resiliency.
• Fixes when using the set_charger_current service call, especially from UI elements.
• Initial setup of entities uses device tree instead of first set of data. Should be more resilient to missing data during startup.
• Swapped off of deprecated units.
• EV chargers return more data on the switch's attributes.

Full Changelog: v0.8.3...v0.9.1

v0.8.3 - Fix for EVSE with Breaker PIN Set

Fixes #208 by passing breakerPIN on requests if set. Added additional error logging around EVSE update exceptions to hopefully make diagnosing these issues easier. That logging update will expand to other areas in a later update.

v0.8.2 - Fix services.yaml

• Fixes the errors with the services.yaml, removing an error message and restoring the ability to call the service from the developer tools in the UI.
• Bump the pyemvue version to 0.17.0. Only effect here is that username will be forced to lowercase.
• Corrected issues that were failing validation. The repo now passes hassfest and HACS validation.

v0.8.1 - Bugfix for Switching Outlets

Small update to fix a 400 error when enabling/disabling an outlet. Bumps PyEmVue version to 0.16.2 which contains the fix.

v0.8 - State Class Change, EVSE Support, Bugfixes

BREAKING - Upgrading from v0.7.3 to this version will result in a one-time jump in the daily and monthly statistics due to the state class changing. You can either ignore it or use the built-in tooling to fix the jump. Upgrading from one of the earlier v0.8 prereleases will not be affected.

• State_class change to total from total_increasing. Allows the Utility Connect to work if you have solar and causes the Energy Dashboard to recover from bad data better.
• Added support for the Emporia EVSE including the ability to turn it on and off and using a service to adjust the charge rate.
• Numerous bugfixes, refactorings, and optimizations

Known issues:

• The API still reports bad data sometimes. For random jumps/drops the state_class change should allow those to auto-fix themselves. For random None values the previous value will be used but for random Zero values the zero will still be reported. Hoping to handle these better in the future.
• The reset around midnight is a minute or two late. This is still an improvement over before and comes down to how I'm checking for a day change. Will try to improve this in the future.
• Adding and removing Emporia devices via the app still requires the integration to be reloaded/Home Assistant restarted to update properly.

Beta v0.8-pre5 - PyEmVue Updates

Updates the version of PyEmVue used to reduce the number of calls needed to get outlet and charger status. Also includes a change to better handle 401 Unauthorized errors: tokens will be refreshed and the call will automatically retry.

Beta v0.8-pre4 - Attempting to Reset Daily Sensors at Midnight

• Possibly fixes random error messages about invalid key errors
• Testing a change to reset daily sensors automatically at midnight instead of waiting for the next API call