Closed lmamakos closed 4 years ago
Hey there @bdraco, mind taking a look at this issue as its been labeled with a integration (elkm1
) you are listed as a codeowner for? Thanks!
I've setup a version with a potential fix can be installed in custom_components
Step 1: Add the following to your configuration.yaml
logger:
default: info
logs:
custom_components.elkm1: debug
Step 2
cd /config
mkdir custom_components
cd custom_components
git clone https://github.com/bdraco/elkm1
Step 3: Restart
I have tested the version cloned from your git repo, and it seems to have resolved the issue. In the states developer tool, I see
hvac_modes:
- 'off'
- heat
- cool
- auto
- fan_only
min_temp: 1
max_temp: 99
target_temp_step: 1
fan_modes:
- auto
- 'on'
current_temperature: 68
target_temp_high: 73
target_temp_low: 68
current_humidity: 0
fan_mode: auto
aux_heat: 'off'
name: Thermostat
mode: 1
hold: false
fan: 0
current_temp: 68
heat_setpoint: 68
cool_setpoint: 73
humidity: 0
index: 1
friendly_name: Thermostat
supported_features: 74
and
This seems to have resolved the issue with the thermostat. I'll poke around a bit further to see if anything was adversely affected.
Tested as well, working great. Thanks again for all you do, Nick.
The problem
The climate entity for ElkM1 attached thermostats seems broken in a recent version 0.108.3 with absurbdly high temperatures .
The attributes from my climate device look like:
Environment
Running
Home Assistant 0.108.3
in the form of the Home Assistant generated docker container, deployed in docker on Ubuntu 18.04. The Elk M1 panel is connected to Home Assistant via its Ethernet interface.Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
Lovelace climate UI: