G8YTZ
(Justin)
March 27, 2019, 5:29pm
1
I’ve found what I think is a bug in Thermostat Operation Modes, any ideas or suggestions would be welcome. YouTube link shows the live issue v0.91 and previous versions.
opened 10:59PM - 23 Mar 19 UTC
closed 08:01PM - 11 Jul 19 UTC
integration: knx
stale
<!-- READ THIS FIRST:
- If you need additional help with this template please r… efer to https://www.home-assistant.io/help/reporting_issues/
- Make sure you are running the latest version of Home Assistant before reporting an issue: https://github.com/home-assistant/home-assistant/releases
- Frontend issues should be submitted to the home-assistant-polymer repository: https://github.com/home-assistant/home-assistant-polymer/issues
- iOS issues should be submitted to the home-assistant-iOS repository: https://github.com/home-assistant/home-assistant-iOS/issues
- Do not report issues for components if you are using custom components: files in <config-dir>/custom_components
- This is for bugs only. Feature and enhancement requests should go in our community forum: https://community.home-assistant.io/c/feature-requests
- Provide as many details as possible. Paste logs, configuration sample and code into the backticks. Do not delete any text from this template!
-->
**Home Assistant release with the issue:**
<!--
- Frontend -> Developer tools -> Info
- Or use this command: hass --version
--> 0.91
**Last working Home Assistant release (if known):**
N/A Ongoing issue
**Operating environment (Hass.io/Docker/Windows/etc.):**
<!-- HASS.io running in Docker
Please provide details about your environment.
--> INtel NUC8i3 Ubuntu 18.04.2
**Component/platform:**
<!-- KNX Thermostat
Please add the link to the documentation at https://www.home-assistant.io/components/ of the component/platform in question.
--> https://www.home-assistant.io/components/climate.knx
**Description of problem:**
Using the Thermostat Card in Lovelace UK in YAML Mode:
Sample Lovelace Configuration of two thermostats are below.
First Issue: when the HASS.io boots, all thermostats are shown in ECO mode, but actually they are in HEAT mode.
Second Issue: If you change the operating mode of one thermostat via HASS.io , all the thermostats in the group should change as they use the same sending group address for all thermostats on a floor. However, If you change the operation mode on the Gira TS3+ Room Controller then HASS.io shows the correct operation mode on all thermostats in the group as expected. I would add the TS3+ is configured for 120 second status updates, this has been allowed for.
Third Issue: Hass.io sometimes displays the wrong operating mode (incorrect thermostat colour) even when selected via HASS.io
All of the issues above are 50/50 reliable, works about half of the time, so I suspect some kind of timing issue with the HASS.io messaging bus.
type: horizontal-stack
cards:
- type: vertical-stack # column 1
cards:
- type: thermostat
entity: climate.study_climate
name: Study
- type: thermostat
entity: climate.lounge_south_climate
name: Lounge South
- type: thermostat
entity: climate.lounge_north_climate
name: Lounge North
**Problem-relevant `configuration.yaml` entries and (fill out even if it seems unimportant):**
```yaml
Configuration.yaml looks like the following for the ground floor, you will note that the Operation Mode is the same group address for all thermostats on the ground floor, same for the first floor, exceptions are the bathrooms that have their own individual schedules
knx:
routing:
local_ip: '192.168.0.24'
fire_event: true
fire_event_filter: ["0/0/*", "0/1/*", "0/2/*","0/3/*", "0/4/*", "0/5/*", "0/6/*", "1/0/*", "3/1/*", "3/2/*", "3/3/*", "3/4/*", "3/5/*", "3/6/*", "3/7/*", "4/1/*", "5/0/*", "5/1/*", "5/2/*", "5/3/*"]
state_updater: true
climate:
- platform: knx
name: 'Study Climate'
temperature_address: '3/1/1' #Measured Temperature Gira TS3+ Output 64
target_temperature_address: '3/4/1' #Setpoint Command Value Gira TS3+ Input 80
target_temperature_state_address: '3/3/1' #Setpoint Status Value Gira TS3+ Output 104
operation_mode_address: '3/7/3' #Operating Mode Command Gira TS3+ Input 82
operation_mode_state_address: '3/6/1' #Operating Mode Status Gira TS3+ Output 90
on_off_state_address: '3/2/1' #command group to Theben HMT12 Gira TS3+ Output 96
max_temp: 25.0
min_temp: 5.0
- platform: knx
name: 'Dining & Hall Climate'
temperature_address: '3/1/2'
target_temperature_address: '3/4/2'
target_temperature_state_address: '3/3/2' #Setpoint Status Value
operation_mode_address: '3/7/3'
operation_mode_state_address: '3/6/2'
on_off_state_address: '3/2/2'
max_temp: 25.0
min_temp: 5.0
- platform: knx
name: 'Lounge North Climate'
temperature_address: '3/1/5'
target_temperature_address: '3/4/5'
target_temperature_state_address: '3/3/5' #Setpoint Status Value
operation_mode_address: '3/7/3'
operation_mode_state_address: '3/6/5'
on_off_state_address: '3/2/5'
max_temp: 25.0
min_temp: 5.0
- platform: knx
name: 'Lounge South Climate'
temperature_address: '3/1/4'
target_temperature_address: '3/4/4'
target_temperature_state_address: '3/3/4' #Setpoint Status Value
operation_mode_address: '3/7/3'
operation_mode_state_address: '3/6/4'
on_off_state_address: '3/2/4'
max_temp: 25.0
min_temp: 5.0
- platform: knx
name: 'Kitchen Climate'
temperature_address: '3/1/3'
target_temperature_address: '3/4/3'
target_temperature_state_address: '3/3/3' #Setpoint Status Value
operation_mode_address: '3/7/3'
operation_mode_state_address: '3/6/3'
on_off_state_address: '3/2/3'
max_temp: 25.0
min_temp: 5.0
```
**Traceback (if applicable):**
```
```
**Additional information:**
Fell free to contact me is you would like some more information, or a demonstration via web desktop share. I live in SE London.