Author Topic: PowerMode vs Connection time  (Read 150 times)

the-wal

  • Newbie
  • *
  • Posts: 15
    • View Profile
PowerMode vs Connection time
« on: August 08, 2016, 01:11:41 am »
Hello and thank in advance for your advice, I am new to MC-Things from the land down under, and I can't wait to get my new toys.

So basically for what I want to start with is setting my nodes up as Tx only not receiving any operational data from the MQTT broker.

I am planning for most of the units to periodically report temp and also use some as a window/door sensor.

Can someone give me an idea of the time between the magnet being tripped and the data getting to the gateway?
I am only asking for data from the module to the gateway as I am thinking for battery life and once it hits the gateway power mode doesn't matter.
If someone could give me an idea for using both SetMidPowerMode and  SetLowPowerMode.

Also I noticed setting both modes you pass an integer, can someone explain with this is for and any impact on power usage.

Thanks heaps
Tony

Share on Facebook Share on Twitter


mc-John

  • Global Moderator
  • Full Member
  • *****
  • Posts: 212
    • View Profile
Re: PowerMode vs Connection time
« Reply #1 on: August 08, 2016, 10:19:21 am »
Hi Tony, welcome at the forum.

For sensors the best mode is Low power mode. In low power mode it can take up to a second to make a connection to the gateway. If you use MQTT it take almost no time to move it into the cloud.

The data you can send has to be moved into a ListOfByte. There are all kind of functions to store and retrieve data from a ListOfByte. Sending more or less data has not much influence on the power usage. The frequency of sending is a big factor though.

-John-

the-wal

  • Newbie
  • *
  • Posts: 15
    • View Profile
Re: PowerMode vs Connection time
« Reply #2 on: August 08, 2016, 12:27:51 pm »
Thanks John.

I am good with a second,  as for how often I will be looking at temp every 15 minutes or so. And triggered events like magnet and gpio as they happen.

Cheers.