Philip Howard

Sure leave it open, I've added to my TODO list.

Bear in mind your sensor might also be thermally coupled to the Pi, which can also cause erroneous temperature readings and - in my experience - has more of an...

I've raised PR #3 to add these as first-party features. I'm running some tests with two sensors side-by-side to see what factors most affect accuracy. From a test with one...

Thank you. I thought I'd caught all of these but Graphics HAT slipped my mind.

I have no clue why I had a brain blip and duplicated effort from - https://github.com/pimoroni/grow-python/pull/36 The main blocker is the lack of PWM and pulse counting, since these were...

It's possible you could pull this pin using a technique similar to the one here: https://github.com/pimoroni/clean-shutdown/blob/master/daemon/lib/systemd/system-shutdown/gpio-poweroff This drops a script into systemd that runs upon shutdown and asserts a GPIO...

New, easier, method, add the following to `/boot/config.txt`: ``` dtoverlay=gpio-poweroff,gpiopin=19,active_low=1 ```

The latest RPi OS - or rather the latest Linux kernel - seems rather more forceful about pins being mutually exclusive so I'm not surprised it's hit the backlight too....

Okay upon further investigation the backlight *should* be turning off with no additional changes since there's a service in `/etc/systemd/system/poweroff.target.wants/rpi-display-backlight.service` that effectively runs `echo 1 | sudo tee -a /sys/class/backlight/rpi_backlight/bl_power`...

This is pretty clunky, but create the following as `/etc/systemd/system/hyperpixel4-backlight.service`: ``` [Unit] Description=Sets up gpio-poweroff to handle Hyperpixel backlight upon shutdown/reboot ConditionPathExists=/usr/bin/hyperpixel4-init ConditionPathExists=/boot/overlays/gpio-poweroff.dtbo ConditionPathExists=/usr/bin/dtoverlay DefaultDependencies=no Before=umount.target [Service] Type=oneshot ExecStart=/bin/sh -c...