@wyovino I suspect some heavy memory corruption - could be anywhere - I’d copy over your config.js and custom.css to another drive and try a new SD card if it continues.
If it continues after that, I’d get a new device…
@wyovino I suspect some heavy memory corruption - could be anywhere - I’d copy over your config.js and custom.css to another drive and try a new SD card if it continues.
If it continues after that, I’d get a new device…
@sdetweil isn’t SIGSEGV a segmentation fault?
@danybony Monitors without any on/off logos is gonna be a tough one - You’ll want to use HDMI sleep to power up and down the monitor or simply blank it (I’d go for the latter if you’re concerned about a “No Signal” image).
As for the others - you’ll have to experiment - sadly.
General advice:
Get a monitor with a bezel on all sides - why? No lopsided display when you pull it out of frame.
Get a monitor with the cables pointing out one side or the bottom. Why? Pointing out the back will cause issues in install and make it harder to make it compact.
Get a monitor with a built in power converter (110v/220v direct into monitor) - why? For compactness reasons - less work to build frame behind it.
@sdetweil That fix helped. A minor configuration error fix helped too. I think I’ve got it back working the way I wanted it.
Ok, Sam - here’s what I got so far:
The calendar marked “No data” isn’t currently working from host, It can be ignored.
The calendar marked “Parsing” is spitting out data in debug mode, but when calendar turns around and broadcasts, it’ll broadcast zero entries. Only truly private URL has been blanked.
here’s my config - minus the calendars:
{
module: "calendar", // Built in
//position: "top_center", // Currently hidden
classes: "page1 page2 page3",
config: {
animationSpeed: 0,
broadcastEvents: true,
broadcastPastEvents: true,
fetchInterval: 60000, // minimum 1 minute.
maximumEntries: 999999,
@sdetweil I see the problem, I think.
The logs I was using was in the console, those logs don’t show the source - PM2’s logs do.
I think something has changed in how it’s putting together the entries.
It used to be that maximumEntries: 99 - now it’s appearing to sort different or reach back further, so I need maximumEntries: 999 to see all my calendars show up.
I do have past events active - as I like to see where I had things happen, just in case I need it…
What’s changed in the logic for calendar loading for 2.30?
99 entries used to be enough to display all my calendars, now I’m getting like 820 entries loading.
Curious if there’s a bug somewhere, or what. I’ve also noticed that the notices in the log indicating which calendar is loading is gone. Would be nice to have that back, at least in debug mode, so that we can tell what calendar is pushing # of entries.
Thanks!
@Niggich The default CSS keeps it tight - because that’s how I like it.
However, it’s easy to change.
in your magicmirror/css directory, there should be a file named custom.css - in that file, paste the following, and modify it to suit.
/* Month Padding */
.MMM-Multimonth .month {
padding: 0px;
}
Cheers.
@sdetweil I’ve given up as other methods smoothed out the transitions anyway (The website that took too long to reload).
I put them both in, and that fixed it - thanks, Tom.
Tom, is it updateDomOnShow or updateDomOnResume ?
Documentation shows the latter.
It shows, then resets, takes 2-3 seconds to show back up, then runs normally. The problem is that it’s just annoying to have it flash in and then blank, then come up and run.
@sdetweil The only modules I’d have animating is the pages module.
I’m not finding any way to change the animation/fade on MMM-Pages - I’d like to change it to something else - It appears to be the default that is system wide.
Anyone know how to change it?
Thanks
I have MMM-pages (@sdetweil 's version) and MMM-EmbedURL (@wishmaster270) - working together on my system. Evertthing is great, EXCEPT this code below.
What happens is that the website at my docker is loading, then it stops itself and reloads - blanking the screen area for 2-3 seconds while it thinks about it. Unfortunately, even though it’s a docker container and I have “Full control” – it is a very rudimentary program - and the web API is weak at best (Thus the turning off of the time stamp, etc)
What’s going on here? Is there anything I can do to keep it from blanking and restarting (I think when it’s hidden it’s paused?)
If it helps, the page is this program -> https://www.clearskyinstitute.com/ham/HamClock/ - you can look around for suggestions.
Thanks.
{
module: "MMM-pages",
config: {
modules: [
["page1"],
["page2"],
["page3"],
],
animationTime: 2000,
rotationTime: 10000,
}
},
{
module: "MMM-EmbedURL",
position: "top_right",
classes: "page2",
config: {
updateInterval: 3600,
animationSpeed: 0,
appendTimestamp: false,
embed: [
"http://docker.local:8081/live.html",
],
},
},
(any malformed JS above is a paste error, it is correct in code)
@mumblebaj Course, I just switched back to X11 for now. 🙃
@Future-Mirror It may be wayland causing that - Try this:
sudo raspi-config
then use
option 6 “Advanced options”,
option A6, “Wayland”, then
option W1 “X11”
and approve the change.
This will switch you over to the old screen design system, where the instructions in the documentation is known to work.
If you would like, I’d be happy to share my configuration files up to the modules and how I did it. Let me know.
@DarrenO-0 Ahh, gotcha. Yes, this is for two on the same system, which linux treats as one huge monitor.
As I rewrote that section in the docs - I’ll give a (semi) live example (My second mirror is down due to lack of space, I’m working on a solution) - this is what works for me at the moment. I do realize I’m doubling up on some things.
In my Pi’s config, I also reverted to X11 desktop rather than wayland for reasons unrelated. I have not tested this on Wayland.
cd /home/bkey1970/MagicMirror
DISPLAY=:0 npm start
cd /home/bkey1970/MagicMirror
export MM_CONFIG_FILE=config/config2.js
export MM_PORT=8081
DISPLAY=:0 npm start
the start of config.js:
var config = {
address: "0.0.0.0",
port: 8080,
ipWhitelist: [],
language: "en",
timeFormat: 12,
units: "imperial",
//logLevel: ["INFO", "LOG", "WARN", "ERROR", "DEBUG"],
modules: [
The start of config2.js:
var config = {
address: "0.0.0.0",
port: 8081,
electronOptions: {
x: 1920
},
ipWhitelist: [],
language: "en",
timeFormat: 12,
units: "imperial",
//logLevel: ["INFO", "LOG", "WARN", "ERROR", "DEBUG"],
customCss: "css/custom2.css",
modules: [
PM2 commands to tie it all together:
pm2 start /home/<username>/<path>/mm.sh --name "MM Main"
pm2 start /home/<username>/<path>/mm2.sh --name "MM 2nd"
pm2 save