MMM-HomeAssistant

[sdetweil]

@adamambarus AWESOME… been looking for this myself…
I have done similar with a diff mirror platform…

I have one problem with mine, when the mqtt server goes down, the connection is not restarted as expected… and the devices in HA are marked as not available

[adamambarus]

@sdetweil Hm great idea! I will investigate what happens with my module in that case, and come up with a handling for it!

[sdetweil]

@adamambarus I have mqtt server in a compose stack with watchtower and it gets upgraded on version updates…

also that machine is on UPS that just recently died after 8 years during a 15 second power outage… so mqtt went away for a LONG time… (I was out of town)

way longer than its reconnect timeout.

I see client is 5.13.0 now, I am using 5.1.3 on this client (last PR on mqtt for this reconnect problem seems to be 5.5.6 SO… maybe
https://github.com/mqttjs/MQTT.js/issues/1727
)

[KristjanESPERANTO]

@adamambarus Nice! Don’t forget to add it to the module list: https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-party-modules :-)

[adamambarus]

@sdetweil
Hi, I just ran a few tests and the module can automatically reconnect if the server reappears. It is handled automatically in the mqtt lib, my part was to stop flooding the MM logs with mqtt error messages.
Give this module a try if you are interested, I would really appreciate other good findings.

[adamambarus]

@KristjanESPERANTO Thanks! I am interested in that, I just don’t know how to do that :D Never changed other repos other than mine ever.

[sdetweil]

@adamambarus you edit this wiki page to add your module entry
https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-Party-Modules#module-creators

[adamambarus]

@sdetweil Hahh, of course how could I not see that button…

[sdetweil]

@adamambarus great… now, suddenly (been running for near 2 years) MY mqtt server cannot be reached from outside the docker host… SO much fun…

[Snille]

Awsome! This changes a lot in my “config”, my Mirror(s) are tightly integrated with Home Assistant.
Thank you for this module!!

I’m currently running 3 different mirrors, but two of them are “mixed” with each other in HA, the third (first one) are separate :). I’ll have to do some more investigating. Have you tested with multiple mirrors against one “HA-MQTT”?

Again, thank you for this! :)

Update: I did some cleaning in the MQTT-queue (with MQTT Explorer) and now it all works. I got to have had my config(s) mixed at some point during my testing. So, now it’s all good. :)

[adamambarus]

@Snille Wow, I am so glad to hear it. I made a test with my real MagicMirror, and a dummy one running on a linux laptop. At this point I added a real uniqueID for the HA device config jsons.

@Snille said in MMM-HomeAssistant:

Update: I did some cleaning in the MQTT-queue (with MQTT Explorer) and now it all works. I got to have had my config(s) mixed at some point during my testing. So, now it’s all good. :)

Hmm, alright!! I will try to think of a handling in case two MM instances want to connect with the same device name. That is the only attribute left on the user.

[schlomm]

I’m just here to say “Thank you” - installed the module yesterday and after some struggling with my MQTT Backend all is working :)

[UncleRoger]

Just to be clear, this is meant to allow you to control the MM from HA, not display HA info on the MM, right?

[sdetweil]

@UncleRoger correct MMM-HomeAssistantDisplay
will display info from ha

[mirrorlover270]

Would you see a chance to include a “sensor” that shows whether an update for a module is available? Right now the sensor on updates can only “hide” the update message on the mirror.

With an update sensor, I could get a message on my phone and at least trigger the update remotely with the MMM-Remote module.

Thanks anyway for this great module.

[raymonvdm]

I found a display (touchscreen) to setup a family dashboard and i`m making babysteps to get it going again after a long time of trying out MagicMirror

I did get this module to work and most of the buttons in HomeAssistant work, but since i`m using a GigabyteBrix debian12 pc the screen off and on does not work.

This however is working to get the screen on/off

apt install vbetool

root@debian:~# sudo vbetool dpms off
root@debian:~# sudo vbetool dpms on

root@debian:~# cat /etc/sudoers.d/magicmirror
magicmirror ALL=(ALL) NOPASSWD: /usr/bin/vbetool

root@debian:~# 

So i changed the on off command to

/usr/bin/sudo /usr/bin/vbetool dpms off
/usr/bin/sudo /usr/bin/vbetool dpms on

But it stops working as soon as i start the MagicMirror using PM2 and i`m not sure why.

Are there any other options?

[Lateadapter]

I was directed from [MagicMirror Forum] Digest for 1/11/2026 to that discussion and I can show you some kind of alternative regarding Home Assistant controlled MagicMirror. It is using TouchKIO as a mirror client.
Recently I did upgrade my many years existing setup and I did summarize it here:
https://github.com/Lateadapter/TouchKIO-as-Kiosk-Application-for-MagicMirror

[sdetweil]

@raymonvdm can you show the log?

I always recommend testing with manual start after you make a module change

pm2 stop all
cd ~/MagicMirror
npm start 

if it comes up ok, ctrl-q, or alt-spacebar, c
then pm2 status
and pm2 start xxxx
where xxxx is the name or number on the row for your application

[raymonvdm]

@sdetweil

I found out that it stil asked for the user password when performing sudo. I had this statement in /etc/sudoers

magicmirror ALL=(ALL:ALL) ALL

And this in /etc/sudoers.d/magicmirror

magicmirror ALL=(ALL) NOPASSWD: /usr/bin/vbetool

For now i removed the line in /etc/sudoers