# Lights disabled in QGC

**URL:** https://discuss.bluerobotics.com/t/lights-disabled-in-qgc/22280
**Category:** Blue Robotics Vehicles
**Created:** [January 15, 2026, 12:40am UTC](https://discuss.bluerobotics.com/t/lights-disabled-in-qgc/22280 "2026-01-15T00:40:55Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)
#### Post date: [January 15, 2026, 12:49pm UTC](https://discuss.bluerobotics.com/t/lights-disabled-in-qgc/22280/2 "2026-01-15T12:49:04Z")

</div>

Hi @coanderson,

The ArduSub firmware [recently got some updates to how it handles lights configuration](https://discuss.bluerobotics.com/t/ardusub-4-5-5-more-intuitive-output-mapping-and-broken-grippers/21533) that QGC doesn’t know about. I _believe_ QGC should still be capable of performing the old configuration approach, which the firmware should then auto-fix on the next reboot, but when that fix happens the QGC Lights page will again present the lights as not configured.

The joystick button functions have not changed, so as long as the relevant buttons are assigned they should still be able to control the lights, and the lights percentage should still be reported. If that’s working in Cockpit then it should also be working in QGC, but it’s possible your joystick configuration is not the same between the two software (which might be the actual cause of your issue).

---

_[View the full topic](https://discuss.bluerobotics.com/t/lights-disabled-in-qgc/22280)._