TobiasLaross / Hass-Lynk-Co

Home Assistant integration for Lynk & Co
MIT License
37 stars 1 forks source link

A lot of reathentications #48

Closed ErikT80 closed 4 months ago

ErikT80 commented 4 months ago

For the last week I need to re authenticate at least every day, but sometimes even multiple times a day.

I also have the feeling I need to login to my account in the car itself. This wasn't happening before.

TobiasLaross commented 4 months ago

I have been experiencing the same, I just increased the polling time to 240min but I don’t think that will help. Hopefully it will start working more stable soon

robbinonline commented 4 months ago

Same issue here, i have to reconfigure every day.

pjgrun commented 4 months ago

Same issue here. In addition, I observed that data update frequency was reduced in past days, and today data is taking hours to update, if at all. Debug logs do not show any abnormal behavior.

pjgrun commented 4 months ago

Furthermore, I have tested that I can get updated values using official app, but integration still reports outdated data, despite logs indicating successful refresh

pjgrun commented 4 months ago

It appears I was suffering from issue #43 . Had to remove integration completely, restart HA and reinstall integration.

b12e commented 4 months ago

Same here. It ran smoothly for a while and then since last week it's asking to re-auth every day or sometimes multiple times a day.

TobiasLaross commented 4 months ago

The issue is that the ccc_token is none which needs to be refreshed every day and when it fails I assumed it would not be able to recover. But last bight I decided not the re-authenticate and today it recovered, so maybe I need to update the logic to ask for re-authentication when refresh_token is None

TobiasLaross commented 4 months ago

I have not found a solution for this, I’m trying now without any reloading/data fetching and will get back in 2 days to see if I’m able to get a new cccToken

Ferrox85 commented 4 months ago

Problem is at the lynk & co end. The official app itself suffers from the same problem. They need to fix it at their end. But the front-office isn't capable of acknowledging the real issue.

TobiasLaross commented 4 months ago

@Ferrox85 Great news because I was out of ideas, I have not used the official app much at all

Ferrox85 commented 4 months ago

Now, if everybody calls the servicedesk with this issue, maybe it will be resolved quicker...

Ferrox85 commented 4 months ago

I've read somewhere else that there has been a software fix for this issue. I have to wait for an few hours to confirm it is fixed.

TobiasLaross commented 4 months ago

Works for me so far at least

Ferrox85 commented 4 months ago

It seems to be fixed for me as well... close this issue?