Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 10 15:59

    pwt on v0.22.6

    (compare)

  • Jun 10 15:59

    pwt on v0.22.fixes

    Increment version number to v0.… (compare)

  • Jun 09 10:21
    pwt demilestoned #841
  • Jun 09 08:00

    pwt on v0.22.fixes

    Fix event unsubscription logic … (compare)

  • Jun 09 07:39

    pwt on master

    Fix event unsubscription logic … (compare)

  • Jun 09 07:39
    pwt closed #842
  • Jun 09 07:38
    pwt edited #842
  • Jun 08 14:05
    pwt milestoned #842
  • Jun 08 14:05
    pwt assigned #842
  • Jun 08 13:56
    jjlawren opened #842
  • Jun 08 09:12

    pwt on master

    Revert "Fix event unsubscriptio… (compare)

  • Jun 08 08:26

    pwt on v0.22.5

    (compare)

  • Jun 08 08:25

    pwt on v0.22.fixes

    Revert "Fix event unsubscriptio… Increment version number to v0.… (compare)

  • Jun 08 08:05

    pwt on v0.22.4

    (compare)

  • Jun 08 08:05

    pwt on v0.22.fixes

    Increment version number to v0.… (compare)

  • Jun 08 08:03

    pwt on v0.22.fixes

    Fix event unsubscription logic … (compare)

  • Jun 08 07:59

    pwt on master

    Fix event unsubscription logic … (compare)

  • Jun 08 07:59
    pwt closed #841
  • Jun 07 20:53
    jjlawren synchronize #841
  • Jun 07 18:41
    pwt edited #841
pwt
@pwt
@stutaines SoCo doesn't currently have any functionality for setting up bonding in home theatre configurations. I'm not personally familiar with the bonding process as I've never used a bonded setup. However, if you have an iOS device, I believe that the SonoSequencr app is able to do what you need: https://apps.apple.com/gb/app/sonosequencr/id967043604
stutaines
@stutaines
Ok! Thank you for your reply!
Gaëtan Trellu
@goldyfruit

Ah man. Finally went back to work on Auth and then I managed to break it :(

Ohhhh nooo :) Thanks for your work on this @KennethNielsen !

pwt
@pwt
SoCo v0.22 is due for release on 17-Apr. I only have one remaining PR milestoned, which will land in the next couple of days: https://github.com/SoCo/SoCo/milestone/18
The changes already committed since v0.21 are: https://github.com/SoCo/SoCo/milestone/18?closed=1
... but note that anything that's a defect fix will already have been included in a 0.21.x patch release.
So ... last call.
danieledge
@danieledge
Hi Folks, I was looking at SoCo to see if I can find a way to unbind and rebind surrounds on demand. I have some decent rear speakers connected to an amp that I wanted to use for music and then occasionally in a 5.1 setup. I saw some references to a PR request for this capability but am I right in that this currently isn’t supported by SoCo? Is there the capability to mute a soundbar thats part of a surround setup even if it can’t be unbound from the rears?
pwt
@pwt
You're correct that there's no support for this at the moment. (I'd have a go at implementing support myself, but I have no Sonos home theatre setups to use for investigation and testing.)If you have an iOS device, it's possible that SonoSequencr might fit your needs: https://apps.apple.com/gb/app/sonosequencr/id967043604
Gaëtan Trellu
@goldyfruit
It seems that get_media_metadata() doesn't apply to albums item but works fine with tracks
I'm trying to get the album's metadata to retrieve the artist
Gaëtan Trellu
@goldyfruit
And using get_metadata() on an item_id, gives me the songs into the album but not the artist
And... I just found the get_extended_metadata() function...
Sorry for the noise.
pwt
@pwt
FYI: Travis check jobs appear to have come back to life. They're running in addition to the GitHub Actions checks.
Kenneth Nielsen
@KennethNielsen
@pwt yeah, I just got en email yesterday (after months) that they had allotted extra minutes and that open source is very important to them. I have zero confidence that TravisCI is a viable way forward, so if you are happy with the Github Actions checks I think it is ok to just disable TravisCI
pwt
@pwt
For now, I think GitHub Actions is the way forward. The new check jobs essentially replicate what's being done by TravisCI, so I think it can be disabled.
Marc Neeley
@neeleym
Hi all ... In looking through the docs and the examples regarding getting events from players, is my understanding correct in saying that I need to subscribe for events for each Sonos device in the topology individually? I have a need to capture events from any devices in the installation, so I was looking for a way to listen for those events without having to inventory and manage a list of subscriptions by device as they come and go. Any thoughts or direction that should be considered for this requirement?
pwt
@pwt
Hi @neeleym You're correct that you have to subscribe to events from each device, or more specifically from each coordinator device. I believe there are events when devices join or leave, so these could probably be used to assist in managing subscriptions, but it's not an area in which I have much experience.
Marc Neeley
@neeleym
Ok ... that sound consistent with what I was reading as well. To get the most common set of events, it seems that 3 or 4 subscriptions per device are going to be required, so will need to think through this a bit. Thank you for the reply.
goblix
@goblix
hey, has anyone used the: https://developer.sonos.com/tools/developer-tools/sonos-simulator/
it seems like sonos removed the node-ssdp dependancy off their repository so it wont actually install.... wondering if there is any way that i can fix this ?
Kenneth Nielsen
@KennethNielsen
@goblix I haven't used it. It would be incredibly useful if it was possible.
goblix
@goblix
@KennethNielsen no doubt... i've emailed sonos developer support but they never get back to my emails lol. #ignored
Kenneth Nielsen
@KennethNielsen
@goblix I suspect they feared that such a tool would also make it easier to make rouge Sonos devices ;)
pwt
@pwt
FYI: SoCo v0.22.0 is now released and is live on PyPI. Release notes at: https://github.com/SoCo/SoCo/releases/tag/v0.22.0. Please do try it out and report any issues.
pwt
@pwt
Following hot on the heels of v0.22.0, I've just released v0.22.1 to address potential installation issues with a couple of sub-dependencies (#819). Release details in: https://github.com/SoCo/SoCo/releases/tag/v0.22.1. Sorry for the churn.
Russell Prince
@eviluser15_gitlab
Hi folks, I'm new to the SoCo API and to the Sonos world. I'm looking to implement a interface that allows me to snooze a running alarm. After breaking down the actions for the AVTransport service, I believe I should be able to run: SnoozeAlarm([("InstanceID", 0), ("Duration", 10)]) but I seem to get a 402 error. Am I missing something?
Russell Prince
@eviluser15_gitlab
Got it. Turns out Duration is misleading. It actually takes a time (e.g 20:40:00).
pwt
@pwt
Good stuff. I was about to suggest that duration should be a string. By 'time' I assume you still mean duration rather than an absolute time o'clock?
Might be a useful addition as a native SoCo method.
Russell Prince
@eviluser15_gitlab
You're correct it is a duration in hh:mm:ss format. It's misleading because the sonos app actually says snoozing for whatever is set. For example, if the alarm is set to go off at 06:00:00 and the snooze duration is set for 10 mins (in the app) but I send the command to only snooze for 1 min, the app doesn't update the time. So it will still say 06:10:00 yet the alarm goes off at 06:01:00
pwt
@pwt
For those that use SoCo-CLI, I've now added a convenient snooze_alarm action: https://github.com/avantrec/soco-cli#alarms
Russell Prince
@eviluser15_gitlab
Nice. Thanks for adding that!
pwt
@pwt
Patch release v0.22.2 is now live on PyPI. See the release notes for details: https://github.com/SoCo/SoCo/releases/tag/v0.22.2
Kenneth Nielsen
@KennethNielsen
:fireworks:
jjlawren
@jjlawren
i've found that music_source_from_uri() may be a little outdated. many services i've tested use x-sonos-http: prefixes which isn't even considered now
when working with subscriptions, the event callback carries a value in variables['enqueued_transport_uri'] which starts with x-sonosapi-radio for radio sources
but as of now calls to soco.media_source just returns "UNKNOWN"
pwt
@pwt
Patch release v0.22.3 is now available for download. See: https://github.com/SoCo/SoCo/releases/tag/v0.22.3
jjlawren
@jjlawren
hey @KennethNielsen do you remember the root cause of SoCo/SoCo#599 ?
jjlawren
@jjlawren
am i missing something, or are the <ZoneGroupState> payloads received from ZoneGroupTopology subscriptions not parsed in any way?
it seems like it could be a shortcut to use the provided subscription payload instead of always requesting a fresh one in SoCo._parse_zone_group_state()
pwt
@pwt
Patch release v0.22.4 is now available for download. See: https://github.com/SoCo/SoCo/releases/tag/v0.22.4
pwt
@pwt
Drat ... v0.22.4 is broken. I've released v0.22.5, which reverts the changes.
jjlawren
@jjlawren
sorry about that :(
pwt
@pwt
No worries ... v0.22.4 was only up for a few minutes before being superseded. I'm sure v0.22.6 will be awesome :)
jjlawren
@jjlawren
:thumbsup:
I haven't been able to definitively prove it yet, but I think that orphaned subscriptions can cause undesirable behavior on the speaker side
pwt
@pwt
v0.22.6 is now released, meaning event unsubscriptions will actually be sent to the Sonos players: https://github.com/SoCo/SoCo/releases/tag/v0.22.6