Skip to content

Soliscloud issues

Jump to bottom
hultenvp edited this page Jan 8, 2023 · 1 revision

Background

SolisCloud is the new monitoring platform from Solis. It is planned to replace the older "platform V2" service somewhere in the coming years. The Solis integration currently supports v1.2 of the SolisCloud API spec. At this moment the SolisCloud service is under active development and this does cause issues. On top of that there are some constraints in registering and using the API.

API registration

Usage of the HomeAssistant Solis integration with SolisCloud requires registration. The README is kept up to date on the registration process. At this moment the API is open for registration, but end of 2022 the registration was temporarily suspended due to GDPR issues. Be aware this may happen again.

API issues

Testing issues

Best to try first is to enable debug in the integration and analyzing the logging.

If the logging does not provide enough detail you can also use the test app:

  • Ensure you have python 3 installed on your computer
  • Download from the test folder the following files:
test
├── soliscloud_api
│   ├── soliscloud_api.py.py
├── apitest_async.py
  • Add your key and secret in the apitest_async.py file ad save:
KeyId = 'XXXXXXXXXXXXXX'
secretKey = b'YYYYYYYYYYYY'
  • Run the test python apitest_async.py or python apitest_async.py -v for more verbose output.
  • If all test fail you can try to override the automatic recognition of station ID (also known as plant ID). You can fine the station ID as described in the readme: (note: remove the # to uncomment the line)
#plant_ids = [1234567891234567891] # 19-digit value, separate multiple ID's with a comma ([ID1, ID2, ID3])
  • If all tests pass you get output like this:
user@MY_SYSTEM:~# python apitest_async.py
user_station_list: [OK]
[1234567891234567890]
station_detail(station_id= 1234567891234567890): [OK]
collector_list(station_id= 1234567891234567890): [OK]
collector_detail(station_id= 1234567891234567890, collector_sn= ABCDEABCDEABCDE): [OK]
inverter_list( 1234567891234567890): [OK]
inverter_detail(station_id = 1234567891234567890, inverter_sn = 1234567812345678 ): [OK]
station_day( 1234567891234567890): [OK]
station_month( 1234567891234567890): [OK]
station_year( 1234567891234567890): [OK]
station_all( 1234567891234567890): [OK]
inverter_day( 1234567812345678 ): [OK]
inverter_month( 1234567812345678 ): [OK]
inverter_year( 1234567812345678 ): [OK]
inverter_all( 1234567812345678 ): [OK]
Exceptions:  [None]
  • Timeout errors may happen, this is "normal"

Abnormal data issue

One of the biggest issues users report is that the login fails. Enabling debug shows a Chinese error message: '数据异常 请联系管理员'. It roughly translates into "Abnormal data, please contact administrator". Solis has recently confirmed the existence of this issue. Raise a ticket on SolisCloud and request them to fix the issue.

'408' errors

If you run HA in a VM and the system clock of the VM is not in sync then you may encounter HTTP 408 errors. The server will reject any requests if your local clock deviates more than 15 minutes from its own time. Ensure the system clock of your HA instance is correct and all will work fine.

Timeout errors

As indicated before, these happen from time to time and are relatively harmless. The integration will automatically retry if it happens.

'502' errors

Hard to reproduce, but they seem to happen if you call the API often. The API has a hard limit of 3 calls per second, but apparently if you call frequent, but less than 3x per second you can get 502 errors.

Clone this wiki locally