Lutron Caseta Pico (Core Integration Only)

captainnapalm · March 8, 2023, 11:26pm

Well that’s unfortunate. Looking forward to it working again.

bunjg · March 10, 2023, 3:35am

Bummer, thanks for investigating and look forward to trying it some day.

stephack · March 10, 2023, 11:03am

@captainnapalm @bunjg
Looks like someone already created an issue on github for this issue. There is a workaround of sorts that I haven’t tested yet myself but seems simple enough.

Feel free to upvote and post in the thread so the HA team sees activity on this issue and it hopefully grabs someone’s attention.

github.com/home-assistant/core

Automation Blueprints Stopped Displaying Lutron Pico Devices

opened 09:14PM - 06 Mar 23 UTC

smartqasa

### The problem Pico devices created by the Lutron integration no longer appe…ar in Automation Blueprint Device Selectors (https://www.home-assistant.io/docs/blueprint/selectors/#device-selector). The issue is quite simple as the devices simply do not display any longer even when all filters are removed. input: pico_remote: name: Pico Remote description: "Select the pico remote to configure:" selector: device: model: PJ2-2B-GXX-X01 (Pico2Button) ### What version of Home Assistant Core has the issue? Home Assistant 2023.3.1 ### What was the last working version of Home Assistant Core? Home Assistant 2023.1.x ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Automation ### Link to integration documentation on our website https://www.home-assistant.io/docs/blueprint/selectors/#device-selector ### Diagnostics information _No response_ ### Example YAML snippet ```yaml blueprint: name: Lutron Pico 2 Button - Light/Switch description: | This automation allows for the control of one or more light or switch entities by a Lutron 2 Button Pico (PJ2-2B-GXX-X01). domain: automation input: pico_remote: name: Pico Remote description: "Select the pico remote to configure:" selector: device: model: PJ2-2B-GXX-X01 (Pico2Button) entity: name: Entity(ies) description: "Light or switch entity to control." selector: entity: domain: - light - switch multiple: true trigger: - platform: device device_id: !input pico_remote domain: lutron_caseta type: press subtype: "on" id: on_pressed - platform: device device_id: !input pico_remote domain: lutron_caseta type: press subtype: "off" id: off_pressed condition: [] action: - choose: - conditions: - condition: trigger id: on_pressed sequence: - service: homeassistant.turn_on target: entity_id: !input entity - conditions: - condition: trigger id: off_pressed sequence: - service: homeassistant.turn_off target: entity_id: !input entity default: [] mode: single ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

captainnapalm · March 10, 2023, 3:55pm

Thanks for the follow-up. Odd that they’re disabled, although I was able to setup a separate automation using the device with no problem.

stephack · March 10, 2023, 9:42pm

The automation and events never stopped working. All my existing automation using this blueprint work fine. It’s the selector that’s now broken with the update. It simply doesn’t list the pico devices that are there. Strange bug for sure. Strange that enabling an entiity within the device suddenly allows its to be detected. One should not have any impact on the other.

bptworld · May 16, 2023, 11:26pm

@stephack, Long time no see! Just getting my feet wet with HA. Looking to get my Pico’s setup. One issue I’m having is when trying to use a ‘virtual’ device. They don’t show up in the device dropdown.

EDIT:

Answer from @stephack
Since what you want to control are actually entities, you can’t use the Device option and you would need to do service call to the entity. Eg Call Service->switch.turn_on->switch.yourSwitchNane.