Latest system update to 6.1.21-v8+broke the RPi Reporter about rpi-reporter-mqtt2ha-daemon

[Anto79-ops]

Ok, I can confirm its related to some system update. I just ran updates on my second RPi (sudo apt-get update/upgrade), and rebooted and now RPi Reporter is broken on my second RPi with the same error message as above.

2 of 3 down. I guess I won't update my 3rd RPi... ahhh :)

[Anto79-ops]

another thing I would like to mention is that if I stop the service and run the RPi Reporter manually, it actually works and updates every 2 minutes, for example:

pi@raspberrypi:~ $ python3 /opt/RPi-Reporter-MQTT2HA-Daemon/ISP-RPi-mqtt-daemon.py
[2023-04-14 10:10:15] * NOTIFY: MQTT subscripton to raspberrypi/nodes/radon-rpi/command/radon-spi/+ disabled
[2023-04-14 10:10:15] * NOTIFY: * MQTT connection established
[2023-04-14 10:10:15] 
[2023-04-14 10:10:16] Announcing RPi Monitoring device to MQTT broker for auto-discovery ...
[2023-04-14 10:10:17] Publishing to MQTT topic "raspberrypi/nodes/radon-rpi/sensor/radon-spi/monitor, Data:{"info": {"timestamp": "2023-04-14T10:10:16-06:00", "rpi_model": "RPi 4 Model B r1.2", "ifaces": "e,w,b", "host_name": "raspberrypi", "fqdn": "raspberrypi", "ux_release": "bullseye", "ux_version": "6.1.21-v8+", "ux_updates": 0, "up_time": "9 min", "up_time_secs": 540, "last_update": "2023-04-14T11:34:36-06:00", "fs_total_gb": 32, "fs_free_prcnt": 71, "fs_used_prcnt": 29, "networking": {"eth0": {"IP": "[redacted]", "mac": "[redacted]", "rx_data": 3923, "tx_data": 7984}, "wlan0": {"mac": "[redacted]", "rx_data": 0, "tx_data": 0}}, "drives": {"root": {"size_gb": 32, "used_prcnt": 29, "device": "/dev/root", "mount_pt": "/"}}, "memory": {"size_mb": 3794, "free_mb": 3483, "size_swap": 100, "free_swap": 100}, "mem_used_prcnt": 8, "cpu": {"hardware": "BCM2835", "model": "", "number_cores": 4, "bogo_mips": "432.00", "serial": "[redacted]", "load_1min_prcnt": 8.0, "load_5min_prcnt": 8.5, "load_15min_prcnt": 6.8}, "throttle": ["throttled = 0x0", "Not throttled"], "temperature_c": 37.0, "temp_gpu_c": 37.0, "temp_cpu_c": 38.0, "reporter": "ISP-RPi-mqtt-daemon v1.8.4", "reporter_releases": "v1.8.4,v1.7.2,v1.7.3,v1.7.4,v1.8.3", "report_interval": 2}}"
[2023-04-14 10:12:18] Publishing to MQTT topic "raspberrypi/nodes/radon-rpi/sensor/radon-spi/monitor, Data:{"info": {"timestamp": "2023-04-14T10:12:16-06:00", "rpi_model": "RPi 4 Model B r1.2", "ifaces": "e,w,b", "host_name": "raspberrypi", "fqdn": "raspberrypi", "ux_release": "bullseye", "ux_version": "6.1.21-v8+", "ux_updates": 0, "up_time": "11 min", "up_time_secs": 660, "last_update": "2023-04-14T11:34:36-06:00", "fs_total_gb": 32, "fs_free_prcnt": 71, "fs_used_prcnt": 29, "networking": {"eth0": {"IP": "[redacted]", "mac": "[redacted]", "rx_data": 149, "tx_data": 293}, "wlan0": {"mac": "[redacted]", "rx_data": 0, "tx_data": 0}}, "drives": {"root": {"size_gb": 32, "used_prcnt": 29, "device": "/dev/root", "mount_pt": "/"}}, "memory": {"size_mb": 3794, "free_mb": 3487, "size_swap": 100, "free_swap": 100}, "mem_used_prcnt": 8, "cpu": {"hardware": "BCM2835", "model": "", "number_cores": 4, "bogo_mips": "432.00", "serial": "[redacted]", "load_1min_prcnt": 6.0, "load_5min_prcnt": 7.8, "load_15min_prcnt": 6.8}, "throttle": ["throttled = 0x0", "Not throttled"], "temperature_c": 35.5, "temp_gpu_c": 35.5, "temp_cpu_c": 35.5, "reporter": "ISP-RPi-mqtt-daemon v1.8.4", "reporter_releases": "v1.8.4,v1.7.2,v1.7.3,v1.7.4,v1.8.3", "report_interval": 2}}"

[bsimmo]

Given I tested. .21 for RPL and it is the SenseHAT fix, mine are still working fine and have been for a eek or so.
Will check though.

[Anto79-ops]

interesting. Maybe its not related to .21 but something else to .21. Having 2 RPi down, something changed for sure.

[ironsheep]

@Anto79-ops I have updated a number of RPi 4's here and am not seeing any issues.

Since the errors you show appear to be access to temps can you please recheck that your daemon account has the correct permissions?
https://github.com/ironsheep/RPi-Reporter-MQTT2HA-Daemon#set-up-daemon-account-to-allow-access-to-temperature-values

(Since you can run interactively, it seems to be an issue with the Daemon account.)

[Anto79-ops]

hey! that was it. Problem is fixed after repeating those steps.

I wonder how that got reset?

thank you for your help.

Closing