I wanted to test some features of the button controller app. I already had the instance named "Living Pushbutton" that operates the living room ceiling light switch. I created another instance named "Office Pushbutton" to use for my test. The "Office Pushbutton" instance uses the same physical pushbutton as the original instance named "Living Pushbutton" but the actions are on the office ceiling light switch.
After the test, I set the disable switch on the "Office Pushbutton" instance.
Even with that disabled. the "Office Pushbutton" instance still executes and takes action.
Is there another way to disable?
I'm not able to replicate this behavior. Can you click/tap the "Office Pushbutton" rule to verify that you can't open it? (It should say that it's disabled and offer the option to enable -- but not the regular UI.)
If you still can, enable all logging (Triggers and Actions) on the rule. Then when you think it should have run, verify that Logs show something -- if not, it wasn't this rule. Use the "Logs" (
) icon in the top right of the app/rule page to go directly to Past Logs filtered to just this app to avoid confusing app IDs if you might have other rules.
EDIT: I disabled the parent app as part of my testing and re-enabled at some point point, but it wasn't happening to me in either state (but maybe doing this before changed something -- didn't test then).
@jgbLC The parent Button Controller 5.1 app is a separate app than each individual Button Rule app created for each button action. Disabling Button Controller app doesn't have any effect on the Button Rules that are its child apps. This is true for all parent-child apps.
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
