Closed mmotley999 closed 6 years ago
I've found a workaround by modifying somecomfort client.py to return "idle" if the equipment output status is "None". I'll verify that I have control over the temperature setpoints tonight, and then post this over at the somecomfort github site. Frankly, I have no clue if "idle" is even the correct thing to return here, but at least the thermostat did magically appear in HASS upon restart.
@property
def equipment_output_status(self):
"""The current equipment output status"""
if self._data['uiData']['EquipmentOutputStatus'] == 0:
if self.fan_running:
return "fan"
else:
return "off"
if self._data['uiData']['EquipmentOutputStatus'] == None:
return "idle"
else:
return EQUIPMENT_OUTPUT_STATUS[self._data['uiData']['EquipmentOutputStatus']]
Actually, the issue is resolved in version 0.5.0 of somecomfort, more elegantly:
@property
def equipment_output_status(self):
"""The current equipment output status"""
if self._data['uiData']['EquipmentOutputStatus'] in (0, None):
if self.fan_running:
return "fan"
else:
return "off"
return EQUIPMENT_OUTPUT_STATUS[self._data['uiData']['EquipmentOutputStatus']]
Any reason why the HASS honeywell component can't require 0.5.0 instead of 0.4.1?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Closing.. I originally hacked somecomfort to fix this, but was resolved for good in 0.59 with somecomfort 0.5.0.
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
): 0.51.2Python release (
python3 --version
): Python 3.4.2Component/platform: Honeywell Thermostat (climate), US version
Description of problem: I have a 4-zone system with 3 wired thermostats and 1 wireless thermostat (by wireless I mean using Honeywell's REDLink proprietary protocol).
So far I replaced 2 of the wired thermostat with WiFi models, and they are working great.
I just added a Honeywell REDLink Internet Gateway for the REDLink thermostat. I can see the thermostat on mytotalconnectcomfort and the phone app and control it fine, however it is not showing up in HASS.
I've tried to decipher the API protocol from somecomfort, as I do notice that on the mytotalcomfort website some features are "missing" with these REDLink thermostats (such as fan condition). I'm just not good enough in Python (although trying desperately to learn!) to make much sense of it.
Expected: The additional thermostat showing up in HASS.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info: The two thermostats in the traceback above (Office and Living Room) are WiFi wired thermostats and appear to be discovered fine. It seems to crash when trying to discover the REDLink thermostat.
I know this is probably not a common setup, and I'm willing to help troubleshoot if somebody could point me in the right direction with regards to the API. I also don't know if this belongs here or on the somecomfort side.... thanks in advance for an awesome piece of software.