Correct! There I can see the Virtual Switch Driver ID -
572a2641-2af8-47e4-bfe5-ad83748fd7a1
1 Like
Hi, @Johnnybegoode
The engineering team corrected this. I just checked and the Driver’s name appears correctly. Can you confirm, please?
Hi @nayelyz
Shows now simply as ‘Virtual Switch’, but without the surrounding selection box as seen in the case of other devices. I understand that is correct as no driver change can be made.
Thanks for the follow up!
2 Likes
Hi, @TapioX and others interested.
The engineering team also included the option to create Locally run devices in the Advaced Users App. Remember only Switch and Switch Level have this option available, so, you will be able to select one of those two.
Thank you!
3 Likes
To Local Virtual Devices is added new preference (Setting).
preferences:
- preferenceId: certifiedpreferences.forceStateChange
explicit: true
Allow virtual device events to not always be a state change
Adds a new certified preference ‘forceStateChange’ that allows users to select whether they want their virtual device events to always be a state change or not.
I made a new virtual switch but the new setting is not shown in the ST App.
Apparently this new setting is just coming into use later.
1 Like
I made a new virtual switch and the new setting is shown in the ST App.
This has come into use perhaps December 2024.
1 Like
Last time I looked, which I thought was only a couple of weeks ago but perhaps could have been a bit longer, the preferences still weren’t being exposed in the Edge driver so the setting didn’t actually do anything and force state change happened regardless. Has that changed?
1 Like
No
I was too hopeful. State Change mode is always on even if I changed the setting.
Let’s keep waiting.
I tested this Force state change again today. I think it works now.
Yes, I agree. I’ve just checked a test device on my beta hub and my infoChanged handler is getting called and device.preferences is now populated.
2 Likes