I tried to set up a Thrustmaster T150 alongside a MSFFB2, but only the one device at a time has FFB, even though each work when set up individually or as the first device in a multi-device config.
settings.json (used settingsXboxAndMSFFB2.json as base.)
Comparison

Console log:
Using setting file: C:\Programs\EDForceFeedback\settings.json
10:40:47 dbug: Journals.Client[0] DeviceName: Thrustmaster T150 Racing Wheel: ProductGuid b677044f-0000-0000-0000-504944564944
10:40:47 dbug: Journals.Client[0] Found Joystick/Gamepad Thrustmaster T150 Racing Wheel
10:40:47 dbug: Journals.Client[0] Effect available Constant Force
10:40:47 dbug: Journals.Client[0] Effect available Ramp Force
10:40:47 dbug: Journals.Client[0] Effect available Square Wave
10:40:47 dbug: Journals.Client[0] Effect available Sine Wave
10:40:47 dbug: Journals.Client[0] Effect available Triangle Wave
10:40:47 dbug: Journals.Client[0] Effect available SawtoothUp Wave
10:40:47 dbug: Journals.Client[0] Effect available Sawtooth Down Wave
10:40:47 dbug: Journals.Client[0] Effect available Spring Force
10:40:47 dbug: Journals.Client[0] Effect available Damper Force
10:40:47 dbug: Journals.Client[0] Effect available Inertia
10:40:47 dbug: Journals.Client[0] Effect available Friction
10:40:47 dbug: Journals.Client[0] Effect available Custom Force
10:40:47 dbug: Journals.Client[0] Effect available Axis Barrier
10:40:47 dbug: Journals.Client[0] Effect available Angle Barrier
10:40:47 dbug: Journals.Client[0] Effect available Axis Wall
10:40:47 dbug: Journals.Client[0] Effect available Angle Wall
10:40:48 dbug: Journals.Client[0] File Effect available Cargo.ffe
10:40:48 dbug: Journals.Client[0] File Effect available CenterSpringXY.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Damper.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Dock.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Gear.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Hardpoints.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Landed.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Vibrate.ffe
10:40:48 dbug: Journals.Client[0] File Effect available VibrateSide.ffe
10:40:48 dbug: Journals.Client[0] DeviceName: Thrustmaster T150 Racing Wheel: ProductGuid b677044f-0000-0000-0000-504944564944
10:40:48 dbug: Journals.Client[0] DeviceName: SideWinder Force Feedback 2 Joystick: ProductGuid 001b045e-0000-0000-0000-504944564944
10:40:48 dbug: Journals.Client[0] Found Joystick/Gamepad SideWinder Force Feedback 2 Joystick
10:40:48 dbug: Journals.Client[0] Effect available GUID_ConstantForce
10:40:48 dbug: Journals.Client[0] Effect available GUID_RampForce
10:40:48 dbug: Journals.Client[0] Effect available GUID_Square
10:40:48 dbug: Journals.Client[0] Effect available GUID_Sine
10:40:48 dbug: Journals.Client[0] Effect available GUID_Triangle
10:40:48 dbug: Journals.Client[0] Effect available GUID_SawtoothUp
10:40:48 dbug: Journals.Client[0] Effect available GUID_SawtoothDown
10:40:48 dbug: Journals.Client[0] Effect available GUID_Spring
10:40:48 dbug: Journals.Client[0] Effect available GUID_Damper
10:40:48 dbug: Journals.Client[0] Effect available GUID_Inertia
10:40:48 dbug: Journals.Client[0] Effect available GUID_Friction
10:40:48 dbug: Journals.Client[0] Effect available GUID_CustomForce
10:40:48 dbug: Journals.Client[0] File Effect available Cargo.ffe
10:40:48 dbug: Journals.Client[0] File Effect available CenterSpringXY.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Damper.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Dock.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Gear.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Hardpoints.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Landed.ffe
10:40:48 dbug: Journals.Client[0] File Effect available Vibrate.ffe
10:40:48 dbug: Journals.Client[0] File Effect available VibrateSide.ffe
10:40:48 dbug: EliteAPI.EliteDangerousApi[0] Initialising EliteAPI v3.0.0.0
10:40:48 dbug: EliteAPI.Events.EventParser[0] Using converter EliteAPI.Events.LocalisedConverter
10:40:48 dbug: EliteAPI.Events.Events[0] Registering events from EliteAPI.Events v3.0.0.0
10:40:48 dbug: EliteAPI.Events.Events[0] Registered 301 events from EliteAPI.Events v3.0.0.0
10:40:48 info: EliteAPI.EliteDangerousApi[0] Starting EliteAPI v3.0.0.0
10:40:48 warn: EliteAPI.Readers.Reader[0] No files found matching Backpack.json in C:\Users\%USERNAME%\Saved Games\Frontier Developments\Elite Dangerous
10:40:48 dbug: Journals.Client[0] Event EliteAPI.Events.Status.Cargo.CargoEvent
10:40:48 dbug: Journals.Client[0] Event EliteAPI.Events.Status.Modules.ModuleInfoEvent
10:40:48 warn: EliteAPI.Events.Events[0] The NavRouteClear event is not registered
10:40:48 dbug: Journals.Client[0] Event EliteAPI.Events.Status.Outfitting.OutfittingEvent
10:40:48 dbug: Journals.Client[0] Event EliteAPI.Events.ShipLockerEvent
10:40:48 dbug: Journals.Client[0] Event EliteAPI.Events.Status.Shipyard.ShipyardEvent
10:40:48 warn: EliteAPI.Readers.Reader[0] No files found matching Custom.4.0.binds in C:\Users\%USERNAME%\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings
10:40:52 dbug: Journals.Client[0] Effect 13541c24-8e33-11d0-9ad0-00a0c9a06e35 starting
10:40:52 dbug: Journals.Client[0] Effect 13541c27-8e33-11d0-9ad0-00a0c9a06e35 starting
10:40:52 dbug: Journals.Client[0] Effect 13541c28-8e33-11d0-9ad0-00a0c9a06e35 starting
10:40:54 dbug: Journals.Client[0] Effect Dock.ffe complete
I did find a workaround:
Dragging settingsT150.json and settingsMSFFB2.json into EDForceFeedback.exe (or running a script like EDForceFeedback.cmd.zip) to launch 2 separate instances allows both devices to have FFB, but I think it'd be more practical to allow both working at once, especially if it fixes the FFB delay between both devices, unless there's a limitation somewhere 🤔
I tried to set up a Thrustmaster T150 alongside a MSFFB2, but only the one device at a time has FFB, even though each work when set up individually or as the first device in a multi-device config.
settings.json (used settingsXboxAndMSFFB2.json as base.)
Comparison

Console log:
I did find a workaround:
Dragging settingsT150.json and settingsMSFFB2.json into EDForceFeedback.exe (or running a script like EDForceFeedback.cmd.zip) to launch 2 separate instances allows both devices to have FFB, but I think it'd be more practical to allow both working at once, especially if it fixes the FFB delay between both devices, unless there's a limitation somewhere 🤔