Lutron Pico remote

… outlets and other non-hue stuff. It’s not perfect (can only read last button state), but it works. If you want a nicer-looking option, you can get some Lutron Pico remotes and the Caseta pro bridge.

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

Frigate - the thing is powerful and solved some camera issues for me that I was struggling with. Lutron - dead solid, simple and the pico remotes are stupid useful for so many things. Monoprice 6 zone amp - replaced a big clunky expensive RTI that requires closed source programming tools. For me I love any integration that is solid and actually solves and issue for me. Frigate allowed my to get the streams from my coax DVR then effectively proxy them to any device without hitting the DVRs limit. The only.other solution if found was gonna be $1300+ in hardware.

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

Looks for cameras that support RTSP/ONVIF - that means you can hook up an NVR like Frigate or Scrypted without the cloud. You’ll be hard pressed to find a decent one you can flash with open source firmware.

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

Yeah, I have 5 Pico switches in HA through the Lutron Caseta integration. I don’t remember how I did it, but probably HACS. It can be done though.

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.

The problem The Lutron Caseta integration supports pico remotes, but it exposes this as a device trigger for each button with "press" and "release" actions. There is no support for distinguishing between short presses, long presses, and double clicks. Also because of the way it exposes these triggers, the HomeKit integration represents this as a stateless programmable switch with 8–10 buttons (e.g. a 4-button pico has 8 HomeKit buttons, two per physical button that represent "press" and "release"). This makes it very awkward to use. Instead the Lutron Caseta integration should support …

Excerpt saved from GitHub on 2026-10-23.

The problem The Lutron Caseta integration supports pico remotes, but it exposes this as a device trigger for each button with "press" and "release" actions. There is no support for distinguishing between short presses, long presses, and double clicks. Also because of the way it exposes these triggers, the HomeKit integration represents this as a stateless programmable switch with 8–10 buttons (e.g. a 4-button pico has 8 HomeKit buttons, two per physical button that represent "press" and "release"). This makes it very awkward to use. Instead the Lutron Caseta integration should support …

Excerpt saved from GitHub on 2026-10-23.

The problem Lutron pico remote stop working. I have them trigger different devices via monitoring lutron events. Now each time I press button it does nothing and the below log popup ### What version of Home Assistant Core has the issue? core-2024.5.1 ### What was the last working version of Home Assistant Core? 2024.5.0 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Lutron Pico Remote ### Link to integration documentation on our website _No response_ ### Diagnostics information ``` Logger: homeassistant.core Source: core.py:1555 First …

Excerpt saved from GitHub on 2026-10-23.

Got hacs running (not very intuitive for me) and set up some automations using picos to controls lights and blinds. I noticed these automations come over as a switch into homekit. Is there a way to remove/stop them from showing up in hk?

Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.