Pico - one of the buttons going south?

[danabw]

I have a Pico that controls a fan...two of the buttons are set to do the same thing (long story, related to WAF).

Button 3 and button 5 have the same logic in the Button Controller app:

When I press button 3, nothing happens. Press button 5, and fan turns on/off as expected. The light on the Pico flashes normally when I press button 3. Button 5 triggers the logic/action normally in the logs, button 3 does not...there is no "Pico Fan Fam: button 3 pushed..." entry when button three is pressed

More logs of button presses from the Pico - button 2 and 4 work fine to set speed to Low and High:

Never had a Pico go south on me in this way - not sure why the button press registers in the logs but nothing happens...anyone seen this? I've tried removing the settings for button 3 completely and re-doing them, but same result.

I'm flummoxed!

[didymus]

Do you have a Caseta dimmer or fan control that you can pair directly to your Pico to see if button 3 works in that configuration?

[danabw]

No, unfortunately I don't have any Caseta devices.

It's just so weird that the button shows up in the box but doesn't kick off the logic attached to the button.

[bertabcd1234]

@danabw

I've tried removing the settings for button 3 completely and re-doing them, but same result.

I assume you hit "Done" after doing this? (I think it's the grandchild app that matters, but the child can't hurt either.) Also, what do event subscriptions on the App Status page look like? I recall some issue with this a while back that was fixed, with the symptom appearing on this page ("null" where the number should be, maybe?).

In any case, this is definitely an app issue. Your Pico is doing what it should, according to the telnet logs. Just something in that Button Controller, it appears...

[danabw]

Thanks for the ideas.

Yup - I've "Donned" all the way out of the child and app, just to be sure.

Event Subscriptions and scheduled jobs are both empty.

Application state seems normal...

Still flummoxed. (Yeah, I like that word. )

I'm going to create a new Button Controller child for the Pico and see if that behaves differently for button #3...

[672southmain]

@danabw

Never had a Pico go south on me in this way

Hmmm… Can you hear it faintly whistling Dixie?

[danabw]

That's IT - Button three is on vacation.

[danabw]

So I disabled the existing button controller child, and created a new child and put the same logic into the Button 3 settings. It works perfectly/normally, w/out issue.

So something had gotten hung up in the first Button Controller child in the settings for button somewhere along the line, but not in a way that is visible as far as I can tell. As I noted above I had completely removed the settings for button 3 in the first Button Controller child, so not much more I could do than that in the app to try to fix this issue.

Robert - should this issue be shared w/Bruce, or ?

Post-script...I had forgotten about this little guy at the bottom of the page for the "Button 3 Push" instance.

Removed the "Button 3 Push" instance, added it back in, added logic back in, and it works fine. So it took removing the button push instance.

[bertabcd1234]

Was your "old" app also a Button Controller-5.1 instance? We can tag Bruce just to see if there's anything he wants to look at, but I recall a similar bug a while back that was fixed, so if it's working now, that may have been addressed already. I can't recall enough details to remember if this was the exact issue or what the fix was...so not helpful.

[danabw]

Thanks.

I only started using Button Controller on 2.3.2, so I've only used the newest version of it.

Also see my addition above about an alternate fix by removing the Button 1 push instance and re-adding it.