Migration for raspberry pi-5 almost complete

[Telemachus1977]

I picked up a raspberry pi 5 1 GB at microcenter for $39. Finally the price of these things is out of the stratosphere.

I'm running all of the software off of an NVMe drive using the m.2 hat, and everything runs at lightning speeds. Installing, updating, running all of the components of the software works like a breeze.

However GPIO pins are nerfed now. Not sure when REM will be able to support the new GPIO infrastructure.

Since I am running REM chem controller alongside an easy touch 8, I never needed anything other than the flow sensor and a virtual feed to an internal Pantera relay from the GPIO. I was using a USB RS-485 adapter.

Without the GPIO functioning, I pulled out a mega-BAS that I inherited from a friend, and I'm now using that for the dry contact for the flow switch, to control the RS45, and to power the pi with 24 volts.

The last part of the puzzle I need is the feed to my internal pentair relay on the easy touch that controls the acid.

I was hoping I could set up a feed from one of the outputs of the mega-bas to circuit 8 on the easy touch, which controls my peristaltic pump. However it does not look like external feeds from the outputs of the mega-bas or an option.

Will it be possible to update the software so that the internal relays of the pentair system show as an option for the acid pump? Then I could bypass the workarounds I have been using for years.

[Telemachus1977]

Claude got the GPIO working in REM on Pi5.

Issue: REM crashes on Raspberry Pi 5 running Trixie with libgpiod assertion failure.
Root Cause: The app auto-selects @bratbit/onoff (libgpiod) for Trixie, but libgpiod has a GPIO line reconfiguration bug on Pi 5 that causes the app to abort.
Solution: Replace relayEquipmentManager/gpio/Gpio-Backends.ts with the fixed version. The fix detects Pi 5 specifically and forces it to use the stable sysfs backend instead of libgpiod. Pi 4 and other boards on Trixie continue to use libgpiod as before.
Changes: Modified the Trixie detection logic in selectGpioBackend() to check if the device is a Pi 5 using /proc/device-tree/model, then routes Pi 5 to sysfs and other boards to libgpiod.
Testing: Verified stable operation on Pi 5 with GPIO configuration and control working without crashes.
Deployment: Replace the single file and rebuild. No configuration changes needed.

Gpio-Backends.zip

[tagyoureit]

Fixed. Thanks!

[mojonba]

Hi,

Getting the following error upon npm run build after uploading Gpio-Backends.zip. Any ideas on how to fix?

Thanks,

`rpi@pool-panel:~/relayEquipmentManager $ npm run build

relay-equipment-manager@10.0.0 build
tsc

gpio/Gpio-Controller.ts:178:49 - error TS2339: Property 'noReconfigureDirection' does not exist on type 'GpioBackendSelection'.

178 this.noReconfigureDirection = selection.noReconfigureDirection || false;
~~~~~~~~~~~~~~~~~~~~~~

Found 1 error in gpio/Gpio-Controller.ts:178
`

[tagyoureit]

This fix was incorporated into the code. You don't need to add this manually.