Met.no platform magically appears?

Configuration
1

Just did a new install of Hassbian with Buster, so far so good! I’ve noticed a weather.home sensor provide by Norwegian Weather Service at the end of my sensor list?

The only weather platform I use in my configuration is DarkSky

Not sure I need this, any ideas how to remove?

2

I can’t say when this first started but I just recently switched from DarkSky Sensor to DarkSky Platform. That part is working great. I live in the US so not sure why I would want to use the Norwegian Meteorological Institute.

In looking at my log I see errors for the Norwegian Meteorological Institute
Retrying in 18 minutes
July 1, 2019, 7:21 PM components/met/weather.py (ERROR) - message first occured at July 1, 2019, 4:02 PM and shows up 2 times

https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/1.9/ returned
July 1, 2019, 7:21 PM main.py (ERROR) - message first occured at July 1, 2019, 4:02 PM and shows up 2 times

Setup of platform met is taking over 10 seconds.
July 1, 2019, 4:02 PM main.py (WARNING)

Any thoughts on how to eliminate this bogus sensor?

3

Following this a little further using logger: debug I see that met is being set-up in homeassistant.setup Is this suppose to happen? Can I override it?

2019-07-02 06:41:38 INFO (MainThread) [homeassistant.setup] Setting up met
2019-07-02 06:41:38 INFO (MainThread) [homeassistant.setup] Setup of domain met took 0.0 seconds.
2019-07-02 06:41:38 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=met>
2019-07-02 06:41:38 INFO (MainThread) [homeassistant.setup] Setting up hacs

4

Solved! I found the following code in /home/homeassistant/.homeassistant/.storage/core.config_entries

            {
                "connection_class": "cloud_poll",
                "data": {
                    "track_home": true
                },
                "domain": "met",
                "entry_id": "3f8ce78b95e447eb9e0381b9007b4e57",
                "options": {},
                "source": "onboarding",
                "title": "Home",
                "version": 1
            }

When I removed this entry, met weather also disappeared.
I clicked the mappoint when I first installed hassbian not knowing what it was used for.

2 Likes
5

Go to Configuration --> Integrations --> Met.no --> upper right corner–> delete

2 Likes
6

hi, when I start my clean install of hass 0.103.4, I get a screen asking me what I want to call my hass, when I say that I don’t care and click on next I see the unwelcome installation of met in my logs. I have nothing in my configuration asking for met. Did you ever find a way to stop met ever being installed or did you just remove it afterwards? I’m trying to do automated installations on machines that don’t need to know the weather and what to stop the initial install. thanks!

Dec 25 20:42:45 entrance sh[407]: 2019-12-25 20:42:45 INFO (MainThread) [homeassistant.setup] Setting up met
Dec 25 20:42:45 entrance sh[407]: 2019-12-25 20:42:45 INFO (MainThread) [homeassistant.setup] Setup of domain met took 0.0 seconds.
Dec 25 20:42:45 entrance sh[407]: 2019-12-25 20:42:45 INFO (SyncWorker_0) [homeassistant.loader] Loaded weather from homeassistant.components.weather
Dec 25 20:42:45 entrance sh[407]: 2019-12-25 20:42:45 INFO (MainThread) [homeassistant.setup] Setting up weather
Dec 25 20:42:45 entrance sh[407]: 2019-12-25 20:42:45 INFO (MainThread) [homeassistant.setup] Setup of domain weather took 0.0 seconds.
Dec 25 20:42:45 entrance sh[407]: 2019-12-25 20:42:45 INFO (MainThread) [homeassistant.components.weather] Setting up weather.met
Dec 25 20:42:45 entrance sh[407]: 2019-12-25 20:42:45 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new weather.met entity: weather.home
7

I’m thinking I still needed to remove it but memory’s a little dim on this.

8

New to HASS. Went to look at DarkSky and I see it is done. Looks like they sold out to Apple?

9

Yes they did, I moved over to weatherbit