This was before child devices become available. Maybe it could be possible now. Also he is able to use capability values from different devices (temperature sensors) that use same driver somehow (groups).
Maybe he can help with this
I think it would not make sense to drear virtualdevices child of another virtual device, it is better to directly create each virtual device separately.
secondary components are not exposed to third-party apps, they can’t even be viewed and controlled on my.smartthings.com.
Hopefully it gets fixed at some point
Component names should be changeable, as they all have their own “label” field.
The name of the main device can be changed because it is the device.label that is changed, not the label of the “main” component, which still appears as the main name in the app.
Hopefully when everything calms down there will be time to improve these things
Have you looked into Linked Places? They were only usable on Galaxy phones but I am no longer seeing that restriction flagged in the app as I used to. I haven’t had a chance to investigate it though. Linked Places are set up in the same way as your Location and the geofence radius can be up to 30 km (18.6 miles).
okay? homekit devices some are lan (wifi) based and work local to homekit. When pairing, you need to enter a code or scan a qrcode. In the home assistant there is an integration called homekit controller that allows you to use these devices directly in the home assistant without needing the homekit. Do you think it is possible to create a lan driver for these devices?
Hello, scanning for devices does not pull up the vEdge Creator. I initially installed v2.8 and was able to create 3 virtual presence sensors. When I went back to try to create a contact sensor, it got stuck on creating devices. I deleted everything, uninstalled the driver, and re-installed, but now I cannot get the creator to show up when scanning for devices. Any idea what could be the issue? I’m willing to provide logs but not sure how to go about doing so.
I’m using the vEdge Creator to support 5 virtual dimmers and a switch. All of the virtuals are being used with the new Smart lighting to do one-way mirroring so that I can operate some groups of lights as one, primarily for use with Alexa.
There is a significant difference in how the virtual dimmer works as compared to a real dimmer or the old IDE-created virtual dimmer.
For my other dimmers if I say “Alexa, dining room ceiling 100%”, the dimmer is turned on and set to the requested brightness. With the vEdge virtual dimmer, the dim level is set but the on/off state isn’t affected. This means I have to give Alexa two commands to get the lights on and set the level.
Possibly related is the dashboard presentation. If I select “dimmer” presentation then the icon appears on any time the dimmer value is non-zero even if the switch is actually off. Again, that’s unlike how real dimmers work and unlike how the IDE-created virtual dimmer worked.
@TAustin , is there any way to get a virtual dimmer that behaves like a real dimmer?
Well believe it or not it’s behaving the way folks requested when I first created it. But this has come up - that it would be good to have a Settings option to enable the behavior you are looking for. I’ll bump this up on the priority list and try to get it done in the coming days.
In the past, many people have requested this specific behavior so that they can change the dim level based on time of day without actually turning the light on. That way the next time someone hits the wall switch, it comes on at the lower level. This is commonly a nighttime routine, but it’s also used to emulate circadian lighting.
Without separating the two, you get the situation where the light turns on at full brightness and then dims to the desired level, which can be a problem, for example, in a nursery.