I don't believe it is active if there is no profile configured against it. In testing against two of my lab FAPs, that is the behavior I can see. If you do a "show" instead of "get" that would also confirm what is configured and active in the profile.
Is there something that you are seeing to indicate that BLE is active?
Yes, I do see that, and I see the same thing in my profile as get will show all the configurable options in the wtp-profile. Without a profile assigned, the feature shouldn't be enabled.
As per the quick start guide (FAP-231F QSG) when LED 5 is orange it means that Radio 3 is turned on. In the case of the 231F, this would mean that the Dedicated Monitor has been enabled on radio 3. If BLE was enabled with radio 3 it would be green. Have a look inside your FAP-231F profile to verify that radio 3 is enabled.
2. If possible, test with the latest FortiAP version on the trunk, for example FortiAP Ver 7.0.5 3. SSH to FGT CLI, execute the following command:
diag wireless-controller wlac -c wtp bleprof
4. SSH to FAP CLI, execute the following command:
fap-get-status
cw_diag -c ble-config
5. Check if it is advertising bluetooth information
6. If it is still advertising bluetooth with no BLE profile configured
7. Try to change the BLE profile settings on the FortiGate and verify whether the correct settings are pushed to the FortiAP using the above mentioned commands
8. If none of the above steps helped, please open a ticket with Fortinet TAC so that it can be investigated further