Excellent, thanks for the fast response. I’ll probably not go down this rabbit hole yet, not until I have a matter temp sensor I want to use with the virtual thermostat. I’m currently using the zigbee sonoff thermometer with the mc child thermostat, and it’s working well. I have a number of zigbee (IKEA tradfri) outlets which act as zigbee repeaters but quite a few have failed over the years, I can see me replacing these with matter over thread outlets which might weaken my zigbee mesh and trigger me to swap other zigbee kit too 
@TAustin I am trying to use your vEdge Virtual Thermostat. I have no problem creating the thermostat but it is stuck in the Heating State or the Cooling State.
In the attached screenshot the Room Temperature is 77°F and the Thermostat is set at 56°F but it is still heating.
I have created several and they all do the same thing.
I started experimenting with this virtual thermostat this week and it seems to be working for me when the mode is auto, not tried “heat”.
You are correct it does work in the Auto mode but it is not working in the heating or cooling modes. I am using it to control an electric heater, so I only need it to work in the heating mode.
Just set the cooling temp super high and it will only ever do heat or idle ?
Just checked today and the virtual thermostat is working as expected in both the heat and cooling modes.
That’s bizarre. Do you think it was a SmartThings issue then?
It was operator error on my part. I created a 2nd virtual thermostat yesterday and had the same problem until I changed the “Mode Automation” in Setting to “Enable”. Then it worked just fine.
I must have changed that settings last week and didn’t realize it fixed what the problem I was having.
Sorry to have bothered you and thanks for sharing your hard work.
Hi,
I have couple of issues with virtual devices. Energy meters doesnt count total energy consumption. Earlier I used your separate virtual energy meter devices and they seemed to work correctly. Virtual energy meters also switched their icon to switch icon at some point.
I also tried to create virtual CO2 level sensor. Creator says “Creating device…” but nothing happens.
Thanks for the report. I will look into both of these. I tried also creating a CO2 device and there does indeed seem to be a problem. Let me get back to you.
Hi,
Could you add one more display mode (presentation) to the virtual thermostat?
I’m using this type device card in my virtual thermostat
- thermostat mode
- temperature measurement
- thermostat state
Definition of three different information dashboard (presentation):
"dashboard": {
"states": [
{
"component": "main",
"capability": "thermostatMode",
"version": 1,
"idx": 0,
"group": "main",
"values": [
{
"label": " {{thermostatMode.value}}",
"alternatives": [
{
"key": "off",
"value": "o",
"type": "inactive"
},
{
"key": "auto",
"value": "A",
"type": "active"
},
{
"key": "cool",
"value": "C",
"type": "active"
},
{
"key": "heat",
"value": "H",
"type": "active"
},
{
"key": "emergency heat",
"value": "EH",
"type": "active"
}
]
}
],
"composite": true
},
{
"component": "main",
"capability": "temperatureMeasurement",
"version": 1,
"idx": 0,
"group": "main",
"values": [
{
"label": " {{temperature.value}} {{temperature.unit}}"
}
],
"composite": true
},
{
"component": "main",
"capability": "thermostatOperatingState",
"version": 1,
"idx": 0,
"group": "main",
"values": [
{
"label": " {{thermostatOperatingState.value}}"
}
],
"composite": true
}
],
"actions": [],
"basicPlus": []
},
Hello again. To follow-up on your issues:
-
the virtual energy device that is created by the vEdge driver does not have any automation built in it. So you will not see any running total of energy consumption. If you need that, I’d recommend using the separate virtual energy meter driver that you referenced.
-
I found the problem with the CO device and am fixing it. By the way this should say ‘CO’ device, not CO2, because it is for Carbon Monoxide values, not Carbon Dioxide. I will attempt to fix this without causing other problems. While I’m at it, I’m also fixing a couple other things as well before I push out the driver update. One thing I noticed both in this driver and the separate virtual energy meter driver is that the energy reset control is returning a network error on the iOS app. It is still zero-ing out the consumption value as it should, but this network error is a bit annoying, so I’d like to see if I can get that fixed as well. Are you seeing this issue? It’s possible that it’s an app problem or a back-end glitch.