smaslennikov / litter-controller Goto Github PK

Either display it on the physical screen or print it in logs when triggered

Add a fake i2c interface to test proper function in CI

Kitties can't see well at night and miss the bowl. Add a light to the interior to avoid this issue.

The sonic sensor is exposed on the very top of the machine. The machine itself is located next to a sink. A brewing session later, it got a little wet and start perpetually reporting distances of around 2200. Brass brush cleaning resolved the issue temporarily, but getting components wet isn't ideal.

Deploy to the pi

• make destination host configurable so that one can fork, set CI variable and go
• lint
• build

journalctl doesn't show much. Fix it

Allow triggering remotely, ideally via CLI

The service started crashing with

litter-controller[24750]: 'Kitty:    23.2mm' called to empty box. Delaying 120s
litter-controller[24750]: Aligning: sonic reports 51.3
litter-controller[24750]: <program name unknown>: relocation error: /lib/arm-linux-gnueabihf/libpthread.so.0: symbol __libc_dlopen_mode, version LIBC_2.12 not defined in file libc.so.6 with link time reference
systemd[1]: litter-controller.service: Main process exited, code=exited, status=127/n/a
systemd[1]: litter-controller.service: Unit entered failed state.
systemd[1]: litter-controller.service: Failed with result 'exit-code'.
systemd[1]: litter-controller.service: Service hold-off time over, scheduling restart.
systemd[1]: Stopped Controller for a litter box.
systemd[1]: Started Controller for a litter box.
litter-controller[25181]: Aligning: sonic reports 51.7

Export this data as in #2

Something with the LEDs, maybe.

Looks like the second relay isn't clicking on - replacements ordered.

• Add pictures
• Document materials used

While avoiding too many interfaces (especially considering we have few GPIO pins left), allow to manually correct bowl position with the existing buttons. This is necessary while the software is still buggy and sometimes tries to unnecessarily align the bowl.

After a couple days of running, it became unresponsive and locked up a core.

Show stats and metrics, most likely on a Web UI

Store metrics such as

• date and time of use
• sonic sensor data for the duration of use - currently the 120sec allotment we provide