I’d read (somewhere) that you had to power up the Kraken before the Pi so the Pi would recognize the Kraken. After doing that and then getting tired of the 2-step process, I thought about slowing the Pi’s boot process in software.
So, using raspi-config, I set the boot order on the Pi to look for a [nonexistent] network boot node before booting from the SD card. That slows it down about 5 seconds. There’s also a boot_delay setting in /boot/config.txt that can slow things down.
I haven’t completely verified this yet, but after making these changes, I can power both devices at the same time and the Kraken is there when the Pi goes looking for it.
I’ll keep poking around on this to confirm or correct this info. But, a software delay is a much cheaper, simpler, and more elegant solution compared to some of the other ideas I had for how to power it on/off remotely.