@sdetweil , @BKeyport :
In the meantime a GeeekPi Ultra Thin ICE Tower Cooler is arrived and just installed.
Fan is bigger than Pi - looks weird.

After 20 minutes temperature is at 52°C nothing to hear.
Keep you posted…

Thanks for your feedback so far!

Ralf

Hi all,
work in progress :-)
I’ve played around, tried a lot and have found a couple of additional information, worth to show up on our mirror.
I’m really happy that one of the additions is an idea of my wife - this seems like a sign of “acceptance” …
Today in the morning she states “we are looking at earth… - The moon is missing”.

Voilá -

(screenshot, not photo)

Modified: strava (less disciplines).

Added:
fuel prices (MMM-Fuel) ,
moon (MMM-MoonPhase),
a countdown to event (MMM-EventHorizon) and a
custom background (MMM-Profilepicture).

Warmest regards and much fun with your own mirror,
Ralf

@crowimu
I‘m not using this module and I do not know which of GPIO‘s you are using for your rotary encoder -
In the module‘s description the author mentioned an eventually necessary modification for some of the PI‘s:

On some Raspberry Pis it is neccesary to put the following line to /boot/config.txt for the GPIO where "rotary press (SW)" is connected:

gpio=19=ip,pu

Background: Sets your GPIO 19 as input (ip) and pull up (pu) Change the entry according to the GPIO pin you use.

Have you double checked this?
Your error-listing shows „invalid argument , write“ in some context to GPIO…
May there is a topic for further investigation….

Good luck!
Regards,
Ralf

@BKeyport OK, thanks for your viewpoint!
Than I‘m on the right way - still works today :-)
Temperature was 45°C today in the morning - was at 56° everytime before …
So even passive cooling seems to be much better.

Nice rest of weekeend to all of you.
Ralf

@olex.s @sdetweil , dear all,

As you know for sure I‘m really a fan of MMM-Pir - for (my) good reasons.
For a friend of mine I‘ve build a second mirror and because he is heavily engaged in smarten his home :-) I‘ve considered to use alternatives to a PIR sensor - because they are definitely unsmart…
With this I‘ve seeked for an integration for his homee solution which is not really capable for MQTT and randomly found a really cool device which I would like to share with you, guys!
This is not a „motion“ sensor but a real „presence“ sensor (radar based, not infrared) which even is able to identify a silently sitting person!
In addition this genius thingy talks MQTT, delivers the „presence“ status in a JSON object and so it is absolutely easy to use it with magic mirror and the herein presented module MQTTScreenOnOff.

This sensor is pretty expensive and invented and build by a small startup here in Germany 🇩🇪 .
You can find this sensor here.
The webpage is in German but for some reason the default UI is in English :-)
From my perspective this is defnitely worth the money (this is the fourth radar sensor I‘ve bought but the first one which is in the near of „working“)

The mqttTopic transmitted is: „tele/senvolon/STATE“ and the mqttPayloadOccupancyField is „presence“.
(The middle part is configurable in the sensor‘s UI, I‘ve decided to use vendor‘s name).

I REALLY miss the nice animation and the dimming of MMM-Pir but I‘m definitely thinking about to use this sensor as well.
(Which would be a major effort because my Mirror has an exact slot for the PIR sensor which is round and this sensor is squared so I will have to do some rough wood-work. On the other hand I MAY place the sensor away from the mirror on the opposite wall or in an other place and hide the hole from PIR sensor ….)

Nice MQTT module - thanks for this idea!

Warmest regards,
Ralf

@plainbroke said

Don’t the authors usually leave their github live…

AFAIK yes, for this reason this seems like an unfriendly farewell to me .

Ralf

@kusselin said

One question: Do you have Netatmo installed and running at home as hardware and searching in MM…?

Nope, Netatmo not used by me …

Regards,
Ralf

@robertybob yes, screen rotation is still possible via CLI/terminal…

edit “/usr/share/dispsetup.sh”
eg:

sudo nano /usr/share/dispsetup.sh

there you will find an if clause at the beginning:

if ! raspi-config nonint is_pi || raspi-config nonint is_kms ; then
if xrandr --output HDMI-1 --primary --mode 2560x1440 --rate 59.951 --pos 0x0 --rotate left --dryrun>
xrandr --output HDMI-1 --primary --mode 2560x1440 --rate 59.951 --pos 0x0 --rotate left

the word after “rotate” defines the rotation :-)

NO rotation = “normal”, rest is obvious.
You must change this in both occurances.

In same statement you define the resolution for the screen, as well - after “mode”(given example 2560x1440)

HTH

Regards,
Ralf

@Cr4z33 Good afternoon,
I do not have the time to dig too deep into MMM-MQTTbridge …
But what I see checking your console logfile and compare this to your first posting:
You obviously had managed that the MQQT message arrives and is acknowledged.

.
The message you receive is:

{
    "Action": "Pulse",
    "Code": "Invite",
    "Data": {
        "CallID": "5",
        "IsEncryptedStream": false,
        "LocaleTime": "2025-04-30 10:40:43",
        "LockNum": 2,
        "RealUTC": 1746002443,
        "SupportPaas": false,
        "TCPPort": 37777,
        "UTC": 1746006043.0,
        "UserID": "101"
    },
    "Index": 0,
    "deviceType": "DHI-VTO3311Q-WP",
    "serialNumber": "****"
}

This is what you trying to capture in your mqttDisctionary.js
I’m not 100% sure if you

1. catch the right data-value : - is your jsonpath correct?
2. is “notiID” the right place for the module name you try to reach?

Just spontaneous thoughts about your issue - maybe misleading …

Regards,
Ralf

@robertybob said in Can´t rotate my display:

Mine looks a little different :(

OK, that’s bad…
(It’s a Pi5, right?).

The complete content of my dispsetup.sh is as follows:

#!/bin/sh
if ! raspi-config nonint is_pi || raspi-config nonint is_kms ; then
if xrandr --output HDMI-1 --primary --mode 2560x1440 --rate 59.951 --pos 0x0 --rotate left --dryrun>
xrandr --output HDMI-1 --primary --mode 2560x1440 --rate 59.951 --pos 0x0 --rotate left
fi
fi
if [ -e /usr/share/tssetup.sh ] ; then
. /usr/share/tssetup.sh
fi
if [ -e /usr/share/ovscsetup.sh ] ; then
. /usr/share/ovscsetup.sh
fi
exit 0

If I interpret your line correctly, you are using the Wayland-Window-Manager?
(wlandr => wayland … ???).
My box is a Pi4B, no wayland.
I’ve seen elsewhere that the Pi5 can be forced to use X11 again - than the above should work directly.
Otherwise you may give it a try to put your code into the dispsetup.sh?

Here I found the description of your commandlines above. Unfortunately there is no description how to get this pesistent…

In Addition I just found a hint in Raspberry-Forum
There a guy stated:

sudo nano .config/wayfire.ini

-> scrolled down and changed the output section as below:

[output:HDMI-A-1]
mode = 1920X1080@60000
position = 0,0
transform = 90

May this is the right way with wayland…

Regards,
Ralf