Read the statement by Michael Teeuw here.
MMM-HomeAssistant
-
@sdetweil Hm great idea! I will investigate what happens with my module in that case, and come up with a handling for it!
-
@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
) -
@adamambarus Nice! Don’t forget to add it to the module list: https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-party-modules :-)
-
@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. -
@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.
-
@adamambarus you edit this wiki page to add your module entry
https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-Party-Modules#module-creators -
@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.
