Skip to content

Latest commit

 

History

History
201 lines (151 loc) · 9.6 KB

info.md

File metadata and controls

201 lines (151 loc) · 9.6 KB
Raw

Pod Point Home Assistant Component

GitHub Release GitHub Activity License

hacs Project Maintenance BuyMeCoffee

Community Forum

Unofficial component to integrate with Pod Point Solo/Solo 3 charging points.

This component will set up the following platforms.

Platform Description
binary_sensor Shows if the pod is connected to a vehicle.
sensor Show info from Pod Point API.
sensor (Total Energy) Show a combined KWh value from all charges for a given pod.
sensor (Current Charge Energy) Show the KWh for the current charge session (or 0).
sensor (*Total Cost) Show the total cost of all **completed charges.
sensor (Last **Completed Charge Cost) Show the total cost of the last **completed charge.
sensor (Completed charge time) Show a combined 'charge time' value from all charges for a given pod.
sensor (Balance) Shows the balance on your PodPoint account.
sensor (Charge Mode) Shows the charge mode your pod is currently in/
sensor (***Charge Override End Time) Shows the end time for any configured 'charge now' override.
switch (****Allow Charging) Enable/disable charging by enabling/disabling a schedule.
switch (Smart Charge Mode) Enable the switch for 'Smart' charge mode, disable it for 'Manual' charge mode.
update (Firmware Update) Shows the current firmware version for your device and alerts if an update is available

*Total cost is based on the energy provider and kWh cost set in Pod Point.

**Charges are considered complete by Pod Point when you disconnect the vehicle, not when power delivery stops.

***Charge override end time will be 'Unknown' if there is no charge override ('charge now') set. Or, the time when the charge override ends.

****When in either Manual or Override charge mode, the Allow Charging switch is inactive. This is because setting a schedule will not affect the charge in these modes.

Service Params
charge_now - Set a charge override for a time period account - Pod Point account we're setting charge_now for.
  hours (0-24) - How many hours should the charge override last for?
  minutes (0-59) - How many minutes should the charge override last for?
  seconds (0-59) - How many seconds should the charge override last for?

example example

{% if not installed %}

Installation

  1. Click install.
  2. In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Pod Point".

{% endif %}

Configuration is done in the UI

NOTE: Due to a breaking change in version 1.0.0, upgrading from previous versions (<= 0.4.4) will cause devices to be duplicated. This can be fixed by removing the configuration and then re-adding.

Once you have installed either manually or via HACS, restart your home assistant instance and then setup the component by either choosing 'Add integration' and search for 'Pod Point', or through using an auto-discovered Pod on the integrations screen.

Auto-discovered Pods

Pods are auto-discovered based on their DHCP host and client MAC address. Any device who's host starts with 'podpoint-*' whilst having a MAC address assigned to Espressif will trigger the auto-discovery feature.

Statuses

Multiple statuses are reported by the main pod sensor. The statuses and their meaning are shown below:

status description
available The pod is available for charging. Connecting a vehicle will begin a charging session.
unavailable The pod is unavailable for charging.
charging Vehicle is connected and charging is possible. Note: If you car has completed charging but it still connected to the pod, the status will remain as 'connected'.
out-of-service This pod is not in service. Reach out to Pod Point for more information.
waiting-for-schedule Pod charging is currently blocked by schedule. Connecting your vehicle will not begin charging.
connected-waiting-for-schedule Your vehicle is connected to the pod but charging is currently prevented due to a schedule.

Energy sensors

We populate two energy sensors for each pod connected to your account. These are for the total energy you have charged on a given pod and the current energy if you are connected and have a charge session ongoing.

If you want to add Pod Point stats to the built in energy dashboard, you should add the Current Charge Energy sensor as a device. This sensor reports when the value is reset and should allow you to track the energy usage of your pod.

Note: The Pod Point APIs perform some rounding on the kWh values returned meaning they may be sightly lower than the true energy consumed. We are unable to address this within the component.

Cost sensors

In order to provide the Total Cost and Last Completed Charge Cost sensors, we are using energy_cost values provided from Pod Point per **completed charge. There are some caveats to bare in mind here:

  • Energy use for each charge is rounded by Pod Point (see Energy sensors above) and energy costs are calculated on this rounded value.
  • You must set an accurate kWh cost within the Pod Point app (and keep this up to date if your provider/cost per kWh changes

Given the above rounding, in my opinion the cost values should be used as a guide rather than taken as gospel

**Charges are considered complete by Pod Point when you disconnect the vehicle, not when power delivery stops.

## Firmware update notifications

If an update is detected for your device, a new repair entry will be created within Home Assistant, prompting you to update using the mobile app. Unforrunately, at this time it is not possible to trigger the firmware update from outside of the Pod Point app but to restrictions with the Pod Point APIs.

Lovelace examples

Header images

In the example below, and for the sensors created by this integration, there are a number of pod 'images' that are included for use in the UI, each image and model is listed below.

For the sensor that comes installed we will add the image based on your pod model number.

Pod Model Image Link
Solo Universal /api/pod_point/static/uc.png
Solo Tethered /api/pod_point/static/2c.png
Solo 3 Universal /api/pod_point/static/uc-03.png
Solo 3 Tethered /api/pod_point/static/2c-03.png

Which pod do I have?

which pod

Entities YAML example:

type: entities
entities:
  - entity: sensor.psl_xxxxxx_status
    name: Pod Status
  - entity: sensor.psl_xxxxxx_charge_mode
    name: Charge Mode
  - entity: sensor.psl_xxxxxx_charge_override_end_time
    name: Charge Override Time Ends
  - entity: binary_sensor.psl_xxxxxx_cable_status
    name: Cable Status
  - entity: switch.psl_xxxxxx_charging_allowed
    name: Charging Allowed
  - entity: switch.psl_xxxxxx_smart_charge_mode
    name: Smart Charge Mode
  - entity: sensor.psl_xxxxxx_current_energy
    name: Current Energy
  - entity: sensor.psl_xxxxxx_total_energy
    name: Total Energy
  - entity: sensor.psl_xxxxxx_last_completed_charge_cost
    name: Last Completed Charge Cost
  - entity: sensor.psl_xxxxxx_total_cost
    name: Total Cost (completed charges)
title: Pod Point
header:
  type: picture
  image: /api/pod_point/static/uc-03.png # See above for options per-model
  tap_action:
    action: none
  hold_action:
    action: none
state_color: true

Entity YAML examples:

Long format charge time

type: entity
entity: sensor.psl_xxxxxx_completed_charge_time
attribute: long
name: Completed Charge Time (long)

Standard format charge time

type: entity
entity: sensor.psl_xxxxxx_completed_charge_time
name: Completed Charge Time
attribute: formatted

Contributions are welcome!

If you want to contribute to this please read the Contribution guidelines