In the StateReport response for a thermostat which is in Heat mode (heat only, not auto), my Lambda is correctly returning the mode as HEAT with a 'lowerSetpoint' = HSP 60, and no other setpoints.
`[{'timeOfSample': '2018-05-04T16:14:48Z', 'uncertaintyInMilliseconds': 500, 'namespace': 'Alexa.TemperatureSensor', 'name': 'temperature', 'value': {'scale': 'FAHRENHEIT', 'value': 76.0}}, {'timeOfSample': '2018-05-04T16:14:48Z', 'uncertaintyInMilliseconds': 500, 'namespace': 'Alexa.ThermostatController', 'name': 'thermostatMode', 'value': 'HEAT'}, {'timeOfSample': '2018-05-04T16:14:48Z', 'uncertaintyInMilliseconds': 500, 'namespace': 'Alexa.ThermostatController', 'name': 'lowerSetpoint', 'value': {'scale': 'FAHRENHEIT', 'value': 60.0}}]`
Still when I check the device state from the Alexa app SmartHome-> Devices , it shows all 3 setpoints: Cool-to = older CSP when it was in auto mode, Target = old target, Heat-to = current HSP and Mode = Heat.
*Why does it keep showing all 3 setpoints? Shouldn't it show just the Heat-To value ?*
Similar behavior for a device switched from AUTO to COOL mode. Even if StateReport returns only the 'upperSetpoint' OR only the 'targetSetpoint' = CSP property with mode = COOL, the Alexa app shows both heat and cool setpoints.
I have also tried returning only a targetSetpoint property for HEAT and COOL modes, but observed same issue.
