I have a Pi 3B+ with official 7 inch screen which I have set up with RoPieee.
Unfortunately I have had a lot of problems where it fails to connect to wifi when booting up, or manages to boot up and connects, then drops connection resulting in the Connection Failure screen.
Ive tried updating the Pi firmware, using a new SD card and reinstalling to no avail.The access point is in the same room within 5 metres of the Pi. Another Pi in the same room is connected as an end point (running HiFiBerry) and has had a steady connection for probably a year
This last failure is slightly different in that it managed to connect, I left it overnight. And in the morning it had the Connection Failure screen…But this time the wifi connection is still active and I can access the web page.
I’m seeing a lot of network issues between the RoPieee unit and your Roon server.
Not really sure what to do about it…
You could test the beta release though that I just pushed out (BETA 2024.11). It contains updated drivers and also an updated wireless connection manager.
Thanks for looking. Looks like the on board Wi-Fi was faulty. I’ve replaced the Pi with another 3B+ and so far it’s run for 24 hours without a single hitch.
Dear Harry,
I am also struggling with wifi issues since a while.
I have been using my Pi4 Model B already for a longer time without any problems on a wired connection (auto update on the stable channel enabled), using the UpnP bridge to integrate my Marantz MCR603 in the Roon environment.
Now, I was preparing the addition of my Teufel Boomster in a wifi-only area of my home, connecting it through an AudioQuest Dragonfly Cobalt USB DAC for the Pi (expected Christmas present ).
So, I enabled wifi on the Pi4 and moved it around in the well-covered WiFi6 groundfloor area of my home.
After the initial wifi turn-on (a while ago), the Pi was dead, did not reboot after disconnecting the power for a couple of minutes, but came back alive after hours of disconnecting the power supply. It continued working for some time and would then suddenly drop out again, being also unreachable via a browser on the IP address which it received via wifi, as well as over a reestablished wired connection. My router would sometimes show the IP addresses as provided though by it’s DHCP server, sometimes not (or only one of the 2).
I observed also that saving a parameter change while it was (temporary) working and applying it would kill Ropieee.
At this very moment of writing, Ropieee is running with both wifi and wired connections active, auto update disabled. It is currently running the stable 2024.10 version (see the screenshot below for detailed information).
I have sent logs with the identifier ec1d38a4dc8155e5
I have set the update channel to beta, because I saw your message in this thread that updated wifi drivers were included in the 2024.11-beta release, but I don’t know whether that’s sufficient at this time to have it pushed to my device?
The 2024.11 beta release was downloaded and has been installed now. Wifi did not come back on and the router doesn’t show it’s IP address (it will assign fixed IP addresses to both wired and wifi connections for ease of opening the home screen)
I have sent new logs, collected after the version update, with the following identifier:
e7408829774ba3ec
Thanks for the quick reaction, Harry!
As I am on the beta channel now and also a regular UPnP Bridge user, I was wondering wether my device would be able to contribute to your earlier request for UPnP beta testers? (At least merely when irregular unattended continuous playback could serve the purpose)
).