RPi 3B bluetooth causes WiFi issues #520
Comments
|
Also: nothing in home-assistant.log |
|
|
|
No problems with bluetooth+ethernet, so it's definitely the bluetooth+wifi combo that has issues. |
|
Just throwing in my 2 cents on personal experience with the same issue. I agree that I've also had this same wifi problem with RP3 and RP zero w when bluetooth_tracker is enabled. Turning off bluetooth_track resolves the network connectivity problem. I've found bluetooth_tracker is best used with a wired network connection, so you don't have network connectivity issues. I also experienced the same wifi issues trying to do bluetooth tracking with this other project called Monitor on a RP zero w and RP3. https://github.com/andrewjfreyer/monitor I think it's either a hardware related issue with trying to use BT and wifi at the same time or both projects are using the same wifi and BT driver with the same bug. |
|
I've moved on to Ethernet with the setup I saw this with, but I plan to try this out with HassOS 3.8 soon with another. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Still going to have a look sometime. |
|
You see the issue that I all time said, RaspberryPi is bad hardware. There are much better chip manufacturers around as Broadcom. On data paper, the RPi looks fine but most people don't know the price which this data papers have. You can never use all resources at the same time. |
|
I'm still not using bluetooth+wifi, but bluetooth was broken even with ethernet for a long time. It works again with 3.13, so now's again a time when it would make sense to test this again if someone feels like it. I don't have plans to move to wifi any time soon though. |
HassOS release with the issue:
3.7 32-bit. Also tested with 3.7 64-bit, 2.5 64-bit, 2.12 32-bit, and 3.6 32-bit.
Supervisor logs:
Journal logs:
Kernel logs:
Description of problem:
Enabling bluetooth scan nearly kills wifi. The connection doesn't drop entirely, but seemingly always whenever there is a bluetooth scan going on, wifi ping times go to several seconds. Bluetooth and otherwise config is minimal, fresh hass.io image setup with just onboarding done and this added to configuration.yaml (via configurator or ssh addon), no other addons or hardware:
Normally when bluetooth scanning is not enabled pings look like:
After enabling bluetooth, they start to go like:
...and sometimes ping loss, and even higher times. Naturally, net access of HA including SSH and web is very shaky in this state.
I have tested this with three different RPi 3B's, and happens the same with all of them. Booting off USB SSD vs SD (and no other USB devices plugged) makes nSSH and web accesso difference. All three RPis have been USB boot enabled, i.e.
program_usb_boot_mode=1.I have successfully used bluetooth on some of these RPis before. But it is possible that at that time they have been connected via ethernet, not wifi. Can't remember. And it could have been even pre-HassOS (i.e. ResinOS) times.
I've found a couple of things that I could try out, but I'm not sure how do I go about it in a RPi3 HassOS setup, i.e. where exactly on the SD card to add the files:
raspberrypi/linux#1552 (comment)
greg-erskine/pCP-github@0083f17
I suppose the modprobe option would be doable via cmdline.txt, will try that out.
Will also try with ethernet soon and report back.
Anyway, help and debugging instructions including where to try out the above settings would be welcome.
The text was updated successfully, but these errors were encountered: