Skip to content

Commit 508866a

Browse files
fboundyfboundy
committed
Readme updates
1 parent 2e11390 commit 508866a

4 files changed

Lines changed: 29 additions & 35 deletions

File tree

‎.github/FUNDING.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
44
patreon: # Replace with a single Patreon username
55
open_collective: # Replace with a single Open Collective username
6-
ko_fi: #
6+
ko_fi: https://ko-fi.com/fboundy#
77
tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
88
community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
99
liberapay: # Replace with a single Liberapay username

‎README.md‎

Lines changed: 28 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,38 @@
1-
# SolisConnect for Home Assistant
1+
# SolisConnect for Home Assistant - EXPERIMENTAL
22

33
## Description
44

55
SolisConnect is a Home Assistant custom integration for Solis and compatible inverters. It can poll and control an inverter over local Modbus, the SolisCloud API, or a combined Modbus + SolisCloud setup that keeps one shared Home Assistant device and entity set.
66

77
The integration stores protocol data in the same register cache, so entities do not duplicate when you add cloud support. Local Modbus remains the broadest and fastest path; SolisCloud is useful when local access is unavailable or as a backup protocol.
88

9+
## This integration is experimental. Please raise issues at (https://github.com/fboundy/solisconnect//issues).
10+
11+
**Inverters Tested**
12+
Solis and equivalent Axitec, Zonneplan inverters
13+
14+
Protocol verification status: ⚪ = not yet verified. The columns will be filled in as test reports come in for each protocol mode.
15+
16+
| Type | Inverter | Modbus | Cloud | Combined |
17+
| ------------- | ----------------- | :----: | :---: | :------: |
18+
| S6-EH3P | [S6-EH3P20K-H] | ⚪ | ⚪ | ⚪ |
19+
| S6-EH3P | S6-EH3P15K-H | ⚪ | ⚪ | ⚪ |
20+
| S6-EH3P | S6-EH3P(12-20)K-H | ⚪ | ⚪ | ⚪ |
21+
| S6-EH3P | S6-EH1P6K-L-PRO | ⚪ | ⚪ | ⚪ |
22+
| S6-EH3P | S6-EH1P6K-L-PLUS | ⚪ | ⚪ | ⚪ |
23+
| S6-EH3P | [S6-EH3P10K-H-ZP] | ⚪ | ⚪ | ⚪ |
24+
| S6-EH3P | [S6-EH3P10K-H-EU] | ⚪ | ⚪ | ⚪ |
25+
| S6-GR1P | [S6-GR1P4K] | ⚪ | ⚪ | ⚪ |
26+
| S5-EH1 | [S5-EH1(3-6)K-L] | ⚪ | ⚪ | ⚪ |
27+
| S5-EH1 | [S5-EH1P5K-L] | ⚪ | ⚪ | ⚪ |
28+
| S5-EH1 | [S5-EH1P6K-L] | ⚪ | ⚪ | ⚪ |
29+
| S5-GC | [S5-GC30K] | ⚪ | ⚪ | ⚪ |
30+
| S5-GC | [S5-GC60K] | ⚪ | ⚪ | ⚪ |
31+
| RAI-\* | [RAI-3K-48ES-5G] | ⚪ | ⚪ | ⚪ |
32+
| RHI-\* | [RHI-3K-48ES-5G] | ⚪ | ⚪ | ⚪ |
33+
| 3P(3-20)K-4G | [3P6K-4G] | ⚪ | ⚪ | ⚪ |
34+
| 1P(2.5-6)K-4G | [1P(2.5-6)K-4G] | ⚪ | ⚪ | ⚪ |
35+
936
## Credits and Acknowledgements
1037

1138
SolisConnect started as a fork of [Pho3niX90/solis_modbus](https://github.com/Pho3niX90/solis_modbus), which provides the local Modbus foundation this integration is built on. Many thanks to Pho3niX90 and the solis_modbus contributors.
@@ -289,33 +316,6 @@ view_layout:
289316
290317
Card inspiration from https://github.com/slipx06/Sunsynk-Home-Assistant-Dash
291318
292-
## Tested
293-
294-
**Inverters Tested**
295-
Solis and equivalent Axitec, Zonneplan inverters
296-
297-
Protocol verification status: ⚪ = not yet verified. The columns will be filled in as test reports come in for each protocol mode.
298-
299-
| Type | Inverter | Modbus | Cloud | Combined |
300-
| ------------- | ------------------------------------------------------------------------------------------------- | :----: | :---: | :------: |
301-
| S6-EH3P | [S6-EH3P20K-H](https://github.com/fboundy/solisconnect/issues/93) | ⚪ | ⚪ | ⚪ |
302-
| S6-EH3P | S6-EH3P15K-H | ⚪ | ⚪ | ⚪ |
303-
| S6-EH3P | S6-EH3P(12-20)K-H | ⚪ | ⚪ | ⚪ |
304-
| S6-EH3P | S6-EH1P6K-L-PRO | ⚪ | ⚪ | ⚪ |
305-
| S6-EH3P | S6-EH1P6K-L-PLUS | ⚪ | ⚪ | ⚪ |
306-
| S6-EH3P | [S6-EH3P10K-H-ZP](https://github.com/fboundy/solisconnect/issues/191) | ⚪ | ⚪ | ⚪ |
307-
| S6-EH3P | [S6-EH3P10K-H-EU](https://github.com/fboundy/solisconnect/issues/202) | ⚪ | ⚪ | ⚪ |
308-
| S6-GR1P | [S6-GR1P4K](https://github.com/fboundy/solisconnect/issues/84) | ⚪ | ⚪ | ⚪ |
309-
| S5-EH1 | [S5-EH1(3-6)K-L](https://github.com/fboundy/solisconnect/issues/89) | ⚪ | ⚪ | ⚪ |
310-
| S5-EH1 | [S5-EH1P5K-L](https://github.com/fboundy/solisconnect/issues/94) | ⚪ | ⚪ | ⚪ |
311-
| S5-EH1 | [S5-EH1P6K-L](https://github.com/fboundy/solisconnect/issues/94#issuecomment-2656512651) | ⚪ | ⚪ | ⚪ |
312-
| S5-GC | [S5-GC30K](https://github.com/fboundy/solisconnect/issues/173) | ⚪ | ⚪ | ⚪ |
313-
| S5-GC | [S5-GC60K](https://github.com/fboundy/solisconnect/issues/180#issuecomment-2887414843) | ⚪ | ⚪ | ⚪ |
314-
| RAI-\* | [RAI-3K-48ES-5G](https://github.com/fboundy/solisconnect/issues/174) | ⚪ | ⚪ | ⚪ |
315-
| RHI-\* | [RHI-3K-48ES-5G](https://github.com/fboundy/solisconnect/issues/97#issuecomment-2639807764) | ⚪ | ⚪ | ⚪ |
316-
| 3P(3-20)K-4G | [3P6K-4G](https://github.com/fboundy/solisconnect/issues/210) | ⚪ | ⚪ | ⚪ |
317-
| 1P(2.5-6)K-4G | [1P(2.5-6)K-4G](https://github.com/fboundy/solisconnect/issues/230) | ⚪ | ⚪ | ⚪ |
318-
319319
**Wifi Dongles Tested**
320320
321321
- S2_WL_ST
@@ -333,8 +333,6 @@ On Home Assistant OS/Supervised systems, live logs are available with:
333333
ha core logs
334334
```
335335

336-
If you also run the separate `hultenvp/solis-sensor` cloud integration, log lines from `custom_components.solis` belong to that integration, not SolisConnect. Running both integrations with the same SolisCloud key can increase cloud `atRead` traffic.
337-
338336
### Restoring Sensor History
339337

340338
If a sensor's entity ID changes (e.g., during migration) and you lose its history, you can manually restore it using Home Assistant's statistics tool:
@@ -348,8 +346,4 @@ If a sensor's entity ID changes (e.g., during migration) and you lose its histor
348346

349347
Alternatively, this integration makes it much easier https://github.com/mayerwin/HA-Merge-Sensor-History
350348

351-
#### ⚠️ Note on Reconfiguration
352-
353-
If the reconfiguration flow does not ask for your **Serial Number**, please delete the device and re-add it as a new device.
354-
355349
- **Tip:** Rename the new device to match your old device's name and select **"Recreate Entity IDs"** during setup. This will ensure your history and dashboards remain functional. as mentioned here [Comment by 0rangutan](https://github.com/fboundy/solisconnect/pull/309#issuecomment-3638890631)

‎images/img_2.png‎

78.9 KB
Loading

‎images/img_jk_bms.png‎

-39 KB
Binary file not shown.

0 commit comments

Comments
 (0)