# Web Console Last Handshake updates after each Particle.publish from an Electron **URL:** \ **Category:** Troubleshooting\ **Tags:** electron\ **Created:** [June 11, 2019, 1:42am UTC](https://community.particle.io/t/web-console-last-handshake-updates-after-each-particle-publish-from-an-electron/50284 "2019-06-11T01:42:01Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![jdash](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/jdash/32/17337_2.png) [@jdash](https://community.particle.io/u/jdash)\ **Post date:** [June 11, 2019, 1:42am UTC](https://community.particle.io/t/web-console-last-handshake-updates-after-each-particle-publish-from-an-electron/50284/1 "2019-06-11T01:42:01Z")
Hi all, just curious if this is just incorrect wording in the web console description of “Last Handshake” or I should dig further into my application code for hidden bugs. The web console states that Last Handshake means when the last secure connection was established. Not necessarily when the device was Last Heard. However, I am seeing that every Particle.publish event seems to update the time for Last Handshake. Is this expected? – I use NO\_ACK Publish events every 2 minutes. – Almost all of the events arrive at 2 minute intervals. On occasion I do see some dropped but likely due to bad cellular connectivity. – When I watch the console, I only see my events every two minutes. I don’t see what I normally see when a full handshake is done (e.g. device vitals, etc.) Main reason I am asking is I don’t want a surprise on data consumption. It doesn’t seem like I am using more data but hard to tell without adding additional debugging code. ---
**Author:** ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)\ **Post date:** [June 11, 2019, 9:18am UTC](https://community.particle.io/t/web-console-last-handshake-updates-after-each-particle-publish-from-an-electron/50284/2 "2019-06-11T09:18:39Z")
Just recently the _Online Indicator_ logic underwent some overhaul, so it may well be that the docs lag behind in that regard. Have a read here > [@Improvements to the online indicator for Gen 2 and Gen 3 hardware](https://community.particle.io/t/improvements-to-the-online-indicator-for-gen-2-and-gen-3-hardware/50101): > > Knowing if your device is online or not is a big deal. That’s why we’re so excited to share that now the Electron and all other Gen 2 and Gen 3 devices accurately report their status in the Console, Web IDE, CLI, and Cloud API. While this feature is not new, important improvements were made to increase the accuracy of the online indicator. One of the challenges that we overcame — and why it’s not a simple problem to solve — is that the low-level protocol used by these Particle devices is UDP. U… ---
**Author:** ![jdash](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/jdash/32/17337_2.png) [@jdash](https://community.particle.io/u/jdash)\ **Post date:** [June 11, 2019, 11:16am UTC](https://community.particle.io/t/web-console-last-handshake-updates-after-each-particle-publish-from-an-electron/50284/3 "2019-06-11T11:16:46Z")
Thanks for the pointer to that article, much appreciated and it was a great read. Have posted my question there for clarification. Thank you. ---
**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:** [June 11, 2019, 12:58pm UTC](https://community.particle.io/t/web-console-last-handshake-updates-after-each-particle-publish-from-an-electron/50284/4 "2019-06-11T12:58:19Z")
@jdash, I have an Electron that’s still running 0.8.0 Firmware with very frequent NO\_ACK publishes. It hasn’t been flashed in a long time. I believe with the recent changes, the console reports the last communication now, not handshake. I agree with you: It’s not consistent with the “Tool-tip” info for Last Handshake: ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/3/9/399d7c0f35ce287f91692ae3798e7d24e39eea1a.png) This likely isn’t a bug in your application Code. BTW: You can easily track daily cellular data in a Browser with: [https://api.particle.io/v1/sims/XXXX/data\_usage?access\_token=YYYY](https://api.particle.io/v1/sims/XXXX/data_usage?access_token=YYYY) Where: XXXX= Electron’s ICCID (go to [Console.particle.io](http://console.particle.io/) , View Device) YYYY = Personal Access Token (go to [Build.particle.io](http://build.particle.io/), Settings) ---
**Author:** ![jdash](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/jdash/32/17337_2.png) [@jdash](https://community.particle.io/u/jdash)\ **Post date:** [June 12, 2019, 2:39am UTC](https://community.particle.io/t/web-console-last-handshake-updates-after-each-particle-publish-from-an-electron/50284/5 "2019-06-12T02:39:14Z")
This tip is fantastic, it totally beats staring at the console which doesn’t provide the granularity needed. Marking as a solution since it will help others :).