I am running my Pironman 5 Max on Raspbian Trixie. When installing that via the Raspberry Pi imager onto a supported NVME SSD and directly installing the Pironman stuff afterwards without installing anything else and making no updates the Pironman Dashboard works as expected.
Making the Pironman a Plex Media Server and installing all the necessary updates to the desktop versions of Raspbian Trixie the Dashboard page loads extremely slow and not to the end.
It was just an incident that I found some sort of solution myself by editing the
/boot/firmware/config.txt
and adding
dtoverlay=disable-wifi
dtoverlay=disable-bt
to the end of that file and rebooting the Pironman. Sunfounder’s support (thanks again a lot for Your help!) pointed me to a related topic in here which solved the problem in another way (https://forum.sunfounder.com/t/pironman-5-dashboard-empty/1218/51). That worked for some days even with BT and WiFi reactivated.
As my Pironman is configured to do security updates automatically and all others manually I don’t control every update whenever it happens. But I am pretty sure that another Trixie update smashed the Dashboard page again. Right now it starts loading but gets stuck at the very beginning of that loading processs, the browsers status bar does not even get close to it’s end (what it did when BT and WiFi where deactivated).
As far as I remember there where three more or less relevant updates to Trixie the last days: EEPROM, influx and raspi-config.
I am not really in need of that Dashboard page but it would be nice to have it on board.
After reboot, we accessed the dashboard via Google Chrome, and all data was displayed normally (see attached image).
These were our exact steps. If your procedure differed in any way, please provide us with the detailed steps you took. This will help us reproduce, analyze, and resolve the issue.
The major difference is that I did not use an SD card. I first installed the bootloader directly to a Lexar 620 NVME SSD and then the 64bit Trixie desktop version onto the same NVME SSD. The Raspberry Pi 16 GB RAM booted directly from that NVME SSD, not any SD card.
The second difference is that I do not use Chrome - solely Safari.
Using the developer console on Safari did not show any useful information, so I switched over to Firefox for Mac OS.
It might (…) be possible that the newest Mac OS update to Tahoe 26.0.1 is the reason but I am not sure of it. Several things in that version are somewhat glitchy.
Not running it yet in any of my 4 Pi’s (all but 1 are in Pironman 5’s) but have upgraded my main system to debian 13 and some things are glitchy there as well. Should have waited for .1.
