Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bluetooth integration adds just bluetooth adapter #79019

Closed
and7ey opened this issue Sep 23, 2022 · 15 comments
Closed

Bluetooth integration adds just bluetooth adapter #79019

and7ey opened this issue Sep 23, 2022 · 15 comments

Comments

@and7ey
Copy link

and7ey commented Sep 23, 2022

The problem

Bluetooth integration adds just bluetooth adapter, no other devices are discovered.
Tried both with bluetooth: added to configuration.yaml and without this part.

What version of Home Assistant Core has the issue?

2022.9.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

bluetooth

Link to integration documentation on our website

No response

Diagnostics information

config_entry-bluetooth-4d02788e3b0deddc395793e79af15632.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

A message handler raised an exception: 'org.bluez.Device1'. Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/dbus_fast/message_bus.py", line 736, in _process_message result = handler(msg) File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/manager.py", line 804, in _parse_msg condition_callback() File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/manager.py", line 664, in callback self._properties[device_path][defs.DEVICE_INTERFACE][property_name] KeyError: 'org.bluez.Device1'

Additional information

Raspberry Pi 3b, built-in bluetooth-adapter, HAOS
bluetoothctl works well, multiple devices are found

@and7ey
Copy link
Author

and7ey commented Sep 24, 2022

Something similar is described here - #76914, but I use the latest release and the problem is still there. Reboot doesn't help.

@homeassistant
Copy link
Contributor

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (bluetooth) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)


bluetooth documentation
bluetooth source
(message by IssueLinks)

@kloemi
Copy link

kloemi commented Sep 30, 2022

Same here, fresh installation of latest release on pi 400, using balena etcher.
config_entry-bluetooth-4d02788e3b0deddc395793e79af15632.json.txt
No device is shown, only the bt adapter

@bdraco
Copy link
Member

bdraco commented Sep 30, 2022

Which integration provides support for the device you are expecting to be found that is missing?

@kloemi
Copy link

kloemi commented Oct 1, 2022

I'd like to use BT for device_tracker and was expecting to find entities at devices&services>bluetooth. But there shows up the device only and no entity.
grafik

I'm new at HA if that is a configuration issue maybe you have a hint.

@and7ey
Copy link
Author

and7ey commented Oct 1, 2022

I wanted to see full list of Bluetooth devices and later to use it with SP110E - roslovets/SP110E-HASS#6

@bdraco
Copy link
Member

bdraco commented Oct 1, 2022

The bluetooth integration offers way for integrations to access the bluetooth stack. Each device needs its own integration.

@kloemi
Copy link

kloemi commented Oct 2, 2022

At my case ist was an issue with the device tracker configuration. Thx for you reply. After copying a full configuration the known_devices was created, and entities exist.

@and7ey
Copy link
Author

and7ey commented Oct 3, 2022

@kloemi could you please describe in details what you did?

@groenmarsmannetje
Copy link

groenmarsmannetje commented Oct 5, 2022

The main problem here is that the documentation of the Bluetooth integration is lagging good explanation about what it is and how it is expected to work from end-user perspective. Also taking in mind that it follows a different approach compared to other integrations. For instance network router integrations show device tracker entities of connected devices as part of that integration and an integration like IKEA Tradfri will show all devices that are connected to the IKEA hub. So it is not strange that something like that is also what users would expect from the Bluetooth integration. This requires more explanation.

A reference to all related integrations that make use/depend on this integration could also help.

Also the Bluetooth tracker documentation doesn’t mention anything about this. For that integration we need to guess or assume that it does or doesn’t make use of this new Bluetooth integration. It is really very confusing.

@kloemi
Copy link

kloemi commented Oct 6, 2022

Im fully ack with your comment @groenmarsmannetje. For me as newby my expectation was to see anything happen. Bluetooth was installed per default, then i tried to add bluetooth tracker via gui. There was the hint to edit the configuration. But with sample from bt tracker documentation I did not get it working. My expectation was to see afterwards a new entitie or at least known_devices. But nothing happened. At the end i copied a configuration snipped from a forum entry. So behaviour was kind of different then with integrations.

@and7ey
Copy link
Author

and7ey commented Oct 7, 2022

then i tried to add bluetooth tracker via gui.

could you please clarify how you tried to do that? I don't use UI and edit everything thru configuration.yaml. How should I add devices in such case?

At the end i copied a configuration snipped from a forum entry.

could you please share the link or paste the configuration here?

@groenmarsmannetje
Copy link

groenmarsmannetje commented Oct 7, 2022

I disabled the Bluetooth Device tracker because it was no longer working after one of the HA releases a couple of months back in which almost all existing Bluetooth integrations broke. As far as I know the Bluetooth Device Tracker is stil not migrated to the new Bluetooth solution. Which wonders me… why would you keep an integration that doesn’t work anymore.

But do not shoot me on that because I also have trouble to understand how this is all currently working or not working. A lot of people seem to be busy with it and the HA Core team is celebrating constantly on new BT stuff that they introduced in last couple of releases… but it seems to me that they have forgotten that they broke something which has not been repaired yet. They are certainly not following a fix first and enhance later strategy.

@friedpenguin
Copy link

friedpenguin commented Oct 9, 2022

If you are using a Supervisor install (Advanced, not HA OS) you need to make sure to enable dbus-broker as per the documentation. I chased my tail a while trying to find that when it's right in the documentation. And don't forget to reboot.
https://github.com/bus1/dbus-broker

@issue-triage-workflows
Copy link

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 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 21, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Mar 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants