Kyle Husmann

Nice work! Sounds you're up to where I left off - I'd also like to know the significance of 0x03 and the body of the 0x01 (audio end). (Let me...

Glad I could help you get up to speed! That's been my guiding goal for the benlink project, to reverse engineer these protocols and setup so folks like you can...

@Ylianst for me, blocking it doesn't affect regular app usage, but does prevent it from checking for new firmware updates. Lmk if you see any different on your end...

Ah ha, it works the first try if you send the commands while simultaneously connected via rfcomm to the audio channel. Looks like you can probe for the channel layout...

@Ylianst in https://github.com/khusmann/benlink/issues/14 you mention: > I would get a notification that HtStatus.is_in_tx would change to false. I changed my code to use that as a way to know when...

Yeah, this might be something that's different on different firmware versions. (What firmware are you currently on? I think I was testing on 0.7.10 when I documented this) For me,...

Just tried this with upgraded firmware 0.8.0 -- no issue with INCORRECT_STATE replies on first send, so that seems to definitely be a firmware bug. So I was incorrect assuming...

> However, I have not encountered this often and could be wrong, but in my case INCORRECT_STATE on a fragment id that is not zero will cause all me to...

@Ylianst nope, don't know how to do this other than sending via your own audio stream

@georges I agree KISS extension is not the way to go - just including it here as a success story of BTech responding to community input. (so maybe a direction...