Read the statement by Michael Teeuw here.
Blank mm after update
-
@evroom think u have good instructions…
ps, 2 of my three systems do not have pi as the user, so the path is wrong, and in the module defaults too
-
@sdetweil said in Blank mm after update:
2 of my three systems do not have pi as the user
Yes, I assumed user pi and the install under the user pi home directory.
Will try to remember that in the future.
Tilde for the home directory should work on all platforms, is my understanding.~/MagicMirrorMy keyboard is lacking a tilde and I always forget the right keystrokes.
So /home/pi is faster. :-) -
@evroom I sat right now and installed a new calendar module and suddenly the
mmm-weatherchartstarted working… :thinking_face:Did the
$ pm2 logs --lines 100and got a lot of errors, but I guess because everything’s working fine so don’t have to bother right now?! -
And of course it didn’t work now when I tried to switch back to default calendar module and then back to the other calendar module…
-
@kvicksson said in Blank mm after update:
so don’t have to bother right now?
As long as the errors are no fatal errors that do not prevent the MagicMirror from starting or prevent a certain module from working right, you might chose to ignore them.
But the problem is, that when you add something new or update something existing, it becomes more and more difficult to debug and/or correct in case of problems.When you do this:
$ pm2 flush $ pm2 restart mm $ pm2 logs --lines 100what is the first error you see ?
Perhaps you post the first 50 to 100 lines of the log.But only if you want to spend some time on it, when not that’s fine too.
-
@evroom actually no errors like I got before…
PM2 | 2019-08-29T21:46:00: PM2 log: pid=1331 msg=failed to kill - retrying in 100ms PM2 | 2019-08-29T21:46:00: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT] PM2 | 2019-08-29T21:46:00: PM2 log: pid=1331 msg=process killed PM2 | 2019-08-29T21:46:00: PM2 log: App [mm:0] starting in -fork mode- PM2 | 2019-08-29T21:46:00: PM2 log: App [mm:0] online /home/pi/.pm2/logs/mm-out.log last 100 lines: 0|mm | Shutting down server... 0|mm | Stopping module helper: updatenotification 0|mm | Stopping module helper: mmm-systemtemperature 0|mm | 0|mm | > magicmirror@2.8.0 start /home/pi/MagicMirror 0|mm | > sh run-start.sh 0|mm | 0|mm | Starting MagicMirror: v2.8.0 0|mm | Loading config ... 0|mm | Loading module helpers ... 0|mm | No helper found for module: alert. 0|mm | Initializing new module helper ... 0|mm | Module helper loaded: updatenotification 0|mm | Initializing new module helper ... 0|mm | Module helper loaded: mmm-systemtemperature 0|mm | No helper found for module: clock. 0|mm | Initializing new module helper ... 0|mm | Module helper loaded: calendar 0|mm | Initializing new module helper ... 0|mm | Module helper loaded: MMM-YrThen 0|mm | Initializing new module helper ... 0|mm | Module helper loaded: mmm-weatherchart 0|mm | Initializing new module helper ... 0|mm | Module helper loaded: newsfeed 0|mm | All module helpers loaded. 0|mm | Starting server on port 8080 ... 0|mm | Server started ... 0|mm | Connecting socket for: updatenotification 0|mm | Connecting socket for: mmm-systemtemperature 0|mm | Starting node helper: mmm-systemtemperature 0|mm | Connecting socket for: calendar 0|mm | Starting node helper for: calendar 0|mm | Connecting socket for: MMM-YrThen 0|mm | MMM-YrThen 8/29/2019 9:46:08 PM: Starting helper for MMM-YrThen 0|mm | Connecting socket for: mmm-weatherchart 0|mm | Starting node helper: mmm-weatherchart 0|mm | Connecting socket for: newsfeed 0|mm | Starting module: newsfeed 0|mm | Sockets connected & modules started ... 0|mm | Launching application. /home/pi/.pm2/logs/mm-error.log last 100 lines: 0|mm | /home/pi/MagicMirror/node_modules/electron/dist/electron: /lib/arm-linux-gnueabihf/libdbus-1.so.3: no version information available (required by /home/pi/MagicMirror/node_modules/electron/dist/electron) 0|mm | /home/pi/MagicMirror/node_modules/electron/dist/electron: /lib/arm-linux-gnueabihf/libdbus-1.so.3: no version information available (required by /home/pi/MagicMirror/node_modules/electron/dist/electron) 0|mm | (node:2465) [DEP0025] DeprecationWarning: sys is deprecated. Use util instead. 0|mm | /proc/self/exe: /lib/arm-linux-gnueabihf/libdbus-1.so.3: no version information available (required by /proc/self/exe) 0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.I really appreciate you want to look into my errors, I’m not too good on this :)
-
Doesn’t look too bad.
Probably you saw the previous errors in your log output, that it is why flushing (pm2 flush) sometimes cannot hurt.In order to know a bit about your environment, can you post the output of the following commands ?
I am assuming you are using a Raspberry Pi$ cat /proc/device-tree/model $ lsb_release -a $ npm --version $ node --version $ pm2 --version $ cat /boot/config.txt | egrep -v '^$|^#|^\['I also would suggest to see if npm shows any errors:
$ cd ~/MagicMirror $ npm auditIn my case a
$ npm audit fixsolved the dependency issues it found.
Perhaps others have different ideas, but as a hobbyist, I would take these steps first myself.
-
@evroom said in Blank mm after update:
In my case a
$ npm audit fixsolved the dependency issues it found.
The npm audit warnings do not create any problems in running the mirror as far as I know. They also do not show up in the pm2 logs.
I would even be very careful as an inexperienced user to do that. “Fixing” these npm warnings on the root MM install could break the whole mirror (not the mirror itself of course :-)). Especially if you mess with the electron/chromium dependencies. -
@evroom got an error on the
egrepcommand:pi@raspberrypi:~ $ cat /proc/device-tree/model Raspberry Pi 3 Model B Rev 1.2pi@raspberrypi:~ $ lsb_release -a No LSB modules are available. Distributor ID: Raspbian Description: Raspbian GNU/Linux 8.0 (jessie) Release: 8.0 Codename: jessie pi@raspberrypi:~ $ npm --version 5.6.0 pi@raspberrypi:~ $ node --version v9.11.2 pi@raspberrypi:~ $ pm2 --version 3.5.1 pi@raspberrypi:~ $ cat /boot/config.txt | egrep -v '^$|^#|^[' grep: Invalid regular expression -
@kvicksson said in Blank mm after update:
got an error on the egrep command
Forgot to escape the [, try this:
cat /boot/config.txt | egrep -v '^$|^#|^\['EDIT: Did not forget to escape it, it is this shitty forum that removes it.
There needs to a backslash
\before the last[ -
@lavolp3 said in Blank mm after update:
Fixing” these npm warnings on the root MM install could break the whole mirror
The npm audit itself suggests to fix it using the fix option.
I personally never had any issues with this command, but perhaps I was lucky till now.
Sometimes it cannot resolve an issue, but it never broke anything.But, if it appears to be that dangerous, then indeed it is perhaps to refrain from it when not really necessary.
-
@kvicksson said in Blank mm after update:
(node:2465) [DEP0025] DeprecationWarning: sys is deprecated. Use util instead.
I saw this error once for a specific module.
Needed a small code change.
Will try to find what is was. -
This is a command to list all your modules that are in the config.js and which ones are enabled/disabled:
$ cat ~/MagicMirror/config/config.js | egrep 'module:|disabled' | sed -e 's/^[ \t]*//' -
@evroom cool… how can u tell which module ‘disabled’ applies to?
system 1
module: "alert", disabled: false, module: "updatenotification", module: "clock", disabled: false, module: "calendar", disabled: false, module: "MMM-SleepWake", module: "newsfeed", disabled: false, disabled: false, module: 'WaterLevels', disabled: false, module: "MMM-ImagesPhotos", disabled: true, module: 'MMM-MQTTfloorplan', disabled: false, module: "MMM-AssistantMk2", module: "MMM-Hotword", disabled: false, disabled: true, module: "default/SampleModule", disabled: true, module: "MMM-GoogleMapsTraffic", disabled: true, module: "MMM-PC-Stats", disabled: true, module: 'mmm-weatherchart',system 2
module: "alert", // module: "updatenotification", module: "clock", // module: "calendar", // module: 'MMM-WunderGround', // module: "newsfeed", disabled: false, module: "MMM-SleepWake", module: "MMM-ImagesPhotos", module: 'MMM-voice', disabled: false, module: 'WaterLevels', module: 'MMM-WatchDog',system 3
module: "alert", module: "updatenotification", module: "clock", module: "calendar", disabled: true, module: "compliments", module: "currentweather", module: "weatherforecast", module: "newsfeed", module: "MMM-ImagesPhotos", disabled: false, module: "MMM-SleepWake",i wrote this little piece of node js to find active modules for my upgrade script
const config = require('../config/config.js');const fs=require('fs'); for(let m of config.modules){ if(!(m.disabled || false)){ console.log(m.module); } } -
@sdetweil said in Blank mm after update:
how can u tell which module ‘disabled’ applies to?
I am assuming it is sequential and that
disabled:comes aftermodule:, when present. Don’t think a ‘runaway’disabledcould exist.
And for the purpose it serves, it does its job, IMHO.Perhaps it is better to first remove the leading blank space and then do the grep (and to ignore the comment parts):
$ cat ~/MagicMirror/config/config.js | sed -e 's/^[ \t]*//' | egrep -w '^module:|^disabled:'Your piece of node.js looks nice, but how to run it standalone ?
If used as part of a script, it makes more sense to do it this way (more control, more flexible). -
@sdetweil said in Blank mm after update:
module: “newsfeed”,
disabled: false,
disabled: false,I see now, that this is rather odd, not correct, without thinking too much about it.
Does my modified command give the same result ?
It sort of contradicts my statement on being sequential, etc.
Or do you really have ?module: "newsfeed", disabled: false, disabled: false, module: "MMM-Hotword", disabled: false, disabled: true, -
-
@evroom i have disabled, before and after module all thruout the config.js
it is not positional
modules: [ { diabled: true, module: "alert", }, { disabled: false, module: "updatenotification", position: "top_bar", config: { updateInterval: 3 * 60 * 1000, refreshInterval: 10 * 60 * 1000 } }, { module: "clock", position: "top_right", config: { showWeek: false, sendNotitifications: false } }, { disabled: false, module: "calendar", position: "top_left", config: { showEnd: false, timeFormat: 'relative', //fetchInterval: 10000, calendars: [ { symbol: "family ", //url: "https://www.ojrsd.com//site/handlers/icalfeed.ashx?MIID=11", //url: "http://localhost:8086/modules/cals/basic.ics" }, ] } }, { disabled: false, module: "MMM-SleepWake", config: { delay: 5, // minutes , default = 15 minutes "source": "External", // choices are PIR -- uses the Raspberry pi hardware dection pins and PIR sensor // or // External -- uses some external source for motion detection, like a video camera // -- see the github motion project // mode // HOW to go to sleep // use hardware(hdmi), software (dpms), or simulate (hide content leaving black screen) "mode":"hide", // mode choices are // 'pi': // executes the tvservice command // // 'dpms' // executes the 'xset dpms force' command // // 'hide' // hides all modules. modules hidden when the sleep is issued will be hidden on wakeup // for energyStar monitors and TVs, this allows the screen to remain powered on so it will come alive on movement // //detectionDir: '/home/odroid/MagicMirror/modules/MMM-SleepWake/motion' // detectionDir: folder containing externally generated file when motion starts // will be created if needed // detectionFile: filename generated for motion start. default = 'detected' } }, { module: "newsfeed", disabled: false, position: "bottom_bar", config: { ignoreOldItems:false, feeds: [ { title: "New York Times", url: "http://www.nytimes.com/services/xml/rss/nyt/HomePage.xml" }, /* { title: "BBC", url: "http://feeds.bbci.co.uk/news/world/rss.xml", }, { title: "SRS", url: "http://feeds.news24.com/articles/news24/SouthAfrica/rss", }, */ ], showSourceTitle: true, showPublishDate: true } }, { disabled: false, module: 'WaterLevels', position: 'top_right', config : { width: 400, height: 400, Pins: [ 'v14','v3' ], labels:['Water Usage','Water level'], yaxis_legend: ['gallons used','gallons'], ranges: [{"min":0,"max":200,"stepSize":100}, {"min":0,"max":2029,"stepSize":500}], pinLimits: [20,1700], dayrange: 3, updateInterval: 5, stacked: true, } }, { disabled: false, module: "MMM-ImagesPhotos", position: "fullscreen", config: { opacity: 0.9, animationSpeed: 0, updateInterval: 15000, backgroundColor: "#808080", path: "/selectedpics", debug:true } }, { disabled: true, module: 'MMM-MQTTfloorplan', position: 'center', // this can be any of the regions config: { mqttServer: { url: "192.168.0.110", user: "", password: "" }, floorplan: { image: "floorplan.png", // image in subfolder 'images'; change to floorplan.png to avoid git repository changes width: 634, // this must be the width of the image above height: 392, // this must be the height of the image above }, subscriptions: [ /*{ topic: '', // MQTT Topic name label: 'Living Light', // Not displayed anywhere! type: 'door', // Using 'door' instead 'light' to get 2-state icon display: { left: 50, top: 50 }, }, { topic: '', label: 'First Floor Corr PIR', type: 'motion', display: { left: 100, top: 150 }, }, */ { topic: 'LivT', label: 'Living Temp', type: 'label', display: { left: 44, top: 159, prefix: "", suffix: " °C", decimals: 1 }, }, { topic: 'LivH', label: 'Living Humidity', type: 'label', display: { left: 44, top: 179, prefix: "", suffix: " %RH", decimals: 0 }, }, { topic: 'GuestT', label: 'Guest Room Temp', type: 'label', display: { left: 255, top: 193, prefix: "", suffix: " °C", decimals: 1 }, }, { topic: 'GuestH', label: 'Guest Room Humidity', type: 'label', display: { left: 255, top: 213, prefix: "", suffix: " %RH", decimals: 0 }, }, { topic: 'eStatus', label: 'Weather', type: 'label', fields: ['OAT','OAH'], //key: 'OAT', //I would like to have configurable keyword for each name of object that I want display. //jsonpointer: '/OAT', display: { left: 55, top: 337, prefix: "", suffix: " °C", decimals: 1 }, }, ] } }, { disabled: false, module: "MMM-AssistantMk2", position: "top_right", config: { record: { recordProgram : "arecord", device : "default", }, notifications: { ASSISTANT_ACTIVATED: "HOTWORD_PAUSE", ASSISTANT_DEACTIVATED: "HOTWORD_RESUME", }, } }, { module: "MMM-Hotword", disabled: false, config: { record: { recordProgram : "arecord", device : "default", }, snowboy: [ { hotwords: "smart mirror", //this will be sent to other module for distinguishing which hotword is detected. file: "resources/models/smart_mirror.umdl", sensitivity: '0.5', }, ], autostart:true, autorestart: false, onDetected: { notification: function (payload) { return "ASSISTANT_ACTIVATE" }, payload: function (payload){ return { profile: payload.hotword } } }, }, }, { disabled: true, module: "default/SampleModule", position:'middle' }, { disabled: true, module: "MMM-GoogleMapsTraffic", position: "bottom_right", config: { lat: 41.8816281, lng: -87.6608605, height: "300px", width: "300px", mapTypeId: "roadmap", styledMapType: "transparent", disableDefaultUI: "true", updateInterval: "60000", backgroundColor: "hsla(0, 0%, 0%, 0)", markers: [ { lat: 41.8816281, lng: -87.6608605, fillColor: "#9966ff" }, ] } }, { disabled: true, module: "MMM-PC-Stats", position: "middle", config: { } }, { disabled: true, module: 'mmm-weatherchart', position: 'bottom_left', // this can be any of the regions config: { country: 'Germany', // as determined above area: 'North_Rhine-Westphalia', // as determined above city: 'Duisburg', // as determined above updateInterval: 60 * 60 * 1000, // update every hour hideBorder: true, // whether or not a border with city name should be shown negativeImage: true, // whether or not the default white image should be inverted mmDirectory: "/home/odroid/MagicMirror/" // required for caching; adjust if it differs } }, ] -
@evroom modified results at least lose the comments
module: "alert", disabled: false, module: "updatenotification", module: "clock", disabled: false, module: "calendar", disabled: false, module: "MMM-SleepWake", module: "newsfeed", disabled: false, disabled: false, module: 'WaterLevels', disabled: false, module: "MMM-ImagesPhotos", disabled: true, module: 'MMM-MQTTfloorplan', disabled: false, module: "MMM-AssistantMk2", module: "MMM-Hotword", disabled: false, disabled: true, module: "default/SampleModule", disabled: true, module: "MMM-GoogleMapsTraffic", disabled: true, module: "MMM-PC-Stats", disabled: true, module: 'mmm-weatherchart', -
If these are the only ‘errors’ you see in the pm2 log, then it looks you are quite okay.
As said, I personally would like to ged rid of npm audit errors, but if other board-members think it imposes a hazard to a good running system, then I would leave it. I remember that sometimes some dependencies just did not want to go away and I left it that way.
The only thing to consider, is that you are still running on Debian jessie, where the majority probably runs using stretch and fast adopters on buster.
I would leave this until you setup a new system.So, when it runs as you expect it to run, then you can close this topic and enjoy your mirror. Otherwise we will hear from you.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login