V-switch Api
Berniece Leonhardt
I upgraded my Windows 11 physical machine to 22H2 this morning. This machine hosts 4 hyper-v virtual machines using 2 different virtual switches. 1 switch is an internal NAT and the other a bridged external.
Up until the upgrade these switches performed flawlessly.
After the upgrade, no internet connectivity from either switch.
Changed all my VMs to use another v-switch.
Deleted the v-switch that wasn't working.
Went into the properties of the external network adapter and unchecked "Hyper-V Extensible Virtual Switch"
Re-created the v-switch using the external network adapter
Changed all the VMs to point to the re-created v-switch.
MikeDriest-2754 3 days ago
On my custom NAT virtual switch I removed the extension Microsoft Azure VFP Switch Filter Extension and it resolved the issue for me. No need to create a new vSwitch and change VM NIC bindings.
One other way I figured out how to fix was to go into each virtual switch and in the virtual switch manager expand the + next to each. This exposes the Extensions property. For me there are 3 extensions, Microsoft Windows Filtering Platform, Microsoft Azure VFP Switch Filter Extension, and Microsoft NDIS Capture. Of those, the last 2 were enabled and the the last one, Microsoft NDIS Capture was throwing an error. I disabled both enabled extensions and it all started working again.
My guess is that recreating the switches as @Sarah Tennyson did essentially corrected the error the older switches were having.
On my custom NAT virtual switch I removed the extension Microsoft Azure VFP Switch Filter Extension and it resolved the issue for me. No need to create a new vSwitch and change VM NIC bindings.
I had the same issue on my setup. Unfortunately, none of the above worked. Also tried to recreate the v-switch, had unchecked the "Hyper-V Extensible Virtual Switch" option, removed the Microsoft Windows Filtering Platform & Microsoft Azure VFP Switch Filter Extension, none worked.
Had to rollback to previous version.
But one important thing about this. When I first updated to 22H2, hyper-v gave me the option to "upgrade" the vm's to new configuration, which I did (my bad).
When did the rollback, the "old" hyper-v did not recognize any of the VM... I had to manually delete the configuration files, remove the vm's using powershell, and then recreate the VM's attaching the disk files.
So the above lines (see vue docs) make your v-model bind to input-value instead of value likely because some components i.e. checkbox (which v-switch uses) have value attribute reserved for something else.
Vuetify is one of the most widely recognized user interface frameworks for Vue.js. It provides a set of reusable and customizable components that allow us to quickly and effectively build modern and user-friendly interfaces.
The v-switch component displays a label depending on what string value we provide the label prop. However, we may want to customize this label to better fit the context of our application by rendering a label with a more complex markup. We can achieve this with the capability that Vue provides us known as slots.
We can use the v-on directive (i.e. the @ shorthand) to listen for the change event and trigger an onChange() function in our component. This onChange() function will emit a console.log message that states whether the switch is on or off depending on the value of the isEnabled reactive property:
The value prop is used to specify the value that the switch should represent when it is toggled on. This is helpful within the context of storing multiple values in an array because we most likely want to store multiple unique values as opposed to storing multiple true/false values.
Would like to either control them directly via HE (haven't found a solution yet), or create an Alexa routine that uses HE virtual switches as a trigger (When this happens) to turn off the group with the Sengled bulbs in it
To get around this limitation, you could use my Virtual Motion-Switch driver. It allows you to use the Switch on/off commands in Hubitat, while using the Motion active/inactive states as triggers in an Alexa Routine.
Every once in a while Alexa will get forgetful... Try removing the switch from the Alexa Echo Skill app, save and exit (this should invalidate the rule on Alexa also). Go back into the app and re-add the switch, then go into Alexa and re-point the routine to the switch.
Finally got it working to turn the light on via an Alexa Routine, however the v-switch-motion device (using the driver suggest above by @ogiewon) doesn't stay active, since it goes inactive with a few seconds, so Alexa turns the lights off right away
Create a new driver using the code I posted and use it instead. Alexa will respond to either a motion sensor (your first implementation) or a contact sensor. A motion sensor by definition will eventually go from active (switch on) to inactive (switch off), A contact switch can stay open or closed until some other action changes it.
Ahhh...sorry about that. I actually use it in the reverse fashion...Amazon turns on the switch, which triggers a motion event in Hubitat momentarily. My driver automatically resets itself to be read for the next event...
NOOB here.
I have installed the Virtual Motion with Switch driver, Created a new device for it and it works from the Device app. The problem is I cannot get the device to show in Alexa, I have removed and re-selected it several times but it refuses to display either on PC or tablet. Is it related to this worrying line ? " If you include a device that isn't compatible with Alexa it will just be ignored and not sent to Alexa."