Peblar

The Peblar integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] integrates the Peblar Rocksolid EV Charger into your smart home ecosystem. It enables real-time monitoring of charging status, tracking energy consumption, controlling charging behavior, and integrating EV charging data into the Home Assistant energy dashboard.

Use cases

The Peblar integration connects your EV charger to Home Assistant, providing comprehensive data and control capabilities. Here’s how you can benefit from this integration in your smart home:

• Monitor your EV charging in real time - Track charging status, current power draw, and session energy consumption directly from your dashboard.
• Optimize your home energy management - Add your charger to the Home Assistant energy dashboard to integrate EV charging into your overall energy monitoring system.
• Create smart charging automations such as:
  • Receiving notifications when your vehicle completes charging
  • Automatically adjusting charging modes based on solar production forecasts
  • Getting alerts when the charger detects errors or issues
  • Scheduling charging during off-peak electricity hours
  • Optimizing charging based on electricity prices and your travel schedule
• Stay up to date with software - Receive notifications when firmware or customization updates are available for your Peblar charger.
• Control charging remotely - Start, stop, or adjust charging parameters from anywhere using the Home Assistant app.

Supported devices

The following Peblar Rocksolid EV chargers are supported by this integration:

• Peblar Home
• Peblar Home Plus
• Peblar Business

Prerequisites

Before setting up the Peblar integration, make sure:

• Your Peblar charger is connected to your home network
• You know the hostname or IP address of the charger on your network
• You have the password used to access the charger’s local web interface

Configuration

To add the Peblar device to your Home Assistant instance, use this My button:

Peblar can be auto-discovered by Home Assistant. If an instance was found, it will be shown as Discovered. You can then set it up right away.

Configuration parameters

The above configuration can also be adjusted later via Settings > Devices & services, click and select Reconfigure.

Supported functionality

Below is a complete overview of the entities this integration provides.

Binary sensors

The following binary sensors are available:

• Active error: Indicates if the charger has detected an error. If this sensor is on (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: on) an error has been detected, otherwise, it is off (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: off). Disabled by default.
• Active warning: Indicates if the charger has raised a warning. If this sensor is on (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: on) a warning has been raised, otherwise, it is off (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: off). Disabled by default.
• Socket lock: Indicates whether the cable is currently locked in the charger. When this sensor is on (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: on), the cable is unlocked; when it is off (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: off), the cable is locked. This follows the Home Assistant convention for lock sensors, where on means open.

If the Active error or Active warning binary sensor is on, you should check the charger’s local web interface for more information about the error or warning.

Buttons

The buttons provided by this integration can be used to trigger an action on the charger. The following buttons are available:

• Identify: This button can be used to identify the charger. This can be useful if you have multiple chargers and want to identify which one is which. Once pressed, the LED on the charger will start blinking for a few seconds. Disabled by default.
• Restart: This button can be used to restart the charger. This can be useful if the charger is not responding as expected. Disabled by default.
• Unlock socket: This button releases the cable from the charger, so you can unplug it by hand. This is useful when Keep socket locked is on and you want to take the cable with you. Only available on Peblar chargers that are equipped with a socket.

Events

This integration provides a single event entity: Session authorization.

It fires every time a charging session is started with an RFID card, and carries the following attributes:

• token: The name the card was given on the charger, so you can tell one person from another.
• session_number: The charger’s own number for the session, counting up with every session.
• started_at: When the charger started the session, by its own clock.

Numbers

This integration provides a single number entity: Charge limit.

Using this entity, you can set the maximum current the charger can provide to your electric vehicle. The value of this entity is in amperes (A).

The minimum value for this entity is 6A, and the maximum value is depending on your charger’s configuration. The value can be set in increments of 1A.

Selects

This integration provides the following select entities.

Buzzer volume

The Buzzer volume select entity controls the volume level of the charger’s built-in buzzer. The following options are available:

• Off (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: off): The buzzer is disabled.
• Low (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: low): The buzzer plays at a low volume.
• Low medium (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: low_medium): The buzzer plays at a volume between low and medium. This level is not offered by the charger’s own web interface.
• Medium (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: medium): The buzzer plays at a medium volume.
• High (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: high): The buzzer plays at a high volume.

LED brightness

The LED brightness select entity controls the brightness of the status LED on the charger. The following options are available:

• Automatic (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: automatic): The charger automatically adjusts the LED brightness based on ambient light conditions.
• Bright (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: bright): The LED is set to its maximum brightness.
• Medium (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: medium): The LED is set to a medium brightness.
• Dim (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: dim): The LED is set to a low brightness.
• Off (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: off): The LED is turned off.

Smart charging

The Smart charging select entity reflects the same smart charging state as is shown on the charger’s local web interface, and allows you to control the charging behavior of the charger.

The following options are available:

• Default (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: default): The charger will charge the electric vehicle as soon as it is connected.
• Fast solar (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: fast_solar): The charger will fast charge the electric vehicle with the overproduction of solar energy, but will also use grid power if the solar production is not sufficient.
• Smart solar (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: smart_solar): The charger will charge the electric vehicle with the overproduction of solar energy, but will also use grid power if the solar production is not sufficient.
• Pure solar (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: pure_solar): The charger will only charge the electric vehicle with the overproduction of solar energy.
• Custom solar (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: custom_solar): The charger will charge the electric vehicle on solar energy, using the thresholds and grid power target you set on the charger itself.
• Scheduled (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: scheduled): The charger will charge the electric vehicle according to the schedule configured on the charger.

Sensors

The Peblar integration provides a lot of sensors to Home Assistant.

• Current: The present current (in amperes) the charger is consuming to charge your electric vehicle. This is a combined value for all your phases. Additionally, three phase-specific sensors are available if your charging is using multiple phases:
  • Current Phase 1**: The current (in amperes) the charger is consuming on phase 1.
  • Current Phase 2**: The current (in amperes) the charger is consuming on phase 2.
  • Current Phase 3**: The current (in amperes) the charger is consuming on phase 3.
• Lifetime energy: The total energy (in kilowatt-hours) consumed by the charger since it was installed. This is the recommended sensor to use in the Home Assistant energy dashboard.
• Limit source: The source/origin of the current charging limit that is in effect. The source can be one of the following:
  • Charging cable (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: charging_cable): The current limit is the maximum current the charging cable can handle.
  • Current limiter (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: current_limiter): The current limit is set by the current limiter.
  • Dynamic load balancing (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: dynamic_load_balancing): The current limit is set by the dynamic load balancing feature.
  • External power limit (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: external_power_limit): The current limit is set by an external power limiter.
  • Group load balancing (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: group_load_balancing): The current limit is set by the group load balancing feature, which is a feature that allows multiple chargers to share the available power.
  • Hardware limitation (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: hardware_limitation): The current limit is limited by the hardware of the charger that can’t provide more current.
  • High temperature (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: high_temperature): The current limit is limited due to high temperatures.
  • Household power limit (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: household_power_limit): The current limit is set by the household power limit feature, which is a feature that allows the charger to limit the current to prevent overloading the household power.
  • Installer limitation (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: installer_limitation): The current limit is set by the installer, for example, to prevent overloading the fuse of the house.
  • Local Modbus API (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: local_modbus_api): The current limit is set by software using the local Modbus API.
  • Local REST API (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: local_rest_api): The current limit is set by software using the local REST API. Home Assistant uses this API to set the current limit, so if you see this state, it means the current limit is likely set through Home Assistant.
  • OCPP smart charging (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: ocpp_smart_charging): The current limit is set by the OCPP smart charging feature.
  • Overcurrent protection (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: overcurrent_protection): The current limit is limited due to overcurrent protection.
  • Phase imbalance (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: phase_imbalance): The current limit is limited due to phase imbalance in the electrical installation.
  • Power factor (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: power_factor): The current limit is limited due to a low power factor in the electrical installation.
  • Solar charging (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: solar_charging): The current limit is set by the solar charging feature of the charger. This means the charger is awaiting an overproduction of solar energy to start charging.
• Power: The power consumption (in Watts) the charger is using to charge your electric vehicle. This is a combined value for all your phases. Additionally, three phase-specific sensors are available if your charging is using multiple phases:
  • Power Phase 1**: The power consumption (in watts) on phase 1.
  • Power Phase 2**: The power consumption (in watts) on phase 2.
  • Power Phase 3**: The power consumption (in watts) on phase 3.
• Session energy: The total energy (in kilowatt-hours) consumed by the charger during the current charging session. This sensor resets when a new charging session starts. While possible, it is not recommended to use this sensor in the Home Assistant energy dashboard. Use the Lifetime energy sensor instead.
• State: The current state of the charger. The state can be one of the following:
  • Charging (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: charging): The charger is currently charging the electric vehicle.
  • Error (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: error): The charger has detected an error and is currently not charging the electric vehicle.
  • Fault (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: fault): The charger has detected a fault and is currently not charging the electric vehicle.
  • No EV connected (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: no_ev_connected): The charger is currently not connected to an electric vehicle.
  • Suspended (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: suspended): The charger is currently not charging the electric vehicle, but is ready to start charging when needed.
  • Invalid (stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more]: invalid): The charger is in an invalid state.
• Uptime**: The total time the charger has been running since the last restart. This sensor is reset when the charger is restarted.
• Voltage: The voltage the charger is using to charge. Only available if your charger is connected to a single-phase power source.
• Voltage Phase 1**: The voltage on phase 1. Only available if your charger is connected to at least a two-phase power source.
• Voltage Phase 2**: The voltage on phase 2. Only available if your charger is connected to at least a two-phase power source.
• Voltage Phase 3**: The voltage on phase 3. Only available if your charger is connected to a three-phase power source.

Switches

This integration provides the following switch entities:

• Charge: This switch allows you to start or stop/pause the charging of your electric vehicle. This can be helpful if you want to temporarily stop charging your electric vehicle, for example, to avoid charging during expensive peak hours.
• Force single phase: This switch can be used to force the charger to use a single phase for charging your electric vehicle. This can be useful if you want to limit your current draw from the charger to a single phase, for example, to prevent overloading your electrical installation.
• Keep socket locked: When enabled, the cable stays locked in the charger. When disabled, the charger releases the cable once your vehicle is disconnected, so anyone can unplug it and take it with them. Turning this on while nothing is plugged in has no immediate effect: the charger locks the cable the next time one is inserted.

Updates

The Peblar integration provides two update entities for the Peblar charger:

• Firmware: Indicates if there is a firmware update available for the charger, and installs it. The firmware can be thought of as the operating system of the charger.
• Customization: Indicates if there is a customization update available for the charger, and installs it. The customization can be thought of as the user interface of the charger that you see when you log in to the charger’s local web interface.

Installing an update takes several minutes. The charger first downloads the package and then restarts itself. While it restarts, the charger is unavailable in Home Assistant.

Home Assistant does not show a progress percentage while an update installs, because the charger does not report one. The version numbers are updated once the charger is back online.

Data updates

This integration uses local pollingData polling is the process of querying a device or service at regular intervals to check for updates or retrieve data. By defining a custom polling interval, you can control how frequently your system checks for new data, which can help optimize performance and reduce unnecessary network traffic. [Learn more], meaning it checks for changes to all entities by regularly communicating with the Peblar charger on your home network.

The integration uses three different polling frequencies:

• Every 10 seconds: Updates all sensors and binary sensors, providing you with the latest insights into your electric vehicle’s charging status.
• Every 5 minutes: Checks for configuration changes to the charger, affecting all configuration entities such as smart charging mode and current limit.
• Every 2 hours: Checks for updates to the charger itself, ensuring you’re aware of any available updates for your Peblar charger.

Although this integration uses local polling, any configuration changes you make to the Peblar charger from Home Assistant will appear on the charger almost instantly.

List of actions

The Peblar integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] provides the following actions. Each link below opens a dedicated page with examples, parameters, and a step-by-step UI walkthrough.

• Add an RFID token (peblar.add_rfid_token) Adds a new RFID token to the Peblar charger’s standalone authorization list.

• Add an autocharge vehicle (peblar.add_vehicle_token) Adds a vehicle to the Peblar charger’s autocharge list.

• Authorize a charge session (peblar.authorize_charge_session) Presents a token to the Peblar charger, as if it were held against the reader.

• Delete an RFID token (peblar.delete_rfid_token) Deletes an RFID token from the Peblar charger’s standalone authorization list.

• Delete an autocharge vehicle (peblar.delete_vehicle_token) Deletes a vehicle from the Peblar charger’s autocharge list.

• List RFID tokens (peblar.list_rfid_tokens) Returns all RFID tokens currently configured in the Peblar charger’s standalone authorization list.

• List autocharge vehicles (peblar.list_vehicle_tokens) Returns the vehicles configured in the Peblar charger’s autocharge list.

For an overview of every action across all integrations, see the actions reference.

Examples

The following examples show how to use the Peblar integration in Home Assistant automations. These examples are just a starting point, and you can use them as inspiration to create your own automations.

Feel free to contribute more examples to this documentation ❤️. Have you created a useful automation with your Peblar charger? Consider contributing it to help other users get the most from their integration!

Notify when a software update is available

The following example sends a notification to your mobile device when a software update becomes available for your Peblar charger.

automation:
  - alias: "Peblar software update available"
    triggers:
      - trigger: state
        entity_id: update.peblar_firmware
        from: "off"
        to: "on"

    actions:
      - action: notify.send_message
        target:
          entity_id: notify.my_device
        data:
          title: "Peblar charger update available!"
          message: >
            There is a software update available for your Peblar charger.
            Please log in to the charger's local web interface to install
            the update.

Automation: notify who started charging

The following example sends a notification naming the person whose card started the charging session. The card names come from the charger’s own authorization list.

automation:
  - alias: "Peblar charging session started"
    triggers:
      - trigger: event.received
        target:
          entity_id: event.peblar_ev_charger_session_authorization
        options:
          event_type:
            - session_authorized

    actions:
      - action: notify.send_message
        target:
          entity_id: notify.my_device
        data:
          title: "Charging started"
          message: >
            {{ state_attr('event.peblar_ev_charger_session_authorization', 'token') }}
            started charging.

Notify when an issue is detected

The following example automation will send out a notification when the charger detects an error or raises a warning.

automation:
  - alias: "Peblar issue detected"
    triggers:
      - trigger: state
        entity_id:
          - binary_sensor.peblar_active_error
          - binary_sensor.peblar_active_warning
        from: "off"
        to: "on"
      - trigger: state
        entity_id: sensor.peblar_state
        to:
          - "error"
          - "fault"

    actions:
      - action: notify.send_message
        target:
          entity_id: notify.my_device
        data:
          title: "Peblar charger issue detected!"
          message: >
            An issue with your Peblar charger has been detected.
            Please check the charger's local web interface for more information.

How this integration talks to your charger

The charger offers more than one way in, and this integration uses most of them.

The integration uses the local REST API to pollData polling is the process of querying a device or service at regular intervals to check for updates or retrieve data. By defining a custom polling interval, you can control how frequently your system checks for new data, which can help optimize performance and reduce unnecessary network traffic. [Learn more] the meter, system state, and EV interface, and to authorize charging sessions. It uses the charger’s internal web interfaces for configuration, firmware versions and updates, RFID and vehicle lists, and meter history. A WebSocket connection reports charging-session state changes, which prompts the integration to refresh the relevant polled data.

The one thing it leaves alone is the Modbus API, which stays entirely yours to use.

Known limitations

Not all functionality of the Peblar charger is available through this integration. The following limitations are known:

• The Peblar APIs currently don’t communicate when the charger is awaiting authentication (for example, using an RFID card) before it can start charging. As a result, you will see a suspended charging status in Home Assistant when the charger is actually awaiting authentication.
• Home Assistant manages the charger’s local REST API for you. If it is switched off, setting up this integration switches it on, and it stays on afterwards. You can keep using that API yourself alongside the integration.
• Peblar is also sold as white-label products, such as CoolBlue BlueBuilt, Eneco Connectric® and Shell Recharge. This integration has been tested only with Peblar branded products, and it’s unknown whether it works with these white-label versions.

Troubleshooting

If you’re experiencing issues with your Peblar charger integration, try these general troubleshooting steps:

1. Make sure your Peblar charger is powered on and properly connected to your home network.
2. Verify that you can access the charger’s local web interface directly using the same hostname or IP address configured in Home Assistant.
3. If the integration shows as unavailable, try restarting both your Peblar charger and Home Assistant.

Removing the integration

This integration follows standard integration removal. No extra steps are required.

To remove an integration instance from Home Assistant

1. Go to Settings > Devices & services and select the integration card.
2. From the list of devices, select the integration instance you want to remove.
3. Next to the entry, select the three dots menu. Then, select Delete.