@sdetweil … thanks for the tip re alternate ssh clients. I will look at that.

I still need to work out the ipWhitelist thing … but it sounds like I can peek at my mm from any networked pc in the house. Does that include a mac?

Edit: Got ipwhitelist to work and both wife and I can see the mm from any location inside my network.

this is impressive … getting started is one thing, finding this forum is a second … the most impressive (to me) is the community help you got.

BTW … pictures would be good What size / type of screen did you use?

Debugging is pretty easy.

Turn on your browser console (ctrl-sht-j) and then put log statements in your code.

Log.info('ruff: shipment ’ + shipments.tag)

They will turn up in the log. Aftership was throwing an error when a shipment was pending, the latest history message was trying to display even though there was a check for history = null. I added a check for Pending and now pending displays.

The aftership code doesn’t like it when the aftership API returns ‘pending’ or ‘Tracking details will be available once carrier returns updates. Please check again later.’. It can’t seem to load the packages.

I can debug this … but I don’t know how to get output from the code. More googling to see if I can get this module to create a log file.

I have been playing with the AfterShip module and really liking this. The mm on my desktop screen reminds me of rainmeter … passive information display.

Further … I have been playing some more with this and added color coding for delivered and not delivered items. I also added a ‘keep delivered items in list’ cutoff so you can see things delivered today … or any time over the last week.

I might have to do some research about forking.

Weird … is started showing packages again today. There were some UPS packages that dropped off the ‘to be delivered’ list … maybe this code doesn’t like UPS?

I would also like it to show DELIVERED that was less than X days ago (ie show packages that were delivered today but don’t show them tomorrow).

Edit: Well - that was easy. There is a show_delivered boolean that … shows the delivered packages once I set it to 1.

I’ve installed samba file sharing on my pi and managed to connect via my win10 machine … so now I can do away with the complicated method I was using to update sh files.

I just added this to my mm and it worked … while Aftership only had a single package to be delivered. I subsequently added some more packages … and now it is just showing LOADING.

I will try to update this … but I am not sure where to start? Does anyone have an example of the info that the API returns?

google to the rescue … must remember to google the actual error message and not what you think the problem is.

I googled “rpi magic mirror cannot open display” and it displayed some posts about this very issue … one of them contained this suggestion …

Ok, there might be a problem with your electron installation.
Can you go into your MagicMirror folder and type “node serveronly”?

Then, go back to your browser window and type in “localhost:8080”

Jump over to the mm folder, mistype ‘note serveronly’ and then ‘node serveronly’ … and my mm is back

how to I make node serveronly permanent? Embed it in the mm.sh start script?

Edit: answer: that worked on reboot.

mm.sh now contains …

cd ./MagicMirror
DISPLAY=:0 npm start
node serveronly

Thx all - lots of interesting suggestions to play around with.

I detached the 7" screen from the RPI and now mm won’t start.

0|mm       | (electron:30477): Gtk-WARNING **: 06:02:18.928: cannot open display: :0
0|mm       | npm ERR! code ELIFECYCLE
0|mm       | npm ERR! errno 1
0|mm       | npm ERR! magicmirror@2.13.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
0|mm       | npm ERR! Exit status 1
0|mm       | npm ERR!
0|mm       | npm ERR! Failed at the magicmirror@2.13.0 start script.
0|mm       | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
0|mm       |
0|mm       | npm ERR! A complete log of this run can be found in:
0|mm       | npm ERR!     /home/pi/.npm/_logs/2020-10-24T10_02_18_961Z-debug.log

Is this something about having to start the magicmirror in server mode?