What are you seeing?  I've been checking voltage and temp, and using beacons instead of MQTT, which is supposed to be similar if not better, but I saw 18 days with the new modules.  My batteries may have been crap though.  I just got a batch of Energizers in now.   Yesterday I changed my code to use SetLowPowerMode(120) in the boot function, which may or may not have been the default, and also lowered the beacon rate to 30 seconds from 10.

Last I heard there is a bug in the firmware, where the numeric co-processor stops the CPU from sleeping - hence it eats batteries.

This is supposed to be resolved "soon" (that was several weeks ago).

I have stopped development on the 120 modules due to this bug, and gone back to 110's.

Hopefully "soon" is getting "sooner" every day...

This has been solved and the 120 should use less than 2uA

This is depending on the settings of connection type, beacons and connection time.
Set the connection type low-power, which is the default. You can store data in the beacon and while not encrypted and is not confirmed it is by far the lowest power. The connection time is the minimum time when the device connects to the gateway even if it does not have anything to send. You lowest battery life you can accomplish is to store data in the beacon and make the connection time 15 minutes. This means that your wait time to connect to mc-Studio is between 0 and 15 minutes.

Beacon 60s Connection time 900s battery life 6.73 years
Beacon 60s Connection time 300s battery life 5.68 years
Beacon off Publish every 60s battery life 2.9 years

We have a lot of customers that measure temperature. Most measure every minute, send only based on exceptions and once every 15 minutes. That gives a battery life of more than 5 years. Some measure every 30 seconds and store the data. They then send all 30 data-points in one message and that still gives you more than 5 year battery life.

The mc-Mod110 has a much higher sleep current and the battery life is about 20 to 25% less

Hope this helps.

John

If the secure connection is needed, so we can't use beaconing, what is the life when taking and transmitting temperature once per minute?

Hello All.
Just a quick update - There was some confusion about the mcMod120 power consumption fix. The fix has been completed but it has not been released yet. Sorry for the confusion!

We will be releasing the firmware update to solve the power consumption issue within the next week or two (along with some other firmware changes). This new firmware will bring the modules down to the expected 2uA in sleep mode. Thanks for the patience and understanding on this!