MagicMirror isn't publishing 'user_presence' on start up?

[sdetweil]

@fribse that’s because it’s not a change. typically the code doesn’t inspect the state, just sets it

so it doesn’t know it was off, and user_presence is different anyhow.

if u can use curl to post a message to the mq channel, then add a line to the startup script to send the user presence notification

[fribse]

@sdetweil Not sure how to do that to the MQTT channel, but can I send a notification when it’s started up? That would be picked up by the MQTT mirror addon?

[fribse]

@sdetweil Ok, I found the mosqitto_pub command, so I can publish with that to MQTT, which startup script is it, and can I make sure it’s done loading before running the command?

[sdetweil]

@fribse how do u start mm? pm2?

if so it runs the installers/mm.sh

pm2 info xx
where xx is the name or number of the pm2 entry shown by pm2 status
will show u the command used to start mm

if you used my install script and selected pm2,
then the script is
~/MagicMirror/installers/mm.sh

[fribse]

@sdetweil Ok, yes, I used your script.

So it just says

# This file is still here to keep PM2 working on older installations.
cd ~/MagicMirror
DISPLAY=:0 npm start

So I guess that just launches it, but it’s not actually ready at that point, thus the MMM-MQTTbridge is also not ready to receive the ‘hdmi off’ command.
Aren’t there some sort of notification that says ‘done, ready for running’ when it starts, I could put that notification in the MMM-MQTTbridge so that would also launch the ‘SCREENON’ back to MQTT.

[sdetweil]

@fribse there is no simple way…

do you get an error from trying to post the message?

if so, I would check and loop and sleep a little, then try again

[fribse]

@sdetweil Darned, that’s really sad, it seems logical to make a notification that says done setting up, and running. Oh well, always room for improvement in the code :-)

[sdetweil]

@fribse yes, inside… but u are outside (Oh I see, change the module)

from the doc
https://docs.magicmirror.builders/development/core-module-file.html#subclassable-module-methods

ALL_MODULES_STARTED

[fribse]

@sdetweil Ahaaaa, way cooler :-)

So I guess I should add this to the notiDictionary.js
I’m unsure of the payloadValue?

{
  notiId: "ALL_MODULES_STARTED",
  notiPayload: [
    {
      payloadValue: '1',
      notiMqttCmd: ["SCREENON"]
    }
  ]
}

[sdetweil]

@fribse sorry, now no idea, don’t know the module internals