Thanks for the suggestion, but being that I am unfamiliar with suse, I'll need a bit more guidance on 'how' to do that. This is on an RPi and is headless as I am connected by ssh to it.
I am at a loss as to how to help resolve this and really want to help get it resolved.
It appears that connman1.38 will initiate a scan via 'connmanctl scan wifi' even though it does not report that it has scanned. The git version (1.38.r23) will report on the cli that it has scanned. So, that is an improvement.
If I use either 1.38 (the current Arch Linux package) or build it from git, I cannot ge tthe Rpi or my laptop to reconnect when the ssid is rebooted even though the 'services' for the SSID
show that it is 'autoconnect' and monitor-connman shows that is 'ses' it. Is there some main.conf setting that I have wrong?
FallbackNameservers = 18.104.22.168,22.214.171.124
DefaultAutoConnectTechnologies = ethernet,wifi
AllowHostnameUpdates = false
AlwaysConnectedTechnologies = ethernet,wifi
AutoConnectRoamingServices = true
As I said previously, the only modifications to the build of the connman package under Arch are that it adds that dbus 'Agent' bits and also that it deletes the tmpfiles.d in the package that calls out a /var/run directory because Arch uses /run/. Other than that it is built under Arch as it is called out in the git to be built.
From my testing, ./monitor-connman seems to 'see' the ssid return, but will not reconnect after the router is rebooted.
If I use systemd-networkd and iwd, it reconnects every time. With connman and iwd, I get no reconnect over a reboot.
How can I help resolve this? We have spent a lot of time and effort getting our UI to work according to the connman manual and if it cannot reconnect over a reboot is it kind of useless to us on our headless music player. I have build capability and rpis and laptops with brcm as well as intel cards to test things. I am willing to try stuff and can test and, hopefully, respond with decent feedback, I just do not know how to modify connman to do this.