From the Web app, click More... and choose Receiver Mode... to select between Low Power and Setup Mode.
In both modes, the radio is turned on for only briefly every 0.7~4 seconds to poll for user commands such as "arm" or "beep". This interval, configurable from wireless settings, directly affects tag response time experienced by user vs. stand-by power hence battery life trade-off. However, in Low Power mode, the receiver is operational for much shorter period (0.5~1ms vs. 4ms) just enough to accurately measure radio signal strength within the channel bandwidth. Then, unless it is increased vs. last few cycles, the radio is turned off immediately.
Our measurement showed that this sacrifices range by less than half, in return the radio stand-by power consumption is reduced by more than 4x vs. the normal setup mode used for 1st generation tags.
Long range radio comes at a price: when transmitting at max power, it drains the battery 3x faster than the old version tags.
However, most of the cases the tag does not need to transmit at max power. When tag manager receives a transmission from the tag, and if the signal strength is higher than -70dBm (4 bars) it automatically calculates how much the tag needs to reduce its power and sends this information back to the tag.
On the other hand, when the tag cannot get acknowledgement from the tag manager, it slightly increases its configured transmit power and tries again.
To see at what transmit power the tag is currently transmitting, press F12 (from Chrome) to open the console, F5 to refresh, find "GetTagList" and open the information the Cloud server returned and look for the line "txpwr" under the tag of interest. This value ranges from 16 to 255 (max power).
One common support request we received with our previous version was how to reset a tag to factory state. A tag can get "orphaned" when unassociation fails, wireless setting migration fails, etc. and with no action taken to remedy this (e.g. undelete the tag and retry) further changes to tag manager wireless setting are made.
We take this issue seriously and have added a way to reset the tag to factory state without using app with the Tag Manager.
On the other hand, one can also "lock the flash memory" to disable this reset capability, so the tag can only be unassociated by its owner's Tag Manager. This makes the tag worthless if stolen.