Hi, would someone have the correct config to mimic the MR42/MR52s LED behavior like is listed at https://documentation.meraki.com/MR/MR_Installation_Guides/MR42_Installation_Guide and https://documentation.meraki.com/MR/MR_Installation_Guides/MR52_Installation_Guide My LuCI > System > LED Config is Blank, for some reason with all stock images. Also, what would it take to implement "Run Dark Mode" (turn the LEDs off)
Hi which version of openwrt are you running?
Latest snapshot. It was this way in the 23.05 builds too.
Bump. Anyone
cat /sys/kernel/debug/gpio
The LEDs aren't even defined in /etc/config/system but:
root@MR42:~# cat /sys/kernel/debug/gpio
gpiochip0: GPIOs 512-580, parent: platform/800000.pinmux, 800000.pinmux:
gpio0 : out low func1 2mA pull down
gpio1 : in low func1 2mA pull down
gpio2 : out high func0 2mA pull up
gpio3 : out high func0 12mA no pull
gpio4 : in high func0 2mA pull down
gpio5 : in low func0 2mA pull down
gpio6 : out high func0 2mA pull down
gpio7 : out high func0 2mA pull down
gpio8 : in high func0 2mA pull down
gpio9 : in high func0 8mA no pull
gpio10 : out low func1 12mA no pull
gpio11 : out low func1 12mA no pull
gpio12 : in high func1 2mA no pull
gpio13 : in high func1 2mA no pull
gpio14 : in high func0 2mA pull down
gpio15 : in high func0 2mA pull up
gpio16 : in low func0 2mA pull down
gpio17 : in low func0 2mA pull down
gpio18 : in low func0 2mA pull down
gpio19 : in low func0 2mA pull down
gpio20 : in high func0 2mA pull down
gpio21 : in low func0 2mA pull down
gpio22 : in low func0 2mA pull down
gpio23 : in low func0 2mA pull down
gpio24 : in high func1 2mA pull up
gpio25 : in high func1 2mA pull up
gpio26 : in high func0 2mA pull up
gpio27 : in low func0 2mA pull down
gpio28 : in low func0 2mA pull down
gpio29 : in high func3 2mA pull up
gpio30 : in high func3 2mA pull up
gpio31 : out low func0 12mA pull down
gpio32 : out high func0 12mA pull down
gpio33 : in high func0 2mA pull down
gpio34 : out low func1 10mA no pull
gpio35 : out low func1 10mA no pull
gpio36 : out low func1 10mA no pull
gpio37 : out low func1 10mA no pull
gpio38 : out low func1 10mA no pull
gpio39 : out low func1 10mA pull up
gpio40 : out low func1 10mA keeper
gpio41 : out low func1 10mA keeper
gpio42 : out low func1 10mA keeper
gpio43 : out low func1 10mA keeper
gpio44 : out low func1 10mA keeper
gpio45 : out low func1 10mA keeper
gpio46 : out low func1 10mA keeper
gpio47 : out low func1 10mA keeper
gpio48 : out high func0 12mA no pull
gpio49 : in high func0 2mA pull down
gpio50 : in low func0 2mA pull down
gpio51 : in high func1 4mA no pull
gpio52 : in high func1 4mA no pull
gpio53 : in low func0 2mA pull down
gpio54 : in low func0 2mA pull down
gpio55 : in low func0 2mA pull down
gpio56 : in low func0 2mA pull down
gpio57 : in low func0 2mA pull down
gpio58 : in low func0 2mA pull down
gpio59 : in low func0 2mA pull down
gpio60 : in low func0 2mA pull down
gpio61 : in high func0 2mA pull down
gpio62 : in high func0 2mA pull down
gpio63 : out high func0 12mA no pull
gpio64 : in high func0 2mA pull down
gpio65 : in low func0 2mA pull down
gpio66 : in high func0 2mA pull down
gpio67 : in low func0 2mA pull down
gpio68 : out high func0 2mA pull up
ls /sys/class/leds
opkg list-installed | grep led
23.05.3 or snapshot?
mr42 or mr52?
I said snapshot above, and MR42, but this also affects the 52.
root@MR42:~# ls /sys/class/leds
ath10k-phy0 ath10k-phy2 green:user red:user
ath10k-phy1 blue:user orange:power white:active
root@MR42:~# opkg list-installed | grep led
kmod-leds-gpio - 6.6.30-r1
kmod-leds-tlc591xx - 6.6.30-r1
Turn them off manually, e.g.:
uci add system led
uci set system.@led[-1].sysfs='ath10k-phy0'
uci set system.@led[-1].trigger='none'
uci commit system
uci add system led
uci set system.@led[-1].sysfs='ath10k-phy1'
uci set system.@led[-1].trigger='none'
uci commit system
uci add system led
uci set system.@led[-1].sysfs='ath10k-phy2'
uci set system.@led[-1].trigger='none'
uci commit system
uci add system led
uci set system.@led[-1].sysfs='green:user'
uci set system.@led[-1].trigger='none'
uci commit system
uci add system led
uci set system.@led[-1].sysfs='red:user'
uci set system.@led[-1].trigger='none'
uci commit system
uci add system led
uci set system.@led[-1].sysfs='blue:user'
uci set system.@led[-1].trigger='none'
uci commit system
uci add system led
uci set system.@led[-1].sysfs='orange:power'
uci set system.@led[-1].trigger='none'
uci commit system
uci add system led
uci set system.@led[-1].sysfs='white:active'
uci set system.@led[-1].trigger='none'
uci commit system
I don't want them turned off. I want them to behave properly
There's only a single system LED on this device. It's pointless to follow the original LED scheme of the OEM firmware. The WIFI radios can perform many more modes in OpenWrt. There's no one-to-one matching.
* Orange: The AP is booting, or there is a hardware issue
* Rainbow: The AP is initializing or scanning
* Blinking blue: The AP is upgrading
* Green: The AP is in Gateway mode with no clients
* Blue: The AP is in Gateway mode with clients
* Blinking orange: The AP can't find an uplink
Sure there is, at least get blue and green working so it's NOT white
If you check the initial git commit, the mr52 LEDs are listed, the mr42 LEDs are white active only.
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=67f52012760ce553ba6393aaba77359a458deeda
Someone needs to submit a PR to update this
So, am I right or wrong here? Also (I'm assuming I need to file a new topic for this) but the MR24 5Gs radio is "Broken" it passes traffic, but shows up as "Generic MAC80211 802.11a/n" 2.4 works fine
You're right here, as far as I can tell from the initial git commits the mr42 LEDs are not fully detailed.
They stop at white LED only.
Thought so. Thank you.
Both MR42 and MR52 have a single System LED, and the DTS for both MR42 and MR52 are the same for this single System LED. The Green LED is part of of the Ethernet port itself and that's not what OP talked about.
Orange and White will only be the only available colors for this single System LED in Openwrt.
MR42
40 led_power: power {
41 label = "orange:power";
42 gpios = <&qcom_pinmux 31 GPIO_ACTIVE_HIGH>;
43 };
44
45 led_active: active {
46 label = "white:active";
47 gpios = <&qcom_pinmux 32 GPIO_ACTIVE_HIGH>;
48 };
MR52
42 led_power: power {
43 label = "orange:power";
44 gpios = <&qcom_pinmux 19 GPIO_ACTIVE_HIGH>;
45 };
56
57 led_active: active {
58 label = "white:active";
59 gpios = <&qcom_pinmux 26 GPIO_ACTIVE_LOW>;
60 };
In other words, it's not broken at all. The naming is purely cosmetic, based on a hand-curated list of PCI IDs and serves no functional task.
Incorrect. The LED (system) CAN go green. Have you ever used Meraki in the field? If no, then STOP spreading incorrect info.
So, it's ok to not be 100% efficient on the software side?