that’s great - i will look how i may use this in my module.
Thank you

Attention / Important

(for our school) Untis GmbH changed url and schoolname.
You may need to log in your (childrens) account(s) an edit the config.js according to the new values.

At least they didn’t switch off te old json-rpc api MMM-Webuntis is using

i found 2-3 ways for you to get rid of the header:

1.: you add “!important” to force the css rule

.MMM-MieleAtHome .module-header {
    display: none !important;
}

2. fork MMM-MieleAtHome and get rid of

	// you have to delete this function at MMM-MietAtHome.js line 92-95
	getHeader: function() {
		return "Miele@Home";
	},

MMM-HomeConnect is similar. But here you have a third option: take my fork: https://github.com/heikogr/MMM-HomeConnect2 (only thing: it has an different styling)

@BGH_H said in MMM-Photoprism:

mmm-imagesphotos

i try to answer this: mmm-imagesphotos can not access the pictures on a photoprism server (demo here: https://demo-de.photoprism.app/library/browse)

@thk thank you for you kind word. I was able to implement a new config option “maxGridLessons” which will cut-off everything below the configured lesson. A “… more” badge is placed if an actual lesson is hidden because of this cutoff.

Windows is working now! You need to install Linux (tested with default [according to WSL] Ubuntu and Debian) and Docker Desktop.

@karsten13 your docker container was/is a great source of inspiration and you are right: every developer needs an own setup. The more (good) alternatives exist - the easier it gets to start developing.

great, that was something i wanted to start my self for a long time - thank you.

I forked your module and added a few extras (mostly with AI, like you did :-D ):

• use of thumbnail api (for reduced file size)
• suspend if not visible (i use MMM-Carousel, and the pictures are not on the frontpage)
• preload and caching (but I’m not sure if it is working as intended…)

this should work, but MMM-MieleAtHome and therefore MMM-Homeconnect as a fork do override the header…

{
  module: “MMM-MieleAtHome”,
  header: "",
  position: “bottom_left”,
 [...]
},

start little ‘advertising’ … (this is what you get when you ask AI to promote your project…)

Stop juggling terminals and fighting file permissions. With MMM-DevContainer you can develop MagicMirror in VS Code using either Docker Compose or Dev Containers — your choice.

Why it’s better:

One workspace for everything: modules, config and css all in one place. No more multiple windows or scattered folders.
Works with Docker Compose and/or VS Code Dev Containers: pick the workflow that fits your setup.
No file-rights hassle: edit and save directly from VS Code without sudo/chmod pain (unlike editing inside a running MM Docker container - if you’ve ever tried that).
Reproducible, clean environment: consistent installs, easy onboarding, and less “it works on my machine.”
Great DX: built-in terminals, IntelliSense, debugging, and Git — all inside the container.
npm install runs automatically on first start, so you can get coding faster.
Get started: https://github.com/HeikoGr/MMM-DevContainer

Quick start

• Clone the repo:
  git clone --depth=1 https://github.com/HeikoGr/MMM-DevContainer.git
cd MMM-DevContainer
• Add your module:
  Create your module inside modules/YourModule (or add it as a Git submodule).
• Keep MagicMirror core, your modules, and config together in this single workspace.
• Choose your workflow from below:

Option A — Docker Compose
docker compose up --build
Open the app in your browser (e.g., http://localhost:8080)
Stop when done: docker compose down

Option B — VS Code Dev Container
Install VS Code + the “Dev Containers” extension.
Open the MMM-DevContainer folder in VS Code.
Reopen in Container when prompted (or use Command Palette: “Dev Containers: Reopen in Container”).

Notes:
At the moment it’s only testet on linux (or windows with ssh on linux…)
Dependencies: npm install runs automatically on first start (via the devcontainer/compose setup). If your module needs extra dependencies, you can still run npm install inside the container terminal.
All source folders are mounted into the container; edits happen from VS Code without permission issues.
Suggestions and feedback welcome!

Have ideas to improve the setup? Issues and PRs are very welcome.
Tell me what works well for you and what could be smoother.