Remote GoPro deployment: ensuring WiFi availability after power cycles (Pi + PoE + iBoot):

[kpgalvin]

Hello,

Our use case is we need to be able to manually start/stop recordings and scheduled timed recordings in advance with set durations. We need to be able to access the GoPros from 1000s of miles away.

System setup:

• Starlink
• GoPro HERO13
• Raspberry Pi controlling the camera via HTTP API
• Tailscale for remote SSH access to the Pi
• PoE injector + iBoot (remote power switch)
• PoE splitter (5V/4A) powering the GoPro (battery removed, solar-powered)

Goal:
We require a system where:

1. GoPro is powered on/off remotely (via iBoot) (need to be able to power cycle due to temperature constraints, deployment will be in desert environment with temps > 113F/45C)
2. After boot, the GoPro reliably enables its WiFi hotspot
3. Pi detects the network and automatically
4. I can resume control (recording, download, etc.) via tailscale

Current issue:
The main failure mode is that after power cycling the GoPro, the WiFi hotspot (GPxxxxx) is not always broadcast or is delayed/unreliable. This prevents the Pi from reconnecting, even though the camera is powered. This is part of a long-duration remote experiment, so reliability after power interruption is critical.

Any guidance from others who’ve done unattended deployments would be hugely appreciated. I am currently playing around with the GoPro HERO13, Raspberry Pi Zero 2 W, and using my home internet as the Starlink stand-in. I own two iBoot PoE extenders (802.3 AT/AF and the 9-70 VDC ~90W max).