Okay I have looked at the documentation around the Rae and tried to implement it. I have had a few problems (and learned more than I wished about systemd in the process). However, I have what may be an essential question: Given that the RobotHub re Luxonis is no longer available is it actually possible anymore to use/develop programs for the Rae? That is, yes I can (in theory) logon to the Rae, but is that the extent of what I can presently do with the Rae?
Aside from that burning question. Here is, perhaps, some useful information: Accessing the Rae locally via the documentation is indeed possible through USB-C cable. From there you can indeed connect the Rae to your wifi network. However, I have not been able to connect to the WiFi access point nor to the Rae once it is on my wifi network (via https on port 9010). Also if I connect the Rae to my wifi network (re the documentation) and reboot the Rae, I must again launch wpa_supplicant.
There is, possibly, a substantial reason for my problem regarding rebooting. That is, wpa_supplicant is a disabled systemd service. So, in hopes, that part of my problem (or yours) may be disabled services, I append all such:
blk-availability.service disabled
can-init.service disabled
charger-fl.service disabled
console-getty.service disabled
containerd.service disabled
debug-shell.service disabled
fsync-stm-startup.service disabled
inbm-node.service disabled
lte.service disabled
lvm2-monitor.service disabled
mender-data-dir.service disabled
mender-grow-data.service disabled
mender.service disabled
mosquitto.service disabled
nvmefc-boot-connections.service disabled
robothub-agent.service disabled
robothub-tunnel.service disabled
run-postinsts.service disabled
sysstats-logger.service disabled
systemd-boot-check-no-failures.service disabled
systemd-network-generator.service disabled
systemd-pstore.service disabled
systemd-time-wait-sync.service disabled
tpm2-abrmd.service disabled
wpa_supplicant-nl80211@.service disabled
wpa_supplicant-wired@.service disabled
wpa_supplicant.service disabled
wpa_supplicant@.service disabled
Of course, enabling any of these may well be wasted effort given my question regarding use/development.