v0.4.4

## Minor release to remove depreciated DEVICE_CLASS_* constants - via @frenck

• Removes DEVICE_CLASS_* constants from the codebase - @mattrayner
• Bump version - @mattrayner

v0.4.3

Santa's watching... Be nice! 🎅

This release add spam mitigation for Pod Point APIs. Now, instead of requesting all data from pod point every 5 minutes (all charges since you opened your account), we request 3. If we need to, we then query 3 more etc. until we have all the 'new' charges.

Also we use pagination for the initial requests too so it should be nicer on the Pod Point API servers.

Changes

• Support pagination rather than relying on all perpage API values
• Limit subsequent data pulls for pods and charges to minimise data being requested every 5 minutes
• Update podpointclient dependency to 1.0.0

v0.4.2

Features

• Added a Last Completed Charge Cost sensor requested by @jimmyeao in #12 - @mattrayner

Changes

• Updated documentation covering cost sensors and updated examples - @mattrayner

v0.4.1

This release fixes some typos (thanks @blundell!) and adds a new 'Total Cost' sensor, using the energy cost provided by Pod Point.

Changes

• Fix typo in README @blundell
• Fix type in Switch @blundell
• Update hacs.json removing redundant entries @mattrayner
• Add 'Total Cost' sensor @mattrayner
• Update README example to include 'Total Cost' @mattrayner

v0.4.0

Features

• Added Completed Charge Time sensor (Only shows completed time i.e. after you disconnect the cable)
  • Raw sensor shows seconds spent actively charging.
  • Formatted provides a ‘day, H:MM:SS’ version (Provided by python date time)
  • Long provides a ‘X years, Y months, Z days, HH:MM:SS’ or ‘3 hours, 4 minutes’ format useful for speakIng or messaging
• Bump podpointcLient to 0.2.1
• Add significant tests to the codebase
• Tidy up code base, refactoring to make it more efficient
• Added CI for pull requests and pushes

Note

DUE TO MULTI ACCOUNT AND ENERGY SENSOR SUPPORT, UPGRADING DATA FROM VERSION BEFORE 0.2.X OR EARLIER IS NOT SUPPORTED. YOU SHOULD DELETE YOUR CONFIGURATION AND RE-CONFIGURE POD POINT AFTER UPGRADING. IF YOU DO NOT YOU WILL HAVE DUPLICATE SENSORS OR ORPHANED CONFIGURATION ENTRIES

v0.3.1

IMPORTANT

DUE TO MULTI ACCOUNT AND ENERGY SENSOR SUPPORT, UPGRADING DATA FROM VERSION BEFORE 0.3.0 IS NOT SUPPORTED. YOU SHOULD DELETE YOUR CONFIGURATION AND RE-CONFIGURE POD POINT AFTER UPGRADING. IF YOU DO NOT YOU WILL HAVE DUPLICATE SENSORS OR ORPHANED CONFIGURATION ENTRIES

Features

• Handle authentication failures at boot or when refreshing data, launching the re-authentication user flow
• Refactored PodPointDataUpdateCoordinator
  • Moved to it’s own file
  • Handle API connection issues (offline)
  • Handle authentication failures
• Entity now supports availability attribute
  • All sensors and switches show as unavailable when coordinator is offline
• All sensors and switches gracefully handle coordinator offline at startup
• Upgraded podpointclient to 0.1.16
• Removed unused error classes
• Brought coordination logging in line with standards
• Marked integration as 'gold' standard

v0.3.0

IMPORTANT

DUE TO MULTI ACCOUNT AND ENERGY SENSOR SUPPORTUPGRADING DATA FROM PREVIOUS VERSIONS IS NOT SUPPORTED. YOU SHOULD DELETE YOUR CONFIGURATION AND RE-CONFIGURE POD POINT AFTER UPGRADING. IF YOU DO NOT YOU WILL HAVE DUPLICATE SENSORS ORPHANED

Features

• Add Total Energy and Current Energy sensors for a given pod.
• Updated README
• Updated podpointclient to 0.1.12
• Add the ability to change polling interval within integration config (see below)
• Support multiple Pod Point accounts and pods

Updating poll interval

1. Click 'Configure'.

2. Set the poll interval in seconds. We don't recommend going below 5 minutes as this is a bit spammy.

Bugfixes

• Fixed an issue where the values of the component would not show new data after a refresh

v0.3.0-rc2

Release candidate

Provided a successful response from [#4], this release will be promoted from release candidate to full release on Friday 20th May. Thanks to everyone that opened issues and contributed to this release including (but not limited to):

• @adamic - thanks for your additional help (Fixed #4)
• @Seaniau
• @mattrayner
• @tomcoleman
• @Murleen
• @FileGo
• @michaelmcneilnet

IMPORTANT

DUE TO MULTI ACCOUNT AND ENERGY SENSOR SUPPORTUPGRADING DATA FROM PREVIOUS VERSIONS IS NOT SUPPORTED. YOU SHOULD DELETE YOUR CONFIGURATION AND RE-CONFIGURE POD POINT AFTER UPGRADING. IF YOU DO NOT YOU WILL HAVE DUPLICATE SENSORS ORPHANED

Features

• Add Total Energy and Current Energy sensors for a given pod.
• Updated README
• Updated podpointclient to 0.1.12
• Add the ability to change polling interval within integration config (see below)
• Support multiple Pod Point accounts and pods

Updating poll interval

1. Click 'Configure'.

2. Set the poll interval in seconds. We don't recommend going below 5 minutes as this is a bit spammy.

Bugfixes

• Fixed an issue where the values of the component would not show new data after a refresh

v0.3.0-rc

Release candidate

Provided a successful response from [#4], this release will be promoted from release candidate to full release on Friday 20th May. Thanks to everyone that opened issues and contributed to this release including (but not limited to):

• @adamic
• @Seaniau
• @mattrayner
• @tomcoleman
• @Murleen
• @FileGo
• @michaelmcneilnet

IMPORTANT

DUE TO MULTI ACCOUNT AND ENERGY SENSOR SUPPORTUPGRADING DATA FROM PREVIOUS VERSIONS IS NOT SUPPORTED. YOU SHOULD DELETE YOUR CONFIGURATION AND RE-CONFIGURE POD POINT AFTER UPGRADING. IF YOU DO NOT YOU WILL HAVE DUPLICATE SENSORS ORPHANED

Features

• Add Total Energy and Current Energy sensors for a given pod.
• Updated README
• Updated podpointclient to 0.1.12
• Add the ability to change polling interval within integration config (see below)
• Support multiple Pod Point accounts and pods

Updating poll interval

1. Click 'Configure'.

2. Set the poll interval in seconds. We don't recommend going below 5 minutes as this is a bit spammy.

Bugfixes

• Fixed an issue where the values of the component would not show new data after a refresh

v0.3.0-beta5

IMPORTANT

DUE TO MULTI ACCOUNT AND ENERGY SENSOR SUPPORTUPGRADING DATA FROM PREVIOUS VERSIONS IS NOT SUPPORTED. YOU SHOULD DELETE YOUR CONFIGURATION AND RE-CONFIGURE POD POINT AFTER UPGRADING. IF YOU DO NOT YOU WILL HAVE DUPLICATE SENSORS ORPHANED

Features

• Add Total Energy and Current Energy sensors for a given pod.
• Updated README
• Updated podpointclient to 0.1.12
• Add the ability to change polling interval within integration config (see below)
• Support multiple Pod Point accounts and pods

Updating poll interval

1. Click 'Configure'.

2. Set the poll interval in seconds. We don't recommend going below 5 minutes as this is a bit spammy.

Bugfixes

• Fixed an issue where the values of the component would not show new data after a refresh