I'm playing with the new Omgea2S+ (Pro) board and I have it tethered to my cell phone for network connectivity. I'm not using the web interface at this moment, but doing everything over the USB serial connection on my computer through Teraterm. (it's like putty)

I've noticed that when I walk away from my desk with my phone, the board loses network and the blue light goes out. When I come back with my phone, the blue light comes back on and a message gets written to the terminal: [17932.593554] Interface apcli0 link up! (WPA2PSK AES)

I said to myself, that's neat! And tried to do it while sitting at my desk by turning off my wifi hotspot. When I turn off my hotspot, the blue light goes out like normal, when I turn on my hotspot, I still get the "link up!" message, but the blue light doesn't come back on. Only when I walk far enough away to the point where it loses signal and then coming back in range does the blue light come back on. What process is controlling the blue LED?

I checked the logs: readlog -e link
and I see
Tue Feb 12 15:54:57 2019 daemon.notice netifd: Network device 'apcli0' link is down
Tue Feb 12 15:54:57 2019 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Tue Feb 12 15:54:58 2019 daemon.notice netifd: Network device 'apcli0' link is up
Tue Feb 12 15:54:58 2019 daemon.notice netifd: Interface 'wwan' has link connectivity

so it must be netifd doing the detection? but something else is controlling the notification led, maybe?

And seeing all of this made me want to create a script that monitors the network or a script that ties into the already running process that monitors the network, to keep track of when it's up and when it's down. When it's up, it could send a payload over MQTT with the times of "up" and "down" events, it could also send other cached data, (temp, location, photos) once there is a network connection again.

I could use this in my car, geo-tagging photos taken while driving, caching everything locally, then when I pull into the garage, it offloads everything once the network connection is reestablished.

I figured it out. I need the battery plugged in in order for it to work. If the battery isn't there, the battery dock doesn't seem to power the hologram board or the Omega2+. When the battery is plugged in, USB power works fine and charges the battery. There must be something on the hologram board that checks for the battery and if it doesn't find it, it doesn't power up?
Maybe it has more integration with the battery doc than I thought. Which is neat. Now I need more batteries.

@Douglas-Kryder I have a 5v 2.4A USB wall wart. It has powered the same dock, with a battery attached and the OLED expansion without issue. I don't think it's a power problem. I'm more inclined to believe there is a short somewhere. Or the power dock isn't compatible with the expansion board, which would be weird.

Has anyone had any luck using this expansion with the Battery Dock? I cannot get mine to turn on when the Hologram Expansion is installed. When the expansion isn't in place, the Omega2+ boots up fine. With it in place, the LEDs flash for a split second then nothing. The dock doesn't haven a LiPo connected at this moment, but I feel that even if it did have a battery, it still wouldn't boot. Do you think I have a defective Hologram Board?

@Matt-Nelson I wonder if we'll get $45 worth of other stuff when they decide hologram isn't going to follow through?

Which packages did you install on your Omega? Do you have example code available?