@jtillinghast, you might want to consider MMM-MicrosoftToDo which allows you to display Microsoft ToDo lists.
Setup is a bit of a hassle but well documenten.
As it is Microsoft ToDo lists can be managed in mobile app and web interface as well.
@lif Thank you very much, I didn’t think of such a solution, even though I work a lot with Gemini. It generated a module, but I can’t test it until tomorrow!Thank you very much, I didn’t think of such a solution, even though I work a lot with Gemini. It generated a module, but I can’t test it until tomorrow!
If MMM-SelfieShot is giving you trouble, you might want to look at MMM-TelegramBot or MMM-OpenCV. Most of the older camera modules struggle with the newer Pi camera drivers (libcamera), but OpenCV is much more flexible. For a university project, using the OpenCV module might even give you some extra ‘tech’ points since it can handle face detection too!
@DarrenO-0 in the output of npm start
There will be a line
Broadcasting xxx events for calendar yyyy
Where yyyy is the full url configured in the calendar
That line will have a timestamp at the beginning of the line
That is the output of the calendar module fetcher and starts the delivery to the front end to display
If you use pm2 that content is captured for you
You could use grep to extract just those lines
cd ~/.pm2/logs
ls
Find the right filename.
Pm2_app name-out.log
grep Broadcasting fffff
Where fffff is the file name you selected
Note the file is added to each time MagicMirror is restarted unless you clear it first
pm2 flush
To clear
Before posting in a public place, make sure to mangle the url on each line so as not to expose your working cal url
@sdetweil
No error message, just black screen on some modules. I am still having some issues with modules just not showing up… Putting that space in, now I get webview and 2 of the iframe modules working. Nixie clock is fighting me for some reason. I just have not had any time to really dig into it the last week or so…
@sdetweil Thank you for the info. However, I finally successfully migrated to Trixie with desired Monitor Resolution and Rotation. And i am using Raspberry Pi 3B+ with an Acer 27 Inch monitor.
With Trixie being launched only three weeks back, there is almost no solutions avaiable. I will shortly share my process of how it was achieved.
Thanks
@carl22 I have not seen any physical connection, but what you seek should be relatively easy
The calendar and weather and clock modules broadcast their data to allow other modules to consume them
So your module receives these events (at the notificationReceived function) and needs to tell the motors to move
Your web side sends a message to the server side, using the sendSocketNotification function
And the server side (node_helper.js socketNotificationReceived) ). Launches your python script to do that
My PythonPrint launches a python script on some cycle and sends the scripts output back to the browser side
https://github.com/sdetweil/MMM-PythonPrint
See the doc here
https://docs.magicmirror.builders/module-development/core-module-file.html
In addition: It’s possible that the old recovery script was part of my problems - due to the above mentioned ping problem.
For this reason I’ve edited my earlier post and deleted the content of the script.
I’ve added an “edit note” instead.
Sorry for confusion and any inconvenience!
Regards,
Ralf
Also, some modules document their css styles,
Some you have to look for a CSS file in their files list
And some you have to use the developers window to discover them
There are no rules enforced here by MagicMirror
@sdetweil said in MagicMirror problem:
Let’s try this
Change your config.js
address:”0.0.0.0”,
ipWhitelist:[],
Then
npm run server
Instead of npm start
Then use another system, phone to connect to that pi
http://pi-address:8080 geometry dash scratch
Thanks for your suggestion. I got it.
Hello, I think you can use the useVLC in embedded mode
In recent forks of MMM-RTSPStream, VLC can be embedded into the browser view with an iframe or HTML5 video tag, which respects DOM positioning. Check the fork you’re using. If it’s still spawning standalone VLC, look for configuration like:
localPlayer: ‘ffmpeg’ // instead of ‘vlc’
Some forks added ffmpeg or jsmpeg options to push the stream into a element.