@BKeyport
You can see the browser-side log in the backend (terminal or log file) without ‘npm run start:dev’ or dev-console of chromium.
Frankly said, I’m a bit tired with always saying “open your dev-console and let’s see whether there be suspicious errors,… no, that is element tab, console tab is another, you can see those tabs in upper right side,… first you should have stopped the pm before,…” :D

MMM-DropboxPictures

MagicMirror module for presenting Pictures from Dropbox (Successor of MMM-DropboxWallpaper)

This module is a direct successor of previous MMM-DropboxWallpaper. I need to rebuild new one, and now it will be hosted by me again.

New Updates

3.0.0 (2023-11-09)

• FULLY REBUILT FROM SCRATCH You need to reinstall and reconfigure.
• Using recent Dropbox V2 API (SDK ^10.34)
• New OAUTH authentification
• Dynamic configuration on the fly(by notification).
• auto-rotation feature is deprecated.
• Remove 3rd-party dependencies as many as possible.

DEMO

Click To Play

https://github.com/MMRIZE/MMM-DropboxPictures

@birdabirda
A1:
Yes, you can. but pay heed to these;

• Be careful when your modules(instances) access the resource(e.g. HTML Element, sounds, sensors,…_ The competes for the same resources would make trouble.
• You need to manage the communications with node_helper from your instances. Instances will share the node_helper at same time, so your socketNotfication or resources of node_helper might have to be controlled by the session per instance.

A2:
Right. 1:M messaging channel tricks might be needed.

A3:
Your module object itself. it has many methods and members. It would be created by MM framework with the definition from your code. Then it would play its role in the MM framework.

A4:
All variables in the `Module.register(“YOURMODULE”,{ … }) will be scoped. They will not be shared unless you refer or link them to global/window scope.

A5:
You might need instance id as payload member on using socketNotification to catch which instance sends this socketNotification to node_helper. Vice versa, instance id might be also needed when node_helper sends socketNotification, to explicit which instance should be aware. Between module and node_helper unlike among modules, only simple basic data type would be transferrable, so you cannot use callback or ‘complex’ class object to make the communication easy.

I recommend not updating MM or modules unless they work. Just leave them. Update them only when you find some issue or need a new feature.

@sdetweil
I prefer bash. For similar experience with real -NIX/MacOS.

@richmp95
MM2.24 changed some codes then showing somewhat annoying “error” message. Not related with real “error”, just ignore it.

MMM-AlertExt

Alternative alert module for MagicMirror

Demo

Click to Youtube

Why?

• I need a more decorated alert feature than the current default alert module.
• Not only SHOW_ALERT, I want to see more various notifications and messages on the screen. (e.g. Log.log(), UnhandledExceptionError, CALENDAR_UPDATED notifications…)
• I made this module for a kind of shared programmable output-presenter of some modules.

https://github.com/MMRIZE/MMM-AlertExt

@birdabirda
ADD to A5.

However, there are some tricks that can be used between node_helper and your instance to make dedicated communication.

• HTTP connection : your node_helper can serve its own web server that can provide URL endpoints for request/response methods. Your front-end module instance could access the dedicated URL.
• websocket or similar technics.

There are several TTS modules, so output would not be a big issue.(And text-only-displaying would not be the issue at all.)

The real issue might be how to ask/input.
One idea is using telegramBot. Hmmm… interesting.

@Egnos
See how usage looks like.
https://youtu.be/BcpZvkcrfHU