All, I have been struggling with this bug for a while so, I tool @ScruffR 's advice and pared down my application to a minimum to isolate the issue. The full code is here: https://go.particle.io/shared_apps/5b76df09aebf32b40900091e Context for the issue: Electron with Firmware 0.8.0-rc4 System …

Do you disconnect from the cloud prior going to sleep? If not, that's the expected behaviour. After wake the system is expected to put the device back into the connection state that was active before going to sleep. [image] chipmc: the Particle does this weird thing: I guess you are talking…

@ScruffR , Sorry, it is the Electron - should have mentioned that. I have not been using the Particle.disconnect() command, just Cellular.off() I thought I saw a note from @rickkas7 that tearing town the whole stack was not needed. I will test this now. Thanks for looking, Chip

I see, I missed the setPowerState(2) calling Cellular.off() However, can you try with 0.8.0.rc.9? If you are testing RC, you should do with the most recent.

@ScruffR , OK, so I updated to 0.8.0rc-9 and added the Particle.disconnect() before Cellular.off() I am still running into an issue with unexpected connections. Why is this doing when in MANUAL mode? Here is the latest rev: https://go.particle.io/shared_apps/5b76efe6aebf32b409000bd5 One more thi…

@rickkas7 , First of all, thank you for the article. I realized that I was indeed publishing before I checked Particle.connected() However, even with this fix, I still see the same behavior: despite being in manual mode and there only being one instance of Particle.connect() in the code, it stil…

I think you need a delay(1000); after Cellular.off(). The problem is that in threaded mode Cellular.off() is non-blocking but there's no way to tell when it's actually done. If you go to sleep immediately the cellular state is recorded as on, because it hasn't been turned off yet, so it wakes, it go…

@rickkas7 , The good news is that I am learning a lot today. The bad news is that adding the Cellular.on() and delays actually made the problem worse. Could it have something to do with using a Particle.function() to set the lowPowerMode. This function returns an ERROR on the mobile app since it …

You don’t need to add the Cellular.on() in your code. Just add the delay after the Cellular.off(). Also, yes, you should not go to sleep from a function handler. Set a flag in your function handler and go to sleep from loop().

@rickkas7 , OK, so I fixed that issue as you suggested. Still no joy. I wanted to make it easier to get the the root of the problem so, I have reduced the code significantly and, over the weekend, did a number of tests to narrow the problem. Here is the new reduced code: https://go.particle.io/sh…

[SOLVED] Unintended Connection to Particle When Waking From Sleep

Troubleshooting

rickkas7 August 17, 2018, 5:59pm 6

Make sure you check Particle.connected() before you call Particle.publish(). If you call Particle.publish() while the cloud is enabled but not connected, the function will block until the cloud is actually connected.

Topic		Replies	Views
Electron NEVER Going Back Online after ANY Sleep() Function Troubleshooting electron	3	502	February 28, 2019
Electron not waking from sleep if connection process is aborted Firmware	0	1401	May 25, 2017
Issues with connecting after Stop Sleep Getting Started	2	967	November 17, 2017
Electron won't process Function calls post-sleep Troubleshooting electron	12	1646	October 2, 2019
Electron not attempting to establish connection to Particle cloud Cellular electron	0	772	September 14, 2020

[SOLVED] Unintended Connection to Particle When Waking From Sleep

Related topics