home_assistant_solarman
Home Assistant component for Solarman collectors used with a variety of inverters.
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
○Committers with academic emails
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (11.9%) to scientific vocabulary
Keywords
Repository
Home Assistant component for Solarman collectors used with a variety of inverters.
Basic Info
Statistics
- Stars: 653
- Watchers: 33
- Forks: 215
- Open Issues: 377
- Releases: 12
Topics
Metadata Files
README.md
Solarman integration
Home Assistant component for interacting with Solarman data collectors used with a variety of inverters. The integration allows Home Assistant to connect in direct-mode over the local network to the collector to extract the information, and no cables are required.
It has been created with a 5kW DEYE/SUNSYNK inverter and since integrated with a variety of other inverters that uses the Solarman data collector.
This component uses Pysolarman by Jonathan McCrohan for the underlying protocol, and also provides service-access to the library for advanced users. See advanced.
Discord
Feel free to discuss the integration by joining the Discord server.
Installation
HACS
This method is prefered.
Manual
For this, it is highly recomended to use the "Samba share" add-on (you will need to enable advanced mode in your user profile).
Clone or download the repo, and copy the "solarman" folder in "customcomponents" to the "customcomponents" folder in home assistant.
After that, the folder structure should look as follows:
bash
custom_components
├── solarman
│ ├── __init__.py
│ ├── const.py
│ ├── manifest.json
│ ├── parser.py
│ ├── solarman.py
│ ├── sensor.py
│ └── inverter_definitions
│ ├── {inverter-definition yaml files}
├── {other components}
Preparation
- Get the IP and Serial Number to use in the configuration.
Find the internal IP of the logger on the DHCP server, and then open a browser and navigate to that address. If you are prompted for a username/password, use "admin" as username and "admin" as password.
Once logged in, expand the "Device information" and note the Device serial number, as well as the IP used.

Check the version of the solarman logger. If the serial number starts with 17xxxxxxx, 21xxxxxxx or 40xxxxxxx (protocol V5), the component should work. If not, you may need to try the component for V4 of the protocol mentioned above.
On your DHCP server, reserve the IP for the WiFi data logger so that it will not change.
Configuration
This integration can be configured using config-flow, or by manually configuring using the configuration.yaml file. Both methods are described below:
Automatic (config flow)
- After the installation of this component, click on the "Configuration" tab on the left, then on "Devices & Services".
- Select the "Integrations" tab on the top of the screen, then on the "+ ADD INTEGRATION" button on the left-hand corner.
- Select the solarman integration.

4.Configure the entity by filling in the details.

Manual Configuration (configuration.yaml)
In your configuration.yaml file, add the solarman platform under "sensor".
Example:
```YAML
sensor: - platform: solarman name: DEYE inverterhost: 192.168.0.100 inverterport: 8899 inverterserial: 1720747149 invertermbslaveid: 1 lookupfile: deye_hybrid.yaml ```
Parameters
| Parameter | Description | | ------------------- | ----------------------------------------------------------------------- | | name | This name will be prefixed to all parameter values (change as you like) | | inverterhost | The IP address of the data logger. (* see: autodiscover) | | inverterport | Always 8899 | | inverterserial | The serial number of the data collector (* see: autodiscover) | | invertermbslaveid | The Modbus Slave ID of the inverter. Defaults to 1 | | scaninterval | Time in seconds between refresh intervals | | lookup_file | ** The yaml file to use for parameter-definition |
** This parameter is optional, and if not specified will revert to deyehybrid.yaml. If you customize the parameters, create a lookup file "customparameters.yaml" and refer to it so that it will not be overwritten during updates.
Lookup Files
| Lookup File | Inverters supported | Notes | |-------------------------|------------------------------------------|------------------------------------------------------------------| | deyehybrid.yaml | DEYE/Sunsynk/SolArk Hybrid inverters | used when no lookup specified | | deyesg04lp3.yaml | DEYE/Sunsynk/SolArk Hybrid 8/12K-SG04LP3 | e.g. 12K-SG04LP3-EU | | deyestring.yaml | DEYE/Sunsynk/SolArk String inverters | e.g. SUN-4/5/6/7/8/10/12K-G03 Plus | | deye2mppt.yaml | DEYE Microinverter with 2 MPPT Trackers | e.g. SUN600G3-EU-230 / SUN800G3-EU-230 / SUN1000G3-EU-230 | | deye4mppt.yaml | DEYE Microinverter with 4 MPPT Trackers | e.g. SUN1300G3-EU-230 / SUN1600G3-EU-230 / SUN2000G3-EU-230 | | sofarlsw3.yaml | SOFAR Inverters | | | sofarg3hyd.yaml | SOFAR Hybrid Three-Phase inverter | HYD 6000 or rebranded (three-phase), ex. ZCS Azzurro 3PH HYD-ZSS | | sofarhyd3k-6k.yaml | SOFAR Hybrid Single-Phase inverter | HYD 6000 or rebranded (single-phase), ex. ZCS Azzurro HYD-ZSS | | solishybrid.yaml | SOLIS Hybrid inverter | | | solid1p8k-5g.yaml | SOLIS 1P8K-5G | | | zcs_azzurro-ktl-v3.yaml | ZCS Azzurro KTL-V3 inverters | ZCS Azzurro 3.3/4.4/5.5/6.6 KTL-V3 (rebranded Sofar KTLX-G3) |
Auto-discovery
The component has the option to auto-discover the logger IP and serial number.
To use auto discovery, the IP should be specified as 0.0.0.0 and/or the serial as 0.
NOTE: This should be used as a temporary or debug measure since the discovery only happens when the component starts and, if the logger is inaccessible at that point, the entities will unavailable until restart. This will not be the case when the IP and serial number were specified.
Manual
The section below shows an example configuration done using manual configuration. This is an option for those that want to customize the component for inverters not supported out of the box.
```YAML
sensor: - platform: solarman name: DEYE inverterhost: 0.0.0.0 inverterport: 8899 inverterserial: 0 invertermbslaveid: 1 lookupfile: deye_hybrid.yaml ```
Config-flow

Entities
Once the component is running, it will add the following entities to Home Assistant.

Status Entities
Apart from the inverter-parameters, it will also add status entities to view the status of the solarman component (in the Diagnostic category).

Energy Dashboard
The entities includes the device classes to enable it to be added to the Energy Dashboard introduced with Home Assistant Core 2021.8.
To configure the energy dashboard with the infirmation provided by this component, see configuring energy dashboard.
Customization
This integration was tested against the DEYE 5kW inverter, and it is possible that the parameter-definitions for other inverters may differ. If you want to try your hand at it, refer to customizing parameters.yaml/
Owner
- Login: StephanJoubert
- Kind: user
- Repositories: 1
- Profile: https://github.com/StephanJoubert
GitHub Events
Total
- Issues event: 57
- Watch event: 104
- Issue comment event: 211
- Pull request event: 14
- Fork event: 23
Last Year
- Issues event: 57
- Watch event: 104
- Issue comment event: 211
- Pull request event: 14
- Fork event: 23
Committers
Last synced: 7 months ago
Top Committers
| Name | Commits | |
|---|---|---|
| Stephan Joubert | s****t@g****m | 55 |
| Jonathan McCrohan | j****n@g****m | 25 |
| Andrea Nasoni | a****i@s****t | 18 |
| Kolbi | M****b@2****e | 15 |
| Dummy0815 | t****m@a****e | 12 |
| Francisco R. Santos | f****s@g****m | 9 |
| virtualdj | v****j | 9 |
| Johan Bogema | 3****. | 7 |
| lmn | 6****r | 5 |
| nedyarrd | x****e@i****l | 5 |
| William Brockhus | p****w@g****m | 5 |
| NH-Networks | 2****s | 5 |
| Sören Beye | g****b@h****e | 4 |
| allx | a****l@g****m | 4 |
| giona | i****o@g****t | 4 |
| Claudio Bartoli | c****o@b****i | 3 |
| kdceddj | k****j@g****m | 3 |
| pepetheprawn | 1****n | 3 |
| Łukasz Szeremeta | l****v@g****m | 3 |
| Tommaso Toniolo | k****o@g****m | 3 |
| David Ignjic | d****c@a****m | 2 |
| Jan | c****e | 2 |
| Kevin Becker | k****r@b****v | 2 |
| Benjamin Gardiner | h****t@g****m | 2 |
| NemesisXB | 4****B | 2 |
| cosote | c****e@g****m | 2 |
| kosmikza | 4****a | 2 |
| wedhorn | h****k@w****t | 1 |
| steve-cox | 3****x | 1 |
| Aliaksei Hirylovich | a****h@o****m | 1 |
| and 21 more... | ||
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 318
- Total pull requests: 101
- Average time to close issues: about 2 months
- Average time to close pull requests: about 2 months
- Total issue authors: 292
- Total pull request authors: 46
- Average comments per issue: 3.5
- Average comments per pull request: 1.94
- Merged pull requests: 38
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 73
- Pull requests: 19
- Average time to close issues: 7 days
- Average time to close pull requests: 2 months
- Issue authors: 69
- Pull request authors: 8
- Average comments per issue: 0.85
- Average comments per pull request: 0.21
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- PV-Joe (5)
- Picard2002 (3)
- torsteinelv (3)
- stamatakisa (3)
- ArmenVanlasso (2)
- denimassi (2)
- cyberrep (2)
- murraythegoz (2)
- silviudc (2)
- markodraca (2)
- 81ondo (2)
- mcderd-coder (2)
- OneScuzzie2k (2)
- grest (2)
- hd00842 (2)
Pull Request Authors
- virtualdj (11)
- mateumann (5)
- jmccrohan (5)
- honikos (5)
- nedyarrd (5)
- gionaf (4)
- StackOverflowEx (4)
- CrazyUs3r (4)
- Kolbi (3)
- mrboogiee (3)
- Cyberbeni (3)
- webartoli (3)
- agirilovich (3)
- Dummy0815 (2)
- basti122303 (2)
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- actions/checkout v2 composite
- hacs/action main composite
- actions/checkout v2 composite
- home-assistant/actions/hassfest master composite