Bose Soundtouch can't handle multiple
AtmanActive opened this issue · comments
The problem
I had two Bose Soundtouch 10 speakers paired as a stereo pair (B1) working with Home Assistant (HA) flawlessly for a year. Then I added Bose Soundtouch Wireless Link Adapter (B2) to my network and HA and since then it stopped working. I checked, double-checked, tripple-checked the config files and my scripts and it would still fail. Today I decided to test the whole setup by unplugging B2 from power and all of a sudden, my B1 pair is again working correctly with HA.
So, my only conclusion right now is that HA's Soundtouch integration doesn't work correctly when there are multiple Soundtouch devices involved.
Bose's own Soundtouch app on Android/IOS is working flawlessly with all three speakers.
HA is failing silently, nothing in the logs, toast shown 'your script has been executed', but no commands ever reach the device(s).
I am a professional software developer myself so if anyone can provide any clues on how to debug this, I can try to shed some more light on the problem.
For now, instead of enjoying HA control of several different Soundtouch systems in several rooms, I have to keep one of them (B2) switched off just to have the other (B1) working with HA. :-(
What version of Home Assistant Core has the issue?
2022.5.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Bose Soundtouch
Link to integration documentation on our website
https://www.home-assistant.io/integrations/soundtouch
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
soundtouch documentation
soundtouch source
(message by IssueLinks)
I've managed to fix the problem by changing the IP address of the Soundtouch adapter. Initially, my DHCP server was configured to assign IPs one next to each other, so configuration.yaml looked like this:
media_player:
- platform: soundtouch
host: 192.168.150.237
port: 8090
name: Soundtouch_Living_Room_L - platform: soundtouch
host: 192.168.150.238
port: 8090
name: Soundtouch_Living_Room_R - platform: soundtouch
host: 192.168.150.239
port: 8090
name: Soundtouch_adapter
and that's when it was failing in Home Assistant but was working fine in the Soundtouch android/ios app. Then, out of pure desperation, I changed my home DHCP server to give another, non-sequential IP to Soundtouch adapter, so my configuration.yaml now looks like this:
media_player:
- platform: soundtouch
host: 192.168.150.237
port: 8090
name: Soundtouch_Living_Room_L - platform: soundtouch
host: 192.168.150.238
port: 8090
name: Soundtouch_Living_Room_R - platform: soundtouch
host: 192.168.151.249
port: 8090
name: Soundtouch_adapter
and now it is working correctly! Both Soundtouch media players work as expected from both Home Assistant and the Soundtouch app on android/ios.
Atman, I have multiple Bose systems and I am struggling to configure in HA. Would you be willing to help me out?
Yeah sure.
But, the latest development is that Home Assistant's integration now went fully automatic and requested that I remove all manual configuration from .yaml, which I did. After that, all of my automations stopped working simply because of entity_id mismatch. So I had to manually rename each and every Soundtouch related entity to match the old names I had in .yaml and now it is all working correctly here. No complaints.
I didn't try to return the IP address of the third device to it's old address yet. I'll test that in the following days and report back here.
Bottom line: things have changed since I experienced problems. Could very well be that my problems did stem from the fact that, for a while, I had both manual .yaml configuration and auto-discovery running at the same time.
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.