Sonos Boost: Cannot read property 'homeTheatre' of undefined #88
Labels
Comments
|
same here |
|
Could you please attach the full debug logfile and list the output of |
|
? I, for my part, don´t know how! |
|
See https://github.com/ebaauw/homebridge-hue#debug-log-file how to create a debug log file.
where |
|
pi@pi-Backup:~ $ zp -H 192.168.178.29 topology -v |
|
|
@mbsaeger thanks! I haven’t come across a Sonos Boost before. It seems to be the only player in a zone of its own, but its marked invisible, causing homebridge-zp to think it’s a slave player. I think it chokes because it cannot find the corresponding master player for the zone. Could you please run @Spy-1 do you also have a Boost? The |
|
@ebaauw interesting.. The boost should be ignored completely - it's just the Sonos Network box basically (e.g. all of the Sonos connect wirelessly to the Boost versus my WiFi. |
|
Hi Erik,
yes i have a Boost!
I think its bettet to ignore it.
von unterwegs gesendet
… Am 24.07.2019 um 18:33 schrieb Erik Baauw ***@***.***>:
@mbsaeger thanks! I haven’t come across a Sonos Boost before. It seems to be the only player in a zone of its own, but its marked invisible, causing homebridge-zp to think it’s a slave player. I think it chokes because it cannot find the corresponding master player for the zone.
Could you please run ph -H 10.0.0.106 description -S > boost.json and attach boost.json here? This lists the SOAP services supported by the Boost, so I can see whether there’s something useful to support (e.g. the status LED) or whether best to ignore it completely.
@Spy-1 do you also have a Boost? The zp command should be installed to /usr/bin or /usr/local/bin, depending on how you installed NodeJS. It should be the same bin directory that homebridge is in.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
ebaauw
added a commit
that referenced
this issue
Jul 24, 2019
Set Sonos Boost as zone master, even though it's invisible. The role remains slave, so it's not exposed as Sonos not TV accessorory. See #88.
|
By the looks of it, the Boost does keep track of the topology and grouping, and could be useful discovering other players. Also, the LED can also be controlled, so I might expose it when Could you try v1.0.2-0, install thru |
|
@ebaauw still getting the same error after updating: |
|
Bugger. Could you please try another |
|
you bet! |
ebaauw
added a commit
that referenced
this issue
Jul 24, 2019
Set master of Boost zone to Boost, see #88.
|
Could you try v1.0.2-1? That should also handle the absence of physical buttons. |
ebaauw
changed the title
|
Unrelated: how many speaker pairs do you have connected to your Sonos Amp? If more than one: how do you control these? Do they share the input source, play/pause? The volume, mute, loudness, equaliser settings? |
|
I've only got one speaker pair connected, but you can connect up to three speaker pairs. They all are treated as one zone, same source, volume, mute, loudness, etc. |
|
@ebaauw it runs without error now! New issue; thinking the BOOST needs to be a slave or invisible as when I try to play/pause/volume it immediately reverts to off. Thinking its sending the request to the boost instead of the speaker perhaps? |
Ah, ok. No special handling needed, then. |
Is the BOOST exposed as Sonos accessory? What does homebridge-zp log for found zones and zoneplayers?
The request should be sent to the coordinator of the group that the zone player is in. I doubt the Boost can be a coordinator. Does the Sonos app show the Dining Room Sonos in any group? What group does the Eve app show for it?
Immediately as in half a second? This could happen when there's no input selected. What Track is displayed in the Eve app? If you start play from the Sonos app, can you then pause/stop from HomeKit. And then play (because now there's an input?). Immediately as in 1-2 seconds? Sometimes this might happen when the zone player takes some time to buffer the audio source. It sends multiple events in succession for connecting..., buffering..., playing. In this case, it should switch to on automatically when playing starts. If you run |
|
Not sure what the BOOST is or should be exposed as - essentially its the newer version of the Sonos Bridge. It has no real controls and isn't considered the "master" for any of the speakers based on zpinfo, each speaker shows as its own 'Master'. Somehow every speaker was ungrouped and all tracks cleared (maybe there was a power outage I missed) but once queue-ing up some tracks in all zones I'm able to get it working again! I am specifying the "exclude airplay" flag and my AirPlay zone is showing up - but that could be due to an accessory cache or something. |
Yes, I still need to implement the removal of accessories. The accessories are cached in If you run As last resort, you can simply remove the file (when homebridge is not running) and restart homebridge. You will lose all cached accessories by all dynamic platform plugins. They will likely be re-created by their respective plugins, but HomeKit will treat them as new accessories, and you'll lose any HomeKit room, scene, automations, etc assignments.
You can check |
|
Perfect - that did it! Thank you very much.. Think we can safely close this issue now 👍 |
|
Cool. v1.0.2 is out. |
This was referenced Jul 25, 2019
That's an omission on my part alright, see #92. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running into the following error once upgrading to 1.0
The text was updated successfully, but these errors were encountered: