In the OpenWRT v18.06.2 release that I published today, I added two patches which enable the 802.11/WIFI LEDs to work. The big patches to the ath10k driver have already been merged into OpenWRT, but the configuration to enable it's use wasn't there yet.
I created patch set v14, which is nearly identical to v13 except that it adds two patches to enable the LEDs.
The method I used is basically identical to what sunnyqeen published. Thanks dude!
For new systems with a fresh configuration, the LEDs will start working immediately by default.
However, for existing systems with an existing configuration, the owner will need to add the system config items to enable the LEDs. They won't just start working on their own due to the way the OpenWRT config system works.
Running the following commands over ssh will enable the 802.11/WIFI LED triggers:
uci set system.led_wlan2g=led
uci set system.led_wlan2g.name='WLAN2G'
uci set system.led_wlan2g.sysfs='ath10k-phy1'
uci set system.led_wlan2g.trigger='phy1tpt'
uci set system.led_wlan5g=led
uci set system.led_wlan5g.name='WLAN5G'
uci set system.led_wlan5g.sysfs='ath10k-phy0'
uci set system.led_wlan5g.trigger='phy0tpt'
That last "system reload" command wasn't working for me on my test system, but that might have been due to some local config changes I've made that broke stuff. If it doesn't work, just reboot and the LEDs should start working.
A couple of lines should appear in your /etc/config/system file:
config led 'led_wlan2g'
option name 'WLAN2G'
option sysfs 'ath10k-phy1'
option trigger 'phy1tpt'
config led 'led_wlan5g'
option name 'WLAN5G'
option sysfs 'ath10k-phy0'
option trigger 'phy0tpt'
If you don't want UCI to touch your config files, you can manually append the config above to your /etc/config/system file.
Here's the wiki doc on LED triggers if you need it: