Pico Trigger Issue

New to Pico Triggers, but kicking myself for not exploring sooner, fantastic use case!

Using the latest Lutron Plugin. I have setup several buttons and triggers. They all work fine with my Caseta Pro bridge.

I noticed after successfully installing an ADDITIONAL Lutron RA2 Select hub, the pico triggers on most picos would no longer work, but one pico worked every time, even with the new RA2 Select hub enabled.

Why? Thats way above my knowledge, but I can tell you if I enable / disable that RA2 Select bridge in Indigo, all pico triggers work or don't work consistently. EXCEPT a single pico.

Photos -
1 - Plug in version
2- list of buttons. With the RA2 installed AND enabled, device 35 / button 3 works EVERY time, and is further away from hubs than button 13
With the RA2 installed AND enabled, device 13 / button 3 NEVER works , and is closer to the hubs than device 35 / button 3

3. This is the trigger that works EVERY time, no matter the status of the RA2 Select hub being enabled
4. This photo shows the method I finally used vs uninstalling the RA2 select as I tested this issue.

So, 2 basic questions:

1. Any thoughts on why one pico device would consistently work even with the RA2 Select hub enabled while the others wont ?
2. Any suggestions on why the pico triggers seem to get "Confused" when that 2nd hub is enabled ?

Multiple hubs/bridges usually work totally independent of each other, so I'm not sure what could be going on. You're only enabling/disabling the new Select hub in Indigo, right? You're not physically disconnecting it from power or network when the behavior changes?

Also, do the buttons actually work to do what they're programmed to do in the hubs? Or are they all unprogrammed for Indigo triggers only?

Those screenshots do me no good. The info you can see in the UI isn't that useful, and I can't read the text on those images anyway. So don't bother with those unless I ask for something specific.

Also, please open a new issue to track this on GitHub at https://github.com/FlyingDiver/Indigo-radiora2/issues

I'm leaving in less than 48 hours for three weeks on vacation, so all this needs to be tracked where I can find it easier later, which is not the forums.

What I need is for you to enable debug logging (NOT detailed debugging), restart the plugin, then activate the pico buttons with and without the Select hub enabled. The turn off debug logging and post the log info in the GitHub issue. That should give me something to work with to see what might be going on.

Also, just so you know, I've never had a Select system to test with, and I've never actually been able to test multiple independent hubs. Others have, but there certainly could be some edge conditions. I suspect that there's something wrong with the way that device addresses are constructed or compared for triggers when there's multiple hubs.

Joe, Thanks for the notes. I will prepare this for your return. We just got back from a Viking "
MEDITERRANEAN ODYSSEY ", would love to hear your plans, always looking for ideas for future travels if you care to share
Thanks,
Brian

This is a scuba diving trip to Indonesia.


Sent from my iPhone using Tapatalk

This is a scuba diving trip to Indonesia.


Sent from my iPhone using Tapatalk

Awesome. Enjoy! Bali? Lembeh? Wakatobi? Raja Ampat? So many possibilities. All great! Hope you have a wonderful trip.


Sent from my iPhone using Tapatalk

Wakatobi


Sent from my iPhone using Tapatalk

Awesome resort. Great diving. I will be there in October. Have a wonderful time.


Sent from my iPhone using Tapatalk

It’s our 9th trip there. We’ve been going since 2004.


Sent from my iPhone using Tapatalk

I'm back, so if you want to pick this up please create a GitHub issue.