Button controller toggle virtual switch not working - Bug?

🧰 Built-In Apps and Drivers
1

I just setup a virtual switch that I want to toggle on/off with a single button controller rule. Simple enough, toggle switch on/off.

It'll turn the switch on, but will not turn it off.

Able to recreate it with a virtual button and virtual on/off switch with button controller.

Found some similar posts where toggle from rule machine doesn't work with virtual switches. Seems like a bug perhaps?

2

What hub platform version are you running? Check Settings > Hub Details.

To troubleshoot, you will also need to:

  1. Enable all logging for the rule (triggers, actions, and events)
  2. Ideally, enable descriptionText logging for the virtual device you are turning on/off in your actions
  3. Provide a screenshot of your actual rule.
  4. Provide a screenshot of the output of Logs, filtered to just #1 or possibly #1 and #2 above, that illustrate the problem
  5. Possibly provide the "Events" history from the device detail page of the same virtual device as above, though descriptionText logging hints are usually good enough to see (though technically not the authoritative source of events)

Links to these would also be helpful, as I do not remember seeing any cases where the problem wasn't one with the device itself, not RM.

3

I just tested this and it works as expected:

image
image2020×1511 198 KB

image
image1306×1057 83.6 KB

4

Well this is weird. I can't recreate it with a new virtual button and new virtual switch now.
But it still fails with my existing virtual switch, and a virtual button.

Could there be an automation the virtual "Deck Lights" switch is used by causing the headache?

[EDIT] Another thought. "Deck Lights" was originally a zwave switch. I created the virtual switch and did a "swap apps device" to move the automations to the new virtual switch.

This hub is on the latest non-beta: 2.4.0.148

Here's the live logs of pressing virtual button 1, twice.

image

And the button controller rule:

image
image895×562 20.7 KB

And here's the thread I found searching:

5

That's the time i created 10 long range ghosts by attempting a mass smart start include, to save my knees from walking up and siren the stairs, lol.

Good times.

Looks like you're well on your way with those fine logs, as directed, lol.

1 Like
6

Just tried duplicating but it acts as it should.
My advice is to fuggedaboudit and carry on. :slight_smile:

7

I guess our cases were a little different. Mine was from a physical switch that I replaced with a virtual switch. When I get a free minute, I'm going to create a new virtual switch and test it as I move automations/apps over to it. I'm thinking maybe it's an automation causing it, or perhaps because I used swap apps device and something is lingering in the backend.

8

I've replaced a real device with a virtual device driver before (using the device UI) and the virtual device operated as expected, in any event there isn't an issue with the button controller app.
If you can enumerate the specific steps taken to reproduce this, let me know and I'll have a look...

1 Like
9

Well I just fixed it. I created a new virtual switch called Deck Lights, and told it to replace my old virtual switch. I then deleted "Deck Lights (old)", and now the button controller rule turns it on and off as it should.

Not a state per se, but could there have been something lingering in the database from the old physical switch I originally replaced?

It's a moot point now, just curious :slight_smile: