Abnormal SIM Card data volume usage on Electron

[simmikolon]

@ScruffR

This seems to pretty much carry on from this other thread (which I closed for that reason)

Yes that's true and I agree that we should close the other.

@ScruffR

What does Particle Console | Build your connected product say?
I recall an issue where after four wakes a full handshake happened for some obscure reason

I've made sure that there is no handshake happening and debugged it on device and in the console as well. Everytime a handshake is being made you see DEVICE-ONLINE Message appearing in the logs - which is not the case with my devices.

Also you have to make sure that between publish and deep sleep there's some idle time - but not with a delay - just to give the system thread some time to run Particle.process() a bit.

There is just a single publish happening with 16 bytes of user data.

But see my latest info on that:

@simmikolon

I've made some test with and without Deep Sleep:

1. Deep Sleep: 3900 Bytes per Hour
2. No Sleep: 2300 Bytes per Hour

When waking from deep sleep 135 bytes are send to reuse current session. So 135 Bytes x 12-Times during an hour = 1620 Bytes - which is exactly the difference between Deep Sleep and No Sleep!!! (and not calculated - these are measured facts)

This exactly behaves as written in the docs:

Connecting to the cloud after reset or wake-up sends just a reconnect message, using 135 bytes of data. (Source)

I also read about how the communication is build up and found this one here:

Electron Data Usage Investigation

Each minimum publish currently with acknowledge is about ~70 sent and ~60 received, so if you add ~14 bytes (“Temp” is 4 bytes) to that let’s call it 144 bytes. Pings are 122 bytes every 23 minutes, but should not be happening if you are sending data every 5 minutes. So 1441224*10 = 414k. This assumes no disconnects or re-handshakes… could be happening if signal strength is low or the tower is bouncing you. I would suggest reducing “Temp” to just “T” and spread out your publish interval a bi…

So - Let's say a single Publish with NO_ACK (just like in my case) takes about 70 Bytes overhead - this makes:

12 Times per Hour x 70 Bytes = 840 Bytes overhead per Hour

and we have to add:

16 Bytes payload x 12 Times per Hour = 192 Bytes per Hour

this makes a total of 1.032 Bytes - or 1 KB per Hour

But I am having 2300 Bytes / 2,3 KB per Hour - So there is a difference - and which cannot be because of a handshake (which really does not take place). It has to be something that happens underneath - or (more realistic) - It's because of encryption of payload since you cannot simply take 16 Bytes payload and encrypt it without adding up to the overall size!