You can use Rules API to update temperature on virtual temperature device.
(MQTT device is also virtual temperature measurement device)
This example is for [ST Edge] vEdge Creator virtual device driver.
Edit: This driver is not supporting any commands for temperature measurement.
If you want use Rules API you have to use [ST Edge] vEdge Creator virtual device driver.
My issue looks like it may be similar to what @Subramanian_Swaminat was experiencing back in October. It looks like @ygerlovin has not been online in the community since then … is all OK with him?
While I’m still unsure about what caused it to begin with (last hub firmware update was weeks ago), I temporarily installed @TAustin driver, switched to it, and switched back as discussed in an October post, and then put the Contact Sensor back into normal state. Hope all is well with @ygerlovin
Is there any way to expose the vMomentary to the updated built in “Smart Lighting” app? The regular vSwitch shows in “Smart Lighting” just fine, but the vMomentary never shows up. I am trying to migrate several virtual momentary switches from DTH “Anidea for Virtual Momentary” to this Virtual Things Edge Driver. Thanks for this great tool and thanks in advance for your help on this.
Answering my own question. It seems quiet here from @ygerlovin so I just gave @TAustin’s vEdge Creator a try, and his Virtual Momentary button is both visible in and works with Smart Lighting. Here is a link in case anybody else runs into this issue:
Regarding the issue that I reported a couple of days ago about the contact sensor / switch becoming inoperable (just 1 of my 25), it appears that it does recur. I think I have narrowed it down to 1 contact sensor (not always the same one) becoming inoperable after my Hub is rebooted. I’ve rebooted it a few times today (unrelated - to test some notification functionality i’ve implemented) and when the hub comes back, one contact sensor is hosed up. If I change to another driver and back it fixes the issue, but it would seen there is an underlying problem. As I believe that I can repeat it frequently, I would be happy to pull logs if that would help … just need some direction on what to do. Thanks, Todd
@DaWeav did you ever get “vThermostat” to work?
And if you did how are you transferring the current temperature from a temperature sensing device to the virtual thermostat?
Small bug @ygerlovin, is that the kwh are not correctly shown when i use a blitzwolf plug with your driver.
An hour of charging at 3,2kwh, adds 0,3kwh usage.
Start: https://i.imgur.com/WIExey3.jpg
Charging rate: https://i.imgur.com/TIQoCdA.jpg
End: https://i.imgur.com/DDfWI3c.jpg
(see the phone time top left corner of screenshots)
Hi,
I’m using the Virtual Things Edge Driver [YG] (version: 2022-09-05) and I would like to start using the Power Meter (vPower [YG]) - but I cannot deal with it.
I tried many different commands to set it up, but I failed.
I suppose the commands should be something like:
./smartthings devices:commands “…its.id…” “powerMeter:value(9)”
./smartthings devices:commands …its.id… {“energyMeter”,“value”:10}}
Could you give me an example what the commands should look like for the vPower virtual device?
I would like to set up the powerMeter and the energyMeter as well.
Thanks,
Robert
Help. Samsung has erased my hub accidentally I’m being told after noticing my devices, scenes, routines all missing from the ST app. Has this happened to anybody else? Is there a way to recover my Vedge devices I created that as I understand live in my hub and nowhere else, right? When I login to the graph.api website, I can still see my missing devices (see pic). Does that mean they are still alive in the cloud?
The status page says that impacted users were sent instructions on how to restore complete functionality. I’d look for that e-mail or contact support if you did not receive it.
I think there is a problem in the virtual door contact device created by vEdge Creator V2.91. When I use door device in routine execution, it doesn’t change open and close status. It appears 3 options blocked unlocked (this is the only one that works) and two other options on of (does not change the values of the door device when executed in the routine). For example! It is not possible to execute a routine that changes open/closed status by routine in smartthings. Example: Routine device A on then device door opens/closes (on off) does not work.
@TAustin
Thanks for letting me know. I’ll try to see if I can recreate the problem and get back to you.
Thx… A suggestion for future implementation would be a Swift alexa 2 in 1 with (opens and closes) and (locked and unlocked) on the same virtual device. do it with door contact, but only the function used with blocking and unlocking worked (when using the open and close button on the door device, it performed perfectly on Alexa, but another device did not change the on off button in the smartthings routine…
I’m having trouble with Alexa routines triggers based on open close contact states in smartthings. They seem to trigger inconsistently. Anyone else noticing this? I have the same issue using Taustin’s virtual edge driver too, and some physical contact sensors.
Yes, today 05/30/23 very inconsistent
I’ve opened a ticket. #1484688 in case you want to do the same. Maybe someone will take notice at Smartthings.
Same issue here. Sometimes Alexa does not recognized contact sensor / switch changes in smartthings. it stops working and later it does. I was going to switch the @TAustin driver to see whether the behavior is the same, but it looks like it is based on @sdbg post. Just out of curiosity are these drivers also supported by @TAustin ? I saw him post a response above but have not seen @ygerlovin post in many months
I’ve tried multiple different edge drivers from various sources including @TAustin and Yacov. At one time I thought maybe Yacov was slightly more reliable, but at this point I’m comfortable in saying that both are equally inconsistant in terms of triggering Alexa on the regular. Wondering if it might be related to the Alexa skill itself? Sometimes I notice that physical contact sensors also do not trigger Alexa despite changing in smartthings. Especially when there are multiple triggers in a short period of time. Could Alexa have an ignore period to avoid getting repeated switch updates within a short period of time?
