Read the statement by Michael Teeuw here.
MMM-HomeAssistant
-
@sdetweil Hahh, of course how could I not see that button…
-
@adamambarus great… now, suddenly (been running for near 2 years) MY mqtt server cannot be reached from outside the docker host… SO much fun…
-
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. :)
-
@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.
-
I’m just here to say “Thank you” - installed the module yesterday and after some struggling with my MQTT Backend all is working :)
