@Scruffy thanks.
Read the statement by Michael Teeuw here.
Posts
-
RE: Failed to Connect to Wayland Display
@Scruffy awesome!!! Thanks for the feedback!
How did you migrate your config ?
Just interested in how people do things -
RE: Default weather module not displaying forecast
@DarrenO-0 get the new apikey, requires a credit card
Remove apiVersion, apiBase, weatherEndpoint,
Let those defaultRemove location
Add lat, lon -
RE: OpenWeather loaded but info is empty since update
@SdR ok. The upgrade script is mine
We meant the system-info section of the MagicMirror startup messages.
Runstart.sh is mine for when electron is not found
Can you
git diff package.jsonAnd
ls node_modules/electron -
RE: Failed to Connect to Wayland Display
@atwist the latest PI OS is larger than the previous versions…
leading to more swapping. This can affect performance because of the speed of the SD card.
free -m
will tell you how much memory and swap space you are using.
-
RE: Failed to Connect to Wayland Display
@Scruffy use my backup/restore scripts to save and restore your MagicMirror config and modules list
https://github.com/sdetweil/MagicMirror-backup-restore
Backup, copy off backup folder, tiny sizeInstall new MagicMirror and copy back folder and restore
-
RE: OpenWeatherMapForecast stopped working
@VPeter custom.css should only be in the config folder on version. 2.35
-
RE: OpenWeatherMapForecast stopped working
@MrPringless thx. Was interested in HOW you upgraded MagicMirror
git pull , aka manual
Or
My upgrade script?Trying to find the cause of the lost
Custom.css -
RE: OpenWeatherMapForecast stopped working
@MrPringless how did you update?
custom.css should have been moved to the config folder -
RE: Too many API calls in default weather module after update
@Perilax I’d still wait, and switch to master before next git pull, after July 1
-
RE: OpenWeatherMapForecast stopped working
@VPeter looks like the openmeteo server is having trouble
-
RE: Failed to Connect to Wayland Display
@Scruffy ok, try
npm run start:wayland
-
RE: Failed to Connect to Wayland Display
@Scruffy
Can you open a terminal window and run this command stringps -ef | grep -v grep | grep -i -e xway -e labwc
Then do
pm2 stop all cd MagicMirror npm run start:x11Does MagicMirror start now?
-
RE: Reverting to previous MM Release
@jca2112 from the log,
saved translations/en.json
make sure you check on this change, as it was stashed but not re-applied…
-
RE: Reverting to previous MM Release
@jca2112 ok edit the mm.sh
and changenpm startto
npm run start:x11I know why… I fixed the script on saturday, but didn’t catch that on my mac I was on a different branch, so the master branch didn’t get updated til about 9pm central last night.
I drove all day yesterday, and fixed it again on master… -
RE: Off the shelf smart mirrors
@magicbeing ok, I missed ‘smart’. never mind
I have not seen anyone report that they reverse engineered getting MM running on some other ‘smart mirror’ platform
-
RE: Reverting to previous MM Release
@jca2112 when did you run it? today?
can you look at ~/MagicMirror/installers/mm.sh
and see if
npm run start:x11is present on line 9
also, can you do
pm2 stop all cd ~/MagicMirrorand try either
npm startor
npm run start:x11is this really a dietpi? what OS version is running
lsb_release -a
also, can you send me ~/MagicMirror/installers/upgrade.log
same userid at gmail