This project is not endorsed by, directly affiliated with, maintained, authorized, or sponsored by Sinapsi
HA Custom Component to integrate data from Sinapsi Alfa device. Tested on my Alfa to monitor the power/energy consumption and photovoltaic power/energy production directly from the energy provider's OpenMeter 2.0.
Alfa is a great product, it provides official measurements, and it provides local API to get the data (for now it's through ModBus).
So finally here we are with the first official version of the HA custom integration for Alfa devices. :)
- Installation/Configuration through Config Flow UI
- Sensor entities for all data provided by the device
- Configuration options: Name, hostname, tcp port, polling period
- Reconfigure options (except device name) also at runtime: no restart needed.
This integration is available in HACS official repository. Click this button to open HA directly on the integration page so you can easily install it:
- Either click the button above, or navigate to HACS in Home Assistant and:
- 'Explore & Download Repositories'
- Search for 'Alfa by Sinapsi'
- Download
- Restart Home Assistant
- Go to Settings > Devices and Services > Add Integration
- Search for and select 'Alfa by Sinapsi' (if the integration is not found, do a hard-refresh (ctrl+F5) in the browser)
- Proceed with the configuration
Download the source code archive from the release page. Unpack the archive and copy the contents of custom_components folder to your home-assistant config/custom_components folder. Restart Home Assistant, and then the integration can be added and configured through the native integration setup UI. If you don't see it in the native integrations list, press ctrl-F5 to refresh the browser while you're on that page and retry.
Configuration is done via config flow right after adding the integration. After the first configuration you can change parameters (except device name) at runtime through the integration page configuration, without the need to restart HA.
- custom name: custom name for the device, that will be used as prefix for sensors created by the component
- ip/hostname: IP/hostname of the inverter - this is used as unique_id, if you change it and reinstall you will lose historical data, that's why I advice to use hostname, so you can change IP without losing historical data
- tcp port: TCP port of the device. tcp/502 is the only known working port, but I preferred to leave it configurable
- polling period: frequency, in seconds, to read the registers and update the sensors
If you like this integration, I'll gladly accept some quality coffee, but please don't feel obliged. :)