'Join' not working properly

[johnnyt]

According to the info at the following link, I need to "Join" secondary speakers to the first one to make a 'group' under that first one. https://github.com/jishi/node-sonos-http-api#grouping

I tried to do this with the following program:
 

Announcement Test - [ID 0446][Parent 0445]

If
   - No Conditions - (To add one, press 'Schedule' or 'Condition')
 
Then
        Wait  13 seconds
        Set 'ST-Sonos / Dining Room' Join Kitchen
        Wait  1 second
        Set 'ST-Sonos / TV Room' Join Kitchen
        Set 'ST-Sonos / Kitchen' Group Volume 20%
        Wait  1 second
        Set 'ST-Sonos / Kitchen' Say Test Phrase 1
Else
   - No Actions - (To add one, press 'Action')

And I end up with this group in the app:

 

Then the 'say' command only comes out the Kitchen speakers, not the group I made above, which is not surprising but not what I asked for. My 'Portable' speaker has never been grouped with the "Kitchen" and "TV Room" so all I can deduce at this point is that the NS did that, and that it's a bug. 

I ran the above program twice with same result. I also tried to group the latter two (Kitchen and TV Room) with a different speaker after ungrouping everything using the app and ended with the same thing. Why the "Portable" speaker becomes the parent doesn't make any sense.

Anyone have any suggestions as to what I did wrong or might be happening? 

Edited August 26, 2023 by johnnyt

[bpwwer]

That sounds more like an issue with the API than the node server, but I don't own any Sonos devices and can't attempt to reproduce or test.

The node-sonos-http-api library has 161 open issues, if you can reproduce the issue using just the API, you can enter an issue with the library.  However, it appears that the maintainer is only updating the library when someone sends an actual bug fix to him so just opening an issue may not get any resolution.

If you can trace the issue to something the node server is doing wrong, I can take a look and attempt to fix it.  However at this point, I believe the node server is simply calling the join API with the two devices so there's little chance that the node server is doing something wrong.

When the node server log is set to debug level, it does output some information about what it is doing when you do the Join.  Maybe that would help.