Venus OS 2.73 Raspberry pi 4 WiFi not working

Question

question

waffleking asked Sep 18, '21

Venus OS 2.73 Raspberry pi 4 WiFi not working

I have a Raspberry Pi 4 running Venus OS v2.73. It has been working fine for a few days and this afternoon VRM stoped getting updates. So I checked the local remote console. No response. Reboot doesn't fix it.

From VictronConnect > Setting > Network settings I can see my wireless AP. I attempt to connect. After attempting to connect it says "Connecting to <WIFI> failed. Could not connect to the network."

I have many other devices connected to the same access point so I don't believe that is the issue.

I can see wlan0 when doing an 'ip addr'

# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul                      t qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1450 qdisc mq state UP gr                      oup default qlen 1000
    link/ether dc:a6:32:af:57:48 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.182/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::dea6:32ff:feaf:5748/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1450 qdisc pfifo_fast                       state DOWN group default qlen 1000
    link/ether dc:a6:32:af:57:49 brd ff:ff:ff:ff:ff:ff
4: ll-eth0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state                       UP group default qlen 1000
    link/ether ee:6c:f9:54:c4:ef brd ff:ff:ff:ff:ff:ff
    inet 169.254.12.22/16 scope link ll-eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::ec6c:f9ff:fe54:c4ef/64 scope link
       valid_lft forever preferred_lft forev

I attempted a fix from another thread with no lock (the Error only shows via ssh not when directly connected to device.

# connmanctl
Error getting VPN connections: The name net.connman.vpn was not provided by any connmanctl> enable wifi
Error wifi: Already enabled
connmanct

Wired Ethernet works fine.

Interesting VictronConnect show Link-Local Address from ll-eth0, which is neither the wired or wireless connection, and doesn't show in /etc/network/interfaces

Here is the /var/log/messages output from connecting to VinctronConnect and attempting to connect to WiFi:

Sep 18 17:27:05 raspberrypi4 daemon.warn bluetoothd[582]: No cache for 3C:28:6D:31:F4:8B
Sep 18 17:27:07 raspberrypi4 daemon.warn wpa_supplicant[736]: wlan0: Failed to initiate sched scan
Sep 18 17:27:27 raspberrypi4 daemon.warn connmand[659]: Skipping disconnect of 535057694669_managed_psk, network is connecting.
Sep 18 17:27:30 raspberrypi4 daemon.notice wpa_supplicant[736]: wlan0: Trying to associate with SSID 'SPWiFi'
Sep 18 17:27:30 raspberrypi4 daemon.info connmand[659]: ntp: time slew -0.006479 s
Sep 18 17:27:33 raspberrypi4 daemon.notice wpa_supplicant[736]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
Sep 18 17:27:33 raspberrypi4 daemon.info connmand[659]: ntp: time slew -0.004943

Venus OS wifi

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Modifications Space

Node Red Space

Answer 1 · 2021-09-18T18:21:40Z

waffleking answered · Sep 18, 2021 at 06:21 PM

While this is still broken using the VinctronConnect App, I was able to get connected using connmanctl. Before I did this I removed the wifi_* directorires in /data/var/lib/connman/wifi_*

$ connmanctl
connmanctl> enable wifi
Enabled Wifi
connmanctl> scan wifi
Scan completed for wifi
connmanctl> services
    MyWiFi         wifi_1234
connmanctl> agent on
Agent registered
connmanctl> connect wifi_1234
Agent RequestInpu wifi_1234
  Passphrase = [ Type=psk, Requirement=mandatory, Alternatives=[ WPS ] ]
  WPS = [ Type=wpspin, Requirement=alternate ]
Passphrase?
Connected wifi_1234
connmanctl> quit

UPDATE:

The real issue with this is it doesn't seem to survive a reboot. So after setting this up I can't then return the device to it's install location and connect to it.

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Answer 2 · 2021-09-19T19:55:31Z

Mike Dorsett answered · Sep 19, 2021 at 07:55 PM

All I had to do for the pi3 was:

root@raspberrypi2:~# connmanctl
Error getting VPN connections: The name net.connman.vpn was not provided by any

connmanctl> enable wifi
Error wifi: Already enabled
connmanctl>

This survived a reboot, but the re-connection of the Wifi remained a bit flaky - particularly at low signal strength. I think that the number of retries is maybe too small.

This fix was needed with 2.6 to 2.8 os.

1

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

waffleking commented · Sep 20, 2021 at 04:42 PM

I re-flashed the 2.72 firmware, and started fresh. I did have to perform the # connmanctl > enable wifi. But after I did that, I was able to setup my wifi via VictronConnect and it has been working fine for me even after reboot.

0 ·

question