Struggling with Weather... module

sdetweil

@D3dl3g you ONLY setup from config.js

please try with NO apibase set

D3dl3g

weather.js and weatherprovider.js i have set back to defaults.

i have set config.js as requested

  weatherProvider: 'ukmetofficedatahub',
  lat: "52.###############",
  long: "-1.###############",
//apiBase: 'https://api-metoffice.apiconnect.ibmcloud.com/v0/forecasts/point/daily/',
  apiKey: 'e52#############################',
  apiSecret: 'd3a#############################',

the result:-

sdetweil

@D3dl3g send me your API key… config from config.js via email or direct message so I can debug

did u look in the browser messages?

my email is my same userid at gmail

D3dl3g

Just to update the forum, as to what happened behind closed doors

Sam kindly tested my code, and it worked for him.

I am recieving browser errors (previously requested but i wasnt looking in the right bit of the browser window)… he is not

Issues Tab

Console Tab

the last 5 entries here will reoccur, im guessing at every “retry” for weather info

attempted to use useCorsProxy: true to no avail

Sam kindly posted into git hub issues.
https://github.com/MichMich/MagicMirror/issues/271

karsten13

tested ukmetofficehub and it works out of the box (without setting the useCorsProxy flag).

Looking into the provided config

  weatherProvider: 'ukmetofficedatahub',
  lat: "52.###############",
  long: "-1.###############",

which is messed up. It has to be:

  weatherProvider: 'ukmetofficedatahub',
  lat: 52.###############,
  lon: -1.###############,

sdetweil

@karsten13 I tested w those in quotes, and it worked ok

karsten13

@sdetweil

did only test without, but there is another error lon vs. long …

sdetweil

@karsten13 I just copy pasted and it worked.

weird

D3dl3g

@karsten13

i too am getting this… showing me some 80+miles SEE of my actual location

D3dl3g

@karsten13
also… replace the hash symbols with various numbers… im not posting my exact Lat/Long for obvious reasons…

make sure ur doing

lat:

and

lon:

i had it set to lat & lon(G) which is incorrect. hence why it was 80+miles, way tf over there!

quote marks or none surronding the numbers doesnt appear to matter, for me at least