home-assistant.io/source/_integrations/pglab.markdown

title	description	ha_category	ha_release	ha_iot_class	ha_config_flow	ha_codeowners	ha_domain	ha_platforms	ha_integration_type	ha_quality_scale
PG LAB Electronics	Instructions on how to integrate PG LAB Electronics with Home Assistant.	Switch	2025.3	Local Push	true	@pglab-electronics	pglab	switch	integration	bronze

The PG LAB Electronics {% term integrations %} allows you to control PG LAB Electronics devices in Home Assistant.

Supported devices

• E-BOARD: Controller board to interface I2C devices by a local LAN connection.
• E-RELAY: 8 Channels relay board controlled by I2C connection.
• [E-SWITCH]: Coming soon

Each E-BOARD device can be connected to a maximum of 8 E-RELAY boards. E-BOARD can control up to 64 relays or 32 shutters or a mixed configuration.

Prerequisites

• MQTT broker and the MQTT integration set up in Home Assistant.
• PG LAB Electronics devices MQTT setting configured to communicate with the MQTT broker.

Once the device is connected to your MQTT broker, it should be discovered by Home Assistant. Add PG LAB Electronics integration.

Device configuration

Configure each PG LAB Electronics devices following these steps:

1. Power the device and connect it to your local network.
2. From your router, get the IP address of your device (for example: 192.168.1.7).
3. Connect to the internal device web server with a web browser (don't use 'https://...', instead, connect to 'http://192.168.1.7').
4. Change the default device name. Use a unique, meaningful name such as E_Board_Office, or E_Board_Garden.
   • Note: Every device MUST have a unique name.
5. Set up the MQTT broker address, port number, username, and password.
6. Save the configuration and restart the device.

{% include integrations/config_flow.md %}

Supported features

PG LAB Electronics relays, shutters, and switches are supported.

• PG LAB Relays will be added as Home Assistant switch entities.
• The integration will also create diagnostic status sensors, with device different information.

Removing the integration

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

{% include integrations/remove_device_service.md %}