I was advised to reboot my router at the stage you get the message in the setup screen.
I’m not sure if anything was done in the background by the SmartThings team but that seemed to force the installation to complete. However continue to assist @TAustin if you can to allow him to find a full resolution.
I’ve had one other person running the beta firmware reporting a similar problem on another driver, and he provided me logs. I saw that when adding a device, sometimes the driver wasn’t getting notified of the device creation and as a result the device wasn’t ever properly initialized. This seems to be the same symptom here. I don’t know if it’s a bug in the beta or what, but I asked him to report it.
1 Like
3 posts were merged into an existing topic: Presence in 2023, including multiple members and multiple locations
Problem solved with the latest firmware 49.8 
Oh I’m relieved to hear that! Thanks for letting me know.
@CAgnew are you working now too?
1 Like
Mine sorted itself out when jkp told me to reboot the router after the vEdge creaatr install step.
Do edge drivers update automatically? Or do I need to delete old version & install the updated version?
Normally yes, they update automatically.
There are cases with this driver that require that you delete and recreate the ‘creator’ device whenever I add a new device type. Unfortunately I haven’t found a reliable way to dynamically add new types to the selection list, so this necessitates recreation in order to get the latest device type list. It’s not very convenient and often causes confusion, but I just don’t have a better solution.
BTW, you can delete and recreate the creator device without any impact to your existing virtual devices.
4 Likes
Can someone screenshot a ST routine that you use to trigger Alexa? I can’t wrap my head on how to trigger an Alexa routine from within ST…
Thx
Turn on the switch from a smartthings routine, and, in the case of the synchronized pairs, that will automatically open the contact sensor.
Then using an Alexa routine (not a smartthings routine) have it trigger from the contact sensor changing state.
That’s all there is to it. It works the same basic way This method has always worked, it’s just that Todd has automatically created the synchronized pairs for you.
You turn the switch on and off by voice, or with a smartthings automation.
The switch changing state causes the sensor to change state.
And you use the sensor changing state to trigger the Alexa routine. 
2 Likes
It may help to understand that only certain SmartThings device types (e.g. ‘contact’ devices) can trigger Alexa routines because Alexa only recognizes certain device types within SmartThings for triggering purposes (“When this happens”).
So to facilitate triggering Alexa routines, vEdge allows you to create a switch & contact device pair. They need to be separate devices rather than combined in order to work reliably.
So if you use this driver to create an “Alexa Switch”, and go into Settings for that switch and turn on the “Separate Contact” option, a second, linked, contact device is also created, which is synched by the driver such that when you turn the switch on, it opens the contact device, and visa versa.
At this point you can create an Alexa routine that triggers based on that contact device going open. On the SmartThings side, you simply have any automation routine that turns on that switch to trigger the Alexa routine by opening the contact.
Sounds a bit convoluted, and it is, but it works reliably 
4 Likes
Thx for the replies @JDRoberts @TAustin. I’ll give it ago tmrw once my brain is rested. Thx again!
1 Like
If there’s an opportunity to show both state and mode on the dashboard it would be perfect, if not, having the opportunity to choose one or the other would be great.
Since we’re talking about the dashboard, in the temp and humidity devices is it possible to show temperature and humidity on the dashboard?
Thanks!
I’ll have to look in to that. There is a way to show multiple state values on the dashboard - it makes the dashboard card twice as big. But the last time I experimented with it, it wasn’t working reliably, so I haven’t tried it again since then.
When I get a chance I’ll look into it again.
3 Likes
First and foremost, thank you. Would it be possible for you to add a combined virtual smoke and carbon monoxide detector?
It might be easier to add a device settings option to the smoke device to allow you to include a CO sensor. I can also add another device settings option to select what to show on the dashboard: smoke or CO state. Would you also want the option to show both if I can get that working?
EDIT: Also - are you confident that you can set the CO measurement value via some kind of mirroring automation?
1 Like
It’s for my Protect, and I think it can be as simple as an additional switch. The alarm event will happen on Google’s end, then pass the alert to the virtual device but it’s unlikely to be able to pass the rawValueUnit data with it. If possible, I would rather not have multiple virtual devices for only one Protect.
1 Like
I was thinking of the carbonMonoxideMeasurement capability which is a measurement value, but I think what you are wanting is carbonMonoxideDetector. Am I correct?
I don’t see a way to script an automation so that the quantitative value would be reported to the virtual device. So, yeah, it just needs to be a detector that functions in the same manner as smoke. An automation based on the qualitative values is good enough for me.
1 Like
One more question: You mentioned that the state change originates in Google. Exactly what mechanism are you using to send the trigger to SmartThings? The reason I ask is that I would normally want to put the smoke detector and CO detector in separate components. Can whatever you are using deal with multiple-component SmartThings devices? Reason I ask is that some 3rd-party integrations can’t, and can only deal with capabilities in the ‘main’ component.