25 lines
1.2 KiB
Markdown
25 lines
1.2 KiB
Markdown
# Future ideas
|
|
|
|
These are feasibility notes for possible tools, not implemented features or
|
|
committed delivery plans.
|
|
|
|
See the [future program task list](docs/planning/program-task-list.md) for the planned
|
|
DMX driver/firmware project and far-future Dante virtual soundcard research.
|
|
|
|
## Flipper Link: USB control from the web and Stream Deck
|
|
|
|
**Feasible for selected actions with official Flipper Zero firmware.** A small
|
|
service on the computer connected to the Flipper would translate HTTP commands
|
|
into USB serial CLI commands or structured protobuf RPC requests. Bitfocus
|
|
Companion could call that service from Stream Deck buttons.
|
|
|
|
Start with device status and saved infrared remote buttons. Prove the workflow
|
|
using Companion's Generic HTTP module, then build a dedicated Companion module
|
|
with action selection, variables and feedback. Remote support varies by Flipper
|
|
application; exposing every internal action is not guaranteed. USB ownership,
|
|
reconnection and stopping held actions need particular care.
|
|
|
|
See [Flipper Link feasibility and proposed design](docs/planning/flipper-link.md) for
|
|
the supported interfaces, limitations, architecture, implementation stages and
|
|
primary sources. Hardware validation is still required.
|