Unable to fetch data from SEMS. (Query not successful (The authorization has expired, please login again.)) about goodwe-sems-home-assistant HOT 11 CLOSED

Did this fix itself after a while?
This sometimes occurs if parallel queries to the api are done. Maybe not use the SEMS portal mobile app at the same time?

from goodwe-sems-home-assistant.

Did this fix itself after a while?
This sometimes occurs if parallel queries to the api are done. Maybe not use the SEMS portal mobile app at the same time?

Unfortunately no. I tried to install it and restart homeassistant several times, no fix. I don't use SEMS portal mobile app currently. I also logged off from sems website but it didn't help :(

from goodwe-sems-home-assistant.

Did you just install for the first time? Or did you update?
You can try to install the previous version 3.2.0.

FYI The token in the debug logs is a login token.

from goodwe-sems-home-assistant.

I installed it a few months ago i think but i removed it because i was using other plugin (which was using local ip). I installed it yesterday again to use with Energy tab.

from goodwe-sems-home-assistant.

I see. Version 3.2.0 indeed does not support the Energy tab.
Just the _energy entity id should be enough for the Energy tab. Maybe this is enough for you? But that one probably also does not show up for you.

from goodwe-sems-home-assistant.

I will try 3.2.0 now

from goodwe-sems-home-assistant.

I copied the 3.2.0 files manually but getting same errors :(

from goodwe-sems-home-assistant.

I don't know. It should work. Did you try increasing the poll rate? So more than 60s per call.
You can also login on semsportal.com?

from goodwe-sems-home-assistant.

I can login on semsportal without any problem. I just tried to increase poll rate but same error unfortunately :(

Login Response: <Response [200]>
Query not successful (The authorization has expired, please login again.), retrying with new token, 1 retries remaining
SEMS - Maximum token fetch tries reached, aborting for now

from goodwe-sems-home-assistant.

Closing this. Reopen if still an issue.

from goodwe-sems-home-assistant.

@nazeg , this might be fixed in 3.7.0-beta. I ran into a similar issue today.

The token authentication response also returns an api field with a url.
Now the next calls use this new api url, since the token should always work there (, at least that is my guess). It seems to work for me again now.

from goodwe-sems-home-assistant.