Reactor setting thermostat setpoint issue/bug

I’ve discovered an apparent Reactor bug (maybe “limitation” is a better word) with regards to setting device values. I have a thermostat (via a Vera plugin) that has two child variables with the same name:

“urn:upnp-org:serviceId:TemperatureSetpoint1_Cool”, “CurrentSetpoint”
“urn:upnp-org:serviceId:TemperatureSetpoint1_Heat”, “CurrentSetpoint”

In a Reactor Activity, if I change ONE of these values (using the UI) the result via the Device Action is that BOTH of these values change on the thermostat.

Now I can work around this by not using a Device Action but running Lua or even a HTTP URL instead, but I thought I should point out the issue.

Logic summary?

Mea culpa. Found it. Thanks for the response.