Communication Error trying to run PiJuice with DAKBoard

[jcn9001]

I'm trying to get PiJuice to work with the DAKBoard OS on a Raspberry Pi 4. I'm not sure if it's even possible to get these to work together but my linux knowledge is minimal so any guidance would be greatly appreciated.
I have the PiJuice working on the same Pi 4 using the latest 64-bit PiOS so this does not look like hardware issues. Here's where I've got to so far:

The SD Card was created using DAKBoard OS. I then ran sudo apt --full-upgrade, then installed PiJuice. DAKBoard appears to running normally but the PiJuice settings show a communication error. The battery is in (and charged), the PiJuice LED is on (blue) and the power is connected to the Pi 4:

I see something similar here:

pi@dakboard:/home/dakboard $ systemctl status pijuice.service
* pijuice.service - PiJuice status service
     Loaded: loaded (/lib/systemd/system/pijuice.service; enabled; preset: enab>
     Active: active (running) since Thu 2025-05-01 10:12:14 BST; 25min ago
   Main PID: 605 (pijuice_sys.py)
      Tasks: 2 (limit: 3909)
        CPU: 2.287s
     CGroup: /system.slice/pijuice.service
             `-605 /usr/bin/python3 /usr/bin/pijuice_sys.py

May 01 10:33:36 dakboard pijuice_sys.py[605]: {'error': 'COMMUNICATION_ERROR'}

...etc..

The ic2 bus shows nothing connected and I'm not sure where to go from here:

pi@dakboard:/home/dakboard $ i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                

Some other details that may be useful:

OS details:

pi@dakboard:/home/dakboard $ uname -a
Linux dakboard 6.12.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.20-1+rpt1~bpo12+1 (2025-03-19) aarch64 GNU/Linux

pi@dakboard:/home/dakboard $ lsmod | grep i2c
i2c_dev                16384  2
i2c_bcm2835            16384  1
i2c_brcmstb            12288  0

PiJuice installation:

pi@dakboard:/home/dakboard $ apt list --installed 'pijuice-*'
Listing... Done
pijuice-base/stable,stable,now 1.8 all [installed,automatic]
pijuice-gui/stable,stable,now 1.8 all [installed]

I had to make a few file ownership and permission changes to get the PiJuice to work on the PiOS installation so I applied those same changes to the DAKBoard installation. I have also added the pi user and assigned it to the same groups.

pi@dakboard:/home/dakboard $ groups pi
pi : pi adm dialout cdrom sudo audio video plugdev users input render netdev spi i2c gpio lpadmin pijuice

pi@dakboard:/home/dakboard $ ls -l /usr/bin/pij*
lrwxrwxrwx 1 root root     22 Apr 29 13:20 /usr/bin/pijuiceboot -> /usr/bin/pijuiceboot64
-rwxr-xr-x 1 root root  22732 Jan 29  2022 /usr/bin/pijuiceboot32
-rwxr-xr-x 1 root root  23904 Jan 30  2022 /usr/bin/pijuiceboot64
lrwxrwxrwx 1 root root     22 Apr 29 13:20 /usr/bin/pijuice_cli -> /usr/bin/pijuice_cli64
-rwsr-xr-x 1 pi   pi     9096 Dec 17  2018 /usr/bin/pijuice_cli32
-rwxr-xr-x 1 pi   pi    14872 Jan 30  2022 /usr/bin/pijuice_cli64
-rw-r--r-- 1 pi   pi   101552 May 16  2021 /usr/bin/pijuice_cli.py
lrwxrwxrwx 1 root root     22 Apr 29 13:20 /usr/bin/pijuice_gui -> /usr/bin/pijuice_gui64
-rwsr-xr-x 1 pi   pi     9096 Dec 17  2018 /usr/bin/pijuice_gui32
-rwxr-xr-x 1 pi   pi    14872 Jan 30  2022 /usr/bin/pijuice_gui64
-rw-r--r-- 1 pi   pi   105446 May 16  2021 /usr/bin/pijuice_gui.py
-rwxr-xr-x 1 root root  11275 Jan 30  2022 /usr/bin/pijuice_log.py
-rwxr-xr-x 1 pi   pi    15664 Jan 30  2022 /usr/bin/pijuice_sys.py
-rwxr-xr-x 1 root root   6205 Jan 30  2022 /usr/bin/pijuice_tray.py

I copied pijuice_config.JSON from the working PiOS installation to the DAKBoard installation

pi@dakboard:/home/dakboard $ ls -l /var/lib/pijuice
-rwxrwxrwx 1 pi pi 1369 May  1 10:53 pijuice_config.JSON

/boot/config.txt (I added the last 4 lines, as part of my troubleshooting):

disable_overscan=1
#framebuffer_depth=24
#gpu_mem=192
hdmi_force_hotplug=1
dtparam=audio=on
avoid_warnings=1
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
arm_boost=1
dtoverlay=i2c-bcm2835
dtparam=i2c_arm=on
core_freq=500
core_freq_min=500