alko
alko copied to clipboard
jonkristian
Option to reconfigure instead of reloading
Thank you once again for this integration that I use all the time. One issue I have is that after a while (a few months) the robot becomes unavailable in the integration and reloading it does nothing. I have to delete the integration and install it again, entering client ID etc. It would be nice to have the option to just reconfigure, essentially setting up the integration with the same user data again without having to type them in manually. I guess the ideal solution would be to have it reconfigure automatically when the robot becomes unavailable (or after a while)
This is the error that raises up: Einrichtungsfehler, wird erneut versucht: 400, message='Bad Request', url='https://idp.al-ko.com/connect/token'
Also ran into the issue. Had the integration active for 23 Days.
For now, it is sufficient to delete the Entity (not the whole Integration) but keep the Application Credentials. Then only the Username/Password is needed for the Setup.
Good tip @AlexHuebi . @afuerhoff Let's use #14 for these Bad Request reports.
We need to implement a reconfigure step. https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/reconfiguration-flow
We need to implement a reconfigure step. https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/reconfiguration-flow
Awesome! Just ran into this issue again today and even though I kept the credentials, I stille had to type in client_id and secret + user and password again.
And it would be great if it would try to reconfigure automatically if the device has been unavailable for a few hours maybe.
Hi :) Any idea when this might be implemented? Just ran into this issue again today (yesterday).
Hi :) Any idea when this might be implemented? Just ran into this issue again today.
Interesting. I believe it was actually yesterday mine disconnected as well. I think this speaks in favor of also having an automatic reconfiguration when the device has been unavailable for a few hours.
In my restful implementation I had no issues. I think it is a problem with the refresh token used for authentication.
Hi :) Any idea when this might be implemented? Just ran into this issue again today (yesterday).
Working on it now, should expect some updates today. I've finally got my mower working again, had some issues with charging cable and loop signal.