Those three identifiers (plus lc, which I couldn't get working as per the comment) were the only ones I was able to learn from USB captures. But by searching firmware binaries for known strings that get returned from info requests, I've found indications of other identifiers that might return different data. I haven't disassembled the source—this is purely based on strings that occur near each other—so there's no guarantee they're what I think they are. But it's worth trying them out anyway to see if they return anything interesting.
So far, I've looked at the SoundLink Color II (Foreman) and SoundLink Mini II (KCup) firmware images.
Both
vr (known)
v2
v4
pl (known)
sn (known)
lc (known, not working)
la
bt
sr
sh
fd
pw
uq
SoundLink Color II only
db
mq
ep
ua
aa
SoundLink Mini II only
rs
list (unsure why not 2 characters like the others)
Currently, we query three different fields from the device, each of which has a two-digit identifier: https://github.com/tchebb/bose-dfu/blob/f79694c87530e90438ed1b477c88903dd88d26f3/src/protocol.rs#L160-L167
Those three identifiers (plus
lc, which I couldn't get working as per the comment) were the only ones I was able to learn from USB captures. But by searching firmware binaries for known strings that get returned from info requests, I've found indications of other identifiers that might return different data. I haven't disassembled the source—this is purely based on strings that occur near each other—so there's no guarantee they're what I think they are. But it's worth trying them out anyway to see if they return anything interesting.So far, I've looked at the SoundLink Color II (Foreman) and SoundLink Mini II (KCup) firmware images.
Both
vr(known)v2v4pl(known)sn(known)lc(known, not working)labtsrshfdpwuqSoundLink Color II only
dbmqepuaaaSoundLink Mini II only
rslist(unsure why not 2 characters like the others)hrvo