emOS v0.9
WiFi from the console on every Echo, including routers running WPA2/WPA3 mixed mode.
What changed
em-wifijoins WPA2/WPA3 transition-mode networks. These are the
default on current UniFi and many other routers, andem-wifilisted them
as "WPA3 - not supported" and refused them. The Echo joins them as WPA2.
Networks it genuinely cannot join (enterprise/EAP, OWE) are now named as
such instead of being tried as open networks (#624).em-wifiis now in FireOS 5 images too, not only FireOS 6, so every
emOS Echo can set WiFi from the console. It no longer writes a config
FireOS 5's supplicant cannot read.- The console prompt names the device by its serial instead of
root@android, so two Echoes on USB can be told apart. - Two boot-time checks on the WiFi firmware path, which log a clear reason
where a failure used to show only as wlan0 never appearing.
Upgrading
Re-run the provisioning wizard's build and flash steps. Nothing on /data is
touched, so your WiFi and console password survive.
Controllers from 2.24.1 build images from this release. FireOS 5 images pick
up em-wifi once the controller is 2.25.0 or later.
Known issues in this release
- WiFi on FireOS 6 with a WPA3-only network does not work and cannot: the
driver has no SAE and the kernel is too old for us to do it in userspace.
Use WPA2 or WPA2/WPA3 mixed (#536).
Checksums
Verify the assets against the release page before flashing anything.