also please don't cross post. I shall also change your title so it will describe your issue better since your not having issues with the sensor but the display
tomatoes6868
No it's HDMI with a separate power source
k9t33n
then you need a way to control that seperate power source
k9t33n
can it be powered via the pis usb?
tomatoes6868
yeah but when i plug in the usb for the touch functionality it wont work if i power by the pi. but it does turn the screen on and boot to dakboard
k9t33n
oh
k9t33n
then however you power it you need to be able to control that from the pi
k9t33n
maybe some switch plug with Bluetooth?
tomatoes6868
i was able to get it to power from the pi and touch works
k9t33n
great
k9t33n
<@&818389709134626826> how can we switch off a usb on the pi at will?
illegitimate_egg
It's tied to the 5v bus isn't it?
k9t33n
no clue
tomatoes6868
it would be switching off the hdmi on and off depending on motion its a argon case with the full size hdmi ports
You could also test kmsblank and the commands kmsprint and kmstest will show what displays that is connected
tomatoes6868
i plugged it into a rpi 3 using the same sd card and i still get the unable to open display error
sravdar
Hello people who discussed @here. On bookworm when using kms "vcgencmd display_power 0" does not work but with fkms it does. Is there any workarounds to make it work with kms?
Also what would be impact of changing from kms to fkms? I am using rpi with wayfire to display webpages in chromium and videos.