Limit log spam by ConfigEntryNotReady

[chemelli74]

Proposed change

Some movable devices, like Plug, can be switched off during HA restart.
This will spam the log every 80sec.

This PR will limit to the first 80sec the logging, still leaving the retry every 80sec.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[MartinHjelmare]

Maybe just log a warning the first time, and let the rest be debug messages?

[chemelli74]

I like the suggestion.
Should I word it

"Config entry '%s' for %s integration not ready yet. Retrying in background"

or something similar ?

[MartinHjelmare]

Sounds good. What do you think @balloob?

[chemelli74]

In the mean time that we wait for Paulus check, I'll updated the code.

[frenck]

I think this makes sense, so approving to support it 👍

[amelchio]

Yeah, this is good. Maybe you can adjust PlatformNotReady as well so both of them have similar behaviour?

2021-03-02 07:21:42 INFO (MainThread) [homeassistant.components.esphome] Trying to reconnect to 10.0.2.166 in 60 seconds
2021-03-02 07:22:45 INFO (MainThread) [homeassistant.components.esphome] Can't connect to ESPHome API for nfc01 (10.0.2.166): Error connecting to ('10.0.2.166', 6053): [Errno 113] Connect call failed ('10.0.2.166', 6053)
2021-03-02 07:22:45 INFO (MainThread) [homeassistant.components.esphome] Trying to reconnect to 10.0.2.166 in 60 seconds
2021-03-02 07:23:48 INFO (MainThread) [homeassistant.components.esphome] Can't connect to ESPHome API for nfc01 (10.0.2.166): Error connecting to ('10.0.2.166', 6053): [Errno 113] Connect call failed ('10.0.2.166', 6053)

[balloob]

@amelchio let's do that in another PR. Btw surprised ESPHome is using PlatformNotReady 🤔

[amelchio]

My bad, ESPHome actually has its own retry logic. I have submitted #47456 to limit it.