Virtual Components v0.8.0.1 not working with core_2023.11.2

[CharlyNaseweis]

Hi there,
I have to virtual switches in my configuration.yaml which are worked perfectly befor uprading to HA core_2023.11.2. If I do a downgrade, they are working as usual.
I also can set the switches in the developer tools or manually on the dashboard. The problem is, that they are not chooseable in the automations.
I already tried a lot like a complete reastart of HA, setting manually the switches but I cannot get it working in the automation.

My configuration.yaml looks like this:

#Virtual Components
virtual:
switch:
  - platform: virtual
    name: TestSwitch 1
    initial_availability: True
  - platform: virtual
    name: Rollo Zustand Auf/Zu
  - platform: virtual
    name: WoZi Tür Auf/Zu
    initial_availability: True

and as said worked with core_2023.10.5 without any issue.

Does somebody have an idea, what could be the issue?

thanks a lot,
charly

[twrecked]

I'll give it a try when I get back home.

Are the device still appearing in the Developer -> States tab?

[twrecked]

And if you're comfortable with Home Assistant - ie, going back a version of a custom component - this might be fixed in the Alpha builds. They work for me but they are very alpha!

[CharlyNaseweis]

Hi,

this was quick! Thank you!

yes, they are still appearing in the Developer -> States tab. I can there manually set the status from off to on and also in the dashboard the virtual switch is moving from off to on.

So for me, it look as the switches are available, bot not usable in automations.

I did not find the Alpha builds and think for me it is better to stay with the released versions.

thx
charly

[twrecked]

I'll be able to properly test this tomorrow, I'm out and about this weekend, but I suspect it's because virtual isn't a full integration yet. They might have made that a requirement in the latest build.

Funnily enough, this is the issue the alpha release is addressing.

[twrecked]

How exactly are you entering the devices in the automations? As a device? As a state?

[CharlyNaseweis]

I'm using it as a switch. The switch can be used by the state manually in developer or I can turn on / off in the dashboard. The switch itself is working, but not choose able in the automations...

[CharlyNaseweis]

Hi, any update on this?

thx,
c

[twrecked]

It's working for me so I need to know exactly what you are doing an how it's failing.

I go to:

Settings -> Automations & Scenes -> CREATE AUTOMATION

Then I set up a Trigger that waits for a state change on a virtual switch. I select the virtual switch from a drop down box.

And I set up an Action to call Switch: Turn on for a virtual switch. I select the virtual switch by clicking Choose entity and picking it from the drop down list.

Toggling my trigger switch causes my automation to run as expected.

[CharlyNaseweis]

Thanks for your quick feedback. I'll try when I find some time and let you know...

[CharlyNaseweis]

Hi,
thank you for your support, but I did not get it running.

I'm using now two helpers as a switch "input_boolean......" which is working pretty good for me.

thx,
charly

[github-actions]

This issue is stale because it has been open for 365 days with no activity. This issue will be automatically closed within 28 days if there is no further activity.