BETA: SolisCloud support

[hultenvp]

Soliscloud support goes beta

With the help of @LucidityCrash and @hawkeye100 Soliscloud support has been added! It will be released soon.

Ginlong is planning to deprecate the m.ginlong.com portal for Solis and all other brands and plans to migrate everyone in the coming years to the new site.

The implementation is still beta; some server-side features do not appear to be working as specified.

Known limitations

Please do not submit bugs for the known limitations. If you have more details, please add them to this discussion.

• The backend always returns 0 for "daily energy exported to grid"
• The backend always returns 0 for "monthly energy purchased" and "yearly energy purchased".

[hultenvp]

To provide a smooth migration path we've tried to keep the sensor names identical to Ginlong V2 portal sensors.
It is not possible to map all sensors, however. For others we are simply unsure because of the difference in terminology.

Sensor	Response JSON Key
'Power state'	'currentState'
'State'	'state'
'Timestamp inverter online'	No Mapping
'Timestamp measurements received'	'dataTimestamp'
'Temperature'	'inverterTemperature'
'DC Voltage PV1'	'uPv1'
'DC Voltage PV2'	'uPv2'
'DC Voltage PV3'	'uPv3'
'DC Voltage PV4'	'uPv4'
'DC Current PV1'	'iPv1'
'DC Current PV2'	'iPv2'
'DC Current PV3'	'iPv3'
'DC Current PV4'	'iPv4'
'DC Power PV1'	'pow1' (Undocumented)
'DC Power PV2'	'pow2' (Undocumented)
'DC Power PV3'	'pow3' (Undocumented)
'DC Power PV4'	'pow4' (Undocumented)
'AC Voltage R'	'uAc1'
'AC Voltage S'	'uAc2'
'AC Voltage T'	'uAc3'
'AC Current R'	'iAc1'
'AC Current S'	'iAc2'
'AC Current T'	'iAc3'
'AC Output Total Power'	'pac'
'AC Frequency'	'fac'
'Energy Last Month'	No Mapping
'Energy Today'	'eToday'
'Energy This Month'	'eMonth'
'energy This Year'	'eYear'
'Energy Total'	'eTotal'
'Remaining battery capacity'	'batteryCapacitySoc'
'Total Energy Charged'	'batteryTotalChargeEnergy'
'Total Energy Discharged'	'batteryTotalDischargeEnergy'
'Daily Energy Charged'	'batteryTodayChargeEnergy'
'Daily Energy Discharged'	'batteryTodayDischargeEnergy'
'Daily On-grid Energy'	'gridSellTodayEnergy'
'Daily Grid Energy Purchased'	'gridPurchasedTodayEnergy'
'Daily Grid Energy Used'	'homeLoadTodayEnergy'
'Monthly Grid Energy Purchased'	'gridPurchasedMonthEnergy'
'Monthly Grid Energy Used'	No Mapping
'Yearly Grid Energy Purchased'	'gridPurchasedYearEnergy'
'Yearly Grid Energy Used'	No Mapping
'Total On-grid Energy'	'gridSellTotalEnergy'
'Total Consumption Energy'	No Mapping?
'Power Grid total power'	'psum'
'Total Consumption power'	'familyLoadPower'
'Total Energy Used'	'homeLoadTotalEnergy'

[LucidityCrash]

Just an update ... Total On-grid Energy is being updated for me ... it has a 1kWh accuracy. Daily On-Grid Energy is stubbornly showing as 0 at all times. I've chased Solis Support but they are saying that this is due to the fact that I'm exporting so little that it is rounding down to 0. I've stopped chasing it at the moment as they are getting a bit upperty with me, but will chase it again with them in a few months when we move into summer and it is Exporting more.

[LucidityCrash]

Interesting thing I just noticed :

this is the eToday value from the SolisCloud inverterDetail endpoint. See how it drops to 0 at about 16:00 ? Looks like it does this every day (except one). This is what is actually being sent back in the JSON so nothing wrong with the integration. It looks like this value (eToday) drops to 0 when the system stops producing power from the panels.

It might be "better" to fetch dayEnergy from the stationDetail endpoint instead as this still reads the "right" value. Though with hybrid/battery systems it might be prone to the same reset to 0 errors that happen for the Daily Grid Energy Purchased.

[LucidityCrash]

At about 19:00 last night what I was getting from the API was :

inverterList

• "etoday": 8.1,

stationDetail

• "dayEnergy": 8.1,

inverterDetail

• "eToday": 0,
  (last non 0 reading was 7.8 at about 15:54)

Not sure when the inverterList and stationDetail ones reset but assume it will be midnight

[LucidityCrash]

I also noticed that I'd not been seeing sunrise and sunset times in the api or on the website recently ... they are back today ... I wonder if that will have an impact on the time the eToday in inverterDetail resets

[LucidityCrash]

Nope ... Still generating over 1kW @ 16:00 and it reset. Damn.
...
Found the issue though ... when I /v1/api/stationDay with the body {"id":"XXXX","money":"GBP","timezone":0,"time":"2022-02-14"} you get a json with every reading for that day so you can make a graph look at the last reading just now :

        {
            "batteryPower": -382.69,
            "batteryPowerFu": 382.69,
            "batteryPowerZheng": 0,
            "bypassLoadPower": 0.0,
            "consumeEnergy": 712.69,
            "familyLoadPower": 617.0,
            "money": 0,
            "moneyPec": "1",
            "moneyStr": "GBP",
            "oneSelf": 330.0,
            "power": 348.0,
            "powerPec": "0.001",
            "powerStr": "kW",
            "produceEnergy": 348.0,
            "psum": 18,
            "psumFu": 0,
            "psumZheng": 18,
            "time": 1644828000000,
            "timeStr": "16:40:00",
            "timeZone": 8
        }

Note the timeZone says 8 and the time is 1644828000000 which sure as hell ain't 16:40. it is 08:40 UTC
Every setting I can find says my timezone is UTC and looking at inverterDetail the dateTimestamp is 1644857420000 which is 16:50 and timeZone is 0.0
Dear ghads this is awful !

[enrique]

Here resets at 10:00. Timezone -6

[LucidityCrash]

Sorry stupid email didn't reply to the coment just added it on the end.
If you are GMT -6 then it resets for you at the same time as mine does (16:00 GMT). Its nice to know it is not just my data that is borked 😁

Looks like their backend isn't taking into account the configured Timezone when resetting this value sigh I wonder if there are others.

[enrique]

Testing with SolisCloud, no luck with Solis support.

Module from HACS: 2.0.6
Home Assistant: core-2022.2.5
Data Logger Firmware : MW_08_512_0501_1.80

This is in my HA configuration.yaml

- platform: solis
   name: "Solis Inverter"
   portal_domain: "www.soliscloud.com:13333"
   # user and pswd to acces SolisCloud
   portal_username: !secret un_solis
   portal_password: !secret pw_solis
   # Can't fin this
   # portal_key_id: "" 
   # portal_secret: "portal_secret" 
   # station_id: "" 
   # ppi_solis is 18 digits from SolisCloud when click on plant 
   portal_plant_id: !secret ppi_solis

Only get the following message: "Failed to discover, scheduling retry"

[enrique]

Start gettin this message:
2022-02-11 13:18:07 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547684342464] Error handling message: not a valid value for dictionary value @ data['period']. Got None

[enrique]

Here seems normal:

[hultenvp]

This looks like errors from the energy dashboard. Saw an issue somewhere on home assistant. IIRC it had something to do with datasource changes and should go away after 48 hrs or so. See if I can find the issue

[enrique]

Is there something i can do?

[hultenvp]

Thanks for the offer. I tried to find the issue, but I could not, so was probably a different error. For this one it is difficult to pinpoint what the root cause is of the error. Could be any integration's HTTP connection error, including this one. Looks in your screenshot that there's some info in the warning. First it got 'none', then 'd', then 'da'. maybe good to keep an eye on your logging to see if it produces some leads.

[LucidityCrash]

Oooooh oooh ... I've got a reading on my Daily to grid graph

and from my test python :

"gridSellTodayEnergy": 0.2,
"gridSellTodayEnergyStr": "kWh",

The thing that is interesting is that at the point it went to 0.1 I'd exported 1kWh that day, and at the point it went to 0.2 I'd exported 2kWh ... so it looks like the data that is coming back is to 1kWh accuracy and is a factor of 10 out.

[viking2010]

Having got setup with this integration recently, I'm also getting exactly the same issue. The sell back to grid on the Solis Cloud is still out by a factor of 10 in the graph, but correct when listed at the top of the page. Plus it's only reporting as zero in HA. Did you get any further with this @hultenvp ?

[hultenvp]

Not really, could not spend much time on the integration and the time I could spend I invested in getting the integration configurable via the UI and adding it to the device registry.

[viking2010]

I suspect some of the issues are at Solis' end rather than 'ours'. They said they're going to be doing an upgrade shortly so maybe things will improve.

[LucidityCrash]

Having got setup with this integration recently, I'm also getting exactly the same issue. The sell back to grid on the Solis Cloud is still out by a factor of 10 in the graph, but correct when listed at the top of the page. Plus it's only reporting as zero in HA. Did you get any further with this @hultenvp ?

it shouldn't be 0 in ha ... the api returns the same out by a factor of 10 as the graph but I put in a patch that multiplies it by 10

[viking2010]

Yeah I've just been looking over the .py files and spotted the "x 10". Oh and it wasn't zero in the end, it was user error on my part 😂

[etzka]

Is it ok with my configuration for soliscloud? Because I get no data from solicloud.
Ginlong configuration works fine...

Copy from log

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:96
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 14:36:17 (4 occurrences)
Last logged: 14:36:18

[1896400856] Received invalid command: energy/info

This error originated from a custom integration.

Logger: custom_components.solis.service
Source: custom_components/solis/service.py:103
Integration: solis (documentation, issues)
First occurred: 14:36:31 (1 occurrences)
Last logged: 14:36:31

Failed to discover, scheduling retry.

[LucidityCrash]

That is a little beyond the scope of a github discussion 😁

Short version:

• Install python
• in a shell install requests:
  • pip install requests
• download the file I linked, edit to put in your details (places where there are x's)
• run the script in a shell:
  • python <full path to script>

the output is what we are interested in ... make sure to anonymize it 😁

[etzka]

ok, here it is :)

`C:\Users\visok\AppData\Local\Programs\Python\Python39>python soliscloud_test.py
POST /v1/api/inveterDetail
Content-MD5: uLVSAN8JATSHUSRg82oxRQ==
Content-Type: application/json
Date: Mon, 14 Feb 2022 09:50:00 GMT
Authorization: API 13xxxxxxxxxxxxx651:F2tyYy8xxxxxxxxxxxxxxP7duoU7Uos=
Body：{"id":"13xxxxxxxxxxxxx872","sn":"110xxxxxxxxxxxx09"}

{
"code": "0",
"data": {
"acOutputType": 1,
"apparentPower": 4.3,
"apparentPowerStr": "kVA",
"batteryCapacitySoc": 0.0,
"batteryChargeEnergy": 0,
"batteryChargeEnergyStr": "kWh",
"batteryChargingCurrent": 0.0,
"batteryChargingCurrentStr": "A",
"batteryDischargeEnergy": 0,
"batteryDischargeEnergyStr": "kWh",
"batteryDischargeLimiting": 0.0,
"batteryDischargeLimitingStr": "A",
"batteryFailureInformation01": "0",
"batteryFailureInformation02": "0",
"batteryHealthSoh": 0.0,
"batteryMonthChargeEnergy": 0,
"batteryMonthChargeEnergyStr": "kWh",
"batteryMonthDischargeEnergy": 0,
"batteryMonthDischargeEnergyStr": "kWh",
"batteryPower": 0.0,
"batteryPowerBms": 0,
"batteryPowerBmsStr": "kW",
"batteryPowerFu": 0,
"batteryPowerPec": "1",
"batteryPowerStr": "kW",
"batteryPowerZheng": 0.0,
"batteryTodayChargeEnergy": 0.0,
"batteryTodayChargeEnergyStr": "kWh",
"batteryTodayDischargeEnergy": 0.0,
"batteryTodayDischargeEnergyStr": "kWh",
"batteryTotalChargeEnergy": 0.0,
"batteryTotalChargeEnergyStr": "kWh",
"batteryTotalDischargeEnergy": 0.0,
"batteryTotalDischargeEnergyStr": "kWh",
"batteryType": 0,
"batteryVoltage": 0.0,
"batteryVoltageStr": "V",
"batteryYearChargeEnergy": 0,
"batteryYearChargeEnergyStr": "kWh",
"batteryYearDischargeEnergy": 0,
"batteryYearDischargeEnergyStr": "kWh",
"batteryYesterdayChargeEnergy": 0.0,
"batteryYesterdayChargeEnergyStr": "kWh",
"batteryYesterdayDischargeEnergy": 0.0,
"batteryYesterdayDischargeEnergyStr": "kWh",
"bstteryCurrent": 0.0,
"bstteryCurrentStr": "A",
"bypassAcCurrent": 0.0,
"bypassAcCurrentStr": "A",
"bypassAcVoltage": 0.0,
"bypassAcVoltageStr": "V",
"bypassLoadPower": 0.0,
"bypassLoadPowerStr": "kW",
"collectorId": "xxxx",
"collectorsn": "xxxxx",
"currentState": "0",
"dataTimestamp": "1644832157000",
"daylight": "0",
"dcBus": 0.0,
"dcBusHalf": 0.0,
"dcBusHalfStr": "V",
"dcBusStr": "V",
"dcInputtype": 1,
"dispersionRate": 0.0,
"eMonth": 116.0,
"eMonthStr": "kWh",
"eToday": 8.2,
"eTodayStr": "kWh",
"eTotal": 1.765,
"eTotalStr": "MWh",
"eYear": 265.0,
"eYearStr": "kWh",
"epmFailSafe": 0,
"fac": 49.98,
"facStr": "Hz",
"familyLoadPercent": 0,
"familyLoadPower": 0.0,
"familyLoadPowerPec": "1",
"familyLoadPowerStr": "kW",
"fullHour": 1.03,
"fullHourStr": "h",
"gridPurchasedEnergy": 0,
"gridPurchasedEnergyStr": "kWh",
"gridPurchasedMonthEnergy": 0,
"gridPurchasedMonthEnergyStr": "kWh",
"gridPurchasedTodayEnergy": 0.0,
"gridPurchasedTodayEnergyStr": "kWh",
"gridPurchasedTotalEnergy": 0.0,
"gridPurchasedTotalEnergyStr": "kWh",
"gridPurchasedYearEnergy": 0,
"gridPurchasedYearEnergyStr": "kWh",
"gridPurchasedYesterdayEnergy": 0.0,
"gridPurchasedYesterdayEnergyStr": "kWh",
"gridSellEnergy": 0,
"gridSellEnergyStr": "kWh",
"gridSellMonthEnergy": 0,
"gridSellMonthEnergyStr": "kWh",
"gridSellTodayEnergy": 0.0,
"gridSellTodayEnergyStr": "kWh",
"gridSellTotalEnergy": 0.0,
"gridSellTotalEnergyStr": "kWh",
"gridSellYearEnergy": 0,
"gridSellYearEnergyStr": "kWh",
"gridSellYesterdayEnergy": 0.0,
"gridSellYesterdayEnergyStr": "kWh",
"homeLoadEnergy": 0,
"homeLoadEnergyStr": "kWh",
"homeLoadTodayEnergy": 0.0,
"homeLoadTodayEnergyStr": "kWh",
"homeLoadTotalEnergy": 0.0,
"homeLoadTotalEnergyStr": "kWh",
"homeLoadYesterdayEnergy": 0.0,
"homeLoadYesterdayEnergyStr": "kWh",
"iAc1": 6.0,
"iAc1Str": "A",
"iAc2": 5.9,
"iAc2Str": "A",
"iAc3": 6.0,
"iAc3Str": "A",
"iPv1": 7.4,
"iPv10": 0,
"iPv10Str": "A",
"iPv11": 0,
"iPv11Str": "A",
"iPv12": 0,
"iPv12Str": "A",
"iPv13": 0,
"iPv13Str": "A",
"iPv14": 0,
"iPv14Str": "A",
"iPv15": 0,
"iPv15Str": "A",
"iPv16": 0,
"iPv16Str": "A",
"iPv17": 0,
"iPv17Str": "A",
"iPv18": 0,
"iPv18Str": "A",
"iPv19": 0,
"iPv19Str": "A",
"iPv1Str": "A",
"iPv2": 0,
"iPv20": 0,
"iPv20Str": "A",
"iPv21": 0,
"iPv21Str": "A",
"iPv22": 0,
"iPv22Str": "A",
"iPv23": 0,
"iPv23Str": "A",
"iPv24": 0,
"iPv24Str": "A",
"iPv25": 0,
"iPv25Str": "A",
"iPv26": 0,
"iPv26Str": "A",
"iPv27": 0,
"iPv27Str": "A",
"iPv28": 0,
"iPv28Str": "A",
"iPv29": 0,
"iPv29Str": "A",
"iPv2Str": "A",
"iPv3": 0,
"iPv30": 0,
"iPv30Str": "A",
"iPv31": 0,
"iPv31Str": "A",
"iPv32": 0,
"iPv32Str": "A",
"iPv3Str": "A",
"iPv4": 0,
"iPv4Str": "A",
"iPv5": 0,
"iPv5Str": "A",
"iPv6": 0,
"iPv6Str": "A",
"iPv7": 0,
"iPv7Str": "A",
"iPv8": 0,
"iPv8Str": "A",
"iPv9": 0,
"iPv9Str": "A",
"id": "130xxxxxxxxxxxxxx72",
"insulationResistance": 0,
"inverterMeterModel": 1,
"inverterTemperature": 11.2,
"inverterTemperatureUnit": "\u2103",
"model": "79",
"name": "Solis-3P8K-4G",
"nationalStandardstr": "User-define",
"oneSelf": 0.0,
"pac": 4.29,
"pacPec": "1",
"pacStr": "kW",
"pepm": 0.0,
"pepmSet": 0.0,
"pepmSetStr": "kW",
"pepmStr": "kW",
"porwerPercent": 0.536,
"pow1": 4386,
"pow10": 0,
"pow10Str": "W",
"pow11": 0,
"pow11Str": "W",
"pow12": 0,
"pow12Str": "W",
"pow13": 0,
"pow13Str": "W",
"pow14": 0,
"pow14Str": "W",
"pow15": 0,
"pow15Str": "W",
"pow16": 0,
"pow16Str": "W",
"pow17": 0,
"pow17Str": "W",
"pow18": 0,
"pow18Str": "W",
"pow19": 0,
"pow19Str": "W",
"pow1Str": "W",
"pow2": 0,
"pow20": 0,
"pow20Str": "W",
"pow21": 0,
"pow21Str": "W",
"pow22": 0,
"pow22Str": "W",
"pow23": 0,
"pow23Str": "W",
"pow24": 0,
"pow24Str": "W",
"pow25": 0,
"pow25Str": "W",
"pow26": 0,
"pow26Str": "W",
"pow27": 0,
"pow27Str": "W",
"pow28": 0,
"pow28Str": "W",
"pow29": 0,
"pow29Str": "W",
"pow2Str": "W",
"pow3": 0,
"pow30": 0,
"pow30Str": "W",
"pow31": 0,
"pow31Str": "W",
"pow32": 0,
"pow32Str": "W",
"pow3Str": "W",
"pow4": 0,
"pow4Str": "W",
"pow5": 0,
"pow5Str": "W",
"pow6": 0,
"pow6Str": "W",
"pow7": 0,
"pow7Str": "W",
"pow8": 0,
"pow8Str": "W",
"pow9": 0,
"pow9Str": "W",
"power": 8.0,
"powerFactor": 1.0,
"powerPec": "1",
"powerStr": "kWp",
"productModel": "79",
"psum": 0.0,
"psumCal": 4.29,
"psumCalPec": "1",
"psumCalStr": "kW",
"psumStr": "kW",
"reactivePower": 0.0,
"reactivePowerStr": "Var",
"rs485ComAddr": "101",
"sirRealtime": 0,
"sn": "11xxxxxxxxxxx09",
"sno": "1xxxxE",
"socChargingSet": 0,
"socDischargeSet": 0,
"state": 1,
"stationId": "129xxxxxxxxxxxxx920",
"stationName": "Saul\u0117s Elektrin\u0117 (Arlauskas)",
"storageBatteryCurrent": 0.0,
"storageBatteryCurrentStr": "A",
"storageBatteryVoltage": 0.0,
"storageBatteryVoltageStr": "V",
"tag": "YingZhen",
"temp": 175.0,
"tempName": "IGBT Temperature",
"timeStr": "2022-02-14 11:49:17",
"timeZone": 2.0,
"uAc1": 231.7,
"uAc1Str": "V",
"uAc2": 235.6,
"uAc2Str": "V",
"uAc3": 243.0,
"uAc3Str": "V",
"uInitGnd": 0,
"uInitGndStr": "V",
"uPv1": 592.7,
"uPv10": 0,
"uPv10Str": "V",
"uPv11": 0,
"uPv11Str": "V",
"uPv12": 0,
"uPv12Str": "V",
"uPv13": 0,
"uPv13Str": "V",
"uPv14": 0,
"uPv14Str": "V",
"uPv15": 0,
"uPv15Str": "V",
"uPv16": 0,
"uPv16Str": "V",
"uPv17": 0,
"uPv17Str": "V",
"uPv18": 0,
"uPv18Str": "V",
"uPv19": 0,
"uPv19Str": "V",
"uPv1Str": "V",
"uPv2": 0,
"uPv20": 0,
"uPv20Str": "V",
"uPv21": 0,
"uPv21Str": "V",
"uPv22": 0,
"uPv22Str": "V",
"uPv23": 0,
"uPv23Str": "V",
"uPv24": 0,
"uPv24Str": "V",
"uPv25": 0,
"uPv25Str": "V",
"uPv26": 0,
"uPv26Str": "V",
"uPv27": 0,
"uPv27Str": "V",
"uPv28": 0,
"uPv28Str": "V",
"uPv29": 0,
"uPv29Str": "V",
"uPv2Str": "V",
"uPv3": 0,
"uPv30": 0,
"uPv30Str": "V",
"uPv31": 0,
"uPv31Str": "V",
"uPv32": 0,
"uPv32Str": "V",
"uPv3Str": "V",
"uPv4": 0,
"uPv4Str": "V",
"uPv5": 0,
"uPv5Str": "V",
"uPv6": 0,
"uPv6Str": "V",
"uPv7": 0,
"uPv7Str": "V",
"uPv8": 0,
"uPv8Str": "V",
"uPv9": 0,
"uPv9Str": "V",
"userId": "13xxxxxxxxxxxxxxx51",
"version": "1F002F"
},
"msg": "success",
"success": true
}`

[LucidityCrash]

cool ... the variable unit fix #90 needs to be implemented for the SolisCloud API too. Looks like we'll also need to do something to manage variable units for other things like eToday/Month/Year/Total

[etzka]

Only ac output total power and Total energy looks bad. eToday, month and year looks good for me

[hultenvp]

Yeah, but when we fix it we should fix it in a generic fashion. and convert energy if needed.

FYI: Busy weeks at work, little time to work on this integration coming week, will be a bit slow in my responses

[LucidityCrash]

Getting 502 bad gateway from all SolisCloud API endpoints since about 09:00 UTC this morning 😢

Edit : m.ginlong.com is still functioning.

[LucidityCrash]

API started returning data at 01:39 UTC again this morning no idea if there has been any significant changes after the maintanence yesterday ... year/month/yesterday for grid sell/purchased are still 0. I've not exported anything today so no idea if the daily exported number is now corrected - the graph on the website is now correct but the exported csv is not.

[LucidityCrash]

Just got this on the soliscloud web pages:

[SolisCloud] The system will be upgraded and maintained from (UTC)0:00 to 4:00 on 18/02/2022. 
Please be notice that some users may be affected during the maintenance period, sorry for any possible inconvenience caused to you.

[LucidityCrash]

woop ... Daily Energy to grid and daily energy from grid graphs are now showing non zero numbers in the web site graph ... the exported CSV however still shows 0. And the same graph in the Android app is showing 0 😁

[hultenvp]

Agile! Next iteration they add CSV, then one after Android app, but then the website fails again 😄

[MartinJSa]

Would anyone be willing to give me a hand trying to get this working with the SolarmanPV side of the service please? I have an API ID and Key from solarman customer service, I've worked out my plantid - but I'm not sure on the correct host/URL to hit? The website URL is home.solarmanpv.com but when getting the API documentation the API is URL is api.solarmanpv.com.

If I use api. I get "Unable to communicate with api.solarmanpv.com, please verify configuration." otherwise I get "Failed to discover, scheduling retry." messages - is there somewhere I can look to get a more detailed error on what I'm doing wrong please?

[hultenvp]

Indeed very odd that they use a different auth mechanism for Solarman.
Lucky for you the ginlong portal will still work for a few years. Not sure where I read it, but IIRC they take 5 years for the phaseout.
Not sure how proficient you are with python, but if you are willing to write and maintain an API similar to the soliscloud API then I'm happy to see how we can work together in supporting solarman. You can always DM me on discord.

On trying to use Soliscloud: For Solis users I'm pretty sure that when you log in on soliscloud for the first time that it will migrate your data from ginlong to soliscloud and remove the logger & data in the old ginlong portal. I really can't tell you if this would also work fine for Solarman devices. If you are not afraid of the risk of losing history you could give it a try. You'll probably not need plantId, but logger S/N, didn't go through the process myself yet.

[MartinJSa]

Thanks very much - I'm afraid I'm not proficient in Python at all, I could happily write the user stories (one of my work roles is as a product owner for a software company) but would need lots of help getting the code written. I'm going to play with the postman collection a bit to try and understand how the solarman API works, and I'll see if I can persuade one of my work friends to give me a hand :)

[hultenvp]

Thanks Martin,

You can use soliscloud_api as a template. I can help with the coding part, but testing I cannot do without the right hardware So I really need an active maintainer if you want it integrated.

[menno-smit]

Hi @hultenvp and @MartinJSa, I have the same issues as Martin that I am on the "home.solarmanpv.com" platform. Given that is not (yet) working with this project, I have created accounts on "soliscloud.com", "m.ginlong.com", and "home.solarman.cn". The first doesn't allow me to add my datalogger (perhaps serial number 17860XXXXX not in specified range?), however the latter two do allow me to add my datalogger but don't see the datalogger as being online, while all the data is coming in fine on "home.solarmanpv.com". I've noticed my datalogger is uploading to access1.solarmanpv.com / access2.solarmanpv.com. Do you have any suggestions on getting the 3 other platforms working, preferably Solis Cloud as that seems to be the newest one? Many thanks! Menno

[skupu]

I'm struggling with solarman.

The valid api address is globalapi.solarmanpv.com and I managed to get data over curl commands.
So the only way would be to modify existing integration or to prepare a new one.

I am not experienced enough to do it.
@hultenvp I could make testing.
I have a valid API documentation from solarman.

[stefaanjespers]

The api soliscloud works perfect for me,
Is it possible to add the batteryPower sensor in the next update?

[LucidityCrash]

Don't see why not.

[TheRealMrSteel]

Works also great for me! I think I messed up in the beginning (after I changed 'name' from My Solis Inverter to Solis. All the entities ended up double. Had to do some searching how to get rid of them, but they're gone now 😄.
I'm super happy with this!
If anyone has their setups to share of nice cards to add, please show some examples. I'm currently only using 'Energy Today' in the Energy dashboard.

Thanks for the work guys 👍🏻 will definitely follow this.

[LucidityCrash]

Not directly related to this plugin but the SolisCloud webUI and App (at least on Android) have recently recieved updates thanks to yours truely that have fixed the daily imported from grid graphs 🙂, unfortunately the latest one has also completely broken the export to CSV as of 3am UTC on the 28th of Feb, the report is completely empty 🙁.
Issues I'm still chasing :

• Daily exported to grid is out by a factor of 10 on both API, and WebUI, and is 0 on CSV export*
• Daily imported from grid is 0 on CSV export*
• Daily Yield resets to 0 at 16:00 UTC - apparently for everyone no matter your TZ

*when it was working 🙂

I kinda think they a) this platform is still seriously Beta release standard and b) they should be paying me for my bug hunting efforts 😁

[LucidityCrash]

Yay ... export to csv is no longer empty ... still showing 0's for daily import and export though

[viking2010]

I've also been submitting numerous bugs and feature requests. They closed all my tickets off yesterday with no explanation as to why, so had to reopen them again. One member of the team said they sent a firmware update to my inverter as they are anticipating a new client app update soon as well as a website update. But you're right @LucidityCrash, it does seem to be very much a BETA system (possibly even ALPHA!) at the moment!
-Adrian

[sulas]

Is there anyone available to help me please. I got letters in my portal_plant_id, not digits only, and as a consequence an error message in the configuration validation: Invalid config for [sensor.solis]: expected int for dictionary value @ data['portal_plant_id'].
How can I fix this issue? I presume the portal_plant_id validation allows only numbers?

[LucidityCrash]

that is the wrong portal domain ... that is for the original API that this plugin supports you want :
portal_domain: "www.soliscloud.com:13333"

[sulas]

now I've got:
`This error originated from a custom integration.

Logger: custom_components.solis.service
Source: custom_components/solis/service.py:103
Integration: solis (documentation, issues)
First occurred: 18:28:29 (1 occurrences)
Last logged: 18:28:29

Failed to discover, scheduling retry.`

Probably I need to request API access?

[LucidityCrash]

If you've not requested api access how are you providing portal_key_id & portal_secret ? These are only obtainable by contacting Solis support and requesting API access 😀

[sulas]

haha, I simply used my login details I have for the portal. Right, sorry for disruption ;)

[LucidityCrash]

No worries.

[markbarnettsa]

Hi all, is there a different way to obtain my key_id and secret. my local support team re-directed me to Ginlong in China and they have now stone-walled me:

"....We have gone through the website you provide, and this is a third-party monitoring portal which is not recognised by our system. And the "key_id" and "key_secret" is part of our API scheme and that is not open to the public. We only can provide that kind of information to the companies which we cooperated and signed the NDA...."

can i find the key_id and secret if i capture a session with wireshark...any other suggestions?

thanks!

[LucidityCrash]

Yeah, I also think it very much depends on that 1st point of contact some of the regional support teams are more helpful than others.

[sulas]

I'm waiting 2 weeks already for API from UK support team, need a lot of patience...

[viking2010]

I called their support number in the UK and got through to a great support guy. He said they are around 1 to 2 months behind answering support tickets online. I asked about the ticket I raised to get the key and secret and he said its not a quick process and would likely need me to sign the NDA too. He has passed my ticket on to sales to deal with. Will be a long wait me thinks!

[dhoogfr]

I just contacted the Dutch support guys and they stated that it was currently not possible to create new keys and secrets because of security issues. And that they are currently working on a fix.

[viking2010]

My key/secret came through yesterday after chasing the ticket I had with support, so it is possible to still get it. I did have to sign the NDA though in order to get it. I've also got them to reduce the monitoring update from 5 mins to 1 min which is great, not real time, but closer to it at least!

[gijssenh]

In the logging I see login succeeded but always " [custom_components.solis.service] Failed to discover, scheduling retry." is returning in the log. Any idea what micht be wrong?

[gijssenh]

I got an error in HA with my plantid on https://www.soliscloud.com:13333/. It seems it has to be a number but mine looks to HEX. So I made an account on m.ginlong.com and created a plant with my wifi logger (I found this workaround somewhere). All works fine on m.ginlong.com and the plantid seems to be a normal number. I used this plantid for the configuration in HA. This is my configuration in HA:

sensor:

• platform: solis
  name: "MySolisInverter"
  portal_domain: "www.soliscloud.com:13333"
  portal_username: FIRSTNAME.LASTNAME@PROVIDER.be"
  portal_password: "MYPASSWORD"
  portal_key_id: "13XXXXXXXXXXXXXXX61"
  portal_secret: "2XXff8XXXXXXXXX8aXXXXXXXXXXXX9b8"
  portal_plant_id: "1X6XXX1"

[hultenvp]

The plantId is different on SolisCloud. It's called StationID and that sold be a hex number. Password is only necessary for m.ginlong.com. Key and secret are needed for soliscloud.

[gijssenh]

After removing the line with portal_password and changing the portal_plant_id to the one from SolisCloud I can not restart Home Assistant due to the following error:

The system cannot restart because the configuration is not valid: Invalid config for [sensor.solis]: expected int for dictionary value @ data['portal_plant_id']. Got '11ABC9'. (See ?, line ?).

Is there maybe somewhere a more recent version of the Solis integration? I have version 2.1.0

[LucidityCrash]

portal_plant_id is not hex it is just an int ... look back here #71 (reply in thread) and #71 (reply in thread)
looks like you are using the wrong plant id :)

[gijssenh]

I found the correct portal_plant_id thanks to your reference to #71 (reply in thread)
The integration is running fine now. Thanks :-)

[Oskar70]

They have done it. But I am sure and agree with you, that on the long run it will cost them to may server resources. I have told them this and asked for a possibility getting data directly from the wifi dongle, attached to the Solis inverter. I was told, that this would be not possible from their side.
As I replied to hultenpv, there is an update for HA Ginlong Solis PV portal integration. I installed it in the afternoon and since then, but from time to time only, I get a series of 4 to 5 datas every 1 minute. Afterwards again the 5 minutes interval. I can't recognize any system in it.
For the setup of my dahboard, W and kWh form Solis have been needed. If I need better data for new high power concumers, I think about purchasing and installing a Shelly 3em to get rid of all my frustration about Solis.

[ececconi99]

I'm using this to try look at power data from my Solis inverter and use the resulting values in a flow chart.
However, this HA Solis integration has ten entities with "power" in the name and of these, currenty, three return "unavailable", 2 return "0W" and one returns "Unknown" .

Not that I'm up to speed yet on how this is all done but, so far, I've not been able to find any of the HA Solis entity names in the Solis API V2.0 documentation. So, could someone explain how and where in the code the HA<> Solis API name correspondances have been set up? Also it would be good if someone could look into why so few useful or meaningful data values are available through this integration, please?

[snigehere]

I use the solis cloud integration and from that sensor.my_solis_inverter_ac_output_total_power

[ececconi99]

My HA returns that one as “unknown “

…

On Fri, 9 Feb 2024 at 18:35, snigehere ***@***.***> wrote: I use sensor.my_solis_inverter_ac_output_total_power — Reply to this email directly, view it on GitHub <#71 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFHBWVHNV55LB3T6DENWNLLYSZT7JAVCNFSM5NAXCH42U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TQNBSGIYTGMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[ececconi99]

Actually, rereading your email, I don’t see that entity with the my_ prefix. Where did you find that?

…

On Fri, 9 Feb 2024 at 18:35, snigehere ***@***.***> wrote: I use sensor.my_solis_inverter_ac_output_total_power — Reply to this email directly, view it on GitHub <#71 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFHBWVHNV55LB3T6DENWNLLYSZT7JAVCNFSM5NAXCH42U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TQNBSGIYTGMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[cdensel]

Hi,

Thanks so much for this addon. I'm very new to HA and to solar. My installation was just brought online yesterday.
I've tried to add the relevant fields to the HA built in "Energy Dashboard". I was hoping somebody can confirm I've used the correct values?

Grid Consumption: Solis Daily Grid Energy Purchased
Return to Grid: Solis Daily On-grid Energy
Solar Production: Solis Energy Today
Battery Systems: Solis Daily Energy Discharged, Solis Daily Energy Charged

The figures in my dashboard aren't matching what I'm seeing in the SolisCloud app, but I wonder if it's just that I haven't waited long enough for the data to be accurate.

Thanks,
Conor

[brida91]

Hi, i have same configuration, all value in home assistant are equals to soliscloud. need one entire day to see accurate data!

[cdensel]

Thanks for confirming! Hopefully that also helps another newbie down the line.

…

On Wed 28 Feb 2024, 13:11 brida91, ***@***.***> wrote: Hi, i have same configuration, all value in home assistant are equals to soliscloud. need one entire day to see accurate data! — Reply to this email directly, view it on GitHub <#71 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APASISFKYP7RSFDMTTSB37LYV4UJVAVCNFSM5NAXCH42U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TQNRRHAZTIMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[jpyounghardy]

Hi i have a Fujitsu Airstage intergration that connects directly to the dongle not the cloud can't solis do the same so we can get more regluar updates

[GPDixon]

You can already do this, you just need the first generation dongle that allows you to connect directly to it. You can then not only get updates every few seconds, you can also control and update the inverter. For example, you can automatically charge or discharge the batteries (if you have any) according to the best import or export prices from your energy provider.

[Oskar70]

I am very keen to get more details how to do it. I am getting data via Solis cloud. During the last year I had more than twenty emails with the EuropeanSupport team. They managed, that sometimes I can get data every minute, but it is not always one minute only (very often 5 to 10 minutes only). It was very hard to make them understand what I wanted,.At the end I got an video, showing how to get the cloud data into Home Assistant. I am only using HA to write the data into influx time series db. Reading it from there into my own node red based smart home system.
I can access the inverter via dongle, using its IP-adrss and user and Password (admin, admin). It is showing me the current power and the Total Yield, the two values I need only. I don't know, how often these values get updated, but a direct access to these would be wonderful! So it would be great to get details.

[GPDixon]

what dongle do you have? If you can already access it via its IP address then try the solarman integration mentioned later in this chain. It's the one I use and it is very reliable.

[snigehere]

I have been through the same discussion as you ... I am also on one minute cycles but, as I pointed out to them, delays in their internal systems sometimes mean that the data is slow cycling from the collection system to the users account and so we end up with stale data being served via the API. The wifi dongle is supposed to be able to serve data to two servers however its never worked - I have tried multiple times to find a solution without success. I am told that the LAN dongle does support this correctly however I can't find anywhere to buy these anymore - I checked with my supplier and they say they are no longer available.

The only real way to solve this is to ditch the solis cloud dongle and use the an RS485 serial cable connection (in the same plug they wifi dongle goes into) that allows the data to be read out and and then to use the mqtt integration https://github.com/incub77/solis2mqtt to process the data.

So far I have not worked up the enthusiasm to do this

Maybe you could also write a screen scraper to read the dongle web page and keep refreshing it .. that's beyond my skills.

[snigehere]

Sorry - just to add ... if you get the right dongle (LAN attached version) you can use this integration to read the data from the second server
https://github.com/StephanJoubert/home_assistant_solarman

[GPDixon]

That's the integration I use. Works very well for both reading and writing via the right dongle. It doesn't have to be a LAN dongle. I have a Gen-1 Wifi dongle and it works beautifully

[LucidityCrash]

That integration doesn't use the 2nd server connection which is an outgoing thing - dongle sends data to server, it connects to the dongle and pulls the data. There just needs to be a modbus service running on the dongle but as pointed out not all dongles have that

[GPDixon]

I keep referring to my dongle as Gen-1. I think it's actually a Gen-2 because the current version is Gen-3. Mine looks like this one in the attached diagram. Has the code DLS-W on its box. I don't think you can buy them now but occasionally I see a brand new one come up on eBay - obviously some people have spare/old stock.

[jpyounghardy]

Is that the one with no buttons or leds on it

[snigehere]

That integration doesn't use the 2nd server connection which is an outgoing thing - dongle sends data to server, it connects to the dongle and pulls the data. There just needs to be a modbus service running on the dongle but as pointed out not all dongles have that

Thanks - I am wrong and you are right ... As you say not all dongles support this - mine is Device serial number starting 71 with Firmware version MW_08_512_0501_1.94 .. its says its a "WIFI (EN2 8M)" and it does not run the mobus server.

[Oskar70]

My Wlan Dongle also has MW_08_512_0501_1.94 Software, but the serial no. starts with 40. According to one the previous emails, this combination might enable direct access to the dongle. I am very busy with some other things, but I will check during the summer and let everybody know.--Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet.Am 03.04.24, 21:05 schrieb jpyounghardy ***@***.***>: Is that the one with no buttons or leds on it —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[jpyounghardy]

will this one work its lan and wifi but gen 3
https://leisurepower.co.uk/solar/solar-accessories/15036/solis-data-logging-stick-wifi-gen-3-sol-s2-wl-st?gad_source=1&gclid=EAIaIQobChMI8IKswbeohQMV05ZQBh3J1Qk5EAQYAiABEgKR-vD_BwE

[LucidityCrash]

https://github.com/fboundy/ha_solis_overview

Shows a matrix of which dongles work with which methods