Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stream Deck Mobile Support? #35

Open
jjeff opened this issue Jan 24, 2022 · 1 comment
Open

Stream Deck Mobile Support? #35

jjeff opened this issue Jan 24, 2022 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@jjeff
Copy link

jjeff commented Jan 24, 2022

I'm guessing the answer here is "no". But I'll ask anyway: Is there a way to use this library (I'm using the WebHID version these days) along with Elgato's Stream Deck Mobile app?

I believe that the app connects to Elgato's Stream Deck Manager desktop app which acts as an intermediary. Since this library (@elgato-stream-deck) doesn't use Elgato's desktop software, I'm guessing that there's no way for Stream Deck Mobile to act as a virtual WebHID/NodeHID device and be seen by @elgato-stream-deck. But I'd love to be wrong! So I'm asking here.

@Julusian
Copy link
Owner

There isnt currently any support for the app. For a few reasons:

  1. why use their paid app instead of a simple standalone webpage?
  2. I have little interest in paying for a subscription to reverse engineer their protocol, especially with not seeing the point of using it (see 1)
  3. It is likely going to require a different level of abstraction to the HID version, as it will likely transfer json over the socket instead. So while it could share types with the rest of this, but probably very little actual code.
  4. Although it is perhaps unlikely, I don't trust elgato to not push breaking protocol updates in the app, requiring another round of reverse engineering.

So from this it is unlikely that I will do anything for this, but I will accept a PR for a new @elgato-stream-deck/mobile package.

One issue I suspect you may have, is that it is likely that the desktop app is being the websocket server. As far as Im aware it is not possible to be a websocket server in the browser, so this will probably need to be a node only package.

@Julusian Julusian added enhancement New feature or request help wanted Extra attention is needed labels Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants