Lutron Pico Issues?

Is anyone else having Lutron Pico issues? For the last 2 firmware versions I've had issues with my Pico remotes. I have to hit the buttons 3, sometimes 4, times for them to do what I've programmed them to do.

This is happening on all my Picos. I haven't made any changes to them or their config.

I haven’t noticed a problem with picos specifically. I only use a couple, but they’re working fine.

I have not had any issues. Do you have anything other than picos on your Smart Bridge Pro? Can you isolate it to just the bridge, by connecting a pico to a dimmer or switch and see if you are seeing the issue outside of the Hubitat integration?

Also, when you are having the issues, check live logging and turn on debuging in that pico device details page in hubitat and see if any errors show up in live logging.

Since we use a direct connection to the Bridge via local network, if something is dropping packets or interfering with the connection, it would effect all picos.

Yeah, I have a couple of lutron dimmers and switches on the hub. I'll give your suggestions a shot when I get home.

1 Like

I have noticed that I have to sometime hit button 1 more than once to get my deck light to turn on, but that's very likely the device it's controlling. I have not notice that issue with my Pico in my bedroom that is controlling Hue, That is instant every time.

I'm thinking @patrick is on the right trail.. The only time I've had a Pico issue ever is when Hubitat's ZWave network is lagging. I'll press a Pico button multiple times, thinking I missed once.

Then I press another Pico button, and it fails, then out of the blue, the ZWave device goes on-off-on in a perfect match to what I had pushed as the ZWave radio catches up.

The Live Logs tells the tale though... I'll see the button push logged long before the ZWave device changes. I'm guessing you'll find Pico logs, near instantly.

No errors in logging but the events did show up in the logs even though nothing happened. I rebooted the lutron hub and everything seems fine now.