Unexpected Lutron Pico Remote Behaviour With lutron_caseta_pro Component

Third party integrations
, ,
1

I’m trying to setup my pico remote so that when I press the favourite button, the remote will switch to controlling my LED strip. Press the favourite button again and the remote goes back to controlling the overhead light. I’m using an MQTT sensor and accompanying automation to detect and store a value for the favourite button press.

I am running Home Assistant 0.91.4 on hassio with an updated Lutron smart bridge pro, lutron wall dimmer, and pico remote using the lutron_caseta_pro component.

I have the automations working, and I can see the right MQTT topics being published using mosquito_sub. However, unexpectedly the remote still sends the default commands to the lights. That is, if the favourite button was pressed, and the On button is then pressed, the LED strip and the overhead light both will turn on. Further, every time I press the favourite button, the MQTT topic state changes as programmed, but also the lights will dim to 50%.

I have tried unpairing my pico remote from the lutron wall dimmer and re-adding the remote to the smart bridge pro. That didn’t change anything.

Here is what I’m using for configuration:

  - platform: mqtt
    name: "pico_mid_button_pressed"
    state_topic: "remote/mid_button"

Here are my automations so far:

- alias: pico middle button pressed
  trigger:
    - platform: state
      entity_id: sensor.main_lights_remote_1
      to: '2'
  action:
    - service: mqtt.publish
      data_template:
        topic: 'remote/mid_button'
        payload: >
          {% if states('sensor.pico_mid_button_pressed') == "1" %}
            0
          {% else %}
            1
          {% endif %}

- alias: pico remote on button pressed
  trigger:
    - platform: state
      entity_id: sensor.main_lights_remote_1
      to: '1'
  action:
    - service: light.turn_on
      data_template:
        entity_id: >
          {% if states('sensor.pico_mid_button_pressed') == "1" %}
            light.desk_led_strip
          {% else %}
            light.master_bedroom_main_lights
          {% endif %}

- alias: pico remote off button pressed
  trigger:
    - platform: state
      entity_id: sensor.main_lights_remote_1
      to: '4'
  action:
    - service: light.turn_off
      data_template:
        entity_id: >
          {% if states('sensor.pico_mid_button_pressed') == "1" %}
            light.desk_led_strip
          {% else %}
            light.master_bedroom_main_lights
          {% endif %}

The button mappings are according to this provided button map.

Here is my debug log for pressing the favourite button then the on button on the remote. When performed, the topic remote/mid_button changes to 1, the lights dim to 50%. Then, the LED light turns on and the celing light turns to 100% brightness:

2019-04-19 04:45:58 DEBUG (MainThread) [custom_components.lutron_caseta_pro] Read value for host 192.168.8.20: DEVICE 3 3 4.000000 2019-04-19 04:45:58 DEBUG (MainThread) [custom_components.lutron_caseta_pro.sensor] Got DEVICE value: DEVICE 3 3 4 2019-04-19 04:45:58 DEBUG (MainThread) [custom_components.lutron_caseta_pro.sensor] Got Button Release, updating value. Previous state: 2 2019-04-19 04:45:58 DEBUG (MainThread) [custom_components.lutron_caseta_pro.sensor] State after button release: 0 2019-04-19 04:45:58 DEBUG (MainThread) [custom_components.lutron_caseta_pro] Read value for host 192.168.8.20: OUTPUT 2 1 50.000000 2019-04-19 04:45:58 DEBUG (MainThread) [custom_components.lutron_caseta_pro.light] Got light OUTPUT value: OUTPUT 2 1 50.000000 2019-04-19 04:45:58 DEBUG (MainThread) [custom_components.lutron_caseta_pro] Read value for host 192.168.8.20: DEVICE 3 2 3.000000 2019-04-19 04:45:58 DEBUG (MainThread) [custom_components.lutron_caseta_pro.sensor] Got DEVICE value: DEVICE 3 2 3 2019-04-19 04:45:58 DEBUG (MainThread) [custom_components.lutron_caseta_pro.sensor] Got Button Press, updating value to: 1 2019-04-19 04:45:58 INFO (MainThread) [homeassistant.components.automation] Executing pico remote on button pressed 2019-04-19 04:45:58 INFO (MainThread) [homeassistant.helpers.script] Script pico remote on button pressed: Running script 2019-04-19 04:45:58 INFO (MainThread) [homeassistant.helpers.script] Script pico remote on button pressed: Executing step call service 2019-04-19 04:45:59 DEBUG (MainThread) [custom_components.lutron_caseta_pro] Read value for host 192.168.8.20: DEVICE 3 2 4.000000 2019-04-19 04:45:59 DEBUG (MainThread) [custom_components.lutron_caseta_pro.sensor] Got DEVICE value: DEVICE 3 2 4 2019-04-19 04:45:59 DEBUG (MainThread) [custom_components.lutron_caseta_pro.sensor] Got Button Release, updating value. Previous state: 1 2019-04-19 04:45:59 DEBUG (MainThread) [custom_components.lutron_caseta_pro.sensor] State after button release: 0 2019-04-19 04:45:59 DEBUG (MainThread) [custom_components.lutron_caseta_pro] Read value for host 192.168.8.20: OUTPUT 2 1 100.000000 2019-04-19 04:45:59 DEBUG (MainThread) [custom_components.lutron_caseta_pro.light] Got light OUTPUT value: OUTPUT 2 1 100.000000`

I’m a bit confused because I see other people programming their pico remote to recreate the dimming effect, as though no one else is having this issue. I can’t find other people having this issue through searching. Any ideas?

2

Solved this through the help of some folks on the discord channel. My pico remote was paired with my wall dimmer in the lutron app. That was the source of my problems, and once I unassociated the remote with the wall dimmer everything worked as expected.