I’ve created a virtual thermostat and I can set the temperature for it manually or by automations. But, however the virtual thermostat is in Auto mode, its state is always Idle. I assumed it will be heating, cooling, etc., according to the actual temperature and the set temperature values for heating and cooling. When I switch to heat mode or cool mode, the state indicate the right mode, when I switch to Emergency mode the state turns to Heating, but nothing happens in Auto thermostat mode. What can be the problem?
Hello @TAustin ,
I’m using the virtual thermostat, and for the most part, it functions OK. However the behavior isn’t quite right, at least from what I understand.
For example, if the mode is set to “Heat” and the temperature is set to 20, and the heating set point is at 22, then the “state” should be “idle” not “heating”. Similar issue with “cool”.
This is important for creating routines that operate HVAC equipment, to turn them on/off when going above/below the set points.
Thanks!
Thanks for your feedback. The virtual device was implemented as kind of a ‘dumb’ virtual device assuming the user would be setting the device values- including mode - to whatever they wanted. In hindsight, and reading your comments, this may not have been the most useful approach.
I can certainly implement some more ‘intelligent’ behavior along the lines you have described. Give me a couple days and I’ll have that done for you.
Thanks, it would be great! I used virtual thermostats in different smart home gateways earlier. I was able to link the temperature data from an existing multisensor in a room to the virtually measured temperature value of the virtual thermostat. So when this virtual thermostat switched to heating status in heating or auto mode, the gateway switched on an existing relay (starting the boiler). Or when it switched to cooling, the gateway switched the A/C with a Remotec IR transmitter. I would like to see similar behaviour from your virtual device too.
Actually I can not assign temperature value from an existing sensor to your virtual thermostat as a “measured” temperature. I can make routines like “If temperature value of sensor is between 23 and 23.9 C, then set temperature of virtual thermostat to 23 C”. But I have to create similar routine for every degree (or even more if I need smaller hysteresis than 1 Celsius), what is not easy and efficient.
Sorry for a reply to an old comment, but wouldn’t a momentary switch work for this?
Thank you very much, works fine.
Just two comments,
1- I have to restart SmartThings app after virtual sensor creation, otherwise it is stuck (not big issue).
2- I created 2 virtual switches and 1 virtual presence sensor, and when i click on the device card for switches i cannot access to the details and routine affected to the switch. It works for a virtual presence but not for two virtual switch. Is it normal ?
Yes it would. I just prefer using a switch.
Martin - I apologize for not responding to your earlier message…
There is a ‘Panic Alarm’ device that should give you want you want. It includes the alarm capability which can be set to off, strobe, siren, both.
Hello - Are you still having this issue? What you were describing is a typical glitch in the mobile app, which usually clears up eventually. You may need to close and re-open the app.
no worries , yeah the panic alarm will do the trick . thanks
I confirm it works now ! Thank you. However I had closed and opened application several times … Finally works ! Great and thank you again for the edge driver. It will help so many people i guess …
DRIVER UPDATE!
Version 2022-09-20T17:11:20.414140104
This update includes:
-
Thermostat automation (@ozsolt @tmielonen)
New device Settings option to enable automation of operating mode based on setpoint temperatures and actual temperature -
Momentary Button toggle switch option
New device Settings option under ‘Button effect’ to implement simple toggle of switch when button is pushed -
Switch Level/Dimmer dashboard option (@NickA)
New device Settings option to choose between switch state and dimmer value for dashboard state display. One caveat: if dimmer value is selected, then the color highlighting on the dashboard icon will no longer reflect the switch state. -
Attribute change notifications for Shade and Light devices (@mrsmartypants)
Prior behavior was that if an identical back to back command was received, automations would not get re-triggered. For example if shade was already open and an open command was given, then an automation testing for state=open would not be re-triggered. That behavior is now changed in that the automation will get re-triggered. This change is to overcome potential virtual device synching issues with the actual device.Those with existing automations using these virtual devices should consider the impact.
-
Fix to vEdge Creator device Controls screen labels
The dreaded labels issue persists for all custom capabilities. However a ‘workaround’ has been provided and implemented here for the creator device so that proper labels are shown for the quantity, create, and inventory buttons. In order to see this fix, you may need to delete your creator device and recreate it via a Scan for nearby devices. You can safely do this without impacting your existing virtual devices. Note that this is purely optional.
I created a virtual switch using the vEdge creator and wanted to use this to trigger Alexa to make a sound. I can’t find the switch that I created in the list of routine trigger devices in Alexa. Any ideas on how to resolve this?
How do I update the driver from an old version? Is it automatic?
It will automatically update within 12 Hrs.
You can force it by trying to delete the old driver. You will get an error say it can’t be deleted because it is being used, but it will force the driver to update
Thank you.
If you are defining the ‘When this happens’ part of the Alexa routine, it will only be able to use certain device types such as contacts and motion sensors. So you won’t find switches listed there.
Switches are selectable for the ‘Action’ part of the routine.
So if I would recommend you create a virtual contact device. It has a switch included which mirrors the contact state (on==open, off==closed). That way you should be able to create an Alexa routine that can use it for either part of the routine definition.
Thank you, this works great now as a good replacement for the old “virtual thermostat” SmartApp 
Todd I’m lost were can I find this setting option?
Latest driver is installed and v2.5 on the device generator. I even created a new dimmer but not seeing anything.
Thanks as always for your contributions to the community.
In the device Controls screen in the upper right corner is a 3-vertical-dot menu. Tap it and then tap “Settings”. You should see the Dashboard State option. If it is not there, you may need to create a new device.