So, I realize nobody will believe me - but I may have figured out what’s happening.
As previously mentioned, I have another Boron LTE on 3xAA batteries, that’s operated by an external timer and it’s EN Pin. It’s in my office about 6 feet away from my test rig that I’m measuring Current/Power/Energy consumption with via Li-Po Connector.
The Boron w/ 3xAA batteries Boots up, sends a NO_ACK Publish, and shut’s down. That takes 12 seconds. That entire cycle is repeated ~78 seconds. It’s performing extremely well, I’ve very excited about the possibilities.
Starting yesterday afternoon, I started seeing the Current Spikes on a different Boron (on the Current/Power test rig), every 78 seconds. Today, I opened up the box on another Boron, same results.
Any Boron in my office receives Something from the Cloud (causing the spike) approximately 4 seconds after the 3xAA Boron sends it’s NO_ACK Publish.
I confirmed by removing a battery from the 3xAA Boron. The others no longer Spike @ 78 Seconds.
Something changed with the Cloud Backend yesterday.
[Edit: additional info]: The Boron LTE powered by 3xAA batteries does not have any Particle.variables, Subscribes, Functions, etc. It makes several changes to PMIC in Setup() and sends a publish with:
Particle.publish(eventName, msg, PRIVATE, NO_ACK);
It then Waits 1 second, and Shuts down. The external timer wakes it after it’s been shutdown for 1 min 5 Seconds, the Run-time is 13 seconds = 78 seconds
I guess it’s possible that the Mesh Radios are initiating a reaction between the Borons ?