Will support for the Home Assistant OS be added at any time? I have five f these cases now and plan on buying more for a community wide automation project and would love to be able to control these more from the Home Assistant OS. Currently the only thing I have been able to control/automate is the CPU fan.
Our engineers are working hard to try to implement this solution.
We’ve done a good job with the suggestions you made. We have made a Home Assistant Addon for Pironman. You can start by reading this how-to guide at GitHub - sunfounder/home-assistant-addon. More detailed documentation is being written and will be available in a while. See our Pironman online tutorials.
1 Like
I have been trying to get this running with the instructions provided, but seem to be running into some issues. I created the CONFIG folder, but if I boot the OS, shut it down and check, that folder is gone.
For the config.txt file it is not clear how to decide whether to use PWM(GPIO12), SPI(GPIO10), or PCM(GPIO21)
If you encounter any problems or do not understand anything in the process of using it, please explain it in detail, preferably with screenshots, so that we can help you analyze and solve it.
Please note that the rpi-i2c.conf file, suffixed with conf
- For PWM(GPIO12), it uses audio to drive LEDs, so turn off audio.
Find dtparam=audio=off, if the default is dtparam=audio=off, you don’t need that, if it is NO, change it to off.
Also select PWM(GPIO12) for the pironman installed on Home Assistant. The IO interface of the motherboard should also correspond to PWM(GPIO12)
PWM (GPIO10, 21) operate in the same way. Choose one of the three
You can directly add the corresponding content at the end of the config.txt file.
I think the main issue I am facing at the moment is that after creating the folder CONFIG in the root of hassos-boot, it somehow gets deleted on startup. One thing to note is that I am running on the SSD module instead of an SD card. The following error is seen when starting up the add-on:
Add-on: Pironman
Pironman support
Add-on version: 1.0.3
You are running the latest version of this add-on.
System: Home Assistant OS 10.3 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.7.1
Home Assistant Supervisor: 2023.07.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[10:58:24] INFO: Configuring timezone (America/Denver)…
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Starting pironman with the following parameters:
temperature_unit: F
fan_temp: 50
display_always_on: true
display_on_for: 30
rgb_on: true
rgb_style: colorful
rgb_color: 0a1aff
rgb_speed: 50
rgb_freq: 1000
rgb_pin: 12
Warning: Cannot find boot configuration file
set temperature unit to F
I am not sure how to track down why the CONFIG folder and all it’s contents get deleted each time it boots.
To create the file I remove the SSD from the PIRONMAN. I connect it to my Windows 11 PC. I open the hassos drive and then create the CONFIG folder as noted in the instructions. I then create the modules folder and the rpi-i2c.conf file with the noted contents. I shut the SSD down and reinstall it in the PIRONMAN and boot and then see the error above.
The CONFIG file does disappear after startup, this is normal. If you have an older version of Pironman, where the RGB pins only have GPIO12 pins, then he can only select PWM (GPIO12). the RGB multi-pin selection is only available in newer versions.
If the logs you posted are complete, then the plugin should be running fine. warning is a warning because the boot folder can’t be read on hassio, it doesn’t affect the plugin’s normal use.
Is there anything that isn’t working properly now?
Hello,
I just managed to install the case with a pi4B running Home Assistant OS (so I used the new add-on). After some trial and error I got the work but still not full feature. The issue is that, if I use the configuration tab from the add-on to change fan temperature start or RGB effect, or the on/off display always on toggle, the changes don’t take effect. I am attaching the log. In the log you will see for example that in the config page I set the CPU fan temp to 45 yet the configuration loaded is with the default value of 50. Could you please provide feedback? Thanks.
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
Add-on: Pironman
Pironman support
Add-on version: 1.0.3
You are running the latest version of this add-on.
System: Home Assistant OS 10.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.7.2
Home Assistant Supervisor: 2023.07.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[19:48:42] INFO: Configuring timezone (Europe/Bucharest)…
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Starting pironman with the following parameters:
temperature_unit: C
fan_temp: 45
display_always_on: true
display_on_for: 30
rgb_on: true
rgb_style: colorful
rgb_color: 0a1aff
rgb_speed: 50
rgb_freq: 1000
rgb_pin: 10
Warning: Cannot find boot configuration file
sed: no input files
sed: no input files
set temperature unit to C
set the fan on temperature to 45
sed: no input files
set screen_always_on to on
sed: no input files
set screen_off_time to 30
sed: no input files
set rgb_enable to on
sed: no input files
set rgb_switch to on
sed: no input files
set rgb_style to colorful
sed: no input files
set rgb_color to 0a1aff
sed: no input files
set rgb_blink_speed to 50
sed: no input files
set rgb_pwm_freq to 1000
sed: no input files
set rgb io to pin 10 (spi)
grep: : No such file or directory
sed: can’t read : No such file or directory
run in foreground
23/08/03 19:48:45,163 [DEBUG] Home Assistant Addon mode
------------------------23/08/03 19:48:45------------------------
pironman version: 2.2.1
username:
config_file: /opt/pironman/config.txt
PCB info:
Revision : c03112
Model : Raspberry Pi 4 Model B Rev 1.2
23/08/03 19:48:45,214 [DEBUG] power_key_pin : 16
23/08/03 19:48:45,215 [DEBUG] fan_pin : 6
23/08/03 19:48:45,215 [DEBUG] update_frequency : 0.5
23/08/03 19:48:45,216 [DEBUG] temp_unit : C
23/08/03 19:48:45,216 [DEBUG] fan_temp : 50.0
23/08/03 19:48:45,217 [DEBUG] screen_always_on : False
23/08/03 19:48:45,217 [DEBUG] screen_off_time : 60
23/08/03 19:48:45,218 [DEBUG] rgb_enable : True
23/08/03 19:48:45,218 [DEBUG] rgb_switch: True
23/08/03 19:48:45,219 [DEBUG] rgb_style : breath
23/08/03 19:48:45,219 [DEBUG] rgb_color : 0a1aff
23/08/03 19:48:45,220 [DEBUG] rgb_blink_speed : 50
23/08/03 19:48:45,220 [DEBUG] rgb_pwm_freq : 1000
23/08/03 19:48:45,221 [DEBUG] rgb_pin : 10
23/08/03 19:48:45,221 [DEBUG]
23/08/03 19:48:45,240 [DEBUG] oled init success
23/08/03 19:48:45,254 [DEBUG] rgb_show
23/08/03 19:48:45,261 [DEBUG] rgb_show: breath
23/08/03 19:48:45,491 [DEBUG] Got IPs: {‘eth0’: ‘192.168.1.245’}
getCPUuse: could not convert string to float: ‘id.\n’
getCPUuse: could not convert string to float: ‘id.\n’
We’ve fixed the problem that you’ve fed back to us.
We have updated the pironman software to version 1.0.6.
Try refreshing, updating the version and starting the pironman service again.
Go to the add-in and click on Refresh in the upper right corner, then click on Pironman Update.
Well, that was fast. I updated to 1.0.6 and works just fine. Great support, thanks!
It would be great if you could keep upgrading this integration. For example, the LEDs look great but are pretty powerful to have them on in the night. Would be helpful to be able to control them via a schedule or IR or some other input (and not change the config every evening/morning).
Regarding the fan, the configuration determines the temperature at which the fan activates. The issue arises because there isn’t a range, such as starting at 50 degrees C and stopping at 45 degrees C. With only a singular setpoint, the fan frequently toggles on and off, given that the temperature hovers around that specific value.
Thank you very much for your suggestions, at present we really can only go to work in this way, the follow-up we will receive user feedback on all issues, comprehensive consideration and analysis, and make adjustments.