Hello I have been using th cmdSwitcht2 plugin for the past 3 years. Last weekend I updated homebridge for the (to me) new UI-X and MM and Raspberry Pi OS… I thought it’d take me an hour or so.

I can’t get the on-command to work. I tried different commands like 'vcgencmd display_power 1* and the one that is suggested here. vcgencmd display_power 1 does not work. /opt/vc/bin/tvservice -p; sudo /bin/chvt 6; sudo /bin/chvt 7 works from user pi, but homebridge runs from a different user also called homebridge.

When turning the switch on, it logs the following: "Failed to turn on Spiegelmonitor

[24.9.2021, 09:59:26] [cmdSwitch2] sudo: Kein TTY vorhanden und kein »askpass«-Programm angegeben

When running tvservice --preferred && sudo chvt 6 && sudo chvt 7 from the console in Homebridge UI X, it says

chvt: ioctl VT_ACTIVATE: Die Operation ist nicht erlaubt

I tried to give homebridge the same rights in /etc/sudoers and checked /dev/fb0 rights but I don’t fully understand everything I did there. Has anyone had the same issue before?

Hello

the idea of the telegram bot is great. I got another idea when I built my own mirror about 1.5 years ago and I still think pretty often about it.

Wouldn’t it be great to enable everyone living in the flat texting to the mirror? Things like “Please call me when you got home” (some people don’t check their phones ) or reminders like “Don’t forget to take your lunch box” or in case there’s a party in the flat being able to change the compliment text live… there are so many use cases. Maybe even keep older messages for a certain time and display the last three of them, and being able to remove them using telegram again.

Thanks for all the work you all put into this project!!

Jan

I got the same issue. But there are other errors as well since I installed PublicTransportHafas.

Is there any clue why this happens?

Best,

Jan

Hallo

I know it’s not how it’s supposed to be but I use a Pi Zero running Stretch lite. I start the Mm using „node /serveronly“ in a .sh script and launch chromium afterwards.

Typing in these commands works perfectly fine. Everything takes some time to boot, but then, it just works.

To start it after bootup, I use Pm2. It takes some time but it works. The problem is: the Pi‘s CPU is at 100 % all the time since node /serveronly runs 4 times and each needs between 15 and 20 %.

How can I fix that? Any idea?

Hello:)

I run it on a Pi ZeroW and I know that’s not the common way. I use PM2 since I could not find any other working solution for Jessie or Stretch. Though it starts MM and chromium and everything looks well, the CPU is at 100 % all the time. When checking the active processes, the “node server only” is listed four times and chromium twice. Each node instance eats up to 20 % of CPU time.

Any idea how to stop that?

Thank you @NoNameRo !! It works now on Stretch. I can’t use localhost:8080 but xxx.xxx.xxx.xxx:8080 works fine.

Since initd is replaced by systemd, how do I run a script at boot up? For the last couple of days, I’ve been using a solution using pm2, but it seems to run the “node serveronly/” process multiple times so that my pi’s cpu has been at 100 % all the time.

Where do I have to place the script with
cd ~/MagicMirror
node serveronly &
sleep 45
sudo xinit /home/pi/chromium_start.sh
and how do I activate it for boot up?

@bbdv did you use Jessie or Stretch for that?

Hello since my Zero’s USB port is broken, I have to run everything from ssh and scripts.

I experienced the same as @Hawking: when starting midori, the screen would either turn black or white. I installed chromium and replaced the line “midori -e Fullscreen -a http://localhost:8080” by “chromium-browser --incognito --kiosk http://localhost:8080”. Chromium only shows a line at the top of the screen saying it can’t be run as sudo.

Any idea on how to fix this? Or how to get midori to work?

Thanks in advance