Support marge group endpoints

[gmuth]

After startup the device queries the marge group endpoint which is not yet implemented:

GET /marge/streaming/account/1823302/device/08A90C52D61F/group HTTP/1.1" 404

device endpoint /addGroup returns

<errors deviceID="...">
    <error value="5580" name="GROUP_CREATE_GROUP_ON_MARGE_ERROR" severity="Unknown"></error>
</errors>

[akpdw]

I haven't seen that one before. Is that for the ST10, like for stereo pairs?

[gmuth]

Yes, indeed - maybe only lrStereoCapable devices submit this request. Once I have another ST10 device I will do more testing.

[pahenning]

I have two ST10, they were a stereo pair a few weeks ago.

After I modified the paired boxes according to prescription, nothing worked, the boxes would not finish booting.
I had to reinstall the firmware from USB stick, then I split the pair in the BOSE app, modified them again according to the same prescription - and now they are working well, adressing the soundcork server.

Conclusion: In the boot process of the stereo pair, something is different, This may very well be query towards the "group" endpoint.

When I boot the ungrouped ST10 devices, I do not see any query of this endpoint, only

  INFO   192.168.0.105:51557 - "POST /v1/scmudc/50338B343509 HTTP/1.1" 404
      INFO   192.168.0.105:51582 - "POST /marge/streaming/support/power_on HTTP/1.1" 200
      INFO   192.168.0.105:51583 - "GET /bmx/registry/v1/services HTTP/1.1" 200
      INFO   192.168.0.105:51586 - "POST /v1/scmudc/50338B343509 HTTP/1.1" 404
      INFO   192.168.0.105:51597 - "GET /media/tunein-monochromePng.png HTTP/1.1" 200
      INFO   192.168.0.105:51598 - "GET /media/orion-monochrome_v2.png HTTP/1.1" 200
      INFO   192.168.0.105:51599 - "GET /media/siriusxm-monochromePng.png HTTP/1.1" 200
      INFO   192.168.0.105:51601 - "POST /v1/scmudc/50338B343509 HTTP/1.1" 404
      INFO   192.168.0.105:51602 - "POST /v1/scmudc/50338B343509 HTTP/1.1" 404
      INFO   192.168.0.105:51605 - "POST /v1/scmudc/50338B343509 HTTP/1.1" 404
      INFO   192.168.0.105:51606 - "GET /marge HTTP/1.1" 404
      INFO   192.168.0.105:51607 - "GET /marge/streaming/sourceproviders HTTP/1.1" 200
      INFO   192.168.0.105:51608 - "GET /marge/streaming/account/6080831/full HTTP/1.1" 200
      INFO   192.168.0.105:51610 - "POST /v1/scmudc/50338B343509 HTTP/1.1" 404
      INFO   192.168.0.105:51586 - "POST /v1/scmudc/50338B343509 HTTP/1.1" 404
      INFO   192.168.0.105:51690 - "POST /v1/scmudc/50338B343509 HTTP/1.1" 404

Regards
pah

[pahenning]

Your post contains a small but critical error. The group id needs to be the same on both devices.

The only difference is the element
<status>GROUP_OK</status>
in the slave (=right speaker)

Regards

pah

[pahenning]

I have added the group endpoints discussed here as pull request #161. However, so far this only adds/modifies/deletes a group info file into the soundcork datastore. It needs to be clarified how these are transported to the ST10 devices.

Regards

pah

[pahenning]

OK, some progress, I am referring to the code additions in the branch group_endpoints.

For the following, please note that my two ST10 boxes have the IPs 105 and 107, IP 94 is the soundcork server.

1. The addGroup endpoint at the ST10 box works with limitations. First of all, one has to submit the addGroup request to both boxes

curl -X POST -H "Content-Type: application/xml" -d @payload_addgroup2.xml http://192.168.0.105:8090/addGroup
curl -X POST -H "Content-Type: application/xml" -d @payload_addgroup2.xml http://192.168.0.107:8090/addGroup

After the first post, the status line in the returned XML reads <status>GROUP_ERROR</status> , after the second post it reads <status>GROUP_OK</status>. Also, the boxes accept the payload with or without the id="{group_id}" attribute in the <group> element. However, nothing is sent to the soundcork server.

2. The endpoint add_group at the soundcork server works nicely,

curl -X POST -H "Content-Type: application/xml" -d @payload_addgroup.xml http://192.168.0.94:8000/marge/streaming/account/6080831/group

produces a group file with id="{group_id}" - but sends nothing to the boxes.

Question No. 1: Is this the normal workflow, e.g. should a frontend application first add the group to the soundcork server to obtain a new id, and then submit the request to both boxes? Why does this not copy the group file to the second box, as e.g. also the removal of a group is communicated among the boxes?

3. The removeGroup endpoint at the ST10 box works.
   curl -X GET -H "accept: application/xml" http://192.168.0.105:8090/removeGroup

returns <?xml version="1.0" encoding="UTF-8" ?><group /> AND also submits the proper delete request to the second box. However, nothing is sent to the proper endpoint at the soundcork server, where the group file still remains.

4. The updateGroup endpoint at the ST10 box
   works with limitations, so far one has to send the request to both boxes in a pair.

curl -X POST -H "Content-Type: application/xml" -d @payload_modgroup.xml http://192.168.0.105:8090/updateGroup
curl -X POST -H "Content-Type: application/xml" -d @payload_modgroup.xml http://192.168.0.107:8090/updateGroup

AND has to submit this also to the soundcork server
curl -X POST -H "Content-Type: application/xml" -d @payload_modgroup.xml http://192.168.0.94:8000/marge/streaming/account/6080831/group/1224567

Question No.2: Is this the normal workflow when modifying a group? Why does this not work in the same way as when deleting a group, where the single box addressed also submits the change to the other box?

5. As requested in the first post, the "normal" query of the group endpoint gives the proper result

curl -X GET -H "accept: application/xml" http://192.168.0.94:8000/marge/streaming/account/6080831/device/50338B343509/group
results in

<?xml version='1.0' encoding='utf-8'?>
<group id="1224567">
  <name>SoundTouchDG1 + SoundTouchDG2</name>
  <masterDeviceId>50338B343509</masterDeviceId>
  <roles>
    <groupRole>
      <deviceId>50338B343509</deviceId>
      <role>LEFT</role>
      <ipAddress>192.168.0.105</ipAddress>
    </groupRole>
    <groupRole>
      <deviceId>0CAE7D70E808</deviceId>
      <role>RIGHT</role>
      <ipAddress>192.168.0.107</ipAddress>
    </groupRole>
  </roles>
  <senderIPAddress>192.168.0.105</senderIPAddress>
</group>

Regards

pah