2025.xx.xx New error after the latest update (can not open gpiochip)

[spanzetta]

I see this in the periodic log console..

It was not present with previous builds..

2026-05-10T20:32:24.664933+02:00 allsky allskperiodic[217642]: /home/admin/allsky/venv/lib/python3.11/site-packages/gpiozero/devices.py:300: PinFactoryFallback: Falling back from lgpio: 'can not open gpiochip'
2026-05-10T20:32:24.664995+02:00 allsky allskperiodic[217642]:   warnings.warn(
2026-05-10T20:35:27.598398+02:00 allsky allskperiodic[218026]: /home/admin/allsky/venv/lib/python3.11/site-packages/gpiozero/devices.py:300: PinFactoryFallback: Falling back from lgpio: 'can not open gpiochip'
2026-05-10T20:35:27.598524+02:00 allsky allskperiodic[218026]:   warnings.warn(
2026-05-10T20:38:30.079956+02:00 allsky allskperiodic[218900]: /home/admin/allsky/venv/lib/python3.11/site-packages/gpiozero/devices.py:300: PinFactoryFallback: Falling back from lgpio: 'can not open gpiochip'
2026-05-10T20:38:30.080018+02:00 allsky allskperiodic[218900]:   warnings.warn(

[EricClaeys]

@spanzetta,
This is on a Pi 4 with the latest v2025.xx.xx ?

@Alex-developer,
any ideas?

[spanzetta]

@spanzetta, This is on a Pi 4 with the latest v2025.xx.xx ?

My setup is RPI5 with fresh OS and 2025.xx.xx installed from the scratch (not an upgrade from previous 2024.xx.xx)

Raspberry Pi 5 Model B Rev 1.1
Linux allsky 6.12.75+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1~bookworm (2026-03-11) aarch64

@Alex-developer, any ideas?

[Alex-developer]

Can you please paste the output of

groups

[spanzetta]

What do you mean ?
What is "groups" ?

This one?
admin adm dialout cdrom sudo audio www-data video plugdev games users input render netdev lpadmin gpio i2c spi

[Alex-developer]

What do you mean ? What is "groups" ?

This one? admin adm dialout cdrom sudo audio www-data video plugdev games users input render netdev lpadmin gpio i2c spi

What do you mean ? What is "groups" ?

This one? admin adm dialout cdrom sudo audio www-data video plugdev games users input render netdev lpadmin gpio i2c spi

Thats the one :-)

That was just to check that your user is in the gpio group which it is.

Can you please run the following on your pi and paste the output

ll /dev/gpio*

Then set the debug level to 4 in the settings, allow allsky run run for a little while ensuring that the error is in the periodic log, like the one you originally posted.

Then attach the latest support info.

At the moment I am not sure whats going on as I cannot reproduce the issue here, which make sit much harder to diagnose and fix.

Thanks

Alex

[spanzetta]

sorry but when I do
ll /dev/gpio*
I get "command not found"!

??

Anyway.. here is the support info if you want to start looking into it (didn't change yet the debug level)
support-repo-type-none-20260512100655.zip