Oh yes… I’ve misunderstood mf_social reply and I’m very sorry for that.
Problem solved guys.
What I cannot understand is why it stopped working with release 0.116… Is this a brand new requirement?
Not really a breaking change, since the overall logic did not change. Arguments that were previously mandatory for sensors of this integration are still mandatory and optional arguments remain optional.
However, we now enforce those mandatory arguments to be present, since otherwise this integration creates entities that cannot do anything, e.g., the sensor for IPv4 addresses cannot do anything if no network interface is specified from which to take the IP.
If the integration fails to load, check the log to see which arguments are missing in your configuration. The documentation also has been updated to clearly show which arguments are mandatory.
anyone else seeing all Bluetooth devices being not_home only?
have I missed a breaking change anywhere…?
not sure if this happened after updating to 116.xx or supervisor maybe.
2020-10-22 12:33:45 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/bluetooth_tracker/device_tracker.py", line 177, in update_bluetooth
await perform_bluetooth_update()
File "/usr/src/homeassistant/homeassistant/components/bluetooth_tracker/device_tracker.py", line 140, in perform_bluetooth_update
devices = await hass.async_add_executor_job(discover_devices, device_id)
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/bluetooth_tracker/device_tracker.py", line 57, in discover_devices
result = bluetooth.discover_devices(
File "/usr/local/lib/python3.8/site-packages/bluetooth/bluez.py", line 26, in discover_devices
device_id = _bt.hci_get_route()
OSError: [Errno 19] No such device
