When I issue the ps -ef | grep node
it returns pi 988 811 3 17:20 pts/0 00:00:00 grep --color=auto node
Read the statement by Michael Teeuw here.
Posts
-
RE: MMM-DarkSkyForecast - Yet ANOTHER weather module
-
RE: MMM-DarkSkyForecast - Yet ANOTHER weather module
Just checked and the module name in the module directory is
MMM-darkSkyForecast and that was created by git cloning as stated in the instructions from the GitHub Repository.So the name of the directory DOES have a lowercase d in it.
-
RE: MMM-DarkSkyForecast - Yet ANOTHER weather module
How about I do a full shut down /power off?
-
RE: MMM-DarkSkyForecast - Yet ANOTHER weather module
[16:51:14.569] [LOG] Starting MagicMirror: v2.10.0-develop
[16:51:14.714] [LOG] Loading config …
[16:51:14.985] [LOG] Loading module helpers …
0 [LOG] Initializing new module helper …
0 [LOG] Module helper loaded: MMM-Remote-Control
0 [LOG] No helper found for module: MMM-DarkSkyForecast.
0 [LOG] No helper found for module: alert.
[16:51:16.448] [LOG] Initializing new module helper …
[16:51:16.469] [LOG] Module helper loaded: updatenotification
[16:51:16.486] [LOG] No helper found for module: clock.
[16:51:21.582] [LOG] Initializing new module helper …
[16:51:21.589] [LOG] Module helper loaded: calendar
0 [LOG] All module helpers loaded.
[16:51:21.619] [LOG] Starting server on port 8080 …
[16:51:21.765] [INFO] You’re using a full whitelist configuration to allow for all IPs
0 [LOG] Server started …
0 [LOG] Connecting socket for: MMM-Remote-Control
0 [LOG] Starting node helper for: MMM-Remote-Control
0 [LOG] Connecting socket for: updatenotification
0 [LOG] Connecting socket for: calendar
0 [LOG] Starting node helper for: calendar
0 [LOG] Sockets connected & modules started …
0 [LOG]
Ready to go! Please point your browser to: http://0.0.0.0:8080
Starting chromium browser now, have patience, it takes a minute
[16:51:23.548] [ERROR] { Error: listen EADDRINUSE: address already in use 0.0.0.0:8080
at Server.setupListenHandle [as _listen2] (net.js:1280:14)
at listenInCluster (net.js:1328:12)
at doListen (net.js:1461:7)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
code: ‘EADDRINUSE’,
errno: ‘EADDRINUSE’,
syscall: ‘listen’,
address: ‘0.0.0.0’,
port: 8080 }
[16:51:29.611] [ERROR] ERROR! Could not find main module js file for MMM-darkSkyForecast -
RE: MMM-DarkSkyForecast - Yet ANOTHER weather module
Ahh looks like the console was behind Magic Mirror and has these entries.
-
RE: MMM-DarkSkyForecast - Yet ANOTHER weather module
Well that did not display the DEV console either. Just Magic Mirror standard display. I have my display rotated 90 degree’s if thats a concern. So its in Portrait Mode essentially and not Landscape.
-
RE: MMM-DarkSkyForecast - Yet ANOTHER weather module
Yup. Thats what I pressed CTRL-SHIFT-lowercase i. Nothing. Strange eh? I will try the method above.
-
RE: MMM-DarkSkyForecast - Yet ANOTHER weather module
I press CTRL-SHIFT-I with Magic Mirror Running and no console is presented. Actually there is no change at all. Its as if I have not pressed any keys.
-
RE: MMM-DarkSkyForecast - Yet ANOTHER weather module
Latest version of Magic Mirror on Raspberry Pi Zero W.
Git cloned directory for MMM-DarkSkyForecast. Directory created under MagicMirror/Modules. Ran npm install. . Installed and mentioned 16 severe vulnerabilities.
Whatever?
Modified /config/config.js with entries from git hub repositiory instructions.
Ran linter against config.js. No lint :)
Restarted Magic Mirror. Module does not display. Here is my config.js/* Magic Mirror Config Sample * * By Michael Teeuw http://michaelteeuw.nl * MIT Licensed. * * For more information how you can configurate this file * See https://github.com/MichMich/MagicMirror#configuration * */ var config = { address: "0.0.0.0", // Address to listen on, can be: // - "localhost", "127.0.0.1", "::1" to listen on loopback interface // - another specific IPv4/6 to listen on a specific interface // - "", "0.0.0.0", "::" to listen on any interface // Default, when address config is left out, is "localhost" port: 8080, ipWhitelist: [], // Set [] to allow all IP addresses // or add a specific IPv4 of 192.168.1.5 : // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.1.5"], // or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format : // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.3.0/28"], language: "en", timeFormat: 12, units: "imperial", // serverOnly: true/false/"local" , // local for armv6l processors, default // starts serveronly and then starts chrome browser // false, default for all NON-armv6l devices // true, force serveronly mode, because you want to.. no UI on this device modules: [ { module: 'MMM-Remote-Control', // uncomment the following line to show the URL of the remote control on the mirror position: 'bottom_left', // you can hide this module afterwards from the remote control itself config: { apiKey: '56cab4b5d5e24cfea8c436ac591d722c' } }, { module: "MMM-DarkSkyForecast", header: "Weather", position: "top_right", classes: "default everyone", disabled: false, config: { apikey: "not gonna share it :)", latitude: "39.164581", longitude: "-119.766922", iconset: "4c", concise: false, forecastLayout: "table" } }, { module: "alert", }, { module: "updatenotification", position: "top_bar" }, { module: "clock", position: "top_left" }, { module: "calendar", header: "US Holidays", position: "top_left", config: { calendars: [ { symbol: "calendar-check", url: "webcal://www.calendarlabs.com/ical-calendar/ics/76/US_Holidays.ics" } ] } }, ] }; /*************** DO NOT EDIT THE LINE BELOW ***************/ if (typeof module !== "undefined") {module.exports = config;}
-
RE: [MMM-Remote-Control](v2-dev) Extensible REST API, Dynamic Menus, and Socket Communications, plus other updates
That works. Now I am struggling with understanding the IP Whitelist area . I want to open up access to all IP Addresses internally between 192.168.1.2 and 192.168.1.254 as I am unsure which of those IP addresses will be dynamically assigned to the device I use to access the MMM-Remote-Control app.
ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1"], // Set [] to allow all IP addresses // or add a specific IPv4 of 192.168.1.5 : // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.1.5"], // or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format : // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.3.0/28"],