Time and Weather problems

[sdetweil]

@Vaughn for clock,
according to the doc,
you add a field to config called

dateFormat: "???",

where ??? follows the doc link here
https://docs.magicmirror.builders/modules/clock.html#configuration-options

u did follow all the instruction on the weather module, right? I don’t see any of the location stuff it the module doc
https://github.com/nigel-daniels/MMM-3Day-Forecast

[Vaughn]

sdetweil

Ok so I did read this config notes, but did not work. Just had another go.

with my code, for the clock, as so:

{
module: “clock”,
position: “top_left”
//config: {
//timeFormat: “12”, //“dddd, LL”, //“DD/MM/YYYY”,
//showDate: false,
//}
},
All works fine, only date in wrong format. Uncomenting the config, even if left blank inside, the mirror crashes.

What am I missing please?

thanks Vaughn

[Vaughn]

Sorry, did have the dateFormat in there, only as that didn’t work, looked at the timeFormate, to see if I could prove the concept.

Thanks again Vaughn

[sdetweil]

@Vaughn said in Time and Weather problems:

position: “top_left” < -------- missing comma
//config: {

general rules, each line needs to end with a comma (more coming) if there is another named line after it
if the thing after “:” is a number or true/false, no quotes, else quotes (doesn’t matter which kind, single or double as long as they are matched )

module: 'clock",
position: ‘top_left’, // < ------
config: {
dateFormat: " ??? " // some string
}
}

[sdetweil]

@Vaughn said in Time and Weather problems:

Wednesday, 05 August, 2020

following the clock doc link for dateFormat
Possible values: Docs -> https://momentjs.com/docs/#/displaying/format/

“dddd - day of week
D - day of month
MMMM - month of year in text
YYYY” year, numeric

“dddd, D MMMM, YYYY”

[Vaughn]

FAB :-)

YES missed the comma at the top, after position, only excuses was I was hacking, so added a line and then did not know the one above needed the comma.

Huge thanks

Now onto the Weather.

Last post said there was no position included. I thought that was the Log/Lat?

I know other parts use a position code, I hoped this would be overwritten as I was including the coordinates, as i cannot find any way to read the ‘city.list.json.gz’ file as I am told in many parts this is where to find the location code.

Nothing I have opens this, any ideas please.

Thanks again Vaughn

[sdetweil]

@Vaughn I meant the module doesn’t use location codes only lat/lon, so u don’t need to read that file.

if u are on the pi, gz means zipped, so the gzip command would unzip it.

a Google search for what file type is gz would have got u this info.

[sdetweil]

@Vaughn can u clarify what the problem was with the dateFormat? seemed pretty easy from the doc

[Vaughn]

YES, as I have now fixed it. The MMM uses the api_key, where as the original forecast code used, appid. Sooo wrong syntax.

Now working great.

Many thanks to all for the help. Please how can I show this is sorted, noticed some of your posts show this.

thanks Vaughn

[sdetweil]

@Vaughn you didn’t open an issue, just a topic. so it can’t be closed/resolved

can u clarify the problem with the dateFormat field. why you couldn’t solve this on your own.
maybe we need to fix something in the doc, or something else.

the intent is to give users, even those with limited experience, access to clear and direct info, so that they don’t become disillusioned with some of the complexities.