Using FSM / SEM with Spad.next - LED access?

[JPVann]

Hi all - I have a varied setup all using Spad.next for profiles and device control and trying to incorporate a FSM and SEM into the mix. However I just learned that there is no way for Spad.next to communicate or even see the button LEDs?

So how - for example - would I have an LED go off when I hit a particular altitude (for example) when the LED cannot talk to any software? For a maker of button boxes this seems extremely weird and locked down. Thanks!

[fallout9]

Usually the software is based on hardware, not the other way around.

[JPVann]

Spad has been around from the Saitek days, is device agnostic and can provide complex functions, calculations and actions to anything that has an open API. My controls have lights, sound, beeps, different led responses, etc - all just with Spad. Except for VKB who doesn’t offer a way to communicate with the device.

[fallout9]

Usually the software is based on hardware, not the other way around.