Raspberry Pi Zero W issues #453
Replies: 3 comments 2 replies
-
The hciDeviceId parameter is only useful if you have multiple BlueTooth controllers. Unless you have a 3rd party USB BT device plugged into your Pi Zero then there is only one controller and the ID is 0. Trying to use another ID is likely to yield the error you are seeing. The Room-Assistant documentation does state that it is possible (with performance impact) to use Classic and BLE on the same controller but given that the Zero-W also shares the BT data bus with the WiFi controller then trying to use BLE with Classic is likely to make the obvious bus contention problems significantly worse. I am facing similar issue and have tried to use a secondary USB BT controller for BLE but have faced bugs (introduced summer 2020) in the core Raspian distro that have broken this setup and I have posted a fix in another thread. Even with this fix I am facing reliability issues and I think the shared UART with WiFi is a likely cause. I have some Banana Pi M2's on order (a modernised Pi Zero) to see if that improves the situation but for now I have cut back my expectations of the Pi Zero to the bare basics. |
Beta Was this translation helpful? Give feedback.
-
Can you post the output that you receive when you run |
Beta Was this translation helpful? Give feedback.
-
Oh man. I apologize for bringing noob issues to the discussion. Long story short, I was confused as to how the pi zero communicated with home assistant. The log I provided was from my HA add-on (not the Pi) and my PC has a Bluetooth dongle that, I just realized, works only with Windows. So, the HA add-on had no bluetooth receiver for my debian vm. I have it running properly on my pi zero now, and MQTT discovered my devices. I'll keep my mouth shut for a bit and try to figure things out before causing any more trouble around here. I have a Pi4 that I'll try this out on as well. I see that Room Assistant sees that I'm Home in my Lovelace card. This is great. |
Beta Was this translation helpful? Give feedback.
-
I am trying to get Room Assistant to work on a Pi Zero W. Whenever I include BLE in my config, there is an
Error: ENODEV, No such device
. I'll post my config and then my logs. Even when I don't include BLE, I have a separate issue. But for now I'll just post this BLE issue in hopes someone will take a look....worked for another user in these threads, but I'm still having issues.
Log
I have tried
for both BTC and BLE at the same time, and I have tried the hci for BTC: 0 and BLE: 1, and I then tried BTC: 1 and BLE: 0, which is what the config currently shows.
Beta Was this translation helpful? Give feedback.
All reactions