Closed pieterbos closed 4 years ago
Hey there @zxdavb, mind taking a look at this issue as its been labeled with a integration (honeywell
) you are listed as a codeowner for? Thanks!
Hey there @zxdavb, mind taking a look at this issue as its been labeled with a integration (evohome
) you are listed as a codeowner for? Thanks!
@pieterbos
As you indicate, the honeywell integration no longer supports the Round Connected Thermostat. However, evohome is intended to fully support it.
evohome offers a lot more functionality than honeywell (except, currently, for high-precision temperatures), and as part of that the entity name
(and thus entity_id
) changed to climate.<location name>
from climate.thermostat
. Feel free to change it back to 'Huis' as this is not the cause of your issue.
I have tested someone's Round Connected Thermostat system on 0.99.3, and as you can see (screenshot below) it is working for me.
However, there are known problems with this part of the code:
File "/usr/src/homeassistant/homeassistant/components/evohome/__init__.py", line 309, in setpoints
day = self._schedule["DailySchedules"][day_of_week]
... that have been addressed in HA 0.100 (currently in beta).
So, two questions for you:
I am happy to work with you to get this working, and if it remains an issue with v0.100, then the best/quickest way froward would be for you to give me temporary access to you system via the TCC website:
Account tab
, then Grant User Access
buttonDM me via the forum, if you're willing to take that option, and I'll provide my email address - you can easily remove my access when we're finished.
Further info: all my testing has been on RoundModulation
, but your system is RoundWireless
.
So there is this bug:
if broker.config["zones"][0]["modelType"] == "RoundModulation":
Which I can fix:
if broker.config["zones"][0]["zoneType"] == "Thermostat":
Thank you for the detailed explanation and fixing the bug. It sounds like that could very well be the cause. I indeed have the wireless on/off, as the district heating system here does not work with a modulating thermostat. the valve I have can only be opened or closed, not set halfway.
I have no schedule set - I use automations for that.
I'm willing to test a beta version. I'm not sure how to do that with hass.io though.
the district heating system here does not work with a modulating thermostat. the valve I have can only be opened or closed, not set halfway.
I think it's the modulation of the temperature of the circulating volume (like OpenTherm)? On/off switches do TPI (turn pump on/off more/less often per hour), and the boiler will modulate that (i.e. throttle the burner). In neither case is a water valve open halfway - although smart TRVs will do this.
Your issue is that you have no control over the district heating - you have to take the heated water from them at whatever temp they have decided, no?
Anyway, closing this Issue as I think I am sure it has been fixed with #27168, which will be part of 0.100.0b1. I will leave it up to you to work out hoe to use the latest beta with hass.io (I have been told this is possible, but I don't use hass.io personally).
Thanks for your very useful debug logs.
Exactly, I have to take the heated water at whatever temperature it comes, although usually it's very hot. The only thing the thermostat can control is whether to fully open or close the valve. That's why I have to use the wireless on/off model.
Anyway, thanks for fixing this!
Just updated to 0.100b3. It works, I can now control the temperature again!
EDIT: Created new issue #27768 for this, since this one is closed
Using Home Assistant 0.100.2 on hassio, I also get this error.
From the first line below, it can be seen that the code which is delivered in the issue above, is already active (because of the "(EvoTouch)" being printed).
Unfortunately it still does not seem to work with the round wireless connected.
2019-10-16 23:20:02 DEBUG (MainThread) [homeassistant.components.evohome.climate] Found the Location/Controller (EvoTouch), id=1228617, name=huiskamer (location_idx=0)
2019-10-16 23:20:02 DEBUG (MainThread) [homeassistant.components.evohome.climate] Found the Thermostat (RoundWireless), id=1228616, name=Thermostat
2019-10-16 23:20:02 ERROR (MainThread) [homeassistant.components.climate] evohome: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 292, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 446, in async_device_update
await self.async_update()
File "/usr/src/homeassistant/homeassistant/components/evohome/climate.py", line 396, in async_update
await super().async_update()
File "/usr/src/homeassistant/homeassistant/components/evohome/climate.py", line 268, in async_update
await super().async_update()
File "/usr/src/homeassistant/homeassistant/components/evohome/__init__.py", line 463, in async_update
self._device_state_attrs = {"setpoints": self.setpoints}
File "/usr/src/homeassistant/homeassistant/components/evohome/__init__.py", line 415, in setpoints
day = self._schedule["DailySchedules"][day_of_week]
IndexError: list index out of range
Home Assistant release with the issue: 0.99.3
Last working Home Assistant release (if known): 0.94.1
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io
Integration: Both honeywell and evohome have problems with this version
Description of problem: I used the honeywell component in version 0.94.1 to control my Honeywell Round Connected Wireless On/Off thermostat. And this has worked for many versions. It stopped working, in the sense that it does not even add an entity. All it does is printing:
I noticed this component was deprecated in favor of evohome. I tried switching to evohome. I can now see the temperature, I can switch hvac_mode from heat to off and back. I can set preset modes. But there is no possible way to set a temperature, other than controlling hvac_mode with off and heat.
there is also no temperature setpoint visible in the state of the entity at all. It does not matter which present_mode I select.
The log contains a traceback with the evohome component, see below.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant): When trying with evohome:And with honeywell:
Traceback (if applicable):
With evohome, the following traceback appears:
Note that there is no entity 'climate.thermostat'. There is only 'climate.huis'. I tried renaming the location to 'thermostat'. That did not help at all, it merely changes the error to 'Update for climate.thermostat_2 fails'.
Also sometimes:
Additional information:
State of evohome entity climate.huis:
Note the lack of a temperature setpoint. Also note that I set the preset mode to 'home', but evohome set the systemModeStatus to 'day off'!
Log with evohome: