(Home Assistant Add-On) LED config is being ignored

[dawid-woitaschek]

Describe the issue you are experiencing

I'm using the current integration on Home Assistant.

Dunno why but suddenly the blue LED on my RPI-RF-MOD started to blink blue every second.

I read about messy internet connection, etc. but it seems to work just fine.

Describe the behavior you expected

Well, the LED settings shouldn't be ignored - at least it seems like so.

Steps to reproduce the issue

Don't know how to reproduce this... But I already disabled the "Info-LED" settings under "General settings" and disabled every check in the "Advanced settings", including the LED options there.

What is the version this bug report is based on?

3.71.12.20231014

Which base platform are you running?

rpi4 (RaspberryPi4)

Which HomeMatic/homematicIP radio module are you using?

RPI-RF-MOD

Anything in the logs that might be useful for us?

/etc/config # ls
InterfacesList.xml     addons                 firewall.conf          homematic.regadom.bak  measurement            rfd.conf               time.conf
NoAddonUpdateCheck     cloudmaticDisabled     firewallConfigured     hs485d                 neoDisabled            rpi4usb3CheckDisabled  timezone
NoBadBlocksCheck       crRFD                  firmware               hss_led_info.conf      netconfig              server.pem             tweaks
NoFSTRIM               crypttool.cfg          hideStickyUnreach      ids                    nut                    shadow                 userAckSecurityHint
NoPortForwardingCheck  disableLED             hm_addons.cfg          internetCheckDisabled  rc.d                   snmp                   userprofiles
ReGaHssVersion         disableOnboardLED      hmip_address.conf      localtime              rega.conf              syslog
TZ                     eshlight               homematic.regadom      log4j2.xml             rfd                    systemLanguage

Additional information

No response

[KHismoom]

I have the exact same problem, as described in the bug report, even on a fresh installation of HomeAssistant and Raspberrymatic CCU.

This is the Raspberrymatic CCU log

Mounting /data as /usr/local (Home Assistant Add-On): OK
Starting watchdog...
Identifying host system: oci, OK
Initializing RTC Clock: grep: /proc/device-tree/model: No such file or directory
grep: /proc/device-tree/model: No such file or directory
rx8130, OK
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Initializing System: OK
Setup ca-certificates: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.1, OK
Identifying Homematic RF-Hardware: ....HmRF: RPI-RF-MOD/GPIO@fe201000.serial, HmIP: RPI-RF-MOD/GPIO@fe201000.serial, OK
Updating Homematic RF-Hardware: RPI-RF-MOD: 4.4.22, not necessary, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: .......OK
Starting rfd: .OK
Starting HMIPServer: .............OK
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting NeoServer: OK
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: 3.71.12.20231014 (raspmatic_oci_arm64)

[dawid-woitaschek]

I'm pretty sure this has something to do with @jens-maus changes to hss_led in this merged commit:
ef8ebf3

Maybe a permission problem?

Oh and btw, I restored a backup of the add-on and disabled automatic updates for now. Everything's fine again now.