And note I still cannot create any more virtual devices with the driver since adding that single presence device earlier today. I keep getting “A network or server error occurred. Try again later.” in the app.
New driver version 2023-02-01T22:35:17.008560957 has been pushed out to everyone’s hub. Your driver will be automatically updated.
New in this update:
Due to a recent change in the way automation routines are configured for switch level (dimmer) devices, I have added a dimmer level-only virtual device. This has no switch; just the dimmer control. (@NickA)
Related to the above, I have added a new Settings option to the Level virtual device (switch+dimmer) that allows you to select whether or not to have the switch affected when changing the dimmer. This will behave like a standard light dimmer switch where if you change the level to anything above 0, it will turn ON the switch automatically. Conversely, if you set the dimmer to 0, it will turn OFF the switch automatically. Turning the switch itself on or off does not affect the dimmer. Note that this behavior had always been available with the Light virtual device, and will continue to be. (@HalD)
New ‘AlexaSwitch’ device. This is basically the same as the Contact virtual device, in that it contains both a contact and a switch useful for Alexa routines. However this new separate device type should be more obvious for newcomers, and hides the contact which some people prefer. You also have several dashboard icon options available through device Settings.
Each of the above new device types include controls for setting the respective values.
What to expect
It continues to be a challenge to update the Creator device buttons with new options. Previously, I recommended everyone to delete and recreate their Creator device. However, this time around, I’m trying a new approach that is intended to be less intrusive. Once the driver has been updated on your hub, it may take some time and fiddling with the SmartThings app, but I’m hopeful the Creator device will automatically update for you.
It is possible that the Create and Inventory buttons may be temporarily non-functional, but give it some time and restart the app to see if it eventually gets fixed.
I anticipate that Android users will have things work fairly quickly, but iOS users may see delays or even have the Creator device not working again. If that is the case, then delete the Creator device and get it re-created through an Add device / Scan for nearby devices action in the app. You can do this without affecting your existing virtual devices. (Those with the CLI can use it to reinstall the driver manually, which should also get things back to normal).
Please report your experiences here (specify Android or iOS) so I can determine if this new approach worked or is a failure!
Be aware that new devices seem to now be created in whatever room your hub device is located in, as opposed to the No room assigned room.
Hi my friend. I just tried to add other new virtual switch. When I click on Select&Create a Network error message appear, tried some more times, different virtual drivers types and get the same warning. After I close the VEdge driver and open it again I found that Select&Create option is banned with a “-” char on it, also Virtual Device Inventroy option is banned and a “-” char on it. Am I missing something ?
@TAustin I deleted the previous version and did scan/add again to have it re-added. I confirmed the driver version is the current release but I don’t see options for the new device types. CLI shows the error log below:
I’ve just installed this driver as I’m migrating a script off of Webcore to Sharptools. I needed the new simulated contact sensor, which I have installed. I must be missing something because in Sharptools, when working with a rule, I only have the options on/off instead of open/close. Am I doing something wrong?
I haven’t tried that particular device from this driver, but that makes sense to me.
The open() and close() commands on the Groovy Virtual Contact Sensor were custom commands that were not associated with a capability (eg. they weren’t ‘official’ or ‘standard’). So I suspect that this driver implements the contactandswitch capabilities so it can expose the native on() and off() commands from the switch capability which then influences the reported attribute state of the contact attribute
Just for statistics, and I have no problem to report:
maybe 10h hours is not enough to get everything updated, i don’t know, i checked, the drive was updated to the latest version, but the device creator was still at 2.3 with no new virtual devices available. (I had never deleted the creator). Deleted and searched again, now I have 2.9 with all the new features.