# BRN404X with device OS 6.2.1 & 5.5.0 - 8X and highly fluctuation power consumption

**URL:** <https://community.particle.io/t/brn404x-with-device-os-6-2-1-5-5-0-8x-and-highly-fluctuation-power-consumption/68802>\
**Category:** Firmware\
**Tags:** boron\
**Created:** [December 18, 2024, 5:50am UTC](https://community.particle.io/t/brn404x-with-device-os-6-2-1-5-5-0-8x-and-highly-fluctuation-power-consumption/68802 "2024-12-18T05:50:13Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Rftop](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/rftop/32/16896_2.png) [@Rftop](https://community.particle.io/u/Rftop)\
**Post date:** [December 18, 2024, 7:53pm UTC](https://community.particle.io/t/brn404x-with-device-os-6-2-1-5-5-0-8x-and-highly-fluctuation-power-consumption/68802/8 "2024-12-18T19:53:10Z")

</div>

Jeff, this is a LONG Shot..... but exactly 6 years ago (to the day!) I recorded the same thing with Borons. Turned out that the Device Under Test would start communicating with the Cloud 4 seconds after a different Boron on my "test" Particle account sent a publish.  
There were no Particle.variables, Subscribes, Functions, etc.

[Here's](https://community.particle.io/t/current-consumption-and-sleep-modes-boron/45612/42) my summary a couple days later. Physical proximity wasn't related, as mentioned later in the thread.

My suspicion was something on the Cloud Side changed on 12/18/2018 which happened to be during my test, so I had specific documentation of the results pre and post.

It might be worth a few minutes to perform your same test on a temp Particle Account with only 1 Boron? Like I said, it's a long shot 😉

---

_[View the full topic](https://community.particle.io/t/brn404x-with-device-os-6-2-1-5-5-0-8x-and-highly-fluctuation-power-consumption/68802)._