Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thermostat "Emergency Heat" mode reports as "Cooling" #45

Open
jdanders opened this issue Jan 2, 2025 · 2 comments
Open

Thermostat "Emergency Heat" mode reports as "Cooling" #45

jdanders opened this issue Jan 2, 2025 · 2 comments

Comments

@jdanders
Copy link

jdanders commented Jan 2, 2025

Describe the bug
My thermostat reports "Cooling" when in "Emergency Heat" mode. That's sort of the opposite :)

To Reproduce
Fetch the equipement info and check equipment.mode

: equipment.mode
<ThermostatOperationMode.COOLING: 3>

Expected behavior
The contents of the equipment info indicate the right status but wrong value:

{'constraints': {'enumText': ['Heating       ',
                              'Cooling       ',
                              'Auto          ',
                              'Fan Only      ',
                              'Off           ',
                              'Emergency Heat'],
                 'enumTextIcon': ['ic_thermo_heating.png',
                                  'ic_thermo_cooling.png',
                                  'ic_thermo_auto.png',
                                  'ic_fan.png',
                                  'ic_device_off.png',
                                  'ic_thermo_emergency_heat.png'],
                 'lowerLimit': 0,
                 'upperLimit': 5},
 'status': 'Emergency Heat',
 'value': 1}

Additional context
I'll keep looking into this issue myself and update as I can.

@w1ll1am23
Copy link
Owner

Hmm thats a complicated one. So its saying reference index 1 which is why we are showing cooling... guess we could add in an extra check for "Emergency Heat" being the status.

@jdanders
Copy link
Author

See my proposed fix. I figure since it's data from the server that is wrong, the best thing to do is to sanitize it when it comes in. I'm not sure if this is the right place or right coding style, but it fixes the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants