Electron turns permanent cyan, then do not publish anymore

Hello,

I am using a couple of electrons (3G and 2G) running on 0.8.0-rc.14. One of them is working fine for an hour or two, but since a while it starts to be permanent Cyan (not breathing, not flashing, really permanent) and then it stops sending event (publish) or stops reacting from subscribes… totally unresponsive until I reset it manually. Then sequence starts again, works for an hour and then cyan permanent, etc…

If I am not mistaking, this status led scheme is not documented. Maybe someone can help me understanding what it means? (I currently cannot connect the electron to a computer serial)

Thanks in advance,

Steven

Because that’s not a “valid” status but indicates a deadlock usually caused by the application firmware hogging a shared resource needed by the system.

There are other threads that address this issue - they can be found via the search terms solid cyan
https://community.particle.io/search?q=solid%20cyan

Thank you for your reply. I decreased the number of publish done (over long period) and it looks better already, so it must has something to do with publish every 5s or so … anyway, I reduced it and found a way to get the output from the serial.

After an hour or a bit more working correctly, I saw some errors in the serial:

0005385522 [comm.protocol] ERROR: Event loop error 1
0005385522 [system] WARN: Communication loop error, closing cloud socket
0005385522 [system] INFO: Cloud: disconnecting
0005385523 [system] INFO: Cloud: disconnected
0005385623 [system] INFO: Cloud: connecting
0005387635 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0005387699 [system] INFO: Cloud socket connected
0005387699 [system] INFO: Starting handshake: presense_announce=0
0005387700 [comm.protocol.handshake] INFO: Establish secure connection
0005387714 [comm.dtls] INFO: (CMPL,RENEG,NO_SESS,ERR) restoreStatus=0
0005387714 [comm.dtls] INFO: out_ctr 0,1,0,0,0,0,7,173, next_coap_id=819
0005387715 [comm.dtls] INFO: app state crc: cached: 70ebea2, actual: 70ebea2
0005387716 [comm.dtls] WARN: skipping hello message
0005387716 [comm.dtls] INFO: restored session from persisted session data. next_msg_id=2073
0005387717 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 2
0005387866 [comm.protocol.handshake] INFO: resumed session - not sending HELLO message
0005387866 [system] INFO: cloud connected from existing session.
0005387867 [system] INFO: Cloud connected

The loop and publishes are still working (for now) but I see a lot of messages I do not understand and I did not see before:

0005402061 [comm.protocol] INFO: rcv’d message type=3
0005402332 [comm.protocol] INFO: rcv’d message type=3
0005402597 [comm.protocol] INFO: rcv’d message type=3
0005402862 [comm.protocol] INFO: rcv’d message type=3
0005403127 [comm.protocol] INFO: rcv’d message type=3
0005403392 [comm.protocol] INFO: rcv’d message type=3
0005403654 [comm.protocol] INFO: rcv’d message type=3
0005403919 [comm.protocol] INFO: rcv’d message type=3

I have searched for this message type=3 in the forum without finding something. Maybe you can tell em what it means (if you know)

Thanks in advance for your help,

Steven