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 ):
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
git clone --depth=1 https://github.com/HeikoGr/MMM-DevContainer.gitcd MMM-DevContainerOption 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.
Achtung, ich habe eine neue Version veröffentlicht und dabei die Konfigurations Variablen umbenannt - es muss die config.js angepasst werden.
Dafür habe ich jetzt aber auch eine Tabellenansicht implementiert:
@HeikoGr a new commit is on github with a fix in the handling of “days” - maybe this fixes your problem.
@Eli maybe your school doesn‘t show more than 2 days to the future (like our school).
Because the only differences in the debug mode are more log output and not filtering past lessons (there is also an undocumented option „debugLastDays“ - so i was able to develop during the holidays…). How many future days do you see in the untis app or on webuntis.com?
@OliWer i pushed a fix to github.
I was able to reproduce your error.
it should work now.
@kurkarte you can try to search your school at https://webuntis.com/ . On the next site the school name in the URL could work if you replace empty spa es with „+“ signs.
Note to myself: enhance error handling
I did a clean reinstall on my machine and it worked with your config (and our qr code).
Maybe the school doesn’t publish personal timetables?
Can you try to set useClassTimetable: true,
@Eli the module surely isn‘t running properly.
I think the module MMM-Remote-Control tries to run git to get the npm module untis (which is required by my module) and has no success.
But this is only a guess… could be totally wrong