hi, i have the same problem, how did you solve it?
Hi, this takes the writing off my screen but the backlight stays on
Great. Worked for me too. Thanks so much for sharing!
not working on my Dell laptop as well
i am using old dell laptop running hassio, it says no directory found
So, I have the same issue. I’m running on an old lenovo convertable that uses eMMC.
However, you can, on boot edit grub (press e). This allows me to blank the screen but not power it down.
Appropriate hardware is tricky.
I want to go with this solution to programmatically turn off or dim my Laptop since recently there has been a massive advancement in using the laptop screen as a dashboard.
I’m running HAOS but whenever I try to run this automation via the call_service it responds with Event fired successfully but NOTHING happens. Trying from the Advanced SSH addon yields a similar result with an error:
tee: /sys/class/backlight/intel_backlight/brightness: Read-only file system
Plugging in a keyboard works, but that option kinda sucks. Any ideas as to why Home Assistant cannot run this as an automation? With the keyboard plugged in I’ve made sure to touch the file with a chmod, giving it maximum permissiveness.
UPDATE: I got it to work, it turns out call_service has been depreciated and replaced by perform action. Thank you, works like a charm!
Hi Blues. I did everything as you wrote but at the end of editing i was not able to save it. “w” was not working. The key simpli didnt work , but “q” did. Is it might be read only? Can you please help how to save the change?
THank you
Zsolt
Did this switch off the back light or did it just clear the screan? Did you check the power user before and after?
Running HAOS bare metal old Dell Latitude E5550, I had problems with consoluteblank=10 which didn’t turn off the screen and left a few random letters of gibberish on the screen. So if you do this, I recommend adding to the cmdline.txt file and putting in a value larger than 10, 60 works, 120 was my choice.
I also tried restoring using SSH, advanced unprotected mode SSH, neither gave me access to mounting the sda1 partition to revert, so I had to live boot Ubuntu, mount the partition and edit from there. Worked a treat, but rather annoying.
This is just a warning to people who choose a value too small, stick with 60 or higher and keep the screen cracked for cooling 