NSPManager
Screen Saver Brightness Not Persisted
At 8pm I set a panel screen saver brightness to 0%. This turns off the screensaver. At 7am i set it back to 50% so it works in daylight. However, if someone uses the panel after the 0 value setting has been activated, the panel reverts to the default (50%) brightness.
I use the number.<panelname>_screensaver_brightness entity to control this value in an automation.
Not sure if this is a bug or expected behaviour.
That sure seems like a bug though I can't replicate it. If I go into home assistant and set the brightness to 0% and then wake the display, when it goes back to the screensaver it's still at 0%. Are you running the beta or stable version?
Spoke too soon. Saw the screen invert but did not do proper testing. The ‘touch’ area of the display don’t seem to correlate to the images. The ‘scenes’ icon does not work and the room dropdown doesn’t open the entities page. Will do some more testing this week to try and provide some more info.
Spoke too soon. Saw the screen invert but did not do proper testing. The ‘touch’ area of the display don’t seem to correlate to the images. The ‘scenes’ icon does not work and the room dropdown doesn’t open the entities page. Will do some more testing this week to try and provide some more info.
Perhaps this was meant for your other issue?
It was indeed. Apologies.
Here is some more testing on this issue
MQTT events for the device once the automation has run, clearly setting screen brightness and screensaver brightness to 0.
Settings from the the panel settings page in NSPanelManager::
Panel is currently behaving as expected. Screen is "off" (barring a few fingerprints)
After tapping the screen to wake it up, however, after the screensaver timeout period it reverts to default brightness (60 per the settings page)
Version Information Version on panel web UI: Version 0.1.152 HA Add-On version: 1.0.4 HA 2025.7.2 HAOS - 15.2
Update: Tried with brightness_screensaver = 1 too in case 0 was an invalid value, but same issue.
Hmm, that is indeed a bug but it seems you are running stable given those version numbers and it is surprising no one else has reported this. I could not reproduce it on beta but beta is a total rewrite. We are in the finishing stages of beta before publishing it as stable. Given that, we won't do any bug fixes in stable.