There isn’t a separate “always on top” option, but Neko should be configured with:
position: "fullscreen_above",
If that’s already set, the calendar may have CSS that puts it above Neko. Which calendar module are you using, and do you have any custom CSS for it? That will help me suggest the right adjustment.
I did something similar with LEDs. I chose to add a separate WLED controller instead of trying to control the LEDs directly from the Pi. The Pi just tells WLED what state or effect it wants, and the WLED board handles the actual timing and LED control. It keeps the responsibilities separate and avoids adding more real-time work to the Pi.
@plainbroke I used this module for a while https://github.com/shbatm/MMM-RTSPStream I then realized I only really needed timestamp images.
I use a Reolink doorbell camera now, but when I did use a Wyze camera I had to find a "DFANG " firmware.
@plainbroke Depending on the camera you might have to update or use a different firmware that supports RTSP for live streams.
Do you use Home Assistant now? Or are you looking to display feed or image directly on your mirror?
@plainbroke Sure. Most modules can be run at the same time with different configs. I run the weather module with two configs at once.
Don’t expect them to chase each other. They will be independent. I would start them in to different locations, to help prevent them from overlapping.
{
module: "MMM-Neko",
position: "fullscreen_above",
config: {
character: "cat",
startPosition: { x: 0.3, y: 0.7 }
}
},
{
module: "MMM-Neko",
position: "fullscreen_above",
config: {
character: "dog",
startPosition: { x: 0.7, y: 0.7 }
}
},
@KristjanESPERANTO Only so many hours in the day. :)
Years ago, I had Neko running on my Macintosh SE. Now it lives on my MagicMirror.
Neko wanders around, pauses to scratch, and takes naps. It works without a mouse or touchscreen, but you can optionally have it walk toward a touch target.
A few features:
Basic configuration:
{
module: "MMM-Neko",
position: "fullscreen_above",
config: {
mode: "wander",
scale: 2
}
}
Code, installation instructions, and configuration options:
https://github.com/bwente/MMM-Neko
Feedback and reports from other setups would be appreciated!
I replaced the default clock with a Literary Clock.
@rmonkey I wonder what the percentage is? I using MM to power by desktop internet appliance. My next upgrade will be a new enclosure.
@kristjanesperanto I got my first real alert from MMM-PublicTransportHub
Toast Alert
Message Center
The toast immediately got my attention, but if I hadn’t been standing in front of the mirror at that moment, I would have missed it. That’s one of the reasons I like using MessageCenter, the alert remains available instead of disappearing completely.
Thanks again for adding support.
I am sharing a new MagicMirror² module called MMM-WorldClockMap.
I originally built it for my own mirror and my particular needs. I have contacts in places such as Stockholm and Tokyo, and I wanted an easy way to see when people might be awake and around without calculating time differences.
The module includes:
I optimized the presentation for my own mirror, but tried to make the layouts flexible enough for an ordinary MagicMirror installation as well. I hope someone else finds it useful.
Repository, screenshots, installation instructions, and configuration options:
https://github.com/bwente/MMM-WorldClockMap
Feedback and testing on different mirror sizes and orientations are welcome.
@sdetweil Thanks! I tried using the editor in MMM-Remote-Control years ago and broke it, so I just used nano since.
The settings are now grouped into sections. Choices such as display, urgency, and retention are dropdowns.
Thanks for pointing me toward the custom layout, it makes a fairly large configuration much more approachable.
One unrelated thing I noticed while testing, my config did not have an explicit language setting because it was using the normal English default. After saving through MMM-Config, the language changed to Afrikaans, which appears to be the first item in the dropdown.
A quick MMM-MessageCenter update: version 0.5.0 is now available.
The big change is that MessageCenter can now collect SHOW_ALERT and SHOW_NOTIFICATION events from other MagicMirror modules automatically. Module authors generally shouldn’t need to add MessageCenter-specific support.
For richer integrations, there is also a standard message API with stable IDs, urgency, expiration, updates, and active-message synchronization. Enhanced integrations are now handled through small, independent adapters; the current examples include the standard Weather module, MMM-Remote-Control, and MMM-PublicTransportHub.
A special thanks to Kristjan ESPERANTO for adding service-alert notifications to MMM-PublicTransportHub and helping work through the integration.
I opened a feature request for MMM-PublicTransportHub to optionally broadcast PTH_SERVICE_ALERT notifications.
For example, a delayed or cancelled departure could appear as an alert.
@Rags I might try that out. But use a Fully Kiosk Browser on an Android tablet for the display.
I could probably use the camera for motion detection.
I’ve been working on MMM-MessageCenter, a module that gives notifications from different sources one consistent place on the mirror.
The idea came from a pretty simple problem: a notification appears, disappears, and nobody knows whether anyone actually saw it. Different modules and services also handle alerts differently, so important information can easily get lost.
MessageCenter adds a small notification history with clear unread, viewed, acknowledged, dismissed, and expired states.
Everything:
It intentionally doesn’t collect every internal MagicMirror event. Modules either use the MessageCenter API or an explicitly enabled adapter, which keeps refresh, navigation, and module-control traffic out of the inbox.
A dishwasher notification can briefly appear as an alert and then remain in history until someone views it.
A doorbell message can include a camera snapshot captured when the event happened, so the image doesn’t change before somebody checks it.
The standard MagicMirror Weather module can add a “Rain approaching” message without requiring a separate weather service.
A local monitoring script can report low disk space, high temperature, network trouble, or another condition that should be visible on the mirror.
MessageCenter can be used as:
It can show temporary alerts, retain message history, expire old messages, update existing messages by ID, and publish attention events for other integrations. It only says that something needs attention, leaving other modules and integrations free to decide what that means.
The module now has a line mode for side regions. It uses a lightweight, transparent layout and can show just the title and time.
Other recent improvements:
Configuration, payload examples, and documentation:
@Niggich looks like trigger.payload_json.remainingSeconds is empty or double quoted. Can you view just the payload and see?
BTW MMM-WeatherHero is a great module for this. It looks right at home.
My Echo know I want to start a Timer but it’s asking for how long.
Great, now that you’ve confirmed MQTT is working, the next step is to add the Home Assistant automation.
alias: MagicMirror kitchen timer started
triggers:
- trigger: mqtt
topic: magicmirror/kitchen-timer/started
actions:
- action: media_player.play_media
target:
entity_id: media_player.kitchen_echo
data:
media_content_type: custom
media_content_id: >-
set a timer for
{{ trigger.payload_json.remainingSeconds | int }}
seconds
I think that will work. I don’t know if it needs to be escaped or not.