I didn’t think i ran it with sudo but apparently i did. Thank you for your help!!

I did try the test first and it didn’t show errors. But, you got it working!

@Scruffy I actually never resolved my issue either. But, my system was very sluggish as well.

That got me fixed up!. Thanks!

For some reason, my mirror is not able to turn on thru MQTT. Below is most of the detail from the log file. MQTT explorer is showing that HomeAssistant is publishing via MQTT “true”. Do you have any suggestions?

[2026-05-22T21:32:28.750Z] PresenceControl: Received config: {“mode”:“MQTT”,“pirGPIO”:4,“mqttServer”:“mqtt://192.168.4.160:1883”,“mqttTopic”:“sensor/presence”,"mqttPayloadOccupancyF>
[2026-05-22T21:32:28.910Z] PresenceControl: [updateScreen] on=true, cmd=“wlopm --on HDMI-A-2”
[2026-05-22T21:32:29.211Z] PresenceControl: [updateScreen] SUCCESS: executed “wlopm --on HDMI-A-2”
[2026-05-22T21:32:29.357Z] PresenceControl: [updatePresence] pirPresence=false, touchPresence=false, presence=false, newPresence=false, locked=false
[2026-05-22T21:32:29.359Z] PresenceControl: Subscribed to MQTT topic: sensor/presence
[2026-05-22T21:33:02.189Z] PresenceControl: [startCounter] Counter expired: presence=false, pirPresence=false, calling updateScreen(false)
[2026-05-22T21:33:02.190Z] PresenceControl: [updateScreen] on=false, cmd=“wlopm --off HDMI-A-2”
[2026-05-22T21:40:24.572Z] PresenceControl: [updatePresence] pirPresence=false, touchPresence=false, presence=false, newPresence=false, locked=false
[2026-05-22T21:40:25.575Z] PresenceControl: [startCounter] Counter expired: presence=false, pirPresence=false, calling updateScreen(false)
[2026-05-22T21:40:25.576Z] PresenceControl: Counter expired, set presence to FALSE and stopped timer.

@Scruffy I actually never resolved my issue either. But, my system was very sluggish as well.

@sdetweil Unfortunately, it still doesn’t start after reboot. It does continue to work if i start it manually.

Log file
|MagicMir | [2991:0228/201716.146315:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
0|MagicMir | [2991:0228/201716.146344:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.
0|MagicMir | /home/twist/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
0|MagicMir | [3075:0228/201721.692197:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)

@sdetweil the file you are referring to is in the installers folder. Correct?

It does start the interface with your suggestions. Is it able to start it in reboot since it no longer does?

@sdetweil yes directly on it

@sdetweil thanks. It shows that the process started successfully but it doesn’t appear on the screen.

weird. Any suggestionon what to do?

@sdetweil

Yes it does:

if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc 
   # if WAYLAND_DISPLAYis set, use it, else set to -0
   export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-0}
   npm run start:wayland
else
   DISPLAY=:0 npm start
fi

nothing is returned