Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#1194 - LED Names Wrongly Assigned For TP-Link TL-WA850RE #7977

Closed
openwrt-bot opened this issue Nov 26, 2017 · 1 comment
Closed

FS#1194 - LED Names Wrongly Assigned For TP-Link TL-WA850RE #7977

openwrt-bot opened this issue Nov 26, 2017 · 1 comment
Labels

Comments

@openwrt-bot
Copy link

p.smith:

Version: 17.01.4-ar71xx-generic-tl-wa850re-v1 created using the image builder. Added and removed some packages for the actual build, none of which should be related to the issue

Device: TP-Link TL-WA850RE(EU) Ver. 1.0

What does not work: LED names on the "LED Configuration" page do not match the physical LEDs on the device.

Steps to reproduce: Attempt to configure LED triggers on the configuration page after a fresh installation on the device

Workaround: Configure the LED triggers by using the ostensibly wrong LED name to match the correct physical LED.

Additional information: There are nine physical LEDs present on the device. The following is a list of the physical LEDs with their labels and the currently matching "LED name" from the configuration page. The order is clockwise, starting at the 12 o'clock position:

  • WLAN 5 [highest] -> tp-link:blue:signal1
  • WLAN 4 -> tp-link:blue:lan
  • WLAN 3 -> tp-link:blue:lan
  • WLAN 2 -> tp-link:blue:wlan
  • WLAN 1 [lowest] -> tp-link:blue:re
  • Ethernet -> tp-link:blue:signal5
  • Power -> tp-link:blue:signal4
  • Wireless -> tp-link:blue:signal3
  • RE -> tp-link:blue:signal2

LED name "ath9k-phy0" does not seem to correspond to any LED on the front of the device

@openwrt-bot
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant