You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user of my integration reports that on his Focus 20 XD speakers, the power on command does not work. Of course there is a lot of application logic in between that I have to debug, but I was just wondering: is there anyone who tested/used this api using these specific speakers? Just to exclude the possibility that the API behaves in a different way on these specific speakers.
Kind regards,
Bas
The text was updated successfully, but these errors were encountered:
I don't think I've ever tested the API with any of the XD speakers, so I can't be 100% sure it uses the same API. However, I would be surprised if it were any different (also because the API is for the Connect - as far as I know of course - and that device hasn't received a significant update on the functionality part in quite a few years). Depending on the user (and if the alternative is much effort), it might be relatively easy to capture the data going between the iOS app and the Connect (unless it's encrypted these days - which I doubt). Just setup a wifi hotspot on a wired computer, connect to it with a device running the mobile app, run Wireshark and hit the commands on the app you're interested in (perhaps an x number of times so you know what to look for, in case it's different).
I'll leave this issue open for now. Please let me know if you discover whether or not there is any difference. I'll keep my eyes open, see if I know someone with these speakers. If so, I'll give it a test run and see what comes back... but that will probably take some time (months at least).
Hey Maarten,
A user of my integration reports that on his Focus 20 XD speakers, the power on command does not work. Of course there is a lot of application logic in between that I have to debug, but I was just wondering: is there anyone who tested/used this api using these specific speakers? Just to exclude the possibility that the API behaves in a different way on these specific speakers.
Kind regards,
Bas
The text was updated successfully, but these errors were encountered: