Picture Controller types Integrations
  • Light (LutronPJ22BLightController; 350ms delay)
  • Media Player (LutronPJ22BMediaPlayerController; 500ms delay)
state, lutron_caseta

Controller types

LutronPJ22BLightController (Light)

This is the default mapping for this controller:

  • Top button → Full brightness
  • Bottom button → Turn off

This is an example configuration:

      
example_app:
  module: controllerx
  class: LutronPJ22BLightController
  controller: < controller_id >
  integration: < state, lutron_caseta >
  light: < light entity >
      
    

LutronPJ22BMediaPlayerController (Media Player)

This is the default mapping for this controller:

  • Top button → Play/Pause
  • Bottom button → Next track

This is an example configuration:

      
example_app:
  module: controllerx
  class: LutronPJ22BMediaPlayerController
  controller: < controller_id >
  integration: < state, lutron_caseta >
  media_player: < media_player entity >
      
    

Note

For the State integration, it requires the LutronCasetaPro CUSTOM integration by upsert. THIS WILL NOT WORK with the default Lutron Caseta integration. All Lutron Caseta Pro Pico remotes supported by LutronCasetaPro are supported using this controller type except for the 4-button PJ2-4B remotes which is separate.

Integrations

Here you will see the actions that the controller fires when pressing or holding the buttons. In case of z2m it shows the state that the sensor takes. In case of deconz it shows the event id (or gesture) and for zha it shows the command concatenated with the args.

State

  • "1" → Top button
  • "4" → Bottom button
  • "0" → Release/Idle state

Lutron Caseta

  • button_2_press → Top button
  • button_4_press → Bottom button
  • button_2_release → Release top button
  • button_4_release → Release bottom button

💡 NOTE

When using words like "on" and "off" in the YAML configuration, you will need to wrap them up with quotation marks ("), otherwise they will be parsed as boolean variables (True and False).