Install

$ pip3 install pibooth-extra-lights-vim4

Configuration

Here below the new configuration options available in the pibooth configuration. The keys and their default values are automatically added to your configuration after first pibooth restart.

The physical pin numbering is used.

[CONTROLS]

# Physical GPIO OUT pin to light a LED at pibooth startup (list of pins accepted)
startup_led_pin = 29

# If True, startup LED is lighting by setting pin(s) to HIGH else by setting to LOW
startup_led_active_high = True

# Physical GPIO OUT pin to light a LED during the entire capture sequence (list of pins accepted)
preview_led_pin = 31

# If True, preview LED is lighting by setting pin(s) to HIGH else by setting to LOW
preview_led_active_high = True

# Physical GPIO OUT pin to light a LED when the capture is taken (list of pins accepted)
flash_led_pin = 33

# If True, flash LED is lighting by setting pin(s) to HIGH else by setting to LOW
flash_led_active_high = True

States description

Here is the pibooth state sequence updated with the lights activated by this plugin:

Circuit diagram

Here is the diagram for hardware connections.

Fork

This is a fork of pibooth-extra-lights by Vincent Verdeil and Antoine Rousseaux, released under the same GPLv3 licence. It is published under its own name so that both can live side by side, and it runs on a Raspberry Pi just as well as on the boards the upstream plugin can not reach.

Change from the upstream version: the LEDs are driven through app.board, the GPIO layer of pibooth-ceeeeb, instead of gpiozero. The plugin therefore also works on boards exposing their GPIO through /dev/gpiochipN, a Khadas VIM4 for instance, and pin numbers stay the physical ones of the 40 pins header. Beware that the header pinout of a Khadas VIM4 is not the one of a Raspberry Pi: see the VIM4 GPIO header documentation.