I have everything working well but when I reboot it does not auto-start. If I manually start it works fine.
here is what I get if I try to turn on auto start:
root@RetroPie:/boot# pironman -a on
enable auto-start at boot
Failed to enable unit: Unit file pironman.service does not exist.
restarting pironman
stopping pironman
pid=8142 10996
run in background
pironman start succeed
I tried starting over and reinstalling everything but get the same issue. any ideas what to try next?
Regarding the power-on autostart issue:
When the Pironman suddenly loses power, the motherboard chip will record the state and automatically boot up next time.
That is to say, when you directly unplug the power to turn off the machine, the motherboard chip will record the state, and the next time it will automatically turn on the machine.
If you press and hold the power button to turn off the computer, it will not turn on the computer next time, and you need to turn off the computer manually.
There is no command to control the power on/off of the pironman.
@SunFounder_Moderator Your response to @shigginswi does not address the original question. And I have the same (or similar) question. If I restate it differently, perhaps you can help both of us?
After I rebooted the Raspberry Pi 5 (installed in the Pironman 5 Max case), Linux resumes and I see all normal startup messages in the Syslog (as near as I can tell). However, the pironman5.service does not listen on port 34001, so when I attempt to use my browser to connect to the Pironman dashboard, I get web browser error:
This site can’t be reached
mainframe refused to connect.
ERR_CONNECTION_REFUSED
I have cleared browser cache and reloaded with same result. Investigating further on RP5 Debian Trixie Lite, and using SSH terminal, I see that the pironman5 daemon is not listening on port 34001 as expected. Here is output showing all listening ports:
raspb@MAINFRAME:~ $
raspb@MAINFRAME:~ $ sudo ss -tuln
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port
udp UNCONN 0 0 127.0.0.54:53 0.0.0.0:*
udp UNCONN 0 0 127.0.0.53:53 0.0.0.0:*
udp UNCONN 0 0 192.168.1.253:68 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:111 0.0.0.0:*
udp UNCONN 0 0 127.0.0.1:323 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:49643 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:38073 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:5355 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:47764 0.0.0.0:*
udp UNCONN 0 0 172.17.0.1:3702 0.0.0.0:*
udp UNCONN 0 0 239.255.255.250:3702 0.0.0.0:*
udp UNCONN 0 0 192.168.1.253:3702 0.0.0.0:*
udp UNCONN 0 0 239.255.255.250:3702 0.0.0.0:*
udp UNCONN 0 0 *:111 *:*
udp UNCONN 0 0 [::1]:323 *:*
udp UNCONN 0 0 *:54032 *:*
udp UNCONN 0 0 *:5353 *:*
udp UNCONN 0 0 *:5355 *:*
tcp LISTEN 0 5 172.17.0.1:5357 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:*
tcp LISTEN 0 100 127.0.0.1:25 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.1:8088 0.0.0.0:*
tcp LISTEN 0 5 192.168.1.253:5357 0.0.0.0:*
tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:*
tcp LISTEN 0 4096 0.0.0.0:5355 0.0.0.0:*
tcp LISTEN 0 50 0.0.0.0:445 0.0.0.0:*
tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
tcp LISTEN 0 511 0.0.0.0:80 0.0.0.0:*
tcp LISTEN 0 4096 0.0.0.0:111 0.0.0.0:*
tcp LISTEN 0 50 0.0.0.0:139 0.0.0.0:*
tcp LISTEN 0 4096 *:8086 *:*
tcp LISTEN 0 4096 [::]:5355 [::]:*
tcp LISTEN 0 50 [::]:445 [::]:*
tcp LISTEN 0 128 [::]:22 [::]:*
tcp LISTEN 0 4096 [::]:111 [::]:*
tcp LISTEN 0 50 [::]:139 [::]:*
raspb@MAINFRAME:~ $
I check the status of the pironman5 daemon:
raspb@MAINFRAME:~ $
raspb@MAINFRAME:~ $ sudo systemctl status pironman5.service
● pironman5.service - pironman5 service
Loaded: loaded (/etc/systemd/system/pironman5.service; enabled; preset: enabled)
Active: active (running) since Thu 2026-02-05 12:33:28 CST; 19min ago
Invocation: 91e9349583394e239c7af03f98d633a1
Process: 1707 ExecStart=/usr/local/bin/pironman5 start --background (code=exited, status=0/SUCCESS)
Main PID: 1708 (pironman5-servi)
Tasks: 6 (limit: 9580)
CPU: 14.659s
CGroup: /system.slice/pironman5.service
└─1708 /opt/pironman5/venv/bin/python3 /opt/pironman5/venv/bin/pironman5-service start
Feb 05 12:33:29 MAINFRAME pironman5[1708]: 26/02/05 12:33:29.108 [INFO] Initializing VibrationSwitch
Feb 05 12:33:29 MAINFRAME pironman5[1708]: 26/02/05 12:33:29.108 [INFO] Initializing VibrationSwitch on pin 26 with pull_up=True
Feb 05 12:33:29 MAINFRAME pironman5[1708]: 26/02/05 12:33:29.108 [INFO] VibrationSwitch initialized
Feb 05 12:33:29 MAINFRAME pironman5[1708]: 26/02/05 12:33:29.109 [WARNING] PM Dashboard not found skipping
Feb 05 12:33:29 MAINFRAME pironman5[1708]: 26/02/05 12:33:29.109 [INFO] PM Auto Start
Feb 05 12:33:29 MAINFRAME pironman5[1708]: 26/02/05 12:33:29.109 [INFO] PMAuto started
Feb 05 12:33:29 MAINFRAME pironman5[1708]: 26/02/05 12:33:29.166 [INFO] Connected to eth0: 192.168.1.253
Feb 05 12:33:29 MAINFRAME pironman5[1708]: 26/02/05 12:33:29.166 [INFO] Connected to docker0: 172.17.0.1
Feb 05 12:33:29 MAINFRAME pironman5[1708]: 26/02/05 12:33:29.287 [INFO] PWM Fan is supported, sync all other fan with pwm fan
Feb 05 12:35:29 MAINFRAME pironman5[1708]: 26/02/05 12:35:29.644 [INFO] OLED sleep timeout, sleeping
raspb@MAINFRAME:~ $
This status message of “[WARNING] PM Dashboard not found skipping” concerns me.
Have you installed the correct Pironman5 software?
You can refer to the installation guide here:
Download and install using the following commands:
cd ~
git clone -b max GitHub - sunfounder/pironman5: Code for Raspberry Pi 5 case (Pironman5) --depth 1
cd ~/pironman5
sudo python3 install.py
After confirming that the software has been installed successfully, please restart the system and check whether all functions are working properly, including whether the dashboard is accessible.
If any issues persist, we recommend providing the log information to help us analyze and resolve the problem:
cat /var/log/pironman5/main.log
Thank you for your response.
Here is the log file you requested. Note this error message had already been provided in my post. “[WARNING] PM Dashboard not found skipping”
Last login: Thu Feb 5 13:50:05 2026 from 192.168.1.61
raspb@MAINFRAME:~ $ cat /var/log/pironman5/main.log
26/02/05 13:49:40.860 [INFO]
26/02/05 13:49:40.860 [INFO] ############################################################
26/02/05 13:49:40.860 [DEBUG] Config path: /opt/pironman5/venv/lib/python3.13/site-packages/pironman5/config.json
26/02/05 13:49:40.860 [DEBUG] Pironman5 version: 1.2.26
26/02/05 13:49:40.860 [DEBUG] Variant: Pironman 5 Max
26/02/05 13:49:40.860 [DEBUG] Config: {'system': {'data_interval': 1, 'rgb_color': '#0a1aff', 'rgb_brightness': 50, 'rgb_style': 'hue_cycle', 'rgb_speed': 34, 'rgb_enable': True, 'rgb_led_count': 4, 'temperature_unit': 'C', 'oled_enable': True, 'oled_rotation': 0, 'oled_disk': '/dev/nvme0n1', 'oled_network_interface': 'all', 'gpio_fan_pin': 6, 'gpio_fan_mode': 1, 'gpio_fan_led': 'follow', 'gpio_fan_led_pin': 5, 'oled_sleep_timeout': 120, 'vibration_switch_pin': 26, 'vibration_switch_pull_up': False, 'debug_level': 'INFO'}}
26/02/05 13:49:40.860 [DEBUG] Device info: {'name': 'Pironman 5 Max', 'id': 'pironman5', 'peripherals': ['storage', 'cpu', 'network', 'memory', 'history', 'log', 'ws2812', 'cpu_temperature', 'gpu_temperature', 'temperature_unit', 'oled', 'clear_history', 'delete_log_file', 'pwm_fan_speed', 'gpio_fan_state', 'gpio_fan_mode', 'gpio_fan_led', 'vibration_switch', 'oled_sleep'], 'version': '1.2.26', 'app_name': 'pironman5'}
26/02/05 13:49:40.860 [DEBUG] PM_Auto version: 1.2.12
26/02/05 13:49:41.111 [WARNING] PM Dashboard not found skipping
26/02/05 13:49:41.112 [INFO] PMAuto started
raspb@MAINFRAME:~ $
The Pironman dashboard website was previously functional, but stopped working for unknown reason. The OLED mini display is functioning, so I know the pironman5 daemon is at least partially functional. The problem is the server is not listening for http on port 34001.
(P.S. I am a technical user. Yes of course I installed using the instructions and of course I restarted the Raspberry Pi 5 computer, that is how I encountered the problem.)
@SunFounder_Moderator Someone else has this symptom, different thread. Let us know. Thanks!
We have followed the steps in your tutorial for testing and verification. The dashboard is accessible, and the data is displaying normally. The issue you encountered may be intermittent.
To better assist in diagnosing the problem, could you confirm: Are you currently booting your system from an SSD?
Additionally, after executing the following commands, does the problem persist?
sudo service pironman5 stop
sudo rm -rf /var/lib/influxdb/data/pironman5
sudo rm -rf /var/lib/influxdb/wal/pironman5
sudo service pironman5 start
You may also refer to the community discussion and solutions shared by other users regarding an empty dashboard here:https://forum.sunfounder.com/t/pironman-5-dashboard-empty/1218/51
Thank you for the reply.
I am booting from a micro SD (SDXC) 32GB flash memory card.
Ran those commands to stop daemon, remove the influxdb data and wal, start daemon, but this did not help. I also looked at the forum topic you linked to and read through it; nothing there seems to apply to my situation. Please note: the problem is the website is not running (at least not on port 34001) and I am getting warning message in the start up.”[WARNING] PM Dashboard not found skipping”.
Here is the most recent console output with symptoms:
login as: raspb
raspb@mainframe’s password:
Linux MAINFRAME 6.12.62+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.62-1+rpt1 (2025-12-18) aarch64
Last login: Fri Feb 6 15:55:49 2026 from 192.168.1.28
raspb@MAINFRAME:~ $ sudo service pironman5 stop
raspb@MAINFRAME:~ $ sudo rm -rf /var/lib/influxdb/data/pironman5
raspb@MAINFRAME:~ $ sudo rm -rf /var/lib/influxdb/wal/pironman5
raspb@MAINFRAME:~ $ sudo service pironman5 start
raspb@MAINFRAME:~ $ cat /var/log/pironman5/main.log
26/02/05 13:49:40.860 [INFO]
26/02/05 13:49:40.860 [INFO] ############################################################
26/02/05 13:49:40.860 [DEBUG] Config path: /opt/pironman5/venv/lib/python3.13/site-packages/pironman5/config.json
26/02/05 13:49:40.860 [DEBUG] Pironman5 version: 1.2.26
26/02/05 13:49:40.860 [DEBUG] Variant: Pironman 5 Max
26/02/05 13:49:40.860 [DEBUG] Config: {‘system’: {‘data_interval’: 1, ‘rgb_color’: ‘#0a1aff’, ‘rgb_brightness’: 50, ‘rgb_style’: ‘hue_cycle’, ‘rgb_speed’: 34, ‘rgb_enable’: True, ‘rgb_led_count’: 4, ‘temperature_unit’: ‘C’, ‘oled_enable’: True, ‘oled_rotation’: 0, ‘oled_disk’: ‘/dev/nvme0n1’, ‘oled_network_interface’: ‘all’, ‘gpio_fan_pin’: 6, ‘gpio_fan_mode’: 1, ‘gpio_fan_led’: ‘follow’, ‘gpio_fan_led_pin’: 5, ‘oled_sleep_timeout’: 120, ‘vibration_switch_pin’: 26, ‘vibration_switch_pull_up’: False, ‘debug_level’: ‘INFO’}}
26/02/05 13:49:40.860 [DEBUG] Device info: {‘name’: ‘Pironman 5 Max’, ‘id’: ‘pironman5’, ‘peripherals’: [‘storage’, ‘cpu’, ‘network’, ‘memory’, ‘history’, ‘log’, ‘ws2812’, ‘cpu_temperature’, ‘gpu_temperature’, ‘temperature_unit’, ‘oled’, ‘clear_history’, ‘delete_log_file’, ‘pwm_fan_speed’, ‘gpio_fan_state’, ‘gpio_fan_mode’, ‘gpio_fan_led’, ‘vibration_switch’, ‘oled_sleep’], ‘version’: ‘1.2.26’, ‘app_name’: ‘pironman5’}
26/02/05 13:49:40.860 [DEBUG] PM_Auto version: 1.2.12
26/02/05 13:49:41.111 [WARNING] PM Dashboard not found skipping
26/02/05 13:49:41.112 [INFO] PMAuto started
26/02/09 13:31:25.602 [INFO] Received signal “Terminated”, cleaning up…
26/02/09 13:31:25.602 [INFO] Stopping Pironman5
26/02/09 13:31:25.602 [INFO] Stopping PMAuto
26/02/09 13:31:26.036 [INFO] Pironman5 stopped
26/02/09 13:31:26.036 [WARNING] Thread Thread-1 is still alive
26/02/09 13:32:22.713 [INFO]
26/02/09 13:32:22.714 [INFO] ############################################################
26/02/09 13:32:22.714 [DEBUG] Config path: /opt/pironman5/venv/lib/python3.13/site-packages/pironman5/config.json
26/02/09 13:32:22.714 [DEBUG] Pironman5 version: 1.2.26
26/02/09 13:32:22.714 [DEBUG] Variant: Pironman 5 Max
26/02/09 13:32:22.714 [DEBUG] Config: {‘system’: {‘data_interval’: 1, ‘rgb_color’: ‘#0a1aff’, ‘rgb_brightness’: 50, ‘rgb_style’: ‘hue_cycle’, ‘rgb_speed’: 34, ‘rgb_enable’: True, ‘rgb_led_count’: 4, ‘temperature_unit’: ‘C’, ‘oled_enable’: True, ‘oled_rotation’: 0, ‘oled_disk’: ‘/dev/nvme0n1’, ‘oled_network_interface’: ‘all’, ‘gpio_fan_pin’: 6, ‘gpio_fan_mode’: 1, ‘gpio_fan_led’: ‘follow’, ‘gpio_fan_led_pin’: 5, ‘oled_sleep_timeout’: 120, ‘vibration_switch_pin’: 26, ‘vibration_switch_pull_up’: False, ‘debug_level’: ‘INFO’}}
26/02/09 13:32:22.714 [DEBUG] Device info: {‘name’: ‘Pironman 5 Max’, ‘id’: ‘pironman5’, ‘peripherals’: [‘storage’, ‘cpu’, ‘network’, ‘memory’, ‘history’, ‘log’, ‘ws2812’, ‘cpu_temperature’, ‘gpu_temperature’, ‘temperature_unit’, ‘oled’, ‘clear_history’, ‘delete_log_file’, ‘pwm_fan_speed’, ‘gpio_fan_state’, ‘gpio_fan_mode’, ‘gpio_fan_led’, ‘vibration_switch’, ‘oled_sleep’], ‘version’: ‘1.2.26’, ‘app_name’: ‘pironman5’}
26/02/09 13:32:22.714 [DEBUG] PM_Auto version: 1.2.12
26/02/09 13:32:22.824 [WARNING] PM Dashboard not found skipping
26/02/09 13:32:22.825 [INFO] PMAuto started
raspb@MAINFRAME:~ $ sudo systemctl status pironman5.service
● pironman5.service - pironman5 service
Loaded: loaded (/etc/systemd/system/pironman5.service; enabled; preset: enabled)
Active: active (running) since Mon 2026-02-09 13:32:22 CST; 1min 39s ago
Invocation: 35d89d86f23743a6951c683eeccb0918
Process: 277170 ExecStart=/usr/local/bin/pironman5 start --background (code=exited, status=0/SUCCESS)
Main PID: 277171 (pironman5-servi)
Tasks: 6 (limit: 9580)
CPU: 3.287s
CGroup: /system.slice/pironman5.service
└─277171 /opt/pironman5/venv/bin/python3 /opt/pironman5/venv/bin/pironman5-service start
Feb 09 13:32:22 MAINFRAME pironman5[277171]: 26/02/09 13:32:22.822 [DEBUG] FanControl initialized
Feb 09 13:32:22 MAINFRAME pironman5[277171]: 26/02/09 13:32:22.823 [INFO] Initializing VibrationSwitch
Feb 09 13:32:22 MAINFRAME pironman5[277171]: 26/02/09 13:32:22.823 [INFO] Initializing VibrationSwitch on pin 26 with pull_up=True
Feb 09 13:32:22 MAINFRAME pironman5[277171]: 26/02/09 13:32:22.824 [INFO] VibrationSwitch initialized
Feb 09 13:32:22 MAINFRAME pironman5[277171]: 26/02/09 13:32:22.824 [WARNING] PM Dashboard not found skipping
Feb 09 13:32:22 MAINFRAME pironman5[277171]: 26/02/09 13:32:22.824 [INFO] PM Auto Start
Feb 09 13:32:22 MAINFRAME pironman5[277171]: 26/02/09 13:32:22.825 [INFO] PMAuto started
Feb 09 13:32:22 MAINFRAME pironman5[277171]: 26/02/09 13:32:22.848 [INFO] Connected to eth0: 192.168.1.253
Feb 09 13:32:22 MAINFRAME pironman5[277171]: 26/02/09 13:32:22.848 [INFO] Connected to docker0: 172.17.0.1
Feb 09 13:32:22 MAINFRAME pironman5[277171]: 26/02/09 13:32:22.962 [INFO] PWM Fan is supported, sync all other fan with pwm fan
raspb@MAINFRAME:~ $ sudo netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 381/systemd-resolve
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1128/master
tcp 0 0 172.17.0.1:5357 0.0.0.0:* LISTEN 188511/python3
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 381/systemd-resolve
tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 381/systemd-resolve
tcp 0 0 127.0.0.1:8088 0.0.0.0:* LISTEN 1185/influxd
tcp 0 0 192.168.1.253:5357 0.0.0.0:* LISTEN 188511/python3
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 188492/smbd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 931/sshd: /usr/sbin
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/init
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 935/nginx: master p
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 188492/smbd
tcp6 0 0 :::8086 :::* LISTEN 1185/influxd
tcp6 0 0 :::5355 :::* LISTEN 381/systemd-resolve
tcp6 0 0 :::139 :::* LISTEN 188492/smbd
tcp6 0 0 :::22 :::* LISTEN 931/sshd: /usr/sbin
tcp6 0 0 :::111 :::* LISTEN 1/init
tcp6 0 0 :::445 :::* LISTEN 188492/smbd
udp 0 0 0.0.0.0:55550 0.0.0.0:* 188511/python3
udp 0 0 0.0.0.0:44479 0.0.0.0:* 802/avahi-daemon: r
udp 0 0 172.17.0.1:3702 0.0.0.0:* 188511/python3
udp 0 0 239.255.255.250:3702 0.0.0.0:* 188511/python3
udp 0 0 192.168.1.253:3702 0.0.0.0:* 188511/python3
udp 0 0 239.255.255.250:3702 0.0.0.0:* 188511/python3
udp 0 0 0.0.0.0:40921 0.0.0.0:* 188511/python3
udp 0 0 127.0.0.54:53 0.0.0.0:* 381/systemd-resolve
udp 0 0 127.0.0.53:53 0.0.0.0:* 381/systemd-resolve
udp 0 0 192.168.1.253:68 0.0.0.0:* 400/systemd-network
udp 0 0 0.0.0.0:111 0.0.0.0:* 1/init
udp 0 0 127.0.0.1:323 0.0.0.0:* 943/chronyd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 802/avahi-daemon: r
udp 0 0 0.0.0.0:5355 0.0.0.0:* 381/systemd-resolve
udp6 0 0 :::44957 :::* 802/avahi-daemon: r
udp6 0 0 :::111 :::* 1/init
udp6 0 0 ::1:323 :::* 943/chronyd
udp6 0 0 :::5353 :::* 802/avahi-daemon: r
udp6 0 0 :::5355 :::* 381/systemd-resolve
raspb@MAINFRAME:~ $ sudo pironman5 -c
{
“system”: {
“data_interval”: 1,
“rgb_color”: “#0a1aff”,
“rgb_brightness”: 50,
“rgb_style”: “hue_cycle”,
“rgb_speed”: 34,
“rgb_enable”: true,
“rgb_led_count”: 4,
“temperature_unit”: “C”,
“oled_enable”: true,
“oled_rotation”: 0,
“oled_disk”: “/dev/nvme0n1”,
“oled_network_interface”: “all”,
“gpio_fan_pin”: 6,
“gpio_fan_mode”: 1,
“gpio_fan_led”: “follow”,
“gpio_fan_led_pin”: 5,
“oled_sleep_timeout”: 120,
“vibration_switch_pin”: 26,
“vibration_switch_pull_up”: false,
“debug_level”: “INFO”
}
}
raspb@MAINFRAME:~ $
Here are the other logs located in the /var/log/pironman5 directory. I don’t see anything to tell me why the dashboard is not being found and why the http service is not starting.
raspb@MAINFRAME:~ $ cd /var/log/pironman5
raspb@MAINFRAME:/var/log/pironman5 $ dir
main.log pm_auto.fan_control.log pm_auto.oled.log pm_auto.pm_auto.log pm_auto.ssd1306.log pm_auto.vibration_switch.log pm_auto.ws2812.log
raspb@MAINFRAME:/var/log/pironman5 $ cat pm_auto.fan_control.log
26/02/05 13:49:41.047 [DEBUG] Initializing FanControl
26/02/05 13:49:41.048 [DEBUG] Update gpio_fan_pin to 6
26/02/05 13:49:41.048 [DEBUG] Update gpio_fan_mode to 1
26/02/05 13:49:41.048 [DEBUG] Update gpio_fan_led to follow
26/02/05 13:49:41.048 [DEBUG] Update gpio_fan_led_pin to 5
26/02/05 13:49:41.048 [DEBUG] Init GPIO Fan with pin: 6, led_pin: 5
26/02/05 13:49:41.097 [DEBUG] Set led to follow
26/02/05 13:49:41.097 [DEBUG] Init PWM Fan
26/02/05 13:49:41.107 [DEBUG] FanControl initialized
26/02/05 13:49:41.291 [INFO] PWM Fan is supported, sync all other fan with pwm fan
26/02/09 13:32:22.789 [DEBUG] Initializing FanControl
26/02/09 13:32:22.789 [DEBUG] Update gpio_fan_pin to 6
26/02/09 13:32:22.789 [DEBUG] Update gpio_fan_mode to 1
26/02/09 13:32:22.789 [DEBUG] Update gpio_fan_led to follow
26/02/09 13:32:22.789 [DEBUG] Update gpio_fan_led_pin to 5
26/02/09 13:32:22.789 [DEBUG] Init GPIO Fan with pin: 6, led_pin: 5
26/02/09 13:32:22.811 [DEBUG] Set led to follow
26/02/09 13:32:22.811 [DEBUG] Init PWM Fan
26/02/09 13:32:22.822 [DEBUG] FanControl initialized
26/02/09 13:32:22.962 [INFO] PWM Fan is supported, sync all other fan with pwm fan
raspb@MAINFRAME:/var/log/pironman5 $ cat pm_auto.oled.log
26/02/05 13:49:41.030 [DEBUG] Update temperature_unit to C
26/02/05 13:49:41.030 [DEBUG] Update oled_rotation to 0
26/02/05 13:49:41.030 [DEBUG] Update oled_disk to /dev/nvme0n1
26/02/05 13:49:41.030 [DEBUG] Update oled_network_interface to all
26/02/05 13:49:41.030 [DEBUG] Update oled_sleep_timeout to 120
26/02/05 13:49:41.030 [DEBUG] Update oled_enable to True
26/02/05 13:49:41.030 [DEBUG] OLED wake up
26/02/05 13:49:41.169 [INFO] Connected to eth0: 192.168.1.253
26/02/05 13:49:41.169 [INFO] Connected to docker0: 172.17.0.1
26/02/05 13:51:41.628 [INFO] OLED sleep timeout, sleeping
26/02/05 19:41:59.419 [INFO] OLED sleep timeout, sleeping
26/02/09 13:32:22.774 [DEBUG] Update temperature_unit to C
26/02/09 13:32:22.775 [DEBUG] Update oled_rotation to 0
26/02/09 13:32:22.775 [DEBUG] Update oled_disk to /dev/nvme0n1
26/02/09 13:32:22.775 [DEBUG] Update oled_network_interface to all
26/02/09 13:32:22.775 [DEBUG] Update oled_sleep_timeout to 120
26/02/09 13:32:22.775 [DEBUG] Update oled_enable to True
26/02/09 13:32:22.775 [DEBUG] OLED wake up
26/02/09 13:32:22.848 [INFO] Connected to eth0: 192.168.1.253
26/02/09 13:32:22.848 [INFO] Connected to docker0: 172.17.0.1
26/02/09 13:34:23.717 [INFO] OLED sleep timeout, sleeping
raspb@MAINFRAME:/var/log/pironman5 $ cat pm_auto.pm_auto.log
26/02/05 13:49:40.984 [DEBUG] Initializing OLED
26/02/05 13:49:41.030 [DEBUG] OLED initialized
26/02/05 13:49:41.047 [DEBUG] WS2812 initialized
26/02/05 13:49:41.112 [INFO] PM Auto Start
26/02/05 19:39:59.233 [INFO] Vibration detected
26/02/09 13:31:26.036 [INFO] PM Auto stoped
26/02/09 13:32:22.732 [DEBUG] Initializing OLED
26/02/09 13:32:22.775 [DEBUG] OLED initialized
26/02/09 13:32:22.788 [DEBUG] WS2812 initialized
26/02/09 13:32:22.824 [INFO] PM Auto Start
raspb@MAINFRAME:/var/log/pironman5 $ cat pm_auto.ssd1306.log
raspb@MAINFRAME:/var/log/pironman5 $ cat pm_auto.vibration_switch.log
26/02/05 13:49:41.110 [INFO] Initializing VibrationSwitch
26/02/05 13:49:41.110 [INFO] Initializing VibrationSwitch on pin 26 with pull_up=True
26/02/05 13:49:41.111 [INFO] VibrationSwitch initialized
26/02/09 13:32:22.823 [INFO] Initializing VibrationSwitch
26/02/09 13:32:22.823 [INFO] Initializing VibrationSwitch on pin 26 with pull_up=True
26/02/09 13:32:22.824 [INFO] VibrationSwitch initialized
raspb@MAINFRAME:/var/log/pironman5 $ cat pm_auto.ws2812.log
26/02/05 13:49:41.031 [DEBUG] Update LED count: 4
26/02/05 13:49:41.031 [DEBUG] Update RGB enable: True
26/02/05 13:49:41.031 [DEBUG] Update RGB color: [10, 26, 255]
26/02/05 13:49:41.031 [DEBUG] Update RGB brightness: 50
26/02/05 13:49:41.031 [DEBUG] Update RGB speed: 34
26/02/05 13:49:41.031 [DEBUG] Update RGB style: hue_cycle
26/02/09 13:32:22.775 [DEBUG] Update LED count: 4
26/02/09 13:32:22.776 [DEBUG] Update RGB enable: True
26/02/09 13:32:22.776 [DEBUG] Update RGB color: [10, 26, 255]
26/02/09 13:32:22.776 [DEBUG] Update RGB brightness: 50
26/02/09 13:32:22.776 [DEBUG] Update RGB speed: 34
26/02/09 13:32:22.776 [DEBUG] Update RGB style: hue_cycle
raspb@MAINFRAME:/var/log/pironman5 $
Please provide the following detailed information about your specific setup and the steps you have taken:
Information Needed:
Operating System Version: Which specific version of Raspberry Pi OS are you using?
Installation Steps: Please share the exact commands and procedure you followed to install the Pironman 5 software.
Other Software: Are any other significant software packages or services installed on the system?
Service Logs: Please provide the startup logs of the Pironman 5 service. You can check them with this command:
sudo journalctl -u pironman5 -n 50 --no-pager
Browser and Mode: Which web browser (and version) are you using to access the dashboard? Have you tried using the browser’s incognito/private mode?
Suggested Troubleshooting Steps:
If possible, we also recommend performing a fresh installation as a diagnostic step:
Try using a different SD card or SSD.
Install a clean version of the operating system.
Reinstall the Pironman 5 software following the official guide.
Check if the dashboard functions correctly on this new setup.
I will try a re-installation. Then if the symptom reoccurs, I will report back with the requested data.
The instructions contained an error in the formatting of the hyperlink, but I worked around it. I do not recall if I included the “-b max” and “–depth 1” in my original install… This installation deviates from the instructions on the pironman5 git article.
After the restart the dashboard is once again working. Time will tell if it stays operational. I’ll give it a week and a few restarts.
Thanks for your help thus far.
I’m pasting the terminal here:
raspb@MAINFRAME:/ $ pwd
/
raspb@MAINFRAME:/ $ git clone -b max GitHub - sunfounder/pironman5: Code for Raspberry Pi 5 case (Pironman5) --depth 1
-bash: syntax error near unexpected token `('
raspb@MAINFRAME:/ $
raspb@MAINFRAME:/ $ sudo git clone -b max https://github.com/sunfounder/pironman5.git --depth 1
Cloning into 'pironman5'...
remote: Enumerating objects: 32, done.
remote: Counting objects: 100% (32/32), done.
remote: Compressing objects: 100% (29/29), done.
remote: Total 32 (delta 2), reused 15 (delta 0), pack-reused 0 (from 0)
Receiving objects: 100% (32/32), 31.01 KiB | 1.55 MiB/s, done.
Resolving deltas: 100% (2/2), done.
raspb@MAINFRAME:/ $ cd /pironman5
raspb@MAINFRAME:/pironman5 $ sudo python3 install.py
Installing for Pironman 5 Max
Version: 1.2.26
Install build dependencies...
- Update package list... Done
- Install build dependencies: python3-pip python3-venv git curl... Done
Run commands before install...
- Run command before install: Setup InfluxDB... Done
- Run command before install: Install LGPIO... Done
Install APT dependencies...
- Install APT dependencies: kmod libopenjp2-7 libjpeg-dev python3-gpiozero influxdb libfreetype6-dev python3-dev i2c-tools lsof... Done
Create working directory...
- Create work directory... Done
- Change work directory mode... Done
- Change work directory owner... Done
- Create log directory... Done
- Change log directory mode... Done
- Change log directory owner... Done
- Remove old virtual environment... Done
- Create virtual environment... Done
Install PIP dependencies...
- Install pip... Done
- Install setuptools... Done
- Install requests... Done
- Install build... Done
- Install smbus2... Done
- Install adafruit-circuitpython-neopixel-spi... Done
- Install gpiod... Done
- Install gpiozero... Done
- Install rpi.lgpio... Done
- Install Pillow... Done
- Install Adafruit-Blinka==8.59.0... Done
Check git URL...
- Use https://github.com/sunfounder/ as git URL
Install Python source packages...
- Uninstall pironman5 old package... Done
- Install pironman5 from source... Done
- Uninstall pm_auto old package... Done
- Install pm_auto from source... Done
- Uninstall pm_dashboard old package... Done
- Install pm_dashboard from source... Done
- Uninstall sf_rpi_status old package... Done
- Install sf_rpi_status from source... Done
Setup auto start...
- Copy binary file... Done
- Change binary file mode... Done
- Copy service file... Done
- Enable service... Done
- Reload systemd... Done
Probe modules...
- add module: i2c-dev... Done
Copy device tree overlay...
- Copy dtoverlay sunfounder-pironman5.dtbo... Done
Change work directory owner...
- Change work directory owner... Done
Finished
Cleanup
- Remove build... Done
Whether to restart for the changes to take effect(Y/N):
The pironman5 service seemed to have hung, the dashboard was unresponsive.
Is there a bug which is actively being worked to develop a fix?
But there is the work-around solution to dashboard missing: See sunfounder forum community solution
sudo service pironman5 stop
rm -rf /var/lib/influxdb/data/pironman5
rm -rf /var/lib/influxdb/wal/pironman5
influx
USE pironman5;
CREATE RETENTION POLICY “7d” ON “pironman5” DURATION 7d REPLICATION 1 DEFAULT;
exit
sudo nano /opt/pironman5/venv/lib/python3./site-packages/pironman5/config.json
→ edit file to change “data_interval”: value from 1 to 5 or 10
→ Ctrl-X and Y to save change
cat /opt/pironman5/venv/lib/python3./site-packages/pironman5/config.json
sudo systemctl restart influxdb
sudo systemctl restart pironman5
sudo pironman5 -c
Recommended Values:
data_interval = 1: Default (writes to InfluxDB every second) - High resource usage
data_interval = 5: Good balance - reduces writes by 80%
data_interval = 10: Recommended for resource savings - reduces writes by 90%
data_interval = 60: Minimal resource usage - only writes once per minute
Complete all of the numbered [1.], [2.], [3.] steps.
sudo git clone -b max https://github.com/sunfounder/pironman5.git` --depth 1
cd /pironman5
sudo python3 install.py`
Thank you to original forum solution at this link: https://forum.sunfounder.com/t/pironman-5-dashboard-empty/1218/51
sudo service pironman5 stop
rm -rf /var/lib/influxdb/data/pironman5
rm -rf /var/lib/influxdb/wal/pironman5
influx
> USE pironman5;
> CREATE RETENTION POLICY "7d" ON "pironman5" DURATION 7d REPLICATION 1 DEFAULT;
> exit
sudo nano /opt/pironman5/venv/lib/python3.*/site-packages/pironman5/config.json
--> edit file to change "data_interval": value from 1 to 5 or 10
--> Ctrl-X to save change
cat /opt/pironman5/venv/lib/python3.*/site-packages/pironman5/config.json
sudo systemctl restart influxdb
sudo systemctl restart pironman5
sudo pironman5 -c
Recommended Values:
data_interval = 1: Default (writes to InfluxDB every second) - High resource usage
data_interval = 5: Good balance - reduces writes by 80%
data_interval = 10: Recommended for resource savings - reduces writes by 90%
data_interval = 60: Minimal resource usage - only writes once per minute
The default Pironman InfluxDB database is located in rootfs /var/lib/influxdb on the 32GB micro SD flash drive. Since I do not want to hammer this flash drive with constant writes (and thus increase the wear rate and reduce its useful life), it is important to redirect the DB writes to another disk. (It isn’t like this monitoring history is critical, but the life of the micro SD flash drive is!) The procedure below updates the influxdb.conf to change the default location for the meta, data, and wal folders. Most of the commands must be run from elevated sudo (root). Your data disk UUID will vary, and of course, you can use a different name for your folders. The shell commands below are unique to my Raspberry Pi 5.
blkid
/dev/nvme0n1p1: UUID="8d7f318f-4fa6-4621-b0e6-5203134f3b22" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="775b5f67-1175-4004-a04e-7c4558df4fe7"
/dev/mmcblk0p1: LABEL_FATBOOT="bootfs" LABEL="bootfs" UUID="EACA-13DA" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="b74c16a4-01"
/dev/mmcblk0p2: LABEL="rootfs" UUID="21724cc6-e5a3-48a1-8643-7917dba3a9fb" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b74c16a4-02"
/dev/sda1: UUID="2602bb14-2801-4226-b3eb-817478e4022d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="8ff4e689-e105-404e-b939-ef28a61427c3"
/dev/loop0: TYPE="swap"
/dev/zram0: LABEL="zram0" UUID="48438c5f-e25c-4805-a901-cb84331b2984" TYPE="swap"
cat /etc/fstab
proc /proc proc defaults 0 0
PARTUUID=b74c16a4-01 /boot/firmware vfat defaults 0 2
PARTUUID=b74c16a4-02 / ext4 noatime,nodiratime,defaults 0 1
# >>> [openmediavault]
/dev/disk/by-uuid/8d7f318f-4fa6-4621-b0e6-5203134f3b22 /srv/dev-disk-by-uuid-8d7f318f-4fa6-4621-b0e6-5203134f3b22 ext4 defaults,nofail,user_xattr,usrquota,grpquota,acl 0 2
/dev/disk/by-uuid/2602bb14-2801-4226-b3eb-817478e4022d /srv/dev-disk-by-uuid-2602bb14-2801-4226-b3eb-817478e4022d ext4 defaults,nofail,user_xattr,usrquota,grpquota,acl 0 2
# <<< [openmediavault]
cat /etc/influxdb/influxdb.conf
### Welcome to the InfluxDB configuration file.
#
...
[meta]
# Where the metadata/raft database is stored
dir = "/var/lib/influxdb/meta"
...
[data]
# The directory where the TSM storage engine stores TSM files.
dir = "/var/lib/influxdb/data"
# The directory where the TSM storage engine stores WAL files.
wal-dir = "/var/lib/influxdb/wal"
...
ls -ld /var/lib/influxdb/meta
drwxr-xr-x 2 influxdb influxdb 4096 Feb 21 17:35 meta
ls -ld /var/lib/influxdb/data
drwxr-xr-x 4 influxdb influxdb 4096 Feb 18 15:15 data
ls -ld /var/lib/influxdb/wal
drwx------ 4 influxdb influxdb 4096 Feb 18 15:15 wal
cd /srv/dev-disk-by-uuid-8d7f318f-4fa6-4621-b0e6-5203134f3b22
mkdir pironman
cd pironman
mkdir influxdb
cd influxdb
mkdir meta
mkdir data
mkdir wal
chown influxdb:influxdb /srv/dev-disk-by-uuid-8d7f318f-4fa6-4621-b0e6-5203134f3b22/pironman/influxdb
chown influxdb:influxdb /srv/dev-disk-by-uuid-8d7f318f-4fa6-4621-b0e6-5203134f3b22/pironman/influxdb/meta
chown influxdb:influxdb /srv/dev-disk-by-uuid-8d7f318f-4fa6-4621-b0e6-5203134f3b22/pironman/influxdb/data
chown influxdb:influxdb /srv/dev-disk-by-uuid-8d7f318f-4fa6-4621-b0e6-5203134f3b22/pironman/influxdb/wal
ls -ld influxdb
drwxr-xr-x 5 influxdb influxdb 4096 Feb 21 18:24 influxdb
ls -ld influxdb/meta
drwxr-xr-x 2 influxdb influxdb 4096 Feb 21 18:23 influxdb/meta
ls -ld influxdb/data
drwxr-xr-x 2 influxdb influxdb 4096 Feb 21 18:24 influxdb/data
ls -ld influxdb/wal
drwxr-xr-x 2 influxdb influxdb 4096 Feb 21 18:24 influxdb/wal
cd /etc/influxdb
nano influxdb.conf
cat influxdb.conf
...
[meta]
# dir = "/var/lib/influxdb/meta" (DEFAULT VALUE)
dir = "/srv/dev-disk-by-uuid-8d7f318f-4fa6-4621-b0e6-5203134f3b22/pironman/influxdb/meta"
...
[data]
# dir = "/var/lib/influxdb/data" (DEFAULT VALUE)
dir = "/srv/dev-disk-by-uuid-8d7f318f-4fa6-4621-b0e6-5203134f3b22/pironman/influxdb/data"
# wal-dir = "/var/lib/influxdb/wal" (DEFAULT VALUE)
wal-dir = "/srv/dev-disk-by-uuid-8d7f318f-4fa6-4621-b0e6-5203134f3b22/pironman/influxdb/wal"
...
There was a power outage overnight, my UPS signaled to a NUT service running on my Raspberry Pi 5 to shutdown as a precaution, the normal shutdown occurred. When power returned (this is a bit confusing since the battery did not drain completely) and Linux restarted.
But now my pironman5 dashboard is BLANK. I thought we had this fixed. Apparently not. Would someone from SunFounder please help look into this? My solution (previous post) does not seem to be bullet proof.
Here is the log:
26/03/13 05:04:32.811 [INFO] Received signal "Terminated", cleaning up...
26/03/13 05:04:32.811 [INFO] Stopping Pironman5
26/03/13 05:04:32.811 [INFO] Stopping PMAuto
26/03/13 05:04:33.149 [INFO] Stopping PmDashboard
26/03/13 05:04:34.367 [INFO] Pironman5 stopped
26/03/13 05:04:34.368 [WARNING] Thread Thread-1 is still alive
26/03/13 06:49:39.901 [INFO]
26/03/13 06:49:39.901 [INFO] ############################################################
26/03/13 06:49:39.902 [DEBUG] Config path: /opt/pironman5/venv/lib/python3.13/site-packages/pironman5/config.json
26/03/13 06:49:39.902 [DEBUG] Pironman5 version: 1.2.26
26/03/13 06:49:39.902 [DEBUG] Variant: Pironman 5 Max
26/03/13 06:49:39.902 [DEBUG] Config: {'system': {'data_interval': 5, 'rgb_color': '#0a1aff', 'rgb_brightness': 33, 'rgb_style': 'hue_cycle', 'rgb_speed': 33, 'rgb_enable': True, 'rgb_led_count': 4, 'temperature_unit': 'C', 'oled_enable': True, 'oled_rotation': 0, 'oled_disk': '/dev/nvme0n1', 'oled_network_interface': 'all', 'gpio_fan_pin': 6, 'gpio_fan_mode': 1, 'gpio_fan_led': 'follow', 'gpio_fan_led_pin': 5, 'oled_sleep_timeout': 60, 'vibration_switch_pin': 26, 'vibration_switch_pull_up': False, 'debug_level': 'INFO'}}
26/03/13 06:49:39.902 [DEBUG] Device info: {'name': 'Pironman 5 Max', 'id': 'pironman5', 'peripherals': ['storage', 'cpu', 'network', 'memory', 'history', 'log', 'ws2812', 'cpu_temperature', 'gpu_temperature', 'temperature_unit', 'oled', 'clear_history', 'delete_log_file', 'pwm_fan_speed', 'gpio_fan_state', 'gpio_fan_mode', 'gpio_fan_led', 'vibration_switch', 'oled_sleep'], 'version': '1.2.26', 'app_name': 'pironman5'}
26/03/13 06:49:39.902 [DEBUG] PM_Auto version: 1.2.12
26/03/13 06:49:39.902 [DEBUG] PM_Dashboard version: 1.2.10
26/03/13 06:49:45.104 [INFO] PMAuto started
26/03/13 06:49:45.193 [INFO] PmDashboard started
Try stopping the service and then manually running it to see what errors are printed:
sudo systemctl stop pironman5
sudo pironman5 start
And please send the error messages to us.
Thanks for the reply. Sorry for the delay replying…
Still blank dashboard. The web page responds, but there is no displayed data. The startup log is the same as I originally posted (namely, no errors reported).
Results from your recommended actions:
login as: raspbroot
raspbroot@mainframe's password:
Linux MAINFRAME 6.12.62+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.62-1+rpt1 (202 5-12-18) aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Mar 3 20:45:47 2026 from 192.168.1.8
raspbernie@MAINFRAME:~ $ sudo systemctl stop pironman5
raspbernie@MAINFRAME:~ $ sudo pironman5 start
26/03/21 17:07:24.082 [INFO]
26/03/21 17:07:24.082 [INFO] ############################################################
26/03/21 17:07:24.082 [DEBUG] Config path: /opt/pironman5/venv/lib/python3.13/site-packages/pironman5/config.json
26/03/21 17:07:24.082 [DEBUG] Pironman5 version: 1.2.26
26/03/21 17:07:24.082 [DEBUG] Variant: Pironman 5 Max
26/03/21 17:07:24.082 [DEBUG] Config: {'system': {'data_interval': 5, 'rgb_color': '#0a1aff', 'rgb_brightness': 33, 'rgb_style': 'hue_cycle', 'rgb_speed': 33, 'rgb_enable': True, 'rgb_led_count': 4, 'temperature_unit': 'C', 'oled_enable': True, 'oled_rotation': 0, 'oled_disk': '/dev/nvme0n1', 'oled_network_interface': 'all', 'gpio_fan_pin': 6, 'gpio_fan_mode': 1, 'gpio_fan_led': 'follow', 'gpio_fan_led_pin': 5, 'oled_sleep_timeout': 60, 'vibration_switch_pin': 26, 'vibration_switch_pull_up': False, 'debug_level': 'INFO'}}
26/03/21 17:07:24.082 [DEBUG] Device info: {'name': 'Pironman 5 Max', 'id': 'pironman5', 'peripherals': ['storage', 'cpu', 'network', 'memory', 'history', 'log', 'ws2812', 'cpu_temperature', 'gpu_temperature', 'temperature_unit', 'oled', 'clear_history', 'delete_log_file', 'pwm_fan_speed', 'gpio_fan_state', 'gpio_fan_mode', 'gpio_fan_led', 'vibration_switch', 'oled_sleep'], 'version': '1.2.26', 'app_name': 'pironman5'}
26/03/21 17:07:24.082 [DEBUG] PM_Auto version: 1.2.12
26/03/21 17:07:24.082 [DEBUG] PM_Dashboard version: 1.2.10
26/03/21 17:07:24.100 [DEBUG] Initializing OLED
26/03/21 17:07:24.142 [DEBUG] Update temperature_unit to C
26/03/21 17:07:24.142 [DEBUG] Update oled_rotation to 0
26/03/21 17:07:24.142 [DEBUG] Update oled_disk to /dev/nvme0n1
26/03/21 17:07:24.142 [DEBUG] Update oled_network_interface to all
26/03/21 17:07:24.142 [DEBUG] Update oled_sleep_timeout to 60
26/03/21 17:07:24.142 [DEBUG] Update oled_enable to True
26/03/21 17:07:24.142 [DEBUG] OLED wake up
26/03/21 17:07:24.142 [DEBUG] OLED initialized
26/03/21 17:07:24.143 [DEBUG] Update LED count: 4
26/03/21 17:07:24.143 [DEBUG] Update RGB enable: True
26/03/21 17:07:24.143 [DEBUG] Update RGB color: [10, 26, 255]
26/03/21 17:07:24.143 [DEBUG] Update RGB brightness: 33
26/03/21 17:07:24.143 [DEBUG] Update RGB speed: 33
26/03/21 17:07:24.143 [DEBUG] Update RGB style: hue_cycle
26/03/21 17:07:24.155 [DEBUG] WS2812 initialized
26/03/21 17:07:24.155 [DEBUG] Initializing FanControl
26/03/21 17:07:24.156 [DEBUG] Update gpio_fan_pin to 6
26/03/21 17:07:24.156 [DEBUG] Update gpio_fan_mode to 1
26/03/21 17:07:24.156 [DEBUG] Update gpio_fan_led to follow
26/03/21 17:07:24.156 [DEBUG] Update gpio_fan_led_pin to 5
26/03/21 17:07:24.156 [DEBUG] Init GPIO Fan with pin: 6, led_pin: 5
26/03/21 17:07:24.178 [DEBUG] Set led to follow
26/03/21 17:07:24.178 [DEBUG] Init PWM Fan
26/03/21 17:07:24.189 [DEBUG] FanControl initialized
26/03/21 17:07:24.189 [INFO] Initializing VibrationSwitch
26/03/21 17:07:24.190 [INFO] Initializing VibrationSwitch on pin 26 with pull_up=True
26/03/21 17:07:24.190 [INFO] VibrationSwitch initialized
26/03/21 17:07:26.588 [INFO] SPC peripheral disabled
26/03/21 17:07:28.994 [INFO] Setting debug level to INFO
26/03/21 17:07:28.994 [INFO] PM Auto Start
26/03/21 17:07:28.994 [INFO] PMAuto started
26/03/21 17:07:29.024 [INFO] Connected to eth0: 192.168.1.253
26/03/21 17:07:29.024 [INFO] Connected to docker0: 172.17.0.1
26/03/21 17:07:29.024 [INFO] Connected to br-b086d067df95: 172.18.0.1
26/03/21 17:07:29.045 [INFO] Influxdb is ready
26/03/21 17:07:29.049 [INFO] Dashboard Server start
26/03/21 17:07:29.050 [INFO] PmDashboard started
26/03/21 17:07:29.062 [DEBUG] Waiting for InfluxDB to be ready
26/03/21 17:07:29.084 [INFO] Influxdb is ready
26/03/21 17:07:29.085 [INFO] Data Logger Start
26/03/21 17:07:29.143 [INFO] PWM Fan is supported, sync all other fan with pwm fan
Then, of course I had to Ctrl-C to break out of the start up console and restart the service:
sudo systemctl start pironman5
After a power outage, the case shut down. After restarting, the dashboard shows blank data. Does refreshing the browser or using an incognito browser also fail to display the data properly?
Aside from the dashboard not displaying data correctly, can all other functions of the case be modified and controlled normally?
We recommend that you go to the dashboard settings page to clear the historical data, then restart the software service to see if that resolves the issue.
If the problem persists, we suggest reinstalling the pironman5 software and checking again.
cd ~/pironman5
sudo python3 install.py
I had previously done a browser clear cache and hard reload on the web page, but per your instructions, tried an incognito (Google Chrome) session; in all cases there is no information displayed. Conclusion: this is not a client browser problem.
Sorry, I should have said that the Max case OLED display is working and the case fan color LEDs are illuminated. Conclusion: this is not a hardware problem.
When I use the download option to capture dashboard history, the downloaded data.csv file is empty. Only a single record containing the word “time” is downloaded. Theory: the database is unable to supply data to the download function?
When I do the CLEAR action in dashboard settings, the dashboard resumes displaying real-time data in the web GUI and when I download the history data to csv, I find valid records in the history file has been downloaded. So, when I modified the influxdb.conf I observed that it is in a format of an older, unsupported version of InfluxDB. Can you ask the SunFounder developers to review whether this is a known problem with older versions of InfluxDB? Theory: a newer version of InfluxDB is needed.
Notice that each sample is being taken at 6 second intervals, which confirms my desired influxdb.conf settings (see earlier in this thread for a description of work-around).
Here is a portion of the data.csv downloaded:
| time | cpu_temperature |
|---|---|
| 2026-03-24T01:12:54Z | 38.6 |
| 2026-03-24T01:13:00Z | 38.05 |
| 2026-03-24T01:13:06Z | 39.15 |
| 2026-03-24T01:13:12Z | 38.6 |
| 2026-03-24T01:13:18Z | 37.775 |
| 2026-03-24T01:13:24Z | 38.6 |
In the Dashboard there is data in the logs and I see this clue, [WARNING] Thread Thread-1 is still alive. Everything else looks like normal messages. Theory: this seems like a bug since the stop signal was sent. The thread should also end?
26/03/21 17:12:14.269 [INFO] Received signal "Interrupt", cleaning up...
26/03/21 17:12:14.270 [INFO] Stopping Pironman5
26/03/21 17:12:14.270 [INFO] Stopping PMAuto
26/03/21 17:12:14.598 [INFO] Stopping PmDashboard
26/03/21 17:12:19.442 [INFO] Pironman5 stopped
26/03/21 17:12:19.442 [WARNING] Thread Thread-1 is still alive
26/03/21 17:07:29.084 [INFO] Influxdb is ready
26/03/21 17:12:19.086 [INFO] Database closed
26/03/21 17:12:19.086 [INFO] Database closed
26/03/21 17:13:43.741 [INFO] Setting debug level to INFO
26/03/21 17:13:43.800 [INFO] Influxdb is ready
26/03/21 17:13:43.817 [DEBUG] Waiting for InfluxDB to be ready
26/03/21 17:13:43.838 [INFO] Influxdb is ready
26/03/23 20:12:57.590 [INFO] Clearing database: pironman5
26/03/23 20:12:57.656 [INFO] Database 'pironman5' cleared successfully
Thank you very much for your feedback.
Regarding whether a newer version of InfluxDB is required, we are not yet certain at this moment and will need to look into this further.