-
Notifications
You must be signed in to change notification settings - Fork 22
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
1.X versions of Satellite no longer support original Streamdeck #74
Comments
This sounds like you have changed the port number in satellite. Try changing it back to the default (16622) |
I did attempt to do so but reverted it back. I’ve since installed fresh copies of companion and satellite on Windows machines and see the same problem. It is specific to the original hardware, if I use the XL version of the stream deck, it works immediately.
What changed? I updated the version of Satellite from the 0.4xxx version that was previously installed. I would like to try to revert to that version but I can’t find it online, I only see 1.X versions from 2023.
… On Jul 18, 2023, at 4:45 AM, Julian Waller ***@***.***> wrote:
This sounds like you have changed the port number in satellite. Try changing it back to the default (16622)
—
Reply to this email directly, view it on GitHub <#74 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBK24IIGIFUPFBKQHK4XJQTXQZLL5ANCNFSM6AAAAAA2NXNV2A>.
You are receiving this because you authored the thread.
|
Hmm strange. The Since 0.4, satellite has had a lot of changes, being almost fully rewritten by this point. But as the XL is working for you, this suggests its something with how we talk to the streamdecks, but companion uses the same code for that Prior to 1.0 of satellite, the downloads are on github https://github.com/bitfocus/companion-satellite/releases/tag/v0.4.0 |
I’ll give the 0.4 a try and see if the problem reverts. Thanks for the link.
For companion I have tried 2.4.2, 3.0.0 RC, and the latest 3.0 beta as of yesterday, no difference was seen.
I’m guessing you have seen and addressed the issue where hundreds of bogus satellite surfaces appear. I didn’t write it up as an issue but somehow in my attempts to test this bug, the hundreds of entries came back that I removed! Any tricks to clearing out that list? Database table perhaps?
… On Jul 18, 2023, at 9:05 AM, Julian Waller ***@***.***> wrote:
Hmm strange. The originalv2 is one variant I don't have access to, but both original and original-mk2 are working for me.
What version of companion are you using?
Since 0.4, satellite has had a lot of changes, being almost fully rewritten by this point. But as the XL is working for you, this suggests its something with how we talk to the streamdecks, but companion uses the same code for that
Prior to 1.0 of satellite, the downloads are on github https://github.com/bitfocus/companion-satellite/releases/tag/v0.4.0
—
Reply to this email directly, view it on GitHub <#74 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBK24IP4QJZF3QWEDZ73IBLXQ2JY3ANCNFSM6AAAAAA2NXNV2A>.
You are receiving this because you authored the thread.
|
No, that is not something I have seen before. What ids are they getting?
Was each of those able to use the streamdeck directly? |
No, that is not something I have seen before. What ids are they getting?
I’ll submit a new issue with screenshots, it is unrelated to this issue. Thanks for confirming.
Was each of those able to use the streamdeck directly?
I believe I tested direct connection of each of these versions. Companion had no issues detecting the old hardware. It is only Satellite. And I confirmed that the 0.4 version you pointed me to, it does work.
I also installed the steam deck software on a separate machine from elgato to update the firmware, it didn’t help.
Let me know if there is anything else I can get you to help correct the 1.X version with this old hardware. I work in quality assurance for over 20 years so I should be able to help you with any testing needed as well. Though I only have 2 stream decks, I have access to all kinds of hardware and network types.
… On Jul 18, 2023, at 10:28 AM, Julian Waller ***@***.***> wrote:
I’m guessing you have seen and addressed the issue where hundreds of bogus satellite surfaces appear.
No, that is not something I have seen before. What ids are they getting?
For companion I have tried 2.4.2, 3.0.0 RC, and the latest 3.0 beta as of yesterday, no difference was seen.
Was each of those able to use the streamdeck directly?
—
Reply to this email directly, view it on GitHub <#74 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBK24IMLAC5BWDUHOQWI4ULXQ2TTNANCNFSM6AAAAAA2NXNV2A>.
You are receiving this because you authored the thread.
|
The 0.4X version of Satellite supported the original hardware fine, however the newer 1.X version does not. The Streamdeck only shows Status:Connected along with the companion logo.
On the Surfaces page, for ID it lists:
satellite-Invalid
and for type, it lists:
Satellite StreamDeck: originalv2
If the same streamdeck is connected directly to companion, it functions fine.
Tried on several Windows PCs.
The text was updated successfully, but these errors were encountered: