Read the statement by Michael Teeuw here.
MMM-DWD-Pollen
-
@sdetweil said in MMM-DWD-Pollen:
if someone knows and is willing to help they will.
this forum is all volunteer communityYes, I know, and that’s absolutely fine, of course. It was just another attempt here.
-
The Number on github is the correct one as statet on the github site
“There is a map that sows all part regions (but you have to match it to the numbers shown above)”
Dumb take but did you try to just wait one day? DWD pushes the numbers out once a day, if there are no new ones it shows nothing on the module.
-
@fatgrandma Thank you for your answer.
When I take the wrong number from the DWD site I got the message “No values today. No values tomorrow”. But you are right. In this case I have to wait a day more. I guess DWD published his new values at 11 a.m. every day, doesn´t it?
But when I take the correct number from the github site(!), I get only the message “Loading”. And this has been the case for several days.
-
Apparently DWD had changed its numbering. I updated the Readme.
Those are the new regions:
10=Schleswig-Holstein und Hamburg
11=Inseln und Marschen
12=Geest,Schleswig-Holstein und Hamburg
20=Mecklenburg-Vorpommern
30=Niedersachsen und Bremen
31=Westl. Niedersachsen/Bremen
32=Östl. Niedersachsen
40=Nordrhein-Westfalen
41=Rhein.-Westfäl. Tiefland
42=Ostwestfalen
43=Mittelgebirge NRW
50=Brandenburg und Berlin
60=Sachsen-Anhalt
61=Tiefland Sachsen-Anhalt
62=Harz
70=Thüringen
71=Tiefland Thüringen
72=Mittelgebirge Thüringen
80=Sachsen
81=Tiefland Sachsen
82=Mittelgebirge Sachsen
90=Hessen
91=Nordhessen und hess. Mittelgebirge
92=Rhein-Main
100=Rheinland-Pfalz und Saarland
101=Rhein, Pfalz, Nahe und Mosel
102=Mittelgebirgsbereich Rheinland-Pfalz
103=Saarland
110=Baden-Württemberg
111=Oberrhein und unteres Neckartal
112=Hohenlohe/mittlerer Neckar/Oberschwaben
113=Mittelgebirge Baden-Württemberg
120=Bayern
121=Allgäu/Oberbayern/Bay. Wald
122=Donauniederungen
123=Bayern nördl. der Donau, o. Bayr. Wald, o. Mainfranken
124=Mainfranken -
I checked your region (32) and there is indeed no data from DWD. The only region is 31 with data.
-
@Sachse Please excuse me for replying to such an old post. But unfortunately I have the same problem as you had. The module only worked fine for a few days, and now it won’t load the data any more. I have now tried to reproduce your solution. But I unfortunately did not solve it. When I enter “pm2 status” and “netstat -plan|grep 8080”, I get the following output.
pi@raspberrypi:~/MagicMirror/modules $ pm2 status ┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐ │ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │ ├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤ │ 0 │ MagicMirror │ default │ 2.26.0 │ fork │ 749 │ 5h │ 0 │ online │ 0% │ 2.6mb │ pi │ enabled │ └────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘ pi@raspberrypi:~/MagicMirror/modules $ netstat -plan|grep 8080 (Es konnten nicht alle Prozesse identifiziert werden; Informationen über nicht-eigene Processe werden nicht angezeigt; Root kann sie anzeigen.) tcp6 0 0 ::1:8080 :::* LISTEN 838/electron.js tcp6 0 0 ::1:8080 ::1:46942 TIME_WAIT - tcp6 0 0 ::1:8080 ::1:46944 FIN_WAIT2 - tcp6 0 0 ::1:8080 ::1:44370 VERBUNDEN 838/electron.js tcp6 0 0 ::1:44370 ::1:8080 VERBUNDEN 941/Electron --shar tcp6 1 0 ::1:46944 ::1:8080 CLOSE_WAIT 941/Electron --shar
It would be really nice if you could please give me the crucial hint where the problem is now and how it can be solved? :-)
-
@Klinge - It appears that your problem isn’t the same. @Sachse had two instances of the Magic Mirror framework running at the same time. You probably don’t have that problem.
The DWD site appears to be up and is hosting a json file. So let’s start at the beginning. Please post the relevant portion of your
config.js
file. We don’t need everything, just the part that configures the MMM-DWD-Pollen module. That will let us try and replicate your problem. Be sure to use the Markdown features when you post your code snippet!