Hi @elit,
ArduSub used to overload the RCIN passthrough outputs for its lights functionality, but in 4.5.5 transitioned to using dedicated Lights1 (181) and Lights2 (182) outputs. The latest firmware detects the old RCIN9/10 configuration and auto-corrects it on startup, but if you change it after booting then the lights won’t work until rebooting the autopilot.
The new lights values should show up correctly in BlueOS 1.4.3, though the Lights page in vehicle setup has only been properly updated in the upcoming 1.4.4 release.
If you want to control multiple sets of lights with a single signal (e.g. Lights1), I’ve confirmed it should work fine to just assign the same function to the relevant outputs.