markwatttech / markwatttech-tutorials

A Collection of Code from Various MarkWattTech Videos

MarkWattTech-Tutorials

A Collection of Code from Various MarkWattTech Videos

markwatttech-tutorials's Issues

A DIY Home Assistant Kiosk - Missed step

Well made tutorial, except I noted one additional command that is needed between Steps 1 & 2.

In the video you execute 'sudo raspi-config', changing the display settings and auto-login. This step not is included in the written tutorial.

Otherwise, super incredible project work!! TY for all of your effort!!

Auto Dimming

Great script, still missing an auto dimming function, or the screen remain to max brightness all the time.

Aspect Ratio for HA UI seems to be 4:3

When Chromium fires up, the tab I have loading for HA shows up in what appears to be a 4:3 box in the middle of a very wide-screen monitor, which should be displaying Chromium full screen. Most of the monitor appears to not be used. Any ideas?

Rotate Screen?

All is working great, except using the official 7inch screen, it's upside down. Everything I find says to add lcd_rotate=2 to /boot/firmware/config.txt, but this is not solving the issue.

RPi3 with Ethernet or WIFI connection doesn't seem to update the UI

I'm not sure what's going on, but after following all of the tutorial for the kiosk on my RPi3b, when it boots, it loads the UI as expected, but the UI never updates states of entities that change...

..example...a markdown card that shows the time, or a clock card, or any sensors, or the calendar. None of them update without a full refresh of Chromium. Is that a Pi3 limitation or a bug?

RPi5 Fails to run xstart without this modification

After following this guide to a tee, I attempted a reboot and was met with a failure to start X.org...the error looked like this:

Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices

I dug through some forums and found that the following solution worked.

Login to the Pi and create a file called 99-vc4.conf in the path /etc/X11/xorg.conf.d/

Add this to the file:

Section "OutputClass"
  Identifier "vc4"
  MatchDriver "vc4"
  Driver "modesetting"
  Option "PrimaryGPU" "true"
EndSection

Reboot. Home Assistant will fire right up. I also noticed that you'll need to enable the cursor the first time in order to set the username and password of the login for the Home Assistant UI.

PSA: 1. Double-byte Characters Display Issue, and 2. Don't pick "root" as the username during initial setup

This 'issue' serves as additional notes for things to do / avoid:

1. If your home assistant interface has any double byte and/or UTF-8 characters, they will not be displayed properly as is. To solve this problem, issue the following command either through the console or through ssh:

sudo apt install fonts-noto

2. When you first install the Pi OS Lite environment and it asks you for a username to use, do not pick 'root' as your username. Otherwise you will run into problems with ssh login (resolvable but requires extra work), and the openbox windows manager (no idea how this can be resolved).

Auto login after reboot

I have setting everything as you and it's perfect. I have added by ssh and browser_mod 2.0 the control about the screen for power on or off the screen only if ther is a person in the room.

the only problem is when i reboot or plug the power supply it need the auth fo home assistant and i 'have already checked in login boot for stay connected, but it doesn't work.

have you any ideas?

Is it set up for Home Assistant, or Home Assistant set up?

Hi @MarkWattTech

I have followed up the instruction and then the videos. And after some time, I found out you are pointing out the kiosk to another IP rather than the rapsis. So is it the setup of Home Assistant or remote screen i.e. setup for Home Assistant?

After each reboot, I get to a site that can't be reached page. Did I miss something or this is actually not the setup of Home Assistant as your video says?

Thx,
Martin

Setup commands does not seem to work right:

Command 4: # Remove exit errors from the config files that could trigger a warning
pi@HA-Display1:~ $ sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
sed: can't read /home/pi/.config/chromium/Local State: No such file or directory
pi@HA-Display1:~ $ sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences
sed: can't read /home/pi/.config/chromium/Default/Preferences: No such file or directory
pi@HA-Display1:~ $ chromium-browser --noerrdialogs --disable-infobars --enable-features=OverlayScrollbar --kiosk $KIOSK_URL --check-for-update-interval=31536000
dpkg-query: no packages found matching bluealsa
[4817:4817:0527/130441.860859:ERROR:ozone_platform_x11.cc(239)] Missing X server or $DISPLAY
[4817:4817:0527/130441.860983:ERROR:env.cc(255)] The platform failed to initialize. Exiting.
pi@HA-Display1:~ $ sudo apt install bluealsa
_Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package bluealsa is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'bluealsa' has no installation candidate_

This a brand new installation of Raspberry pi OS Lite 05-03-2023

Please advise.
Thanks