Offline
Here is another option:
ASRock N3150DC-ITX Mini-ITX Motherboard - if you can find one.
SoC – Intel Celeron N3150 quad core processor @ up to 2.08 GHz with Intel HD Graphics Gen8 @ up to 640 MHz – 6W TDP
There are some other Celeron SoC boards that take 19v DC power. The Asus Q1900DC-ITX uses the J1900.
Look for “Thin Mini-ITX” normally that means the DC in.
-Earle
This is going to be my Family Info Board. Still need to get the actual H/W though :-)
Pool info is from my in progress AutelisPentair module - almost done.
I made a small change to this module.
If you add the following:
awayTempColumn.setAttribute(“team-name”, games.away_team_name);
homeTempColumn.setAttribute(“team-name”, games.home_team_name);
Then you can do this in your custom.css:
.MMM-MLB .awayteam[team-name=“Giants”] { color: #FB5B1F; font-weight: bold; }
.MMM-MLB .hometeam[team-name=“Giants”] { color: #FB5B1F; font-weight: bold; }
And now, my Giants are in Giant orange…
-Earle
This module is great - a couple items related to support for the ‘official 7" pi touchscreen’
I can probably code this up and submit a PR if you want - the on/off is easy to do because that is already in the helper. Brightness would need to get moved to the helper away from the CSS tricks.
It is interesting that controlling the brightness of a monitor itself over HDMI is surprisingly non-existent, but the 7" touchscreen h/w rev: 1.1 does indeed support direct brightness manipulation:
You can control the brightness of the backlight itself by:
echo X > /sys/class/backlight/rpi_backlight/brightness
where X is a value between 0 and 255
And you can turn off the backlight with
echo 0 > /sys/class/backlight/rpi_backlight/bl_power
and turn it back on with:
echo 1 > /sys/class/backlight/rpi_backlight/bl_power
Earle
In the spec sheet you posted, see where it says CN3 on page 4 &5. This is an optional connector that may (or may not) be on the board.
Pins 3 & 4 are 5v and 5 & 6 are GND.
Note, however, unless you want to do some simple PCB soldering this isn’t the way to go. What I did was attach some header pins to the board, cut one end off a USB cable and attached it to the pins, then plugged it in the normal way into the RPi.
I realize this is an old thread - but the rpi3 does have an OpenGL driver that you can install via raspi-config under “Advanced”
It does have a GPU - “Broadcom Video Core”
-Earle
That is an early look at @Sean 's upcoming module MMM-calendarExtDays.
He is about to release an updated version under a new name - look on the forum here for MMM-calendarExtDays
-Earle
I’m terrible with the soldering iron but here is what I did
$ uptime
21:34:37 up 37 days, 58 min, 3 users, load average: 0.08, 0.13, 0.09
$ cat /etc/issue
Raspbian GNU/Linux 8 \n \l
$ uname -a
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
$ free -m
total used free shared buffers cached
Mem: 923 878 44 149 64 487
-/+ buffers/cache: 326 596
Swap: 99 99 0
$ df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 5863924 4248140 1294864 77% /
devtmpfs 468148 0 468148 0% /dev
tmpfs 472756 147656 325100 32% /dev/shm
tmpfs 472756 12364 460392 3% /run
tmpfs 5120 4 5116 1% /run/lock
tmpfs 472756 0 472756 0% /sys/fs/cgroup
/dev/mmcblk0p6 66528 21418 45110 33% /boot
tmpfs 94552 0 94552 0% /run/user/1000
tmpfs 94552 0 94552 0% /run/user/1001
/dev/mmcblk0p5 30701 463 27945 2% /media/elowe/SETTINGS
$ npm ls | grep -i magicmirror
magicmirror@2.1.3
$ npm ls | grep electron
├─┬ electron@1.7.5
│ ├─┬ electron-download@3.3.0
│ ├─┬ electron-chromedriver@1.6.0
│ │ ├── electron-download@3.3.0 deduped
│ │ │ └── electron-to-chromium@1.3.24
Modules:
Love it!
Installed it on the family info board, and the kids think its great.
Very nice. I have done something similar, although I prefer the Pi 3 Model A+. It’s slightly bigger than the zero 2w but is clocked faster (1.4 GHz vs 1) and has a full-size HDMI port. (they both use essentially the same SoC).
Note I have historically had problems with running out of memory running electron in the 512 MB limited memory space - but using dietPI has really help stability
I had considerable problems with running on a model A - but I found dietPI (https://dietpi.com/) to be a solid distro that works well even when using the default electron GUI front-end. (Previously OOM’d consistently)
Note, also I frequently have trouble with the calendar events appears as there seems to be some problem in the websocket communication layer (this bug: https://github.com/MagicMirrorOrg/MagicMirror/issues/3380)
I basically use MMM-RemoteControl to force a refresh in a daily cron job (curl http://localhost:8080/api/refresh) and this works. Why? No One knows
uname -m
armv7l
cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 12 (bookworm)"
free -h
total used free shared buff/cache available
Mem: 425Mi 316Mi 99Mi 8.1Mi 67Mi 108Mi
Swap: 732Mi 274Mi 457Mi
swapon -s
Filename Type Size Used Priority
/var/swap file 204796 0 -2
/dev/zram0 partition 544892 299760 15
zramctl
NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 lz4 532.1M 292.7M 98.2M 101.8M 4 [SWAP]
Jan 26 22:00:46 kid-mirror kernel: Out of memory: Killed process 23127 (WebKitWebProces) total-vm:1178000kB, anon-rss:184084kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:1044kB oom_score_adj:0
Although it’s not related to your problem - I have a lot of trouble getting MM to run on the 512MB Pi3 A+.
It freezes often - possibly it’s bad h/w or sd card although it all tests fine - but after several days of running and it ends up frozen and inaccessible. (ie can’t ssh to it, etc unless I restart it)
I tried using some of the lower memory options instead of using electron without much success. It runs for a little longer but eventually still dies. None of my Pi3 B models with the 4GB RAM have had similar problems - so I tend to think it is something related to RAM
Just to say that you may find the experience in running on the Pi 3 A+ to be “complicated”
Then use Ext3Agenda in the normal way vertical way.
In any event, it sounds like you don’t want the month view - and Ext3 does have just a week view - so maybe it’s as simple as just using week view for you.
Ext3Agenda supports calendars in the same way AFAIK as Ext3 - so I would expect if Ext3 works then Ext3Agenda also works
I would try using Ext3Agenda version in horizontal layout - it is by the same author and it sounds like the Horizontal layout might be what you want
https://github.com/MMRIZE/MMM-CalendarExt3Agenda
https://github.com/MMRIZE/MMM-CalendarExt3Agenda/wiki/Horizontal-layout
Something even stranger - if I immediately refresh the page it also works. Here I mean is:
npm run server
got to browser and bring up host:8080
calendar will say “Loading” for a very long time
(despite the events getting broadcast)
But if I :
npm run server
go to browser and bring up host:8080
calender says “Loading”
Refresh the page immediately
calendar says “Loading”
calendar will immediately show the events as soon as the events are broadcast
I added various log outputs to node_helper.js and calendar.js
node_helper is sending the socket notification for CALENDAR_EVENTS
this is not received by the front end code in calendar.js
I don’t know what happens to it, but I added logging to print out in calendar.js whenever the socketNotificationReceived handler is called and it doesn’t print.
(unless I refresh the page - at which point it does)
@sdetweil You mean fetchInterval: 5 * 60 * 1000?
the calendar module doesn’t have refreshinterval does it?
@sdetweil No errors in the console log
If I wait long enough where this seems anywhere between 15min to an hour or more, they do appear without a manual refresh.
maybe it’s a complexity issue - when I curl the calender link (it’s a google private ICS link) - the resulting file is 4.8MB - I imagine parsing that is somewhat time-consuming