Help with setup

[peledudok]

Hi,

I want to setup Solis inverter. I got yesterday teh API credentials.

I see that in hSECRE API field 00 are already filled in a past the secret code after the 00.
However without the 00 it is also not working.

What do i wrong? Can you help me

[hultenvp]

The secret should indeed just be the secret you got and it should replace the 00 already there (that's just default).
Do you have debug logging on? If not, please do so (See wiki) and paste the error you're seeing in the log.

PS: You might want to blur out personal info.

[peledudok]

This is what is found in the log with the DEBUG on

2022-11-04 12:54:25.402 DEBUG (MainThread) [custom_components.solis.soliscloud_api] workarounds: {'correct_daily_on_grid_energy_enabled': True}
2022-11-04 12:54:25.589 WARNING (MainThread) [custom_components.solis.soliscloud_api] No inverters found

Also which station id should i use :
https://soliscloud.com/:13333#/station/stationdetail_1?id=1298491919448858888
https://soliscloud.com/:13333#/station/collector/collectordetail?id=1306858901387579052
https://soliscloud.com/:13333#/station/collector/collectordetail?id=1306858901387579052&stationId=1298491919448858888

[hultenvp]

The station id is the one ending with 8888 so you have the right one.

Note the big disclaimer on the readme. Currently the API is officially closed until further notice. Some people that already had an active key& secret still can access data, but many can't. The reasons for closure is gdpr, not sure what that means for people outside eu, but big chance you'll not be able to use the API because of that.

I sometimes see that if the time on my test VM is wrong that I also cannot fetch inverter lists. Check your time, but if that is not the case then probably you are locked out of using the API until Solis fixes the API.

[peledudok]

The thing is that i created a ticket on 18/10 for requesting an api. They told me it was not possible due gdpr issue.
However on 1/11 i received suddenly an answer that my api was created. I actived in the soliscloud dashboard.
Yesterday i received an answer from Solis EU service department:
"There is no issues with your API access we have just checked. Apologies but we can not assist any further"_

My opnion is that my new API is and should work according to the EU Solis service department.

The time is correct on the converter.

BTW the error in the popup is not always the same and i saw once in the log that is was logged on but didn't find the inverter strange enough.

[terppatyyppi]

Is the API really closed also for people who do have an active API key that shows "Activated" on SolisCloud API Management page?
That would explain my issue then as well....however, from the README disclaimer, I had understood that for those that already have the key and secret, this would still work?

[terppatyyppi]

I have concluded the same, they have reopened it on Oct 26:
https://solis-service.solisinverters.com/support/solutions/articles/44002212561-api-access-soliscloud

But maybe something has changed and now the integration can not access it in it's current form (maybe with the authentication rules or something)? Anyway, I'm no expert, so can only make stupid guesses.

[peledudok]

I'm also not an expert let's hope that hultenvp can solve the issue.

[terppatyyppi]

There's a document describing the interface behind the link I shared above, maybe that provides some clues into what has changed with their access method, if anything.

[peledudok]

Yrs i saw that but to technical for me . 😏

[terppatyyppi]

Yes, it has no value for a user of the integration, but maybe for the developer it could tell if something has changed. Then again, I'm sure they know that inside-out already anyway.

[peledudok]

@hultenvp is did see that the wintertime was not set on the converter i changed it and tried to installed the solis inverter intergration and got a unknown error. Here is the debug log output:

2022-11-05 16:03:29.032 DEBUG (MainThread) [custom_components.solis.soliscloud_api] workarounds: {'correct_daily_on_grid_energy_enabled': True}
2022-11-05 16:03:29.381 INFO (MainThread) [custom_components.solis.soliscloud_api] Login successful
2022-11-05 16:03:29.381 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Found inverters: ['1002010226020296']
2022-11-05 16:03:29.381 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Fetching data for serial: 1002010226020296
2022-11-05 16:03:29.471 INFO (MainThread) [custom_components.solis.soliscloud_api] /v1/api/stationDetail responded with error: 1:数据异常 请联系管理员
2022-11-05 16:03:29.472 DEBUG (MainThread) [custom_components.solis.ginlong_base] AttributeError, plantName does not exist
2022-11-05 16:03:29.472 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/config/custom_components/solis/ginlong_base.py", line 70, in getattr
return self._data[name]
KeyError: 'plantName'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 82, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 180, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
result = await method(view, request, data, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 280, in async_configure
result = await self._async_handle_step(
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File "/config/custom_components/solis/config_flow.py", line 117, in async_step_credentials_secret
if await api.login(async_get_clientsession(self.hass)):
File "/config/custom_components/solis/soliscloud_api.py", line 200, in login
self._plant_name = getattr(data, INVERTER_PLANT_NAME)
File "/config/custom_components/solis/ginlong_base.py", line 73, in getattr
raise AttributeError(name) from key_error
AttributeError: plantName

[hultenvp]

The server reports an error which translates to "Data anomalies Contact your administrator". No clue what that means

The login sequence has 3 calls:

1. InverterList(PlantId) --> Success
2. InverterDetails(inverterId) --> Success
3. PlantDetails(PlantID) --> Fail

The call to get station (=plant) details fails although it takes plant ID as a param, just like the inverter list call.
So, it looks like server side something is going wrong. Your Plant ID is fine, otherwise the first call would have failed.
I've also looked into the document you refer to. This is a newer version of the document, but there's no change in parameters of the plantDetails call.
What's adding to the confusion is that my own test instance runs fine, I do not see any issues with the call. So why is yours failing?

[peledudok]

Perhaps using my username instead of emailadress?
My plantid is simpelzon.
I can't tedt it now the inverter is already offline

[jonathanmandrews2022]

Wonder if this is related only to new installs? Eg something is happening at Solis side on first runs or in this case not happening - I am a new user

[terppatyyppi]

Wanted to report to you on this:
My integration started working, with exact same credentials and information that previously yielded the "credentials not accepted" error.

The only difference I can think of, is that on Friday the plant was offline, and now when retrying, it was online.
I did not expect this to be any kind of a factor, but maybe it was. Since the API is for the cloud, I assumed it's enough to access that when installing the integration, but maybe in addition the plant indeed needs to be in production.

[hultenvp]

@peledudok PlantId is a number. "simplezon" is probably the name you gave the plant. I hope you use the number ending with "8888" as we discussed higher up this thread.
Try uninstalling and installing the integration, see if that helps.

[peledudok]

yes i use the plantid 1298491919448858888 and i'm not using the final forward slash "/"in the pv portal name.

i remove the hacs Ginlong Solis PV portal integration and installed it again (v3.0.8).
Still not working see attachment for the logging
log solis inverter 1339.txt

[hultenvp]

I'm going to make a new version for you that at least the integration doesn't crash anymore.
Worst case it's going to retry for eternity, best case it somehow recovers and allows you to move on.

[peledudok]

thx for your help....i hope some how some day it will work. I created again a ticket at the Solis support portal.
Let see if the are willing to support in this issue

[hultenvp]

I made a new version, v3.0.9. Give it a go and let me know

[peledudok]

@hultenvp,
i removed/restart HA and installed the new version V.3.09.
No luck.
Intergration still crashes
I attached 2 logs.
1 i tried to login with email and one i tried to login with username.
Both attempts failed.

I see in the log:
2022-11-06 17:26:48.647 DEBUG (MainThread) [custom_components.solis.ginlong_base] AttributeError, plantName does not exist
2022-11-06 17:26:48.648 INFO (MainThread) [custom_components.solis.soliscloud_api] Failed to acquire plant name, login failed

What does it do: custom_components.solis.ginlong_base] AttributeError, plantName does not exist ????
Do i need to do something with solis ginlong?

[peledudok]

the 2 logs from the earlier post

log solis - email.txt
log solis - username.txt

[peledudok]

more logs i don't have because the intergration is not running.
The intergration gives in the popup menu a unknow error. I have to close the popup to use HA.
So it is not running as you think

[hultenvp]

Indeed. I made a small mistake. v3.0.10 should fix it. Time for me to start looking into how to run unit tests.

[peledudok]

Tomorrow first thing todo when the converter is online.

[peledudok]

goodmorning, sorry to write it but also the new version v3.0.10 crashes (i have to close the popup).
i have only 1 log:
2022-11-07 10:00:56.381 DEBUG (MainThread) [custom_components.solis.soliscloud_api] workarounds: {'correct_daily_on_grid_energy_enabled': True}
2022-11-07 10:00:56.623 INFO (MainThread) [custom_components.solis.soliscloud_api] Login successful
2022-11-07 10:00:56.623 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Found inverters: ['1002010226020296']
2022-11-07 10:00:56.623 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Fetching data for serial: 1002010226020296
2022-11-07 10:00:56.973 INFO (MainThread) [custom_components.solis.soliscloud_api] /v1/api/stationDetail responded with error: 1:数据异常 请联系管理员
2022-11-07 10:00:56.974 DEBUG (MainThread) [custom_components.solis.ginlong_base] AttributeError, plantName does not exist
2022-11-07 10:00:56.974 INFO (MainThread) [custom_components.solis.soliscloud_api] Failed to acquire plant name, login failed

[peledudok]

@hultenvp,
Vandaag weer eens een poging gedaan om de integration te installeren.
In de logging zie ik wel andere foutmeldingen dan een paar dagen geleden:

2022-11-10 13:05:14.571 DEBUG (MainThread) [custom_components.solis.soliscloud_api] workarounds: {'correct_daily_on_grid_energy_enabled': True}
2022-11-10 13:05:23.305 INFO (MainThread) [custom_components.solis.soliscloud_api] Login successful
2022-11-10 13:05:23.306 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Found inverters: ['1002010226020296']
2022-11-10 13:05:23.306 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Fetching data for serial: 1002010226020296
2022-11-10 13:05:23.335 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Error from URI (/v1/api/inveterDetail) : 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://www.soliscloud.com:13333/v1/api/inveterDetail')
2022-11-10 13:05:23.335 INFO (MainThread) [custom_components.solis.soliscloud_api] Unable to fetch details for device with ID: 1308675217947420064
2022-11-10 13:05:23.357 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Error from URI (/v1/api/stationDetail) : 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://www.soliscloud.com:13333/v1/api/stationDetail')
2022-11-10 13:05:23.357 INFO (MainThread) [custom_components.solis.soliscloud_api] Unable to fetch details for Station with ID: 1298491919448858888
2022-11-10 13:05:23.357 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Unexpected response from server: None
2022-11-10 13:05:23.357 INFO (MainThread) [custom_components.solis.soliscloud_api] Failed to acquire plant name, login failed

[hultenvp]

(responding in English, so others can also use the info)

The SolisCloud API does not excel in stability, I see the same issues: TimeOuts, wronge mimetype in JSON response, empty responses.
Normally the integration doesn't care and just retry and all is fine again.

With the big change of introducing the UI config the service code that triggers the read calls has changed as well. The code was however not fully robust against server errors. My test setup was not equipped to run day-long tests, so never captured it.
I fixed the retry now in 3.1.0. Ran it for >2 days without a hitch in my own HA system.

I really hope both the UI config and the recovery on server errors are now stable, but if not, just open a new ticket.

[peledudok]

sorry to tell you but the intergration keeps crashing and the logs are the same:2022-11-11 11:19:42.280 DEBUG (MainThread) [custom_components.solis.soliscloud_api] workarounds: {'correct_daily_on_grid_energy_enabled': True}
2022-11-11 11:19:42.446 INFO (MainThread) [custom_components.solis.soliscloud_api] Login successful
2022-11-11 11:19:42.446 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Found inverters: ['1002010226020296']
2022-11-11 11:19:42.446 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Fetching data for serial: 1002010226020296
2022-11-11 11:19:42.550 INFO (MainThread) [custom_components.solis.soliscloud_api] /v1/api/stationDetail responded with error: 1:数据异常 请联系管理员
2022-11-11 11:19:42.551 DEBUG (MainThread) [custom_components.solis.ginlong_base] AttributeError, plantName does not exist
2022-11-11 11:19:42.551 INFO (MainThread) [custom_components.solis.soliscloud_api] Failed to acquire plant name, login failed

Is it possible you can help me by taken over my pc?

[hultenvp]

Hi @peledudok: Sorry, but it is not crashing, it just nicely reports what the problem is. As per the other discussion thread, the integration cannot log in as one API call responds with an error.

[peledudok]

5 days ago i opened a ticket at solis support side. Still no answer.

[matteoa66]

Hello when I try to configure for the first time i receive this message "Cannot login with provided URL and credentials"
I have apikey from solis, Im trying to access to soliscloud.

My problem could be that I'm not using the right station ID, infact if I try to use https://soliscloud.com/#/station/stationdetail_1?id=.
to discover station ID I receive the following message "The plant do not exist..."
Who can I find my station ID?
tks a lot Matteo

[terppatyyppi]

I can not promise this will help you, but in my own experience/opinion, the following two things were the only possible reasons why I first received the same error like you, but then later succeeded:

1. For whatever reason, I could not log in during the same day I received the API key and secret from Solis (the day they activated my API access), but next day I was able to.

2. I could not log in for the first time when my plant was offline in the evening. Next day it was online when I tried once again and succeeded.

It's possible these things were some kind of factors in my case, but it might as well be that they were only insignificant details.

[peledudok]

Hello when I try to configure for the first time i receive this message "Cannot login with provided URL and credentials" I have apikey from solis, Im trying to access to soliscloud.

My problem could be that I'm not using the right station ID, infact if I try to use https://soliscloud.com/#/station/stationdetail_1?id=. to discover station ID I receive the following message "The plant do not exist..." Who can I find my station ID? tks a lot Matteo

I have the same issue.....waiting for an answer almost 10 days from soliscloud support

[matteoa66]

SOLVED FOR ME, as I found in other discussion.....

How you can find station ID
Go to solis cloud, click on plant overview, click on your plant (under online)
the browser will open another page, the address will be: https://www.soliscloud.com/#/station/stationdetail_1?id NUMBER OF YOUR STATION

[peledudok]

@matteoa66 You mean

clikck on (the yellow) online ?

[matteoa66]

yes!

…

________________________________ Da: peledudok ***@***.***> Inviato: lunedì 21 novembre 2022 10:33 A: hultenvp/solis-sensor ***@***.***> Cc: matteoa66 ***@***.***>; Mention ***@***.***> Oggetto: Re: [hultenvp/solis-sensor] Help with setup (Discussion #189) @matteoa66<https://github.com/matteoa66> You mean [image]<https://user-images.githubusercontent.com/88967555/203015477-ac6ffa23-1f7f-4021-8477-c692805e1db8.png> clikck on (the yellow) online ? — Reply to this email directly, view it on GitHub<#189 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APHQMA7BSDZWZCNNMOHHJK3WJM6W3ANCNFSM6AAAAAARVBHCHI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[peledudok]

thx for confirmation...i'm using that station id all the time and still the error "Failed to acquire plant name, login failed"

[matteoa66]

Latest possibility……… are you removing the final / from the Solis address: https://www.soliscloud.com:13333 No more suggestion……. Ciao, Matteo Da: peledudok ***@***.***> Inviato: lunedì 21 novembre 2022 12:57 A: hultenvp/solis-sensor ***@***.***> Cc: matteoa66 ***@***.***>; Mention ***@***.***> Oggetto: Re: [hultenvp/solis-sensor] Help with setup (Discussion #189) thx for confirmation...i'm using that station id all the time and still the error "Failed to acquire plant name, login failed" — Reply to this email directly, view it on GitHub<#189 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APHQMA4PWIBWL6CFJ57RJCLWJNPR3ANCNFSM6AAAAAARVBHCHI>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[peledudok]

Yes also no / at the end

[pjvankessel]

This worked for me! Thanks!

[peledudok]

@hultenvp Hi,
I finally received an answer from Solissupport :

Hello B.manglie,

Try with this updated document. I checked your account and its good. Can you try again on your side? We are a bit stumped here because nobody else is reporting your problem

I tried to install the soliscloud integration again but stil the same error:

DEBUG
(MainThread) [custom_components.solis.soliscloud_api] workarounds: {'correct_daily_on_grid_energy_enabled': True}
INFO (MainThread) [custom_components.solis.soliscloud_api] Login successful
DEBUG (MainThread) [custom_components.solis.soliscloud_api] Found inverters: ['1002010226020296']
DEBUG (MainThread) [custom_components.solis.soliscloud_api] Fetching data for serial: 1002010226020296
INFO (MainThread) [custom_components.solis.soliscloud_api] /v1/api/stationDetail responded with error: 1:数据异常 请联系管理员
DEBUG (MainThread) [custom_components.solis.ginlong_base] AttributeError, plantName does not exist
INFO (MainThread) [custom_components.solis.soliscloud_api] Failed to acquire plant name, login failed

I attached the new documentation they sent me I don't have enough knowledge what is in the document.
Can you help me with this to solve?

thx

SolisCloud API 1.2.pdf

[hultenvp]

The API doc is the latest indeed. But there's no encoding of the version in the endpoint or the header, so all people using the API are using this version. So this does not explain your situation.
I'm unable to find back, but did you already use the test app?
I'm really interested to see what output that app produces.

[peledudok]

sorry no i'm not using the test app. What should i do?

[peledudok]

@hultenvp sorry no i'm not using the test app. What should i do?

[Sahkari68]

I try set uo Solis and allways get "Cannot login with provided URL and credentials"

I have Api keys and solis in online, what i make wrong

[peledudok]

What goes wrong is the big questions.
Parently no one knows the answer..
Do you have the same message in the log as I have?
Perhaps also create a solis support ticket.
The more tickets the more change solis will solve it ( answer from solis : We are a bit stumped here because nobody else is reporting your problem)

[jonathanmandrews2022]

Hi has anyone managed to resolve this? Looks like I am not alone!

[peledudok]

Hi has anyone managed to resolve this? Looks like I am not alone!

no that i know. Still waiting for an answer on the solis support ticket.
and waiting for an answer from @hultenvp how-to use the test app

[jonathanmandrews2022]

@peledudok

I have just posted the results so hopefully will help as did not get the Chinese writing in the results

[peledudok]

@peledudok

I have just posted the results so hopefully will help as did not get the Chinese writing in the results

thx, due lack of time i can only test it coming week.

[hultenvp]

Thanks for bumping me, work is crazy last few weeks.

THe recipe for the test app is as follows:

• Install python on your system of choice. Linux, Mac, Windows doesn't matter. On windows I'd advise to install Linux support and use Linux. Should be a simple install of a linux distribution from the Windows Store, but also normal windows will do.
• Download the test app to your home folder
• Open the test app in a file editor and add your key and secret on lines 11 and 12
• Remove the comment (#-sign) at stationdetail (line 27 & 28)
• Add your station Id in line 28
• Add comment line (#-sign) to inverterdetail (lines 33&34), exactly as with other lines commented out.
• Save file and exit
• run the test app from the command line. Go to the folder where the test app is located and type python solicloud_test.py. If you get an error that the system cannot find python try python3 soliscloud_test.py
• If it throws the same chinese error in the output then you need to bugger Solis more: then it's server-side problem. If it returns data then we have a lead and I'd really like to have the output.

[peledudok]

@hultenvp yes sure:
{"code": "0", "data": {"acInType": 0, "acOutputType": 0, "apparentPower": 20.0, "apparentPowerStr": "VA", "backupMonthEnergy": 0.0, "backupMonthEnergyStr": "kWh", "backupTodayEnergy": 0.0, "backupTodayEnergyStr": "kWh", "backupTotalEnergy": 0.0, "backupTotalEnergyStr": "kWh", "backupYearEnergy": 0.0, "backupYearEnergyStr": "kWh", "backupYesterdayEnergy": 0.0, "backupYesterdayEnergyStr": "kWh", "batteryAcvSet": 0.0, "batteryAlarm": "0", "batteryCDEnableSet": 0.0, "batteryCDISet": 0.0, "batteryCDSet": 0.0, "batteryCMaxiSet": 0.0, "batteryCapacitySoc": 0.0, "batteryChargeEnergy": 0, "batteryChargeEnergyStr": "kWh", "batteryChargingCurrent": 0.0, "batteryChargingCurrentStr": "A", "batteryDMaxiSet": 0.0, "batteryDischargeEnergy": 0, "batteryDischargeEnergyStr": "kWh", "batteryDischargeLimiting": 0.0, "batteryDischargeLimitingStr": "A", "batteryFailureInformation01": "0", "batteryFailureInformation02": "0", "batteryFcvSet": 0.0, "batteryHealthSoh": 0.0, "batteryLaTemp": 0.0, "batteryMonthChargeEnergy": 0, "batteryMonthChargeEnergyStr": "kWh", "batteryMonthDischargeEnergy": 0, "batteryMonthDischargeEnergyStr": "kWh", "batteryOlvEnableSet": 0.0, "batteryOvpSet": 0.0, "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.0", "batteryUvpSet": 0.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, "bypassAcCurrentB": 0.0, "bypassAcCurrentC": 0.0, "bypassAcCurrentSet": 0.0, "bypassAcOnoffSet": 0.0, "bypassAcVoltage": 0.0, "bypassAcVoltageB": 0.0, "bypassAcVoltageC": 0.0, "bypassAcVoltageSet": 0.0, "bypassLoadPower": 0.0, "bypassLoadPowerStr": "kW", "collectorId": "1306858901387579052", "collectorName": "Datalogger", "collectorsn": "5A1225091E8023D5", "ctrlCommand": 1, "currentState": "3", "dataTimestamp": "1671182800484", "daylight": 0, "daylightSwitch": 1, "dcBus": 347.2, "dcBusHalf": 204.0, "dcBusHalfStr": "V", "dcBusStr": "V", "dcInputtype": 1, "dispersionRate": 0.0, "dsp14Ver": "", "eMonth": 14.0, "eMonthStr": "kWh", "eToday": 0.0, "eTodayStr": "kWh", "eTotal": 142.0, "eTotalStr": "kWh", "eYear": 142.0, "eYearStr": "kWh", "energyStorageControl": "0", "epmFailSafe": 0.0, "epmSafe": 1, "epsDDepth": 0.0, "epsSwitchTime": "0", "fac": 49.99, "facStr": "Hz", "familyLoadPercent": 0, "familyLoadPower": 0.0, "familyLoadPowerPec": "1", "familyLoadPowerStr": "kW", "fullHour": 0.0, "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", "homeGridMonthEnergy": 0.0, "homeGridMonthEnergyStr": "kWh", "homeGridTodayEnergy": 0.0, "homeGridTodayEnergyStr": "kWh", "homeGridTotalEnergy": 0.0, "homeGridTotalEnergyStr": "kWh", "homeGridYearEnergy": 0.0, "homeGridYearEnergyStr": "kWh", "homeGridYesterdayEnergy": 0.0, "homeGridYesterdayEnergyStr": "kWh", "homeLoadEnergy": 0, "homeLoadEnergyStr": "kWh", "homeLoadTodayEnergy": 0.0, "homeLoadTodayEnergyStr": "kWh", "homeLoadTotalEnergy": 0.0, "homeLoadTotalEnergyStr": "kWh", "homeLoadYesterdayEnergy": 0.0, "homeLoadYesterdayEnergyStr": "kWh", "iAc1": 0.7, "iAc1Str": "A", "iAc2": 0.0, "iAc2Str": "A", "iAc3": 0.0, "iAc3Str": "A", "iLeakLimt": 240, "iPv1": 0.2, "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": "1308675217947420064", "insulationResistance": 200.0, "inverterMeterModel": 1, "inverterTemperature": 23.2, "inverterTemperatureUnit": "\u2103", "ipvTotal": 0, "ipvTotalStr": "A", "meter1SiteHigh": 0, "meter1Type": 0, "meter1TypeLow": 0, "meter2SiteHigh": 0, "meter2Type": 0, "meter2TypeLow": 0, "model": "201", "nationalStandardstr": "EN50549NL", "offGridDDepth": 0.0, "oneSelf": 0.0, "pEpm": 0.0, "pEpmSet": 0.0, "pEpmSetStr": "kW", "pEpmStr": "kW", "pac": 0.03, "pacPec": "1", "pacStr": "kW", "parallelAddr": 0, "parallelBattery": 0, "parallelPhase": 0, "parallelStatus": 0, "porwerPercent": 0.01, "pow1": 52, "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", "powTotal": 0, "powTotalStr": "W", "power": 3.0, "powerFactor": 1.0, "powerPec": "1", "powerStr": "kWp", "productModel": "201", "psum": 0.0, "psumCal": 0.03, "psumCalPec": "1", "psumCalStr": "kW", "psumStr": "kW", "reactivePower": 0.0, "reactivePowerStr": "Var", "rs485ComAddr": "101", "simFlowState": -1, "sirRealtime": 0, "sn": "1002010226020296", "sno": "1418CB", "socChargingSet": 0.0, "socDischargeSet": 0.0, "state": 1, "stateExceptionFlag": 0, "stationId": "1298491919448858888", "storageBatteryCurrent": 0.0, "storageBatteryCurrentStr": "A", "storageBatteryVoltage": 0.0, "storageBatteryVoltageStr": "V", "temp": 150.0, "tempName": "IGBT Temperature", "timeStr": "2022-12-16 10:26:40", "timeZone": 1.0, "timeZoneStr": "UTC+01:00", "totalLoadPower": 0, "totalLoadPowerStr": "kW", "uAc1": 223.9, "uAc1Str": "V", "uAc2": 0.0, "uAc2Str": "V", "uAc3": 0.0, "uAc3Str": "V", "uInitGnd": 0, "uInitGndStr": "V", "uPv1": 261.8, "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", "upvTotal": 0, "upvTotalStr": "V", "userId": "1300386381676639596", "version": "780035", "warningInfoData": 0}, "msg": "success", "success": true}

[hultenvp]

THanks @peledudok . That's good news, it means at least the API works! Hopefully all data records are correct, let's find out.

Now, the log-in sequence does the following calls:

1. InverterList
2. InverterDetail
3. StationDetail

3 is now confirmed working, can you also try 1 and 2? You can do that by commenting and uncommenting the right lines in the python file and making sure the ID is added.
If all work, then things get really interesting ;-)

[peledudok]

THanks @peledudok . That's good news, it means at least the API works! Hopefully all data records are correct, let's find out.

Now, the log-in sequence does the following calls:

1. InverterList
2. InverterDetail
3. StationDetail

3 is now confirmed working, can you also try 1 and 2? You can do that by commenting and uncommenting the right lines in the python file and making sure the ID is added. If all work, then things get really interesting ;-)

i can do that but is allready uncomment in the first run inverterdetail right?
#CanonicalizedResource = "/v1/api/userStationList"
#Body = '{"userId":"xxxxx"}' # userId = id number from the url bar of your inverter detail page

CanonicalizedResource = "/v1/api/stationDetail"
Body = '{"id":"1298491919448858888"}' # id = id number from the url bar of your station overview

#CanonicalizedResource = "/v1/api/inveterList"
#Body = '{"stationId":"xxxxxx"}' # id = id number from the url bar of your station overview

CanonicalizedResource = "/v1/api/inveterDetail"
Body='{"id":"1298491919448858888","sn":"1002010226020296"}' # userId = id number from the url bar of your inverter detail page; sn = the serial number of your inverter

#CanonicalizedResource = "/v1/api/stationDayEnergyList"
#Body = '{"time":"' + Date2 +'"}'

#CanonicalizedResource = "/v1/api/stationDay"
#Body = '{"id":"xxxxx","money":"GBP","timezone":0,"time":"' + Date2 +'"}' # id = id number from the url bar of your station overview

#CanonicalizedResource = "/v1/api/stationAll"
#Body = '{"id":"xxxxx","money":"GBP"}' # id = id number from the url bar of your station overview

#CanonicalizedResource = "/v1/api/addUser"
#Body='{"userName":"xxxxx","userType":0}' # Username field from https://www.soliscloud.com/#/my

[hultenvp]

Okay, indeed inverterdatail has been checked now.
What happens because both stationdetail and inverterdetail are decoded is that the values assigned for stationdetail are overwritten with those of inverterdetail.

Take the following steps:

1. Comment the 2 inverterdetail lines
2. Run the app, check output, it should, like above, give a list of values
3. commment the stationdetail lines also and remove comments from the inveterList (mark the typo!) lines
4. Add the stationId at the XXXXXX's
5. Run the app again and it should also give a nice list of values.

If any of the steps gives a very short output that looks like the one you posted earlier, then something's wrong. I mean this one:
{"code": "1", "data": null, "msg": "\u6570\u636e\u5f02\u5e38 \u8bf7\u8054\u7cfb\u7ba1\u7406\u5458", "success": true}

[peledudok]

Okay, indeed inverterdatail has been checked now. What happens because both stationdetail and inverterdetail are decoded is that the values assigned for stationdetail are overwritten with those of inverterdetail.

Take the following steps:

1. Comment the 2 inverterdetail lines
2. Run the app, check output, it should, like above, give a list of values
3. commment the stationdetail lines also and remove comments from the inveterList (mark the typo!) lines
4. Add the stationId at the XXXXXX's
5. Run the app again and it should also give a nice list of values.

If any of the steps gives a very short output that looks like the one you posted earlier, then something's wrong. I mean this one: {"code": "1", "data": null, "msg": "\u6570\u636e\u5f02\u5e38 \u8bf7\u8054\u7cfb\u7ba1\u7406\u5458", "success": true}

1. done
2. done output : {"code": "1", "data": null, "msg": "\u6570\u636e\u5f02\u5e38 \u8bf7\u8054\u7cfb\u7ba1\u7406\u5458", "success": true}
3. done
4. done
5. step 5.txt

Perhaps i filled in the wrong id numbers?

[peledudok]

@hultenvp,

Output of: inveterDetail

#CanonicalizedResource = "/v1/api/userStationList"
#Body = '{"userId":"xxxxx"}' # userId = id number from the url bar of your inverter detail page

#CanonicalizedResource = "/v1/api/stationDetail"
#Body = '{"id":"1298491919448858888"}' # id = id number from the url bar of your station overview

#CanonicalizedResource = "/v1/api/inveterList"
#Body = '{"stationId":"xxxxxx"}' # id = id number from the url bar of your station overview

CanonicalizedResource = "/v1/api/inveterDetail"
Body='{"id":"1298491919448858888","sn":"1002010226020296"}' # userId = id number from the url bar of your inverter detail page; sn = the serial number of your inverter

#CanonicalizedResource = "/v1/api/stationDayEnergyList"
#Body = '{"time":"' + Date2 +'"}'

#CanonicalizedResource = "/v1/api/stationDay"
#Body = '{"id":"xxx
xx","money":"GBP","timezone":0,"time":"' + Date2 +'"}' # id = id number from the url bar of your station overview

#CanonicalizedResource = "/v1/api/stationAll"
#Body = '{"id":"xxxxx","money":"GBP"}' # id = id number from the url bar of your station overview

#CanonicalizedResource = "/v1/api/addUser"
#Body='{"userName":"xxxxx","userType":0}' # Username field from https://www.soliscloud.com/#/my

inverterdetail.txt

#CanonicalizedResource = "/v1/api/userStationList"
#Body = '{"userId":"xxxxx"}' # userId = id number from the url bar of your inverter detail page

#CanonicalizedResource = "/v1/api/stationDetail"
#Body = '{"id":"1298491919448858888"}' # id = id number from the url bar of your station overview

CanonicalizedResource = "/v1/api/inveterList"
Body = '{"stationId":"1298491919448858888"}' # id = id number from the url bar of your station overview

#CanonicalizedResource = "/v1/api/inveterDetail"
#Body='{"id":"1308675217947420064","sn":"1002010226020296"}' # userId = id number from the url bar of your inverter detail page; sn = the serial number of your inverter

#CanonicalizedResource = "/v1/api/stationDayEnergyList"
#Body = '{"time":"' + Date2 +'"}'

#CanonicalizedResource = "/v1/api/stationDay"
#Body = '{"id":"xxxxx","money":"GBP","timezone":0,"time":"' + Date2 +'"}' # id = id number from the url bar of your station overview

#CanonicalizedResource = "/v1/api/stationAll"
#Body = '{"id":"xxxxx","money":"GBP"}' # id = id number from the url bar of your station overview

#CanonicalizedResource = "/v1/api/addUser"
#Body='{"userName":"xxxxx","userType":0}' # Username field from https://www.soliscloud.com/#/my

output inverterlist:
invertlist.txt

all lines uncomment:
CanonicalizedResource = "/v1/api/stationDetail"
Body = '{"id":"1298491919448858888"}' # id = id number from the url bar of your station overview

CanonicalizedResource = "/v1/api/inveterList"
Body = '{"stationId":"1298491919448858888"}' # id = id number from the url bar of your station overview

CanonicalizedResource = "/v1/api/inveterDetail"
Body='{"id":"1308675217947420064","sn":"1002010226020296"}' # userId = id number from the url bar of your inverter detail page; sn = the serial number of your inverter

alluncomment.txt

Is it all correct because i don't know if i filled in all the correct id's

[hultenvp]

@peledudok, @jonathanmandrews2022.

I'm at loss what's going on. I'd like to debug further, but I need to be able to reproduce the issue.

I still see 2 options:

1. Attached a modified test app. This version uses the same aiohttp library that the integration uses, plus it can do multiple requests at the same time. I've set it to 3 times plantDetail (the one that fails). Could you please try this version? Remove the txt extension.
   solis_test_async.py.txt
2. One of you sends me your details: key, secret, station ID, inverter SN and I try to exactly reproduce your situation here. If you're willing to send me the details you can send them to me via discord (Peter van Hulten#8923) or via mail to peter[dot]vanhulten[at]gmx.net

[jonathanmandrews2022]

@hultenvp I have just emailed you all the details above and added you as a guest to my Solis Cloud account to aid you in your testing.

[hultenvp]

@jonathanmandrews2022 , @peledudok : I just managed to reproduce the issue based on Jonathan's data. The hunting can begin ;-)

[peledudok]

@hultenvp,

Great news....i also sent you my details....perhaps there can be some difference in the cases (or not) .

[spiderpigsam]

Happy to test whatever let me know if you need another set of details. Also translating the Chinese gives "
The data is abnormal, please contact the administrator"

[jonathanmandrews2022]

@hultenvp

{"code": "1", "data": null, "msg": "\u6570\u636e\u5f02\u5e38 \u8bf7\u8054\u7cfb\u7ba1\u7406\u5458", "success": true}

I have tried this five time now and can't see anything wrong but as don't know which areas this is failing on not sure where to go next

Not sure how but if there is a way of sending you the details so you can do your testing i will add you as a guest to SolisCloud as well

[digitaldai]

Hello, nice to see if anybody sorts and finds the problem I cant login wth correct details either! good luck.

[hultenvp]

@peledudok , @jonathanmandrews2022 , @spiderpigsam , @digitaldai

I've released a version 3.2.2 that I believe solves the issue.

[hultenvp]

PS: a workaround for your situation, and also for @digitaldai:
Note that the configuration.yaml still works for now, it can save you a whole lot of UI clicking. You can add the config as follows:

sensor:
  - platform: solis
    name: "SolisCloud test"
    portal_domain: "www.soliscloud.com:13333"
    portal_username: "your_username"
    portal_key_id: "your key_ID"
    portal_secret: "your secret"
    portal_plant_id: "the plantID/stationID as described in the readme"

Add it, reboot and let the integration import the config for you.
After that it will retry automatically, can't do that with the UI unfortunately.

When it works you can remove the config from the yaml again. It has been imported.

[peledudok]

o wow.....i see it is/was working lets hope during the day it will connect :). Keep you posted

[peledudok]

well i see not something on my dashboard.

Test...in the sensor names where is that coming from...oops is it already :)

[hultenvp]

I guess you kept the name from my example 🤣 . but it runs!

If you hate it, delete the integration, change the configuration.yaml and restart HA et voila!

[peledudok]

@hultenvp i changed and.

Everything is working thank you so much solve the issue.

[digitaldai]

https://www.soliscloud.com:13333/

Should it be that on the first screen or is it specfic to each setup? thanks

[jonathanmandrews2022]

Remove the / off the end of URL

[hultenvp]

It will work with or without '/' since 3.2.1

[digitaldai]

Could I send you my details? I cant see what I am doing wrong. thxs

[hultenvp]

If the above doesn't work then please enable debug logging and drop the logs here.

Thanks!

[SmilooSmitje]

I have same issues as above

System log output is

2022-12-25 17:33:55.616 DEBUG (MainThread) [custom_components.solis.soliscloud_api] workarounds: {'correct_daily_on_grid_energy_enabled': False}
2022-12-25 17:33:55.978 INFO (MainThread) [custom_components.solis.soliscloud_api] /v1/api/inverterDetail responded with error: 1:数据异常 请联系管理员
2022-12-25 17:33:55.978 WARNING (MainThread) [custom_components.solis.soliscloud_api] No inverters found

Any idea how i can solve this??

[jonathanmandrews2022]

Update to very latest version - show beta versions

[SmilooSmitje]

I have latest version 3.2.2 installed.

[hultenvp]

See #232 , still issues reported. Also inverterDetail and userStationList calls can fail on the server.