Pico Remote Integration Not Responding to Select Actions

[user1831]

I am having a strange issue with a Pico remote integration and certain commands for a fan connected via a Bond integration.

First, however, let me confirm that I have several pico remotes connected and working properly. I obtained the ID through the Lutron Integration Report. All my pico remotes are of the 5-button variety.

I have two ceiling fans that are connected via the Bond integration. All commands for both fans work without issue, and I can control them similarly via Alexa.

I have a Zooz smart switch (ZOOZ ZEN71 ON | OFF SWITCH – ZOOZ) that also controls these fans through the Bond Integration. The button control for these switches is shown below.

All is well thus far.

I recently added a pico to control one of these fans. Here is the button control for it:

Every button works...except Button 1 Pushed to set the Fan to Low.

I tried to assign Fan to Low to another button (and tried pushed, held, double tapped), no luck.

If I go into the Hubitat button rule "Select Actions for" page for Button 1 Pushed of the pico remote in question, I can push "run actions" and it will work. It just won't work if I push the button on the pico remote.

I also tried to assign "Cycle Fan" to the pico remote. The same issue, won't respond when button is pushed.

Keep in mind that the exact same action "Bedroom Fan to Low" is assigned to a Zooz Switch and works without problem.

And yes, the logs do reflect when I push button 1 on the pico remote, but the corresponding action to set the Bedroom Fan to Low is not carried out.

Needless to say, I am out of ideas...

[bertabcd1234]

Go to the Application Status (gear icon) page for the "granchild app" for that specific Button Rule (e.g., button 1 pushed). Scroll down to "Event Subscriptions" and see if anything is there; there should be. If not, try hitting "Done" in that button rule/grandchild app again to see if that fixes the issue.

If that is there, what do Logs actually say? I know you say they show what you want isn't "carried out," but there could be multiple reasons for that, not all related to the Button Rule. Enabling all logging for the button rule (triggers and actions) will be the most helpful for figuring this out, along with the command history for the fan device itself, accessible from the "Events" button on its device detail page (even though this is not technically an event).

[bill.d]

Check that your Pico device has the correct number of buttons selected. Different models of Picos have internal numbering that is different from top to bottom. If you have the wrong number of buttons in the Hubitat device the mapping will be off.

[user1831]

Here is the Application Status:

You will have to zoom in, but the Event Subscription is similar to the other buttons with the exception that the Event is "pushed.null" while other button rules list the button number in place of the null. Also, in the settings section the other button rules have row called "ButtontDev1" with a value equivalent to the button number. The button in question here is missing that line. It seems this is the problem...

Once again, here are the button rules for the pico remote in question:

And here is the rule itself for Button 1 Push:

The logs showed that the other actions for button 1 worked (held and double tapped):

I went ahead and deleted the complete button rule/s and created it again. Same issue. Deleted a second time and now it works.

Strange error, considering I did the same thing each time.

Thanks for the help directing me to the Application Status. I had looked at it before, but after you mentioned it I reviewed it in more detail and compared it to the other buttons.

[user1831]

The number of buttons was correct, I only use the 5 button pico remote.

I had to delete the whole button rule and redo it twice to get it to work. Did the same thing each time. The hold and double-tap for button 1 worked fine. Turns out it didn't assign the button number to the push function and left it with a "null"

Strange...

Thank you and have a great one.