Stream Deck + Proclaim

Shara Heiniger (Logos)
Member, Logos Employee Posts: 132
Hi, in our church we use multiple Stream Deck devices for controlling
many parts of the service, Proclaim is one of the few things that isn't
yet managed with one.
All our Stream Decks run the Companion software
( https://bitfocus.io/companion) rather than the standard Stream Deck
software, so when I saw the release of the official Stream Deck plugin I
started work on porting it to Companion (as it seems there's also demand
from several other people too).
See current discussion:
https://github.com/bitfocus/companion-module-requests/issues/600
And previously,
https://github.com/bitfocus/companion-module-requests/issues/240 and
https://github.com/bitfocus/companion-module-requests/issues/295
I've quickly run into an issue where the API for remote control is only
accessible from the device running Proclaim and in both my development
environment and our church Proclaim isn't run on the same computer that
the Stream Decks are attached to.
I'm wondering if it would be possible to add an option for allowing
access to this API from any device, and possibly an IP/subnet whitelist
option - assuming security was the main reason for restricting the API
in the first place.
many parts of the service, Proclaim is one of the few things that isn't
yet managed with one.
All our Stream Decks run the Companion software
( https://bitfocus.io/companion) rather than the standard Stream Deck
software, so when I saw the release of the official Stream Deck plugin I
started work on porting it to Companion (as it seems there's also demand
from several other people too).
See current discussion:
https://github.com/bitfocus/companion-module-requests/issues/600
And previously,
https://github.com/bitfocus/companion-module-requests/issues/240 and
https://github.com/bitfocus/companion-module-requests/issues/295
I've quickly run into an issue where the API for remote control is only
accessible from the device running Proclaim and in both my development
environment and our church Proclaim isn't run on the same computer that
the Stream Decks are attached to.
I'm wondering if it would be possible to add an option for allowing
access to this API from any device, and possibly an IP/subnet whitelist
option - assuming security was the main reason for restricting the API
in the first place.
Tagged:
13
Comments
-
Yes, please consider this FaithLife!0
-
Yes faithlife, please do this - I would think many of us use companion (Bitfocus) for our streamdecks. An official companion module from you guys would be great.0
-
Proclaim version 3.2 or newer now support stream deck
https://support.faithlife.com/hc/en-us/articles/4409308832525-Stream-Deck-Support0 -
0
-
I think this one should be marked as done now. https://support.faithlife.com/hc/en-us/articles/49723730930050
-
I marked this as done, as Proclaim has added a new Network control password, and documented the new API here:
https://support.faithlife.com/hc/en-us/articles/4972373093005
I made a new feedback item for getting the Companion module:
https://feedback.faithlife.com/boards/faithlife-proclaim/posts/support-for-bitfocus-companionMac | iOS | Android | Windows | Web Developer
0