Cannot login with provided url and credentials

mvereecken commented 1 year ago

Describe the bug When upgraden to 3.0.5 I had the message that I had to remove the integration from configuration.yaml, so I did. I reinstalled HACS integration, but when entering the credentials I get a "Cannot login with provided url and credentials". Just to make sure I have the right values, I checked again in my Solis account, and the values were still the same as before.

Versions HA version: 2022.10.5 HACS: 1.28.3 Solis-sensor: 3.0.5

mvereecken commented 1 year ago

I manually reverted to 2.3.5, added my old settings in configuration.yaml and it works again.

hultenvp commented 1 year ago

What does the log say?

mvereecken commented 1 year ago

I couldn't find anything in the log about it. Or maybe I looked in the wrong place? I looked into the Home Assistante Core logs.

hultenvp commented 1 year ago

Enable logs as described here and then indeed look in the core log details.

Note that there's a 3.0.8 with quite a lot of small improvements and fixes. Also fixes an issue where the UI would still proceed if no platform was specified causing a failing init

hultenvp commented 1 year ago

Oops accidentally closed

hultenvp commented 1 year ago

See also #197. You'll probably have so wait for Solis to fix this.

Du7chManiac commented 1 year ago

I have the same issue, yet the test script gives me results from the API

geduxas commented 1 year ago

Hello i am new here, and just stuck with same problem.. that i have found that timeout for soliscloud response is only 10sec. For me solis cloud responded only in 23sec.. so i prolonged timeout to 100s.

greigallen commented 1 year ago

@geduxas I'm having the same issue, how did you extend the timeout?

geduxas commented 1 year ago

@geduxas I'm having the same issue, how did you extend the timeout?

Just change timeout from 10 to 100

https://github.com/hultenvp/solis-sensor/blob/86c087371f5df2688401413adeebf10e5b2015fa/custom_components/solis/soliscloud_api.py#L496-L498

wyliecoyoteuk commented 1 year ago

Hi, I had this issue, so I changed the timeout, I now get "Unknown error occurred" I have the V3 datalogger, should this work with it.

geduxas commented 1 year ago

Hi, I had this issue, so I changed the timeout, I now get "Unknown error occurred" I have the V3 datalogger, should this work with it.

Maybe your problem is different..

wyliecoyoteuk commented 1 year ago

Tried again, nowgett

Hi, I had this issue, so I changed the timeout, I now get "Unknown error occurred" I have the V3 datalogger, should this work with it.

Tried again, now "getting cannot log in with supplied credentials" after 100 sec. In logs, I am getting "no inverters found". One question. Is the "inverter name" requested, a generic name (e.g.Solis), the plant name, or the actual inverter name (default is "inverter")?

geduxas commented 1 year ago

Tried again, nowgett

Hi, I had this issue, so I changed the timeout, I now get "Unknown error occurred" I have the V3 datalogger, should this work with it.

Tried again, now "getting cannot log in with supplied credentials" after 100 sec. In logs, I am getting "no inverters found". One question. Is the "inverter name" requested, a generic name (e.g.Solis), the plant name, or the actual inverter name (default is "inverter")?

which system do you use? if you are trying to connect to soliscloud so you need to use plant ID from URL when you are in soliscloud website...

wyliecoyoteuk commented 1 year ago

Tried again, nowgett

Hi, I had this issue, so I changed the timeout, I now get "Unknown error occurred" I have the V3 datalogger, should this work with it.

Tried again, now "getting cannot log in with supplied credentials" after 100 sec. In logs, I am getting "no inverters found". One question. Is the "inverter name" requested, a generic name (e.g.Solis), the plant name, or the actual inverter name (default is "inverter")?

which system do you use? if you are trying to connect to soliscloud so you need to use plant ID from URL when you are in soliscloud website...

I have the plant ID, but what is the inverter name?

Is it the plant name or the inverter name?
E.g. Id is 466abc, plant name is Fred, inverter name is inverter1 which is the string needed for login?

wyliecoyoteuk commented 1 year ago

The problem is that everyone assumes they are using the correct terms, when there are multiple vague options. I may be doing everything right and still having problems, but incorrect naming causes errors.

geduxas commented 1 year ago

The problem is that everyone assumes they are using the correct terms, when there are multiple vague options. I may be doing everything right and still having problems, but incorrect naming causes errors.

For solis cloud, you will need api url, login e-mail, api key, and api secret, also station id. Station id you should login to yours soliscloud, open your inverter.. and in full url you should find your station id:

https://soliscloud.com/#/station/stationdetail_1?id=[your_station_id]

wyliecoyoteuk commented 1 year ago

The problem is that everyone assumes they are using the correct terms, when there are multiple vague options. I may be doing everything right and still having problems, but incorrect naming causes errors.

For solis cloud, you will need api url, login e-mail, api key, and api secret, also station id. Station id you should login to yours soliscloud, open your inverter.. and in full url you should find your station id:

https://soliscloud.com/#/station/stationdetail_1?id=[your_station_id]

I have all of those, they are clearly labelled. What I am asking about is the inverter name which is required on the first screen. This is prefilled with Solis. Should I use the plant name or the inverter name? I have tried both but still get rejected.

geduxas commented 1 year ago

The problem is that everyone assumes they are using the correct terms, when there are multiple vague options. I may be doing everything right and still having problems, but incorrect naming causes errors.

For solis cloud, you will need api url, login e-mail, api key, and api secret, also station id. Station id you should login to yours soliscloud, open your inverter.. and in full url you should find your station id: https://soliscloud.com/#/station/stationdetail_1?id=[your_station_id]

I have all of those, they are clearly labelled. What I am asking about is the inverter name which is required on the first screen. This is prefilled with Solis. Should I use the plant name or the inverter name? I have tried both but still get rejected.

My fault :D no, its just label for home assistant device. All you need from first screen server address and protocol type.. inverter name is just for you.. if you have couple of them.

wyliecoyoteuk commented 1 year ago

Thanks. I didn't realise that. I have tried to connect several times now, without success, I suppose I was looking for any possible cause for it to fail.

geduxas commented 1 year ago

Thanks. I didn't realise that. I have tried to connect several times now, without success, I suppose I was looking for any possible cause for it to fail.

Dou you have api access? Have you enabled it from soliscloud?

wyliecoyoteuk commented 1 year ago

Thanks. I didn't realise that. I have tried to connect several times now, without success, I suppose I was looking for any possible cause for it to fail.

Dou you have api access? Have you enabled it from soliscloud?

Yes, I have the url, key and the secret, etc.

gutyex commented 1 year ago

I'm also getting this error when trying to set up the integration with a newly-created API access key (access was enabled over the weekend by Solis support)

Debug logs show:

2022-11-28 10:07:37.680 WARNING (MainThread) [custom_components.solis.soliscloud_api] No inverters found

soliscloud_test.py works fine, I'm able to get a response for all 8 of the requests in it. Most of them return what looks like good data, numbers match what I'm seeing in the web interface, but UserStationList gives:

{
    "code": "0",
    "data": {
        "mpptSwitch": 0,
        "page": {
            "current": 1,
            "optimizeCountSql": false,
            "orders": [],
            "pages": 0,
            "records": [],
            "searchCount": true,
            "size": 20,
            "total": 0
        },
        "stationStatusVo": {
            "all": 0,
            "building": 0,
            "fault": 0,
            "mppt": 0,
            "normal": 0,
            "offline": 0
        }
    },
    "msg": "success",
    "success": true
}

wyliecoyoteuk commented 1 year ago

Output from logs after enabling debug 2022-11-28 12:32:04.323 ERROR (MainThread) [frontend.js.latest.202211080] :0:0 ResizeObserver loop completed with undelivered notifications. 2022-11-28 12:33:15.092 DEBUG (MainThread) [custom_components.solis.soliscloud_api] workarounds: {'correct_daily_on_grid_energy_enabled': True} 2022-11-28 12:33:23.196 WARNING (MainThread) [custom_components.solis.soliscloud_api] No inverters found

Nolb commented 1 year ago

Been struggling with this since getting the api key last week, kept getting the 'No inverters found' warning, found the solution here https://github.com/hultenvp/solis-sensor/discussions/71

Just drop the / from the API URL after 13333

gutyex commented 1 year ago

I tried setting it up without the trailing / on the URL as @Nolb suggested, logs now show:

2022-11-28 12:47:26.257 DEBUG (MainThread) [custom_components.solis.soliscloud_api] workarounds: {'correct_daily_on_grid_energy_enabled': True}
2022-11-28 12:47:26.667 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Error from URI (/v1/api/inveterList) : 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://www.soliscloud.com:13333/v1/api/inveterList')
2022-11-28 12:47:26.668 WARNING (MainThread) [custom_components.solis.soliscloud_api] No inverters found
2022-11-28 12:48:10.153 DEBUG (MainThread) [custom_components.solis.soliscloud_api] workarounds: {'correct_daily_on_grid_energy_enabled': True}
2022-11-28 12:48:20.156 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Error from URI (/v1/api/inveterList) :
2022-11-28 12:48:20.157 WARNING (MainThread) [custom_components.solis.soliscloud_api] No inverters found

This was two attempts using the ID and stationID from the InverterDetail page (https://www.soliscloud.com/#/station/inverter/inverterdetail)

wyliecoyoteuk commented 1 year ago

could it be the typo inveterlist?

Error from URI (/v1/api/inveterList)

Nolb commented 1 year ago

The only other things I did were on the first setup page where it asks for inverter name I used the exact name I have it set as on the Solis cloud, not inverter I'd (don't know if it matters or not) and used my email address rather than user name on the other page, not sure what else it could be sorry

wyliecoyoteuk commented 1 year ago

One thing, if i look at the station ID using the URL above, I get an 18 digit decimal number. whereas I was using the one on the web page which is a six digit hexadecimal number. Neither seems to work, but which one should I use?

Nolb commented 1 year ago

I used the 18 digit ID (actually mine is 19 digits) in the URL for the station ID, when it connected it then returned the 6 digit hexadecimal value as the inverter name against the integration which matches the one in Solis cloud

Nolb commented 1 year ago

The url above is the inverter detail, although it does have the station at the end as well as the inverter id, it should be the same as on this url (https://www.soliscloud.com/#/station/stationdetail_1?id=)

wyliecoyoteuk commented 1 year ago

Working! The number needed is 19 digits long, the number I had was missing the end digit, probably cut and paste error. Thank you for your patience

hultenvp commented 1 year ago

Nice to see it works, I've updated the readme to make the registration and configuration more transparent. To answer some more of the discussions in this thread:

Just change timeout from 10 to 100

I will add this to the code. I notice that the current version of HA processes a lot asynchronically during startup and needs more slack on timeouts.

Just drop the / from the API URL after 13333

I want to add some robustness to the code to remove any trailing slashes.

could it be the typo inveterlist?

No, they typo is in their endpoint.

I used the 18 digit ID (actually mine is 19 digits) in the URL for the station ID, when it connected it then returned the 6 digit hexadecimal value as the inverter name against the integration which matches the one in Solis cloud

Yes, you need the 19 digit ID, I made that more clear in the readme. On the inverter name: Before the API lockdown the API would return the Station/Plant name. Now it no longer does, so in the device registry I now have to use the 6-digit HEX value instead of a real name.

The problem is that everyone assumes they are using the correct terms, when there are multiple vague options. I may be doing everything right and still having problems, but incorrect naming causes errors.

@wyliecoyoteuk: Please check the new readme. Would be helpful if you could let me know if this is now more clear or still needs further improvement.

wyliecoyoteuk commented 1 year ago

That's great. I have now noticed that the number is sometimes truncated on some screens in soliscloud, not sure why. I did a brief how-to on my blog. https://wyliecoyoteuk.wordpress.com/2022/11/28/home-assistant-with-a-solis-hybrid-inverter/

jjeuriss commented 1 year ago

@hultenvp A suggestion for the readme: it would would be to clarify that if you select soliscloud as PV Portal version, you also need to specify the API URL. By default https://m.ginlong.com was filed in and I didn't realize I needed to change it to https://www.soliscloud.com:13333 (without slash) after selecting soliscloud.

jmason commented 1 year ago

could it be the typo inveterlist?

No, they typo is in their endpoint.

BTW, I think this is fixed -- it looks like the endpoints are now duplicated with and without the typo.

matthewbyrne commented 1 year ago

Having this issue too. PV URL: https://www.soliscloud.com:13333 Copying the secret and key from the API settings, and the station ID from https://www.soliscloud.com/#/station/stationdetail_1?id=xxxxxxxxxxx

Result: Cannot login with provided URL and credentials

jonathanmandrews2022 commented 1 year ago

Seem to get this strange error when attempt to set up (put * on serial no)

2022-12-11 12:12:48.688 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Found inverters: ['6031023228200'] 2022-12-11 12:12:48.688 DEBUG (MainThread) [custom_components.solis.soliscloud_api] Fetching data for serial: 6031023228200 2022-12-11 12:12:48.809 INFO (MainThread) [custom_components.solis.soliscloud_api] /v1/api/stationDetail responded with error: 1:数据异常请联系管理员 2022-12-11 12:12:48.809 DEBUG (MainThread) [custom_components.solis.ginlong_base] AttributeError, plantName does not exist 2022-12-11 12:12:48.809 INFO (MainThread) [custom_components.solis.soliscloud_api] Failed to acquire plant name, login failed

roshanabady commented 1 year ago

I'm a beginner, and I had the same issue, as there are up to 3 different IDs in the URL. And the correct one is actually what most everyone has suggested, which is: https://www.soliscloud.com/#/station/stationdetail_1?id=xxxxxxxxxxx But I believe a visual guide is always the best(My apologies for the Pictoral guide):

log in to your Solis Cloud Account
In the Plant Overview tab, under the Plant Name column, Click on your actual plant name, per the screenshot below:
Find the 19-digit ID in the new screen at the end of the page URL, and take the screenshot as a guide:
For the rest of the process, follow the main guide @hultenvp cheers, mate, You Rock!

matthewbyrne commented 1 year ago

Still no success here! https://www.soliscloud.com:13333 without the trailing / Email address that I use to login to solis cloud API Secret = KeySecret from soliscloud API Key ID = KeyID from soliscloud Station ID = As shown above from https://www.soliscloud.com/#/station/stationdetail_1?id=19digits

Any ideas!?

geduxas commented 1 year ago

@matthewbyrne

Try to increase timeout from 10 to 100

I have noticed that solis cloud response very delayed for me.. so increase of timeout solved problem..

https://github.com/hultenvp/solis-sensor/blob/86c087371f5df2688401413adeebf10e5b2015fa/custom_components/solis/soliscloud_api.py#L496-L498

matthewbyrne commented 1 year ago

@matthewbyrne

Try to increase timeout from 10 to 100

I have noticed that solis cloud response very delayed for me.. so increase of timeout solved problem..

https://github.com/hultenvp/solis-sensor/blob/86c087371f5df2688401413adeebf10e5b2015fa/custom_components/solis/soliscloud_api.py#L496-L498

Just tried that, but the integration never takes near 10 seconds to fail. The 100 seconds timeout made no difference. No errors in the homeassistant logs either.

geduxas commented 1 year ago

@matthewbyrne just double check, do you reloaded home asistant after change?

hultenvp commented 1 year ago

People are reporting various connectivity issues in different tickets. Let me summarize:

Sometimes the server throws a HTTP 408 error, this happens when there's time drift between client and server (i.e. your system time is off more than 15 minutes). ==> I have an update ready that at least will give you a nice warning if that's the case.
Sometimes the server throws a HTTP 502 error. This is a server side error that comes and goes, but some people seem to have more trouble with it than others. ==> I have an update ready that throttles the amount of calls made per second to avoid overloading the server. I'm not sure this solves the issue, because I cannot reliably reproduce.
Some people report a debug output error in Chinese that translates into "The data is abnormal, please contact the administrator", see here ==> There's no solution yet.

@matthewbyrne: Maybe it's caused by problem number 2, but I'm not sure. If the coming update does not solve it, please try to run the test app, in discussion 189 is manual how to do that. The login sequence makes the calls in the following order: InverterList, InverterDetail, StationDetail. You might want to try using the test app if the individual calls do report correct data.

hultenvp commented 1 year ago

I'll close this issue, further issues after release 3.2.0 please report in #232

hultenvp commented 1 year ago

By the way, @roshanabady : I used your screenshots and description to improve the readme. Thanks!

matthewbyrne commented 1 year ago

People are reporting various connectivity issues in different tickets. Let me summarize:

Sometimes the server throws a HTTP 408 error, this happens when there's time drift between client and server (i.e. your system time is off more than 15 minutes). ==> I have an update ready that at least will give you a nice warning if that's the case.

Sometimes the server throws a HTTP 502 error. This is a server side error that comes and goes, but some people seem to have more trouble with it than others. ==> I have an update ready that throttles the amount of calls made per second to avoid overloading the server. I'm not sure this solves the issue, because I cannot reliably reproduce.

Some people report a debug output error in Chinese that translates into "The data is abnormal, please contact the administrator", see here ==> There's no solution yet.

@matthewbyrne: Maybe it's caused by problem number 2, but I'm not sure. If the coming update does not solve it, please try to run the test app, in discussion 189 is manual how to do that. The login sequence makes the calls in the following order: InverterList, InverterDetail, StationDetail. You might want to try using the test app if the individual calls do report correct data.

Thanks for the info. That soliscloud_test.py test app should be in a troubleshooting readme. It's very handy. I get Chinese characters unfortunately. Or specifically unicode of chinese characters: {"code": "1", "data": null, "msg": "\u6570\u636e\u5f02\u5e38 \u8bf7\u8054\u7cfb\u7ba1\u7406\u5458", "success": true} Site to translate unicode

How to use test app: link Test app code: soliscloud_test.py

hultenvp commented 1 year ago

Yup, that's the "abnormal data" issue.

I'm working on a new test app to get more insights if there are more commonalities between the various people reporting the issue. Could you check what response inverterDetail and stationAll endpoints give? They should respond with data, and I'm interested what data they give

matthewbyrne commented 1 year ago

Anything in particular you're looking for? Nothing jumping out at me as overly important. i've redacted a few personal ids and serial numbers etc.

stationsAll

{
  "code": "0",
  "data": [
    {
      "batteryChargeEnergy": 0,
      "batteryDischargeEnergy": 0,
      "consumeEnergy": 1146.3,
      "energy": 202,
      "energyPec": "1",
      "energyStr": "kWh",
      "errorFlag": 0,
      "fullHour": 40.4,
      "gridPurchasedEnergy": 1018.01,
      "gridPurchasedIncome": 0.52,
      "gridSellEnergy": 73.71,
      "gridSellIncome": 20.894,
      "homeLoadEnergy": 198,
      "id": "<id here>",
      "money": 56.962,
      "moneyPec": "1",
      "moneyStr": "GBP",
      "offSetEnergy": 0,
      "offSetIncome": 0,
      "oneSelf": 128.29,
      "produceEnergy": 202,
      "timeZone": 8,
      "year": 2022
    }
  ],
  "msg": "success",
  "success": true
}

inverterDetails:

{
  "code": "0",
  "data": {
    "acInType": 0,
    "acOutputType": 0,
    "apparentPower": 0,
    "apparentPowerStr": "VA",
    "backupMonthEnergy": 0,
    "backupMonthEnergyStr": "kWh",
    "backupTodayEnergy": 0,
    "backupTodayEnergyStr": "kWh",
    "backupTotalEnergy": 0,
    "backupTotalEnergyStr": "kWh",
    "backupYearEnergy": 0,
    "backupYearEnergyStr": "kWh",
    "backupYesterdayEnergy": 0,
    "backupYesterdayEnergyStr": "kWh",
    "batteryAcvSet": 0,
    "batteryAlarm": "0",
    "batteryCDEnableSet": 0,
    "batteryCDISet": 0,
    "batteryCDSet": 0,
    "batteryCMaxiSet": 0,
    "batteryCapacitySoc": 0,
    "batteryChargeEnergy": 0,
    "batteryChargeEnergyStr": "kWh",
    "batteryChargingCurrent": 0,
    "batteryChargingCurrentStr": "A",
    "batteryDMaxiSet": 0,
    "batteryDischargeEnergy": 0,
    "batteryDischargeEnergyStr": "kWh",
    "batteryDischargeLimiting": 0,
    "batteryDischargeLimitingStr": "A",
    "batteryFailureInformation01": "0",
    "batteryFailureInformation02": "0",
    "batteryFcvSet": 0,
    "batteryHealthSoh": 0,
    "batteryLaTemp": 0,
    "batteryMonthChargeEnergy": 0,
    "batteryMonthChargeEnergyStr": "kWh",
    "batteryMonthDischargeEnergy": 0,
    "batteryMonthDischargeEnergyStr": "kWh",
    "batteryOlvEnableSet": 0,
    "batteryOvpSet": 0,
    "batteryPower": 0,
    "batteryPowerBms": 0,
    "batteryPowerBmsStr": "kW",
    "batteryPowerFu": 0,
    "batteryPowerPec": "1",
    "batteryPowerStr": "kW",
    "batteryPowerZheng": 0,
    "batteryTodayChargeEnergy": 0,
    "batteryTodayChargeEnergyStr": "kWh",
    "batteryTodayDischargeEnergy": 0,
    "batteryTodayDischargeEnergyStr": "kWh",
    "batteryTotalChargeEnergy": 0,
    "batteryTotalChargeEnergyStr": "kWh",
    "batteryTotalDischargeEnergy": 0,
    "batteryTotalDischargeEnergyStr": "kWh",
    "batteryType": "0.0",
    "batteryUvpSet": 0,
    "batteryVoltage": 0,
    "batteryVoltageStr": "V",
    "batteryYearChargeEnergy": 0,
    "batteryYearChargeEnergyStr": "kWh",
    "batteryYearDischargeEnergy": 0,
    "batteryYearDischargeEnergyStr": "kWh",
    "batteryYesterdayChargeEnergy": 0,
    "batteryYesterdayChargeEnergyStr": "kWh",
    "batteryYesterdayDischargeEnergy": 0,
    "batteryYesterdayDischargeEnergyStr": "kWh",
    "bstteryCurrent": 0,
    "bstteryCurrentStr": "A",
    "bypassAcCurrent": 2.3,
    "bypassAcCurrentB": 0,
    "bypassAcCurrentC": 0,
    "bypassAcCurrentSet": 0,
    "bypassAcOnoffSet": 0,
    "bypassAcVoltage": 231.1,
    "bypassAcVoltageB": 0,
    "bypassAcVoltageC": 0,
    "bypassAcVoltageSet": 0,
    "bypassLoadPower": 0,
    "bypassLoadPowerStr": "kW",
    "collectorId": "<REDACTED>",
    "collectorsn": "<REDACTED>",
    "ctrlCommand": 2,
    "currentState": "3",
    "dataTimestamp": "1671789283221",
    "daylight": 0,
    "daylightSwitch": 0,
    "dcBus": 389.1,
    "dcBusHalf": 0,
    "dcBusHalfStr": "V",
    "dcBusStr": "V",
    "dcInputtype": 1,
    "dispersionRate": 0,
    "dsp14Ver": "",
    "eMonth": 67,
    "eMonthStr": "kWh",
    "eToday": 0.2,
    "eTodayStr": "kWh",
    "eTotal": 202,
    "eTotalStr": "kWh",
    "eYear": 202,
    "eYearStr": "kWh",
    "energyStorageControl": "21",
    "epmFailSafe": 0,
    "epmSafe": 0,
    "epsDDepth": 0,
    "epsSwitchTime": "0",
    "fac": 50.08,
    "facStr": "Hz",
    "familyLoadPercent": 0,
    "familyLoadPower": 0,
    "familyLoadPowerPec": "1",
    "familyLoadPowerStr": "kW",
    "fullHour": 0.04,
    "fullHourStr": "h",
    "gridPurchasedEnergy": 0,
    "gridPurchasedEnergyStr": "kWh",
    "gridPurchasedMonthEnergy": 0,
    "gridPurchasedMonthEnergyStr": "kWh",
    "gridPurchasedTodayEnergy": 2.8,
    "gridPurchasedTodayEnergyStr": "kWh",
    "gridPurchasedTotalEnergy": 1.018,
    "gridPurchasedTotalEnergyStr": "MWh",
    "gridPurchasedYearEnergy": 0,
    "gridPurchasedYearEnergyStr": "kWh",
    "gridPurchasedYesterdayEnergy": 15.8,
    "gridPurchasedYesterdayEnergyStr": "kWh",
    "gridSellEnergy": 0,
    "gridSellEnergyStr": "kWh",
    "gridSellMonthEnergy": 0,
    "gridSellMonthEnergyStr": "kWh",
    "gridSellTodayEnergy": 0.1,
    "gridSellTodayEnergyStr": "kWh",
    "gridSellTotalEnergy": 73.71,
    "gridSellTotalEnergyStr": "kWh",
    "gridSellYearEnergy": 0,
    "gridSellYearEnergyStr": "kWh",
    "gridSellYesterdayEnergy": 1.5,
    "gridSellYesterdayEnergyStr": "kWh",
    "homeGridMonthEnergy": 0,
    "homeGridMonthEnergyStr": "kWh",
    "homeGridTodayEnergy": 0,
    "homeGridTodayEnergyStr": "kWh",
    "homeGridTotalEnergy": 0,
    "homeGridTotalEnergyStr": "kWh",
    "homeGridYearEnergy": 0,
    "homeGridYearEnergyStr": "kWh",
    "homeGridYesterdayEnergy": 0,
    "homeGridYesterdayEnergyStr": "kWh",
    "homeLoadEnergy": 0,
    "homeLoadEnergyStr": "kWh",
    "homeLoadTodayEnergy": 0.1,
    "homeLoadTodayEnergyStr": "kWh",
    "homeLoadTotalEnergy": 198,
    "homeLoadTotalEnergyStr": "kWh",
    "homeLoadYesterdayEnergy": 1.6,
    "homeLoadYesterdayEnergyStr": "kWh",
    "iAc1": 2.4,
    "iAc1Str": "A",
    "iAc2": 0,
    "iAc2Str": "A",
    "iAc3": 0,
    "iAc3Str": "A",
    "iLeakLimt": 0,
    "iPv1": 0.5,
    "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": "<REDACTED>",
    "insulationResistance": 0,
    "inverterMeterModel": 5,
    "inverterTemperature": 20.1,
    "inverterTemperatureUnit": "℃",
    "ipvTotal": 0,
    "ipvTotalStr": "A",
    "meter1SiteHigh": 0,
    "meter1Type": 0,
    "meter1TypeLow": 0,
    "meter2SiteHigh": 0,
    "meter2Type": 0,
    "meter2TypeLow": 0,
    "model": "3104",
    "nationalStandardstr": "EN50549IE",
    "offGridDDepth": 0,
    "oneSelf": 89,
    "pEpm": 0,
    "pEpmSet": 0,
    "pEpmSetStr": "kW",
    "pEpmStr": "kW",
    "pac": 0.089,
    "pacPec": "1",
    "pacStr": "kW",
    "parallelAddr": 0,
    "parallelBattery": 0,
    "parallelPhase": 0,
    "parallelStatus": 0,
    "porwerPercent": 0.018,
    "pow1": 89,
    "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": 5,
    "powerFactor": 0,
    "powerPec": "1",
    "powerStr": "kWp",
    "productModel": "3104",
    "psum": -0.094,
    "psumCal": -0.094,
    "psumCalPec": "1",
    "psumCalStr": "kW",
    "psumStr": "kW",
    "reactivePower": 0,
    "reactivePowerStr": "Var",
    "rs485ComAddr": "101",
    "simFlowState": -1,
    "sirRealtime": 0,
    "sn": "<REDACTED>",
    "sno": "1447C1",
    "socChargingSet": 10,
    "socDischargeSet": 20,
    "state": 1,
    "stateExceptionFlag": 0,
    "stationId": "<REDACTED>",
    "storageBatteryCurrent": -0.2,
    "storageBatteryCurrentStr": "A",
    "storageBatteryVoltage": 4.9,
    "storageBatteryVoltageStr": "V",
    "temp": 105,
    "tempName": "inverter internal operating ambient temperature",
    "timeStr": "2022-12-23 09:54:43",
    "timeZone": 0,
    "timeZoneStr": "UTC+00:00",
    "totalLoadPower": 0,
    "totalLoadPowerStr": "kW",
    "uAc1": 231.1,
    "uAc1Str": "V",
    "uAc2": 0,
    "uAc2Str": "V",
    "uAc3": 0,
    "uAc3Str": "V",
    "uInitGnd": 0,
    "uInitGndStr": "V",
    "uPv1": 178.9,
    "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": "<REDACTED>",
    "version": "3D0037",
    "warningInfoData": 0
  },
  "msg": "success",
  "success": true
}

wyliecoyoteuk commented 1 year ago

I am having the same problem. It worked until a few days ago. the test script gives {"code": "1", "data": null, "msg": "\u6570\u636e\u5f02\u5e38 \u8bf7\u8054\u7cfb\u7ba1\u7406\u5458", "success": true}. I was also getting HTPS: false failures in the Home assistant logs. I tried to reinstall and got the login error.

hultenvp / solis-sensor

Cannot login with provided url and credentials #183