I’m running Flint 3 and an Aqara doorbell and have noticed intermittent doorbell offline messages. I just assumed it was flaky wifi or 2.4ghz congestion. If you do track down a bug or a solution please share it!
replyWe've tried a few things but it hasn't really helped.
replyWhen it goes offline I get the following error on the Flint 3:
# dmesg | grep -i '54:EF:44:5C:BC:B1' | grep kicked
[3356208.016938] wlan: [0:I:ANY] [INACT] vap-0(wlan0): [54:ef:44:5c:bc:b1]station kicked out due to excessive retries associd 4 (from target) reason 1
[3363271.980807] wlan: [0:I:ANY] [INACT] vap-0(wlan0): [54:ef:44:5c:bc:b1]station kicked out due to excessive retries associd 4 (from target) reason 1
I had some devices with similar (I think) problems when I did my last round of AP upgrades and tried to do roaming extensions...
replyI think I'm still running r, but k and/or v were problematic for a few of my clients. Wifi band steering can potentially also be problematic.
Maybe I'll try again when I get wifi 7 APs.
> even logging into my router (with my permission)
replyThis is exactly why I want to migrate to a OpenWRT router, companies should not just be able to hop in my network like this. And I'd love to like the Flint 3 I stayed away from it because it didn't have upstream openwrt compatibility but I just saw this repo that might fix my issue: perceival/openwrt-flint3
Is that the context? In thinking op here might just opened a port and added the keys off the support agent and removing them after.
replyNot sure, that's what i thought reading it but you might be right
replyThey release new models and completely abandon the old ones. You are happy now. Have you asked owners of Flint 1 (or other older models), how they feel now?
reply