I discovered that moonraker.log has lot of this polling coming from the IP of the CYD-Klipper screen:
2025-10-29 02:20:19,072 [application.py:log_request()] - 404 GET /machine/device_power/devices (192.168.1.109) [TRUSTED_USER] 10.46ms
2025-10-29 02:20:44,775 [application.py:log_request()] - 404 GET /machine/device_power/devices (192.168.1.109) [TRUSTED_USER] 9.87ms
2025-10-29 02:21:10,088 [application.py:log_request()] - 404 GET /machine/device_power/devices (192.168.1.109) [TRUSTED_USER] 9.80ms
2025-10-29 02:21:35,690 [application.py:log_request()] - 404 GET /machine/device_power/devices (192.168.1.109) [TRUSTED_USER] 7.43ms
checking moonraker docs I found that it's possible to create a dummy power device, because I don't have any power device (i.e. intelligent plug) to control so I added this section to moonraker.conf:
[power dummy]
type: gpio
pin: gpio999 # fake pin number
initial_state: on # Or "off"
and finally all those errors disappeared.
I discovered that moonraker.log has lot of this polling coming from the IP of the CYD-Klipper screen:
2025-10-29 02:20:19,072 [application.py:log_request()] - 404 GET /machine/device_power/devices (192.168.1.109) [TRUSTED_USER] 10.46ms
2025-10-29 02:20:44,775 [application.py:log_request()] - 404 GET /machine/device_power/devices (192.168.1.109) [TRUSTED_USER] 9.87ms
2025-10-29 02:21:10,088 [application.py:log_request()] - 404 GET /machine/device_power/devices (192.168.1.109) [TRUSTED_USER] 9.80ms
2025-10-29 02:21:35,690 [application.py:log_request()] - 404 GET /machine/device_power/devices (192.168.1.109) [TRUSTED_USER] 7.43ms
checking moonraker docs I found that it's possible to create a dummy power device, because I don't have any power device (i.e. intelligent plug) to control so I added this section to moonraker.conf:
[power dummy]
type: gpio
pin: gpio999 # fake pin number
initial_state: on # Or "off"
and finally all those errors disappeared.