Read the statement by Michael Teeuw here.
Time and Weather problems
-
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
-
@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.
-
@Vaughn can u clarify what the problem was with the dateFormat? seemed pretty easy from the doc
-
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
-
@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.
-
The issue was I used the wrong call for the key. This I think was as I had been trying so many, I had got stuck on this city.list.json file I could not open. the original code insists it is required for your location. I’m still not fully sure I have the correct location.
To get mine:
I first went to the MMM world map site.
Here I saw a full map with all the cities and their weather locations. Mine was 35, I think, Ipswich
I added this to my code. I also added the Lon and Lat, hoping they would take the correct info.The forecast looks OK, similar to that on the TV earlier, so maybe I got it correct.
this is my working code:
{
module: “MMM-3Day-Forecast”,
position: “bottom_left”,
header: “3 Day forecast”,
config: {
location: “Ipswich”,
locationID: “35”, //ID from http://bulk.openweathermap.org/sample/city.list.json.gz; unzip the gz file and find your city
api_key: “correct call for key”, // weatherbit
//appid: “Old call for key”,
lat: 52.062569,
long: 1.233907,
units: “M”,
lang: “en”,
interval: 900000
}
},
Now the LocationID:“”, I got from a map. No idea where this was from, cant find it again, but think its OK. If it is wrong please let me know.Main area Of problem I had was in reading the city.list.json file. Does this need a program to read? as noting I found would open it. I presume, there is a program/code you can use that finds the locationID with just the city name or, Long/Lat numbers?
this is the area I feel needs a little more explanation for novices like me please :-)
Hope this helps Vaughn
-
@Vaughn once again, that module, MMM-3Day-Forecast, doesn’t use the city list file, so it doesn’t matter.
but, net, you appear not to be reading the documentation for the modules you are using. ( the module that DOES use the file gives instructions, which h u have copied, but still not read)
//ID from http://bulk.openweathermap.org/sample/city.list.json.gz; unzip the gz file and find your city -
the gz file I did try to unzip, but this was on the PC, Win10, and this failed.
Sis not know the code/way to unzip in the pi.
Did read the notes, but then understanding is another thing. Missing a comer, is sooo important, but not seen, if not known it should be there. Your comment, ;more comers;, was the key thanks
-
@Vaughn
Sis not know the code/way to unzip in the pi.did u ask anyone? that exact phrase on Google would have got u the answer.
I still haven’t answered on the actual date format problem
