@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.

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

@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
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.

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

Hello,

After configuring my MagicMirror frame, I realized there is no straightforward module to establish a good connection with Home Assistant using its available features. Please take a look at the module I have been working on recently:

https://github.com/ambarusa/MMM-HomeAssistant

This module makes the MagicMirror available as an MQTT device automatically in Home Assistant, with the browser/monitor as a light entity, modules as switch entities, and sensors connected via GPIO as sensor entities. Everything happens through MQTT Autodiscovery, without needing to touch any configuration files in Home Assistant. This is what I really missed in other solutions like MMM-MQTTBridge.

Once connected, the possibilities for automations are endless and can be managed in the same place as other home automations. Once the GPIO pins are read and published, toggling the screen based on motion can be triggered from the central server, and this information can be used for other triggers in the house. This is what MMM-PIR is lacking.

So please have a look, give feedbacks and have fun with it!!

For anyone interested in the future, an elegant solution that worked for me :

custom.css:

#remote-control-overlay {
  position: fixed;
  top: 0;
  left: 0;
  width: 100%;
  height: 100%;
}

Where the key is to add top: 0; left: 0; to the #remote-control-overlay. The rest is already in the module’s remote-control.css file.

Hello guys,

Sorry to revive this topic, but I have the same problem, and I am looking for the most elegant solution for it

A margin setting like this is kind of messing up my layout, and I really like how the default is looking like:

body {
    margin: 0px;
    position: absolute;
    height: 100%;
    width: 100%;
}

Thank you so much… :)

@sdetweil Ah I cannot believe. I just noticed that address: "::" was probably blocking the electron instance out… and everything is works as it should with address: "0.0.0.0"

@sdetweil Nothing seems to work… What about GPU memory? Some advise to increase it, however, others say that it’s not relevant from Raspi 4 (that is why it’s taken out from raspi-config)