sampsyo
commented
5 years ago Huh; that's really strange! I don't have a great answer for why this would happen on your system. For the first error, that error indicates that the given key isn't in the ACMode enum that I wrote. But at least here on my machine, it really does seem to be present:
>>> import wideq
>>> wideq.ACMode
<enum 'ACMode'>
>>> wideq.ACMode('@AC_MAIN_OPERATION_MODE_ENERGY_SAVING_W')
<ACMode.ENERGY_SAVING: '@AC_MAIN_OPERATION_MODE_ENERGY_SAVING_W'>In contrast, this is what an invalid key does:
>>> wideq.ACMode('foo')
ValueError: 'foo' is not a valid ACMode
[...]Any chance you have a modified or out-of-date version of the library?
bifurcated
jsmath
gulfy32
I just set up SmartThinQ on HomeAssistant, and was having trouble seeing the entity. After some fiddling around, I realized that it was because my AC unit was set to Energy Saver/Eco mode, and hass-smartthinq didn't like it. I changed the mode to "cool" and was able to add the entity.
Here's the homeassistant log from when my AC unit was in Energy Saver mode:
2019-05-25 15:16:16 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved ValueError: '@AC_MAIN_OPERATION_MODE_ENERGY_SAVER_W' is not a valid ACMode
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/src/app/homeassistant/helpers/entity.py", line 225, in async_update_ha_state self._async_write_ha_state() File "/usr/src/app/homeassistant/helpers/entity.py", line 248, in _async_write_ha_state state = self.state File "/usr/src/app/homeassistant/components/climate/init.py", line 192, in state if self.current_operation: File "/config/custom_components/smartthinq/climate.py", line 161, in current_operation mode = self._state.mode File "/config/deps/lib/python3.7/site-packages/wideq.py", line 1028, in mode return ACMode(self.lookup_enum('OpMode')) File "/usr/local/lib/python3.7/enum.py", line 310, in call return cls.new(cls, value) File "/usr/local/lib/python3.7/enum.py", line 564, in new raise exc File "/usr/local/lib/python3.7/enum.py", line 548, in new result = cls.missing(value) File "/usr/local/lib/python3.7/enum.py", line 577, in missing raise ValueError("%r is not a valid %s" % (value, cls.name)) ValueError: '@AC_MAIN_OPERATION_MODE_ENERGY_SAVER_W' is not a valid ACMode 2019-05-25 15:18:44 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140432664712304] '@AC_MAIN_OPERATION_MODE_ENERGY_SAVING_W'
When trying to set the operation mode to "Eco" (which appears as a valid operation mode in the HA dropdown) via HA, this is the error I received:
Traceback (most recent call last): File "/usr/src/app/homeassistant/components/websocket_api/commands.py", line 121, in handle_call_service connection.context(msg)) File "/usr/src/app/homeassistant/core.py", line 1141, in async_call self._execute_service(handler, service_call)) File "/usr/src/app/homeassistant/core.py", line 1163, in _execute_service await handler.func(service_call) File "/usr/src/app/homeassistant/helpers/entity_component.py", line 194, in handle_service required_features File "/usr/src/app/homeassistant/helpers/service.py", line 316, in entity_service_call future.result() # pop exception if have File "/usr/src/app/homeassistant/helpers/service.py", line 337, in _handle_service_platform_call await getattr(entity, func)(*data) File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(self.args, **self.kwargs) File "/config/custom_components/smartthinq/climate.py", line 181, in set_operation_mode self._ac.set_mode(mode) File "/config/deps/lib/python3.7/site-packages/wideq.py", line 914, in set_mode mode_value = self.model.enum_value('OpMode', mode.value) File "/config/deps/lib/python3.7/site-packages/wideq.py", line 688, in enum_value return options_inv[name] KeyError: '@AC_MAIN_OPERATION_MODE_ENERGY_SAVING_W'