-
Notifications
You must be signed in to change notification settings - Fork 52
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
Doesnt work with Sonos Playbar? #2
Comments
@amitgandhinz - do you have a Sonos Sub as well (paired with the playbar) or do you maybe even also pair another set of speakers (play1, play3 or play5's) with the playbar to a 5.1 surround home cinema setup? |
@fwboettger Thanks for getting back to me. The only Sonos device i have is the Playbar. No sub or play1/3/5's. It randomly started finding the device the other day (ie no longer errors). However, the controls dont turn the speaker on/off. Doing so would be a nice way to mute the TV via Siri Homekit. Thanks |
@amitgandhinz - and the name of the room / the zone you've given in your Sonos smartphone/tablet/desktop app is exactly "Family Room"? |
I have a similar issue. In my case I successfully setup Homebridge and homebridge-sonos and can start/stop 2 different Sonos as well as control with Siri. But at some point it stops working and I see errors like:
FWIW this is running on a Raspberry Pi. Rebooting doesn't fix the problem. Config file is
|
@chadyj - did you change the "grouping" of your devices (your rooms) via the Sonos Desktop/Smartphone/Tablet app (after you started homebridge)? Would be good to know which devices you have in which room, and if there are any paired/grouped ones... |
@fwboettger Didn't touch the groupings. None are paired/grouped. |
@chadyj - sorry, then i don't have an idea i'm afraid, sorry to not being able to help.... |
I have a similar problem - Sonos Playbar and a Play:3 and I get errors connecting to one or the other - I'll investigate and get back to this thread. |
So i finally found time to dig back into the sonos playbar integration with this plugin. It looks like a lot of the updates this year fixed my detection issue - yay =) However, the I have made a fix for this locally, where instead of doing the current actions in the code, flipping the speaker switch off will instead call I will need to investigate how I can override these in the main branch only if the device type is a Playbar, so it doesnt interfere with Sonos Play 1/3/5 devices. See #46 for work on this. |
This is now resolved in #46 |
Also note I just discovered why play/stop wasnt working on the playbar. Those endpoints dont work when the Playbar is using the TV Audio In line. If the playbar is put into music mode via the Sonos App, then the play/stop commands via homebridge appear to work. The trick is now to find a way to programmatically switch the audio source for the playbar. I am tracking the issue for switching the inputs here - bencevans/node-sonos#148 |
I havent been able to get this working with my Sonos Playbar.
I have set up the Sonos in the "accessories" section of the config.json, with the "room" value matching the Room Name in the Sonos iOS app.
"accessories": [
{
"accessory": "Sonos",
"room": "Family Room",
"name": "TV Speakers"
}
]
Here are my logs:
Loading 1 accessories...
[TV Speakers] Initializing Sonos accessory...
Sat, 28 Nov 2015 18:52:05 GMT EventedHTTPServer [::ffff:192.168.1.69] HTTP request: /characteristis
Sat, 28 Nov 2015 18:52:05 GMT HAPServer [b8:27:eb:44:f8:79] HAP Request: PUT /characteristics
Sat, 28 Nov 2015 18:52:05 GMT Accessory [PiBridge] Processing characteristic set: {"characteristic":[{"aid":2,"iid":9,"value":false}]}
Sat, 28 Nov 2015 18:52:05 GMT Accessory [PiBridge] Setting Characteristic "On" to value false
[TV Speakers] Ignoring request; Sonos device has not yet been discovered.
Sat, 28 Nov 2015 18:52:05 GMT Accessory [PiBridge] Error setting Characteristic "On" to value fals: Sonos has not been discovered yet.
Sat, 28 Nov 2015 18:52:05 GMT HAPServer [b8:27:eb:44:f8:79] Error setting characteristics: Sonos hs not been discovered yet.
The text was updated successfully, but these errors were encountered: