Do not activate Met.no without setting a Home coordinates

[frenck]

Proposed change

Based on issue #48730, we do a lot of traffic to the Met.no APIs/servers based on the default location. This happens when a user doesn't set a location explicitly during onboarding and causes the core configuration to default to the example data from the frontend:

const amsterdam = [52.3731339, 4.8903147];

https://github.com/home-assistant/frontend/blob/109910d18f379e9a23cfc54f3f209e1d06042d72/src/onboarding/onboarding-core-config.ts#L29

Met.no is letting us know that we are in violation of their terms of services. This PR is to mitigate that. For more information see #48730.

Changes:

• If during onboarding no location is set, abort the config flow entry creation. This prevents a configuration entry to be created in those cases.
• For existing installations and configuration entries, this PR checks if we are tracking the Home location of the instance and if those coordinates are the default home location, if so, we log an error and abort the entry setup.

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: Weather forecast spam for a Dutch herring fast food shop #48730
• 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.

[probot-home-assistant]

Hey there @Danielhiversen, @thimic, mind taking a look at this pull request as its been labeled with an integration (met) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[pvizeli]

I think that is a frontend issue, we should not set some things somewhere. But I like the approach to abort it, should also work if we set 0.0 instead amsterdam

[frenck]

I agree this is a frontend issue at some level, however, we currently have a lot of these instances out there. So this is more or less mitigating raised issues/concerns.

Should I add 0.0 for the aborts as well?

[balloob]

This is an ok stop-gap measure for now. Let's get it out asap. We will work on more properly skipping setting a location .

[balloob]

Yes, let's also check on 0,0.

[Danielhiversen]

Tested, and seems to work correct here 👍