Version 2.30.0 weather module, stuck loading, worked fine before upgrade

sdetweil

@Rberry91 now you have to follow the module instructions to get authorization again

Rberry91

@sdetweil
I reverted to the older version and I have tried updating using your command and other ones and still doesn’t update tell me that “pulling without specifying how to reconcile divergent branches is etc”

The other problem I am having is the weather, the forecast works but the current Weather doesn’t and they are the same code.

sdetweil

@Rberry91 divergent branches sounds like you have both modules trying to merge to the same folder

delete then git clone again
the nan says the apikey is wrong

and you have a typo, MagicMirror is case sensitive

butchkemper

The configuration parameters I use are:

module "MMM-OpenWeatherForecase"
latitude and NOT lat
longitude and NOT lon
apikey and NOT apiKey   <----  Notice the "K"

Some MM configuration keywords have abbreviations but not all. The module README file gives the values for the keywords.

Also, since your apikey has been revealed to the world, you should cancel the posted key and generate a new key. Always keep the apikey secret.

Butch

butchkemper

@sdetweil I noticed this discretion between the Weather module documentation:

The “Weather” documentation has “apiKey” - large case “K”,
The “MMM-OpenWeatherForecast” documentation has “apikey” - small case “k”.

Butch

sdetweil

@butchkemper modules can go anything they want
what is used internally can be anything required

I looked at the doc for the default weather module before posting above. as there are two instances, one works the other doesn’t. apikey is the issue

Assassins

Work on 2.29.0 with api2.5

But now on 2.33.0
It say “NaN”
I get the error 401, it say the apiKey i wrong, but is write from my api key from the website.
How can i get a apiKey to api3.0 without to paid for it. ???
The api2.5 still work, but not on this modul.

    {
      module: 'weather',
      position: 'bottom_left',
      header: 'Ballerup',
      config: {
         lat: "55.7317",
         lon: "12.3633",
         apiKey: "xxxxx765xxxx98xxxjhx888"
       }
    },

sdetweil

@Assassins you cannot get V3 apikey from open weather without providing a credit card.
they don’t charge unless you go over 1000/request per day.

now, you CAN make 2.5 work (if they still accept api requests they keep telling us they are going to do (have done!!)) just be warned that they can/will end this function sometime…

in the module config section
apiKey: 2.5_key
apiVersion: 2.5

and

weatherEndpoint: “current” OR “forecast”

edited

Assassins

@sdetweil
I can only see the header now, where is write Ballerup

{
  module: 'weather',
  position: 'bottom_left',
  header: 'Ballerup',
  config: {
    apiVersion: "2.5",
    weatherEndpoint: "/current",
     lat: "55.7317",
     lon: "12.3633",
     apiKey: "xxxxx765xxxx98xxxjhx888"
   }
},

sdetweil

@Assassins

sorry

weatherEndpoint: “current” or 'forecast" , no /

also, the old api use location or locationID, not lat/lon
and I see you can’t look them up anymore on OWM site

here is from the old doc

locationID	Location ID from OpenWeatherMap This will override anything you put in location.

Leave blank if you want to use location. <------=======

Example: 1234567
Default value: false

Note: When the location and locationID are both not set, the location will be based on the information provided by the calendar module. The first upcoming event with location data will be used.

======================================================================
location	The location used for weather information.

Example: 'Amsterdam,Netherlands'
Default value: false

Note: When the location and locationID are both not set, the location will be based on the information provided by the calendar module. The first upcoming event with location data will be used.

so it ‘seems’ that location by itself would do it.