Wetek Play 2 no Wifi with Box Image

    Hi,

    I have trouble getting a wifi connection with the box image on a Wetek Play 2. I don't see any wifi network at all (I do if I boot the stock (Android) firmware on the device). I connected an ethernet cable and iw list at least shows a phy. Is there something I am doing wrong?

    kodi.log:

    http://ix.io/4suB

    dmesg output:


    http://ix.io/4suC

    Any hint or advice is welcome :)

    Many thanks

    Rainer

    The dmesg log looks fine, the WiFi NIC is probed without errors. Some German users (a guess based on your name) need to have the 80211 regdomain configured in LE settings (under Network) before networks can be seen. See if setting to 'DE' makes a difference?

    I configured the regdomain and now it seems I can at least see the wireless network.

    I managed to connect to the AP of an Android phone in tethering mode.

    I did not manage to connect to an

    OpenWrt 22.03.3 router, I get invalid key. I use this router since many years with many devices and I do not recall that I ever had an issue that a device did not want to connect.

    dmesg has quite a few entries

    ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel <number>

    (not sure if that is relevant)

    http://ix.io/4swH

    Output of "iw dev wlan0 scan"

    http://ix.io/4swW

    Output of "iwlist wlan0 scanning" looks ok for me:

    and the kodi.log:

    http://ix.io/4swI


    What is very weird: Sometimes all connections show up twice, see

    PXL_20230402_194352852.jpg
    Nextcloud - a safe home for all your data
    nc.d5x.de

    Is that expected?

    Many thanks

    Rainer

    The "invalid-key" error is probably bugs in iwd affecting a small number of users. We've bumped iwd to the latest release in LE11 nightlies and this appears to resolve it for most users. Update to the latest nightly here: https://test.libreelec.tv/11.0/Amlogic/wetek-play2/ and report back. The issue is tracked here: https://github.com/LibreELEC/LibreELEC.tv/issues/7166

    The dmesg messages are correct and harmless.

    For double results; an educated guess is that connman is scanning in the background so its results are visible to the dbus agent in the LE settings add-on, and then you're running scans via iwd and its results are also visible. If you don't run the manual iwd scan do you still see duplicates?

    With

    Code
    2023-04-03 16:32:16.090 T:908      info <general>: Starting Kodi (20.1 (20.1.0) Git:20.1-Nexus). Platform: Linux ARM 32-bit
2023-04-03 16:32:16.090 T:908      info <general>: Using Release Kodi x32
2023-04-03 16:32:16.090 T:908      info <general>: Kodi compiled 2023-04-03 by GCC 12.2.0 for Linux ARM 32-bit version 6.1.19 (393491)
2023-04-03 16:32:16.091 T:908      info <general>: Running on Amlogic Meson GXBB (S905) WeTek Play 2 with LibreELEC (community): nightly-20230403-bb4c561 11.0, kernel: Linux ARM 64-bit version 6.1.19

    I checked in the openwrt syslog, but did not find any entry there from the connection attempt. For successful connections, I see entries like

    Code
    Mon Apr  3 21:09:54 2023 daemon.info hostapd: wlan0: STA 78:11:dc:ed:a7:e3 IEEE 802.11: associated (aid 5)
Mon Apr  3 21:09:54 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 78:11:dc:ed:a7:e3
Mon Apr  3 21:09:54 2023 daemon.info hostapd: wlan0: STA 78:11:dc:ed:a7:e3 WPA: pairwise key handshake completed (RSN)
Mon Apr  3 21:09:54 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED 78:11:dc:ed:a7:e3

    on the openwrt side. I conclude that the connection process aborts very early.

    I see still the same behavior. I used the box image instead of the wetek-play2, since I still have the Android FW for reference testing on the emmc.

    The double results I cannot deterministically reproduce. I keep an eye if the double results show up again w/o manual iwd run.

    Edited 2 times, last by rdorsch (April 3, 2023 at 8:35 PM).