Never used WPA3. WPA/WPA2 mixed or WPA-only or WPA2-only didn't make a difference.
I will try without encryption!
If I find my WiFi dongle I will try that as well.
Already increased wait time but that's not it. No matter the waiting (tried different methods, even on boot), the first connection will still fail with "invalid key" and thus connman(?) will disable auto-connect for this network for the time being.
Thinking a little further: Have you also considered that the counterpart to the Wi-Fi connection: the router/repeater,
Of course! That's why I've tried other routers as well.
might not be "enthusiastic" about this type of connection interruption by the Broadcom client and block the reconnection?
There is no reconnection. It happens on first connection attempt after hours/days.
It's a very large number of the users with RPi, LE and wifi connection. So, in the case of the clear iwd/broadcom bug, this forum would be filled with bug reports
There are plenty of bug reports! Forum and Github. From many reports you can see that people are simply switching to cable or external WiFi adapter because they cannot find a solution.
and probably solved long time ago. I don't say all it's perfect with iwd, just this probably isn't a simple software "bug" case.
Has to be solved by iwd or broadcom folks. I don't think they monitor bug reports as closely.
I had this wifi "thing" or something very the same, but at least I tried few things.
I also tried a few things: simpler password/ssid, different routers, Pi is within 1 m of router, 2.4 vs 5 GHz, WPA vs WPA2.
With external antenna, I only disconnected that tiny and weak on-board antenna and connected one with "normal size", the broadcom wifi and the iwd remains the same (nightly build LE, so the iwd it's more or less up to date). I don't know if in my case what triggered that issue, was the signal strenght or something in the router... but now it's working well.
As I said, the Pi is more or less next to the Pi. And once it is connected, there is no issue whatsoever. For hours. The only problem is autoconnection after ungraceful shutdown.
My current workaround is to have both 2.4 and 5 GHz networks configured for autoconnect. So after ungraceful shutdown, the first one to connect to will fail and LE will then just connect to the other one.
And it was already LibreELEC with iwd?
chewitt did you use the internal WiFi? Set auto-connect to your wifi? Pull the power plug and put it back in? And after that it connected without issue?
I proved it. Look at my logs. No WPA3, RPi close to router, tested with different routers, tested both 2.4 and 5 GHz, 100% replicable issue, only after ungraceful shutdown.
You said you almost never use WiFi let alone internal WiFi. If you would try, you'd be able to replicate the issue! Important: only after ungraceful shutdown! That's why it seems random to many users. It is not!
When it finally boots, most of the time it looses the password to the wifi and just show a notification of invalid-key and asks again for Wireless Network Passphrase.
It's a bug in iwd and/or the underlying broadcom driver. It doesn't have to do with signal strength or WPA mode as others suggested.
Some of the feedback / known issue / suggestions on the issues - please try these first.
Disabling fast-transition (FT) in access-point radio properties (this may be resolved in current connman/iwd/drivers, there have been changes in all 3 code bases around this)
Not using WPA3 (this may be resolved in current connman/iwd/drivers, there have been changes in all 3 code bases around this)
Moving the device closer to the access-point to improve signal strength
Different underlying issues. The main issue, however, is not related to any of those. The main issue is some software/firmware issue on boot after unclean shutdown.
It's not related to signal strength or wifi settings. It's an issue inside iwd or the broadcom driver or the way iwd interacts with the broadcom driver:
The solution with 2 WiFi networks kind of satisfies my needs at the moment as it will just switch after every boot. Of course only works because my router and my RasPi have good 2.4 and 5 GHz reception.
Ok, so I tried a different router and the problem is absolutely the same.
USB-wifi dongle with better antenna
It has nothing to do with the reception/signal strength.
BTW, did you tried with the same wifi source every times?
Actually, no. Since it works fine with Raspbian (which of course doesn't use iwd) the issue must be with iwd or the wifi firmware used by iwd/libreelec. But it is definitely something that I will try!
Well, I believe it just hasn't been viewed isolated and is instead mixed with other unrelated WiFi issues. What is clear: THIS problem only (but always!) occurs when there was no graceful shutdown (reboot or boot after shutdown), but never occurs when the system was shutdown properly, on at least the RPi4 platform.
It most likely affects everyone. It's just that many people went for cable as a workaround (or in general) and never noticed that their WiFi isn't working.
So yes, the overall user base that insists on using WiFi might be low, but it's most likely every WiFi user out there.
I'll try a different platform than RPi4 when I find the time.
I counted at least 30 people, and those are just the ones that spoke up about it. I wonder if iwd devs are actually aware about the issue. Furthermore, I can only find bug reports regarding LinreELEC, but I guess that is due to the small number of distributions having made the switch to iwd. Actually, I couldn't find any other that uses iwd by default.
So, since the issue is not magically going to disappear, I eventually found the time to capture the logs of iwd.
Here is the log where the autoconnect after a powerloss fails:
And here is the log where autoconnect works after reboot/graceful shutdown:
I don't think it's only affecting a few users as mentioned in this infamous thread: invalid wifi key
I see a lot of posts about this error, also a very long github issue: https://github.com/LibreELEC/LibreELEC.tv/issues/7166
Fyi: Issue is also not resolved on the latest LE12-nightly.
Thanks. I can rule out poor signal strength as router and RPi4 are in direct vicinity of each other and also because the error is 100% reproducible and the workaround also works 100% of the time. Also both 2.4 and 5 GHz networks are affected. Once connection is established, there is no issue with it and I never had any dropouts/disconnects.
I'll post the full log but it'll take some time to redact as there's lots of sensitive information (neighboring WiFi stations in particular) contained within.
Can I somehow get the wireless stack to be more verbose in its output?
Of course I meant the key is NOT invalid. Unfortunately I cannot edit my post.
Edit: corrected.
Had a look at the journal now. Nothing obvious. iwd just fails telling me the key was invalid (which of course it is not as it works after the next boot). Unfortunately, only connmand is verbose, iwd not so much:
LibreELEC iwd[469]: event: connect-failed, status: 16
LibreELEC iwd[469]: event: state, old: connecting, new: disconnected
LibreELEC iwd[469]: event: state, old: disconnected, new: autoconnect_quick
LibreELEC connmand[651]: ../plugins/iwd.c:cm_network_connect_cb() /net/connman/iwd/0/3/465249545a21426f78203735323020574f_psk connect failed: net.connman.iwd.Failed
LibreELEC connmand[651]: ../src/network.c:connman_network_set_error() network 0xef27a60 error 3
LibreELEC connmand[651]: ../src/service.c:__connman_service_indicate_error() service 0xef27cb0 error 7
LibreELEC connmand[651]: ../src/service.c:set_error() service 0xef27cb0 (wifi_d83add53bde1_465249545a21426f78203735323020574f_managed_psk) error 7 (invalid-key)
LibreELEC connmand[651]: Interface wlan0 [ wifi ] error "invalid-key"
LibreELEC connmand[651]: ../src/service.c:__connman_service_ipconfig_indicate_state() service 0xef27cb0 (wifi_d83add53bde1_465249545a21426f78203735323020574f_managed_psk) type 1 (IPv4) old state 3 (configuration) new state 7 (failure)
LibreELEC connmand[651]: ../src/ipconfig.c:__connman_ipconfig_disable() ipconfig 0xef27ff0
LibreELEC connmand[651]: ../src/ipconfig.c:__connman_ipconfig_unref_debug() 0xef27ff0 ref 2 by ../src/ipconfig.c:1998:__connman_ipconfig_disable()
LibreELEC connmand[651]: ../src/service.c:service_indicate_state() service 0xef27cb0 (wifi_d83add53bde1_465249545a21426f78203735323020574f_managed_psk) old configuration - new failure/idle => failure
LibreELEC connmand[651]: Interface wlan0 [ wifi ] state is failure
LibreELEC connmand[651]: ../plugins/vpn.c:vpn_disconnect_check()
LibreELEC connmand[651]: ../src/session.c:service_state_changed() service 0xef27cb0 (wifi_d83add53bde1_465249545a21426f78203735323020574f_managed_psk) state 7
LibreELEC connmand[651]: ../src/provider.c:provider_service_changed() service 0xef27cb0 wifi_d83add53bde1_465249545a21426f78203735323020574f_managed_psk state 7 index 3/-1
LibreELEC connmand[651]: ../src/notifier.c:notify_idle_state() idle 1
LibreELEC connmand[651]: ../src/manager.c:idle_state() idle 1
LibreELEC connmand[651]: ../src/agent.c:connman_agent_report_error_full() agent (nil) sender (null) context 0xef27cb0 path -
LibreELEC connmand[651]: ../src/service.c:service_save() service 0xef27cb0 (wifi_d83add53bde1_465249545a21426f78203735323020574f_managed_psk) new 0
LibreELEC connmand[651]: ../src/ipconfig.c:__connman_ipconfig_save() ipconfig 0xef27ff0 identifier wifi_d83add53bde1_465249545a21426f78203735323020574f_managed_psk method dhcp
LibreELEC connmand[651]: ../src/ipconfig.c:__connman_ipconfig_save() ipconfig 0xef280d0 identifier wifi_d83add53bde1_465249545a21426f78203735323020574f_managed_psk method off
LibreELEC connmand[651]: ../src/service.c:service_list_sort() from service_indicate_state()
LibreELEC connmand[651]: ../src/gateway.c:__connman_gateway_update()
LibreELEC connmand[651]: ../src/gateway.c:gateway_data_debug() from __connman_gateway_update() default_gateway (nil)
LibreELEC connmand[651]: ../src/gateway.c:__connman_gateway_update() updated4 0 updated6 0
LibreELEC connmand[651]: ipconfig state 7 ipconfig method 1
LibreELEC connmand[651]: ../src/network.c:__connman_network_disconnect() network 0xef27a60
LibreELEC connmand[651]: ../src/network.c:connman_network_set_associating() network 0xef27a60 associating 0
LibreELEC connmand[651]: ../src/network.c:set_disconnected() service 0xef27cb0 ipv4 0xef27ff0 ipv6 0xef280d0
LibreELEC connmand[651]: ../src/network.c:set_disconnected() method ipv4 4 ipv6 1
LibreELEC connmand[651]: ../src/dhcp.c:__connman_dhcp_stop() ipconfig_table 0xef10400 ipconfig 0xef27ff0
LibreELEC iwd[469]: event: state, old: autoconnect_full, new: disconnected
