7th gen NUC (Pulse Eight CEC) doesn't wake from S3 when TV is turned on

1. Computer is a nuc7i3bnk using an internal Pulse Eight CEC adapter.
2. The NUC's native CEC feature has been disabled in the BIOS.
3. Running LibreELEC 11.0.5.

The Pulse Eight CEC appears to work fine (I can control Kodi via the remote, the NUC enters S3 when the TV is turned off), but the TV won't re-wake the NUC from S3 when the TV is turned on. I've checked the LibCEC menu under System -> Input -> Peripherals but didn't see any relevant option?

I don't think it's a TV issue because the NUC will wake from S3 if I enable the native CEC feature in the BIOS. This isn't a good long-term solution because it creates a conflict with the Pulse Eight CEC adapter.

I'm out of ideas...

I'm beginning to wonder if the LSPCON converter the gen8 NUC uses is causing the problem?

AFAIK this was Intel's solution for getting 4k60 output to the HDMI 2.0 port. I'm not playing anything above Blu-ray quality on a 1080p television. Is there a way to bypass the LSPCON and fallback to HDMI 1.4? I'm already connected via HDMI, not USB-C.

I looked in the LibreELEC wiki and found the EDID section. I acquired the following info:

Kodi:~ # tail /sys/class/drm/*/status
==> /sys/class/drm/card0-DP-1/status <==
connected

==> /sys/class/drm/card0-DP-2/status <==
disconnected

==> /sys/class/drm/card0-HDMI-A-1/status <==
disconnected

How do I select HDMI-A-1?

I could force it to connect to HDMI-A-1 by following the Wiki for creating an EDID file. That didn't fix the problem...

I've also noticed that when my soundbar goes to sleep Kodi won't wake it up, either by scrolling the GUI or playing a file. I have to switch to another active input on the TV and switch back.

"Force AVR to wake up when Kodi is activated" is selected under the CEC Peripherals menu, but that doesn't fix the problem...

Is this a LibCEC issue? Or are 7th gen NUCs effectively broken for LibreELEC?

Took a look at the technical manual for my NUC and can't see how the LSPCON could cause the issue. The external CEC header goes through a separate controller.

This appears to be a software/firmware bug...