Read the statement by Michael Teeuw here.
[MMM-FlightsAbove] Problem receiving and seing JSON from node_helper
-
@E3V3A Actually the API doesn’t return json. It returns an array of Javascript objects. You can very easy iterate over the array and access any properties of the objects in the array with dot syntax.
const radar = require("flightradar24-client/lib/radar"); radar(53, 13, 52, 14) .then((flights) => { flights.forEach((flight) => { console.log("id: " + flight.id + ", origin: " + flight.origin); }) }) .catch((err) => { console.error(err); process.exit(1); });
-
It returns an array of Javascript objects.
Thanks! That is certainly important to know! :) But I don’t see how that help me here… :(
As for the rest of the test code above, it’s probably not very helpful in my case, but it could be great for another module though. In my code I already have (according to console.log the right output to be fed.) But somehow my feed mechanism is not working and I’m not able to check it.
For example, another dummy question:
Why doesn’t the followingconsole.log
’s print anything?// This comes from YOUR module, usually "node_helper.js" socketNotificationReceived: function(notification, payload) { console.log("=====> " + this.name + " received a socket notification: " + notification); //+ " - Payload: " + payload); switch (notification) { case "NEW_DATA": console.log("-----> FlightsAbove: NEW_DATA received!"); // Why doesn't this show? let ping = payload; console.log("-- PING!\n"); console.log(ping); //console.log("-- PING DATA:\n", ping); this.loaded = true; this.setTableData(payload); break; default: console.log("Did not match the Notification: ", notification); } },
Similarly, here in node_helper.js. Everything before the
//WTF
comments prints, but the rest is never seen! ???radarPing: function() { console.log("ENTER (inside)"); Promise.all([ //radar(-8.20917,114.62177,-9.28715,115.71243) // "PDS" (Bali Airport) radar(53.05959,12.52388,51.98161,14.29552) // (Berlin) ]).then(function(results) { var ping = JSON.stringify(results); console.log("Sending NEW_DATA:"); console.log(ping); // WTF! This below is never shown! this.sendSocketNotification("NEW_DATA", ping); //self? console.log("Sent NEW_DATA!"); console.log("NEW_DATA is: %O", ping); console.dir(ping, {depth: null, colors: true}); //return ping; }).then(function(error) { //console.log("ERROR:") console.log(error); }); console.log("EXIT (inside)"); },
So at the end of the day, I have no idea if the
NEW_DATA
socket notification was actually sent, nor what was the payload, nor if it was received. -
Inside the module itself
console.log
doesn’t work. UseLog.error
instead and check the output in your browser console, not the terminal/cmd -
@yawns That is not correct.
console.log()
works fine in your module. But the output is not shown on the log of your mirror but on the browser’s log. You need to open the developer tools in your browser to see it. -
Oh, really? Maybe this was changed, in the beginning it wasn’t working at all in the main module file.
-
@E3V3A This function works just fine:
radarPing: function () { radar(53.05959, 12.52388, 51.98161, 14.29552) .then((flights) => { this.sendSocketNotification("NEW_DATA", flights); //self? console.log("New radar data: "); console.log(flights); }) .catch(function (error) { //console.log("ERROR:") console.log(error); }); },
It receives data, prints them on the mirror’s log and sends it to the module. The module is receiving the data and logs them to the browser’s console. And your table is populated too.
-
-
@E3V3A
console.log()
is a standard Javascript function it works anywhere.Log.info()
and so on are functions from the MagicMirror’s module system. So they will only work in the module file.node_helper.js
is executed in the server context. Any console output is therefore on the server’s log.The module file is executed in the client context (the browser). So console output from the module file is logged in the browser console.
-
@raywo OMG!! I missed your post by not updating my open tabs. Now I found it and it bloody hell it works! I got so excited I fell off my chair!
I have no idea why the eeek I have been trying to over-engineer this thing. I guess I’m simply not familiar enough with the JS/node notations, and constantly get bogged down with beginners conceptual trivialities.
Thank you! Tomorrow it will be party!
-
@yawns BTW. The
console.log
from main module didn’t want to work in my Firefox (Dev Tools), butconsole.error()
do. It could be a browser issue…