-
Notifications
You must be signed in to change notification settings - Fork 465
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
Snapcast with a beacon scanner doesn't work #768
Comments
There is no data received on the client. Is the client connected over WiFI? Maybe your beacon thing interferes with your WiFi. |
Yes, the client is connected over WIFI, and yes I can ping while beaconing. You were right, without a beacon scanner average time for ping is 62ms, while with the scanner it is over 500ms. Beacon scanner interferes with the WIFI but don't know why though. Thanks for the help. |
There used to a problem with using WiFi and Bluetooth at the same time on the raspberry pi, there were many reports in the rpi forums. And I guess there still is a problem. I thought it was restricted to the pi zero w but I'm not 100% about that. |
I connected my RPI 4 to the internet through ethernet cable, it resolved the problem. I would still prefer to use WIFI as it is easier to set up. |
I believe the problem is specific to the wireless chip on the Raspberry Pi. You can use a USB WiFi dongle or USB Bluetooth dongle to workaround the issue. Doesn't sound like this is a bug in Snapcast. |
Describe the bug
I want to create a multi-room audio (something like this: https://www.home-assistant.io/blog/2016/02/18/multi-room-audio-with-snapcast/). Everything works fine with snapclient on the raspberry and snapserver on ubuntu. I want to also run a simple beacon scanner on raspberryPI to check how close it is to my phone (phone is a beacon emitter). Right after running a node script, snapcast starts to error, when I stop the node script snapcast gets back to normal and I hear the music again.
Steps to Reproduce
Environment details
Attach logfile if applicable
The text was updated successfully, but these errors were encountered: