Use loop.time in DataUpdateCoordinator

[emontnemery]

Proposed change

Use loop.time in DataUpdateCoordinator

Rationale: Calls to utcnow() are expensive on some platforms. The DataUpdateCoordinator does not need to sleep until a precise wall clock time, so we can use loop.time() instead

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)
• Deprecation (breaking change to happen in the future)
• 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
• I have followed the perfect PR recommendations
• 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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

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

[MartinHjelmare]

Looks promising. Are there other questions?

[bdraco]

Looks like its close to passing. Happy to put this on all my production for live testing when its ready for final review

[bdraco]

Pushing on to my houston production now.. Will report back in the morning

[bdraco]

Profile looks good, manual testing looks good.

Will report back tomorrow

[bdraco]

Tested overnight. All good

Looks like this is good to go once tests are sorted

[emontnemery]

@bdraco tests pass now, do you think it's OK to merge it?

[bdraco]

@bdraco tests pass now, do you think it's OK to merge it?

Yes. Been running on multiple production for a while now with no issues

[bdraco]

Thanks @emontnemery

[elupus]

I'm pondering if this could be the background to: #100221