Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning message and accessories not showing #269

Closed
Juanpermon opened this issue Apr 4, 2024 · 2 comments
Closed

Warning message and accessories not showing #269

Juanpermon opened this issue Apr 4, 2024 · 2 comments

Comments

@Juanpermon
Copy link

Plugin Version

0.41.3

Home Connect Appliance(s)

All of them

Log File

[4/4/2024, 2:00:15 PM] [HomeConnect] Waiting 1 hour 8 minutes before issuing Home Connect API request

Additional Information

During plugin configuration I can't find the AUTHORISE button, could that be the reason of the warning message?

@Juanpermon Juanpermon added the api keys/values Unrecognised Home Connect API keys or mismatched value types label Apr 4, 2024
@thoukydides thoukydides added bug Something isn't working and removed api keys/values Unrecognised Home Connect API keys or mismatched value types labels Apr 4, 2024
@thoukydides
Copy link
Owner

Your report does not provide anywhere near enough information to provide a useful diagnosis.

The Waiting 1 hour 8 minutes before issuing Home Connect API request message is caused by hitting a Home Connect API rate limit. There are six different limits, and many reasons why those limits could be exceeded. It may be perfectly normal and expected, with this plugin needing to issue a lot of requests to discover details of your appliances and their supported features and options. Alternatively, there could be something going wrong.

There are also many possible reasons why you might not be presented with the AUTHORISE button. I am not going to even start guessing about that. However, I will note that I am not seeing any issues myself - I can authorise a new installation without any problems - so it is most likely to be due to something wrong in your configuration.

Please provide a full log file, not just a single line. Please also ensure that debug logging is enabled.

@thoukydides
Copy link
Owner

I am closing this issue because no useful information has been provided in the 3 weeks since it was created.

@thoukydides thoukydides removed the bug Something isn't working label Apr 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants