Closed JojjeErvalla closed 6 years ago
Second that! Having the same issue. Does not import all sensors such as Fibaro Multisensor anymore. My automations based upon Lux (LX) does not work anymore. General functions works such as turning on lights/switches.
Home Assistant release (hass --version): 0.58.1
Python release (python3 --version): Python 3.6.0
Log Details (ERROR)
Thu Nov 23 2017 07:46:18 GMT+0100 (W. Europe Standard Time)
Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 55, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/tellduslive.py", line 101, in update
self._sync()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/tellduslive.py", line 141, in _sync
identify_device(device))
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/tellduslive.py", line 114, in identify_device
if device.methods & DIM:
TypeError: unsupported operand type(s) for &: 'NoneType' and 'int'
I hope/think this will be fixed by the latest version of the tellduslive library, which has proper locking to protect the internal state. Please reopen if not fixed in next release.
Does this meen it will be included in the next Home Assistant version?
This is fixed here: https://github.com/home-assistant/home-assistant/issues/10922 (duplicate)
@JojjeErvalla, sorry for not responding, but yes, the fix is now included in the latest version.
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.58.1Python release (
python3 --version
): Python 3.5.3Component/platform: Telldus Live
Description of problem: Telldus Live component throws an error when HA starts up
Expected: Expected no error :)
Problem-relevant
configuration.yaml
entries and steps to reproduce: