@SimoneMSR we don’t run on Android. So I’m not sure we are talking about the same thing

MagicMirror is a single page web server. The page is composed of live JavaScript code in multiple modules to dynamically render their little bits of the page at runtime

So you would download the empty MagicMirror project somewhere. Add modules, configure the modules. Test
And distribute that. Or make that the server the client devices connect to using the native device browser, which they would already have

@MarkV did you get this working

@BKeyport I just pushed some changes for the next release to autodetect the custom regions in index.html and use those for validating and using in config.js
(and npm run check:config)

@Dennys1 English for others

your module is very nice, but I would like to ask you if it is possible to integrate a function to load a list of TV channels in m3u/m3u8 format.
Thank you.

Hi again!

Sorry for replying on my own post, but here is the solution I was able to make with a little modification, so I though I would gather these into a new message.

To make it work with username / api key combo:

Open MagicMirror config.js and add a new line to the octomirror module config a new parameter called user: “username”, then save it. Open octomirror-module.js in the modules/octomirror-module directory, and modify this:
let user = “_api”, session = “”;
to this:
let user = this.config.user, session = “”; Save it, and restart the mirror. That should fix the connection issue :)

Hope it might help someone.
bigzolly

@Nneuland not very hard.

add a test to notificationReceived

if the topic is nextImage , then call this.updateDom…

Is there any good practice for catching the moment updateDom() finishing? Or the moment of contents that are created by getDom() are rendered on the screen?
I have to do some job after rendering, but hard to measure or guarantee when it finishes.

... this.updateDom(options) this.doSomethingWithRenderedDom() ... The module this itself is not the only module that can call .updateDom() .updateDom() is not promise-able or doesn’t have a callback function to notify rendering finished. .getDom() is promise-able, but not consumable by the module itself. in .getDom(), the contents are not rendered yet, so I cannot do certain job at that moment. The only way I can do is using MutationObserver, but that is not convenient.

What I need might be module.domUpdated(). or await module.updateDom() or module.updateDom(options, callback). or DOM_UPDATED notification.

Or… Is there any better way to achieve this?

@karsten13 don’t worry, I have a real job too ;)
I will just make a PR (draft),

After, we will see if we push it or not
Sincerely, for me, this PR will not really important, it is mainly to understand how it works
I will mention you in the PR to give me your opinion (that’s just what matters to me)

@vvrangler
Hi,

you could use my MMM-EmbedURL module for this purpose.
Simply set the embedElementType to img like in the following example:

{ module: "MMM-EmbedURL", position: "top_center", header: "Embed-URL", config: { embedElementType: "img", updateInterval: 10, attributes: [ "frameborder=0", ], embed: [ "http://SOME_SERVER/SOME_SVG.svg", ] }, },

You can change the updateInterval to your needs.

so you could install it on a Pi with no desktop version

should be possible, but don’t think you find a script for this.

MM (with electron) runs on Fedora CoreOS in VirtualBox with 2 docker images (1x MM, 1x xserver), so this should also work with raspian lite.

@asc11 It’s easy CSS to do, so, not needed to be a feature request. In my mirror, I have 3 side by side.

/* adjust modules to display side by side */ .MMM-FlipClock, .MMM-Worldclock, .MMM-Multimonth { display: inline-flex; }

@cweinhofer each instance client causes request to data providers (even thru node helpers). almost NO module shares data with other instances
(I made concerted efforts in my MyCovid19 module to do that… not easy) ( I think one of the third party climacell weather modules does this)

so same or different port doesn’t help here. same or different instance doesn’t help, same or different server.

all the same.

for the 4 or 5 of you that might want to do this, you can create scripts to merge common elements, use source repositories and other approaches to minimizing the work of config construction, without burdening the core support with out of scope function.

this is a composable information display panel with a single view.

as this is open source, you are welcome to take the repo and do what you suggest.

to have your idea considered more specifically, you should open an issue on the GitHub repo to engage the core team.

nothing said here will affect this kind of change

@kayakbabe set address:‘0.0.0.0’
and ipWhitelist:[]

then it works anywhere.

@Jan-0 one could change the code to do that.
it will not do that currently

@MMRIZE , yes, your getScripts function suggestion worked! Thanks!

FontAwesome is already at version 6. It would be nice if MagicMirror in the future considers a flexible version in case of future updates, where you can choose in config.js if you want “fas” (by default) of “fab”, for example 😁

Please read the whole post below
https://forum.magicmirror.builders/topic/16489/three-module-issues-from-a-new-user/

@sdetweil I totally get the difficulty in supporting people. I have been picking njk apart by examples already in the njk templates that I’ve found.

@karsten13 mmpn does install from the 3rd party list, but does not support module config

Assuming URL with PATH might be an almost general solution, but Sometimes, People install modules in weird ways like using Symlink. (That way could have some benefit, anyway, this is out of issues) In that case, assuming is somehow picky.

My purpose is to rewrite the Translator class to use in Module and node_helper together with one common class. (So that is the reason why pre-connection is needed.)To access translations in both layers, there could be many ways to achieve. However, if the exact URL could be obtained in the background layer, it would be easier and simpler and with the least dependency. (To work on browser and on nodejs layer together)

Of course, there could be many alternative approaches. I’m just curious if there could be a better way.

@sdetweil use my MMM-Config module
https://github.com/sdetweil/MMM-Config