Fifine Ampligame D6 Support

[Lyagva]

https://fifinemicrophone.com/products/fifine-ampligame-d6-stream-deck

Hello everyone reading this. My friend gave me this piece of hardware 3x5 streamdeck by fifine. I'm thinking of making it into a Companion Surface. I tried capturing HID data of the device but got an issue of it not emitting any signals unless the app is launched. Then it exchanges some data with Fifine's software and "activates is". When the app closes it deactivates device back.
Also, I managed to trace pattern of key presses (like how to get key state and key number from the signal).

For capturing I used USBPCap and Wireshark to sort things out. I can share .pcap files if someone would like to offer their help. I'll still try to explore the "activation" method, but am not sure if I'll hit any success

[alturnative]

While it would definitely be nice to have the D6 work natively with Companion, it's worth noting that it can already work with companion using the Bitfocus Companion plugin and disabling direct connection to stream deck in Companion.

Make sure when configuring the plugin in the Fifine control software to set the Companion websocket port to 28492. The URL should be adjusted as normal depending on where you've got Companion running, but that websocket port should always be set up 28492.

[GSS2001]

Hi everyone,

Just wanted to add some context to help with this integration. The Fifine AmpliGame D6 is essentially a direct hardware copy/rebrand of the original Mirabox Stream Dock architecture. They share the exact same button/knob layout and internal base protocol.

Instead of creating a new module from scratch, it would be awesome if the existing Mirabox Stream Dock plugin could be updated to also recognize and accept this Fifine model. Since they share the same underlying base, simply expanding the current plugin to detect the Fifine version would instantly integrate it with all the native features.

Hopefully, this is a straightforward addition for the module maintainers. Thanks for the amazing work!

[GSS2001]

Hi everyone,

I noticed in issue bitfocus/companion-module-requests#1494 that support for other similar hardware clones (like the HSV 293S) was successfully integrated directly into the MiraboxStreamDock.ts surface driver by expanding the model definitions.

Since the Fifine AmpliGame D6 shares the exact same core architecture, we could apply the identical blueprint here. Instead of a brand new module, the maintainers could simply update the existing Mirabox module to include the Fifine D6 configuration, just like it was beautifully executed in bitfocus/companion-module-requests#1494.

This would be the cleanest way to bring native support to the D6 within the current Companion ecosystem. Thank you!

[peternewman]

You'll probably need to start with sharing the USB VID and PID, and then anyone who is keen might be able to try and add support for it.

[Ramon20000]

Since no one shared them, here it goes

Device Description       : USB Composite Device
Device Path              : \\?\USB#VID_3142&PID_0060#81D0DA784037#{a5dcbf10-6530-11d2-901f-00c04fb951ed} (GUID_DEVINTERFACE_USB_DEVICE)
Kernel Name              : \Device\USBPDO-22
Device ID                : USB\VID_3142&PID_0060\81D0DA784037
Hardware IDs             : USB\VID_3142&PID_0060&REV_0002 USB\VID_3142&PID_0060
Driver KeyName           : {36fc9e60-c465-11cf-8056-444553540000}\0014 (GUID_DEVCLASS_USB)
Driver                   : \SystemRoot\System32\drivers\usbccgp.sys (Version: 10.0.26100.8328  Date: 2026-06-02)
Driver Inf               : C:\WINDOWS\inf\usb.inf
Legacy BusType           : PNPBus
Class                    : USB
Class GUID               : {36fc9e60-c465-11cf-8056-444553540000} (GUID_DEVCLASS_USB)
Service                  : usbccgp
Enumerator               : USB
Location Info            : Port_#0002.Hub_#0005
Location IDs             : PCIROOT(0)#PCI(0801)#PCI(0003)#USBROOT(0)#USB(3)#USB(2), ACPI(_SB_)#ACPI(PCI0)#ACPI(GP13)#ACPI(XHC0)#USBROOT(0)#USB(3)#USB(2)
Container ID             : {554c49c1-2538-5d52-b9c7-b75396bed9c2}
Manufacturer Info        : (Standard USB Host Controller)
Capabilities             : 0x94 (Removable, UniqueID, SurpriseRemovalOK)
Status                   : 0x0180400A (DN_DRIVER_LOADED, DN_STARTED, DN_REMOVABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER)
Problem Code             : 0
Address                  : 2
Power State              : D0 (supported: D0, D2, D3, wake from D0, wake from D2)
 Child Device 1          : USB Input Device
  Device ID              : USB\VID_3142&PID_0060&MI_00\8&286CC422&0&0000
  Class                  : HIDClass
  Driver KeyName         : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0018 (GUID_DEVCLASS_HIDCLASS)
  Service                : HidUsb
  Location               : 0029.0000.0003.003.002.000.000.000.000
  LocationPaths          : PCIROOT(0)#PCI(0801)#PCI(0003)#USBROOT(0)#USB(3)#USB(2)#USBMI(0)  PCIROOT(0)#PCI(0801)#PCI(0003)#USBROOT(0)#USB(3)#USB(2)#USB(2)  ACPI(_SB_)#ACPI(PCI0)#ACPI(GP13)#ACPI(XHC0)#USBROOT(0)#USB(3)#USB(2)#USBMI(0)  ACPI(_SB_)#ACPI(PCI0)#ACPI(GP13)#ACPI(XHC0)#USBROOT(0)#USB(3)#USB(2)#USB(2)
  SelectiveSuspEnabled   : 0
  EnhPowerMgmtEnabled    : 1
 Child Device 1          : HID-compliant vendor-defined device
  Device Path            : \\?\HID#VID_3142&PID_0060&MI_00#9&3016145&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (GUID_DEVINTERFACE_HID)
  Kernel Name            : \Device\00000139
  Device ID              : HID\VID_3142&PID_0060&MI_00\9&3016145&0&0000
  Class                  : HIDClass
  Driver KeyName         : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0056 (GUID_DEVCLASS_HIDCLASS)
 Child Device 2          : USB Input Device
  Device ID              : USB\VID_3142&PID_0060&MI_01\8&286CC422&0&0001
  Class                  : HIDClass
  Driver KeyName         : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0055 (GUID_DEVCLASS_HIDCLASS)
  Service                : HidUsb
  Location               : 0029.0000.0003.003.002.000.000.000.000
  LocationPaths          : PCIROOT(0)#PCI(0801)#PCI(0003)#USBROOT(0)#USB(3)#USB(2)#USBMI(1)  ACPI(_SB_)#ACPI(PCI0)#ACPI(GP13)#ACPI(XHC0)#USBROOT(0)#USB(3)#USB(2)#USBMI(1)
  SelectiveSuspEnabled   : 0
  EnhPowerMgmtEnabled    : 1
 Child Device 1          : HID Keyboard Device
  Device Path 1          : \\?\HID#VID_3142&PID_0060&MI_01#9&1ac4ed8a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd (GUID_DEVINTERFACE_HID)
  Device Path 2          : \\?\HID#VID_3142&PID_0060&MI_01#9&1ac4ed8a&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd} (GUID_DEVINTERFACE_KEYBOARD)
  Kernel Name            : \Device\0000013a
  Device ID              : HID\VID_3142&PID_0060&MI_01\9&1AC4ED8A&0&0000
  Class                  : Keyboard
  Driver KeyName         : {4d36e96b-e325-11ce-bfc1-08002be10318}\0020 (GUID_DEVCLASS_KEYBOARD)
  Service                : kbdhid

[peternewman]

Since no one shared them, here it goes

Device ID                : USB\VID_3142&PID_0060\81D0DA784037

So with that, someone who's feeling keen could try the various 239S based models in here to see if it functions and get it added to the module:
https://github.com/bitfocus/companion-surface-mirabox-stream-dock/tree/main/src/models

If you add to the USB IDs with the suitable VID (vendor ID) and PID (product ID), like these ones here:

companion-surface-mirabox-stream-dock/src/models/HSV-293S.ts

Lines 8 to 15 in 6e33810

	{
	vendorId: 0x6602,
	productIds: [0x1014],
	},
	{
	vendorId: 0x6603,
	productIds: [0x1014],
	},

Follow the instructions to build it here:
https://github.com/bitfocus/companion-surface-mirabox-stream-dock/blob/main/README.md

Then see if it finds it (it should) and crucially whether it works.

If not, remove it from that file and try one of the other 293 files, build again, probably restart Companion and try again...

If it works for one, then you're 95% of the way there to getting it added into the module properly.