Screen Brightness only 30%

RolandFran · July 2, 2023, 10:00am

Hi

I want to control the screen brightness from a tablet.
The following service is working, but only to about 30% of the maximum screen brightness.

service: notify.mobile_app_wkrr
data:
  message: command_screen_brightness_level
  data: 
    command: 255

Are there any restrictions, that I have to turn off, to reach maximum brightness?

RolandFran · July 2, 2023, 10:56am

Same result with Fully Kiosk
If I set the brightness on the mobile phone, I see 803% on the light entity

I couldnt find any workaround!

RolandFran · July 2, 2023, 11:20am

In Fully Kiosk Browser in “Device Management/Screen Brightness”, I can set value 2047 to get 100%.
How can I send this value via HA service - max value there is 255

dshokouhi · July 3, 2023, 3:05pm

Make sure you don’t have automatic brightness enabled.

RolandFran · July 3, 2023, 4:45pm

I tried both automatic brightness enabled and disabled.
After changing the brightness to 255 via HA, the result is the same (~30% brightness on the device)

endurance71 · September 22, 2024, 7:07pm

Hello, I have the same issue as you. Were you able to solve this problem?

RolandFran · September 25, 2024, 3:20pm

I dont use Fully Kiosk anymore. I use a http_request node in NodeRed, to send Screen on/off and dim commands to Tasker.
Would be great to see this functionality in the Companion App too.

dshokouhi · September 25, 2024, 5:07pm

we have everything but screen off

also your device may have something liek adaptive brightness enabled that can also impact this number IIRC

endurance71 · September 26, 2024, 1:10pm

I just tested with automatic brightness both enabled and disabled, and the result is that it’s not possible to set it above 255, which corresponds to 30% of the actual brightness.

dshokouhi · September 26, 2024, 2:11pm

automatic brightness is not the same thing as adaptive brightness. Double check which ones you set. Also you may need to use a notification command to turn off automatic brightness if the sensor state does not correspond to the UI. On a pixel device we have an adaptive brightness toggle but the automatic brightness command and sensor reflect different values.

https://companion.home-assistant.io/docs/core/sensors#screen-brightness-sensor

see the attribute mentioned

https://companion.home-assistant.io/docs/notifications/notification-commands#auto-screen-brightness

that should correspond to this command ,but not may not reflect the UI state. Both of these can cause weirdness to the value.

RolandFran · September 26, 2024, 6:34pm

On a Redmi 9A there is no adaptive brightness but Sunlight-Mode which is probably the same.
automatic brightness and Sunlight-Mode is disabled

dshokouhi · September 26, 2024, 6:45pm

interesting your sensor state for screen brightness is 2016 ? the docs state it can only be 0 to 255

https://developer.android.com/reference/android/provider/Settings.System#SCREEN_BRIGHTNESS

The screen backlight brightness between 0 and 255.

github.com

home-assistant/android/blob/282ffc50d69d205197c7f1c52cf73f24c7fbf2fe/common/src/main/java/io/homeassistant/companion/android/common/sensors/DisplaySensorManager.kt#L58


      
          private fun updateScreenBrightness(context: Context) {

              if (!isEnabled(context, screenBrightness)) {

                  return

              }

          

              var brightness = 0

              var auto = false

          

              try {

                  brightness =

                      Settings.System.getInt(context.contentResolver, Settings.System.SCREEN_BRIGHTNESS)

                  auto = Settings.System.getInt(

                      context.contentResolver,

                      Settings.System.SCREEN_BRIGHTNESS_MODE

                  ) == Settings.System.SCREEN_BRIGHTNESS_MODE_AUTOMATIC

              } catch (e: Exception) {

                  Log.e(TAG, "Unable to get screen brightness settings", e)

              }

          

              val icon = if (auto) "mdi:brightness-auto" else screenBrightness.statelessIcon

              onSensorUpdated(

github.com

home-assistant/android/blob/282ffc50d69d205197c7f1c52cf73f24c7fbf2fe/app/src/main/java/io/homeassistant/companion/android/notifications/MessagingManager.kt#L1887


      
          val command = data[NotificationData.COMMAND]
          val contentResolver = context.contentResolver
          val success = Settings.System.putInt(
              contentResolver,
              when (data[NotificationData.MESSAGE].toString()) {
                  COMMAND_SCREEN_BRIGHTNESS_LEVEL -> Settings.System.SCREEN_BRIGHTNESS
                  COMMAND_AUTO_SCREEN_BRIGHTNESS -> Settings.System.SCREEN_BRIGHTNESS_MODE
                  else -> Settings.System.SCREEN_OFF_TIMEOUT
              },
              when (data[NotificationData.MESSAGE].toString()) {
                  COMMAND_SCREEN_BRIGHTNESS_LEVEL -> command!!.toInt().coerceIn(0, 255)
                  COMMAND_AUTO_SCREEN_BRIGHTNESS -> {
                      if (command == DeviceCommandData.TURN_ON) {
                          Settings.System.SCREEN_BRIGHTNESS_MODE_AUTOMATIC
                      } else {
                          Settings.System.SCREEN_BRIGHTNESS_MODE_MANUAL
                      }
                  }
                  else -> command!!.toInt()
              }
          )

that would explain why its off because we coerce the command to the max value the docs dictate but your device seems to be something undocumented

feel free to file a bug in github and we can look into it

https://github.com/home-assistant/android/issues/new?assignees=&labels=bug&projects=&template=Bug_report.md&title=