@mykle1 I am also using your MMM-BMW-DS module

@mcnahum MMOS is good for what it does, but a lot of the instructions you will find here and other places won’t work as MM is running inside a docker container… so all the maintenance work will be different

for migrate…

I wrote a little backup/restore

which saves config.js, and custom.css and the links to the modules you have installed

and then restore reads that info and reinstalls modules to a new MM install (previously completed, maybe with the automated install script, see https://github.com/sdetweil/MagicMirror_scripts) …

my idea is that you would use git to hold the info from the backup (really small as just 2 files and links)
(so you are not backing up gigabytes for stuff)

and then clone it and restore from there

https://github.com/sdetweil/MagicMirror-backup-restore

the commands have help --help will display that

@earnestrichards openweathermap says their forecast is updated every 3 hours, so at 9pm they would be forecasting for tomorrow…

current weather is different than forecast

@cgillinger

see the

suspend() and resume() functions you can add to be notified when being hidden (suspend) and shown (resume)

see
https://www.raspberrypi.com/news/raspberry-pi-os-64-bit/

note the issues w 64 bit chromium in the text

@johans see this issue comment

https://github.com/MichMich/MagicMirror/issues/2779#issuecomment-1011124060

@Xsoldier2000 the symbols, if defined in the config.js and not in a customEvents list should have been broadcast to Ext3

Size, maybe you want to start from bottom bar

See the second link in my signature below for using the developers windows to discover and test css

Width and height are the two primary size items
And he has lots of styles to adjust cell size, text size…
Read his doc

in an attempt to limit spammers from registering and posting goo, we have enabled a higher level of reputation required to fill out the ‘About me’ and signature fields in the use profile.

edit: and the website and picture content as well
no more free advertising

sorry. I know this will be trouble for some

@spospordo yeh, the change was a year ago… but I understand…

thats why I post and pin resolutions to known problems at the top of the troubleshooting section.

starting with one of the newer electron builds, (and chrome, and mozilla) they have implemented a new ’ no autoplay’ policy.
they require a user to click on the web page somewhere to enable autoplay…

there is a workaround

edit mm/js/electron.js
and change the code like this

function createWindow() {
    app.commandLine.appendSwitch('autoplay-policy', 'no-user-gesture-required');  //< -------- added
    var electronOptionsDefaults = {

then restart MM… autoplay will work now

@SymmetriC what url did u provide?

if using the mm web server

http://localhost:8080/modules/MMM-Text/filename 

for reading from filename in the module folder

if some other file NOT using the mm web server

file:///full_path_to_filename

and of course if on some server someplace else

http{s}://server name/path?parms_if_any

@ZiggidyZ the pm2 error in remote control is a module packaging problem

it demands the library to be able to do the job, but didn’t install it (see package json does not list it as a dependency

do this
change to the module folder and do

npm install pm2

then restart mm and try again

@raymondjspigot i’d make a fork of the module
clone that
add a parameter to set the format differently
and submit that as a pull request back to the module github

others probably would like to change that format

@crisvdn there are really a list of issues here

most importantly, most modules are created by someone for their own use, and shared
but then they go on to other life things

maybe for a while they hang around and take issues and PRs.

but life goes on.

some modules haven’t been updated in 5-6 years. mm has been active for 10.

I would guess that 99% of the authors are not programmers, and have other day jobs. never experiencing the details , or life cycle.

as this is open source, there is no commitment to maintain a module.

we get waves of new authors maybe 5-6 a year.

without fork, there is no way to ‘fix’ an abandoned module.

now we are at the 'where do I find modules ’ problem. there is one voluntary list. others are trying to improve the usability of the list, but it’s still voluntary.

we keep up the core with issues and PRs and changelog and test cycles. but not any of the 3rd party modules.

I’m a moderator here, never a professional programmer. I do it all for for fun. I keep my stuff up to date. but I don’t list my modules in the 3rd party list.

I don’t use the Developer or Contributor tags on my ID cause I show my support thru my actions. I don’t need an outside label to differentiate myself… I’m no better than anyone else here.

@ahmed245275111 your node/npm level is below the required for this module

mm 2.26 requires node version 18 or above

if you used my mm install or upgrade scripts it would have handled that for you.

see
https://github.com/sdetweil/MagicMirror_scripts

I deleted the duplicate topic

the two parts of a module talk to each other thru socket notification events…

the node_helper can interact with the system ,but not the dom, and the module (js) interacts with the dom and not the system…

the two sides would use the sendSocketNotification(event_id, buffer) method…

each would have a method called socketNotificationReceived(event_id, buffer) that will be called when the event arrives…

the buffer can be any kind of data. formatted or not.

to open the socket the first time, the module.js MUST be the first side to sendSocketNotification().

typically the module sends the config info to the node_helper when its starts up.

this is another event notification, which is called notificationReceived(event, buffer, sender)
there are a a few builtin events, I use the ‘ALL_MODULES_STARTED’ event to send my module config to my helper and open the socket.
see the doc here for the additional specifics
https://github.com/MichMich/MagicMirror/tree/master/modules

the event id strings for socketnotification are completely up to you… the MM system does not send socket notifications. it DOES send notifications (notice no ‘socket’) to the notificationReceived() method

but summary

• create both files (per the doc)

• when module receives the ‘ALL_MODULES_STARTED’ event, send a socket notification from the module to the helper to open the communications channel

• when the node_helper gets new data, it sends a socket notification (will ONLY be to the module(js)) with the data

• the module(js) uses the data to update the dom

• if the module(js) decides when there should be new data, then the module sends a socket notification to the helper, and the helper responds with a socket notification with the new data (if any).

@crisvdn here is a link to the list work
https://forum.magicmirror.builders/topic/18092/automatic-checking-of-all-magicmirror-modules?_=1704465730999

i’ve just pinned it to the top of the Development section so it won’t get lost
(I couldn’t find it when I mentioned it the first time)

@james1787 fantastic! 2fer… fixes and like more

@justjim1220 others noted that you will also have to edit the index.html to add the regions and the main.js

var updateWrapperStates = function() {
var positions = [“top_bar”, “top_left”, “top_center”, “top_right”, “upper_third”, “middle_center”, “lower_third”, “bottom_left”, “bottom_center”, “bottom_right”, “bottom_bar”, “fullscreen_above”, “fullscreen_below”];

which lists all the known regions

hopefully this will help us all work on quicker responsiveness and shorter

get this
what did you do last

cycles…

but there is a side effect.,… the automated build process failed (on master, which itself hasn’t changed)… oops… and our banner shows the build failed…
on code and doc sites…

just to let you know, we know and are working on it.

conversation about the templates here