Sensor freeze after a variable get...

[epierre]

Hello,

my water meter worked for nearly one month and suddently no nothing... it as well powered...

I took it away and wanted to have a look at it through the console.. Here is the last messages, then nothing more... I reproduced it several time... any ihint about the final "Me "? ?

Relaying message back to gateway.
Tx: fr=2,to=0,la=2,ne=0,ci=5,mt=2,ty=24,cr=163: 
Ack: received OK
Relaying message back to gateway.
Tx: fr=2,to=0,la=2,ne=0,ci=5,mt=2,ty=24,cr=163: 
Ack: received OK
Message available on pipe 1
Sent ack msg to 0
Rx: fr=0,to=2,la=0,ci=5,mt=3,t=24,cr=214(ok): 36890
Me

[epierre]

I flashed it on another one, here is the missing part... what do you think about the problem ?

ssage available on pipe 1
Sent ack msg to 0
Rx: fr=0,to=6,la=0,ci=5,mt=3,t=24,cr=153(ok): 10
Message addressed for this node.
Last pulse count from gw:10
currentTime20862
lastPulse0
currentTime40863
lastPulse0

[hek]

Looks like some trash coming in from gateway. It could be that debug-print hanging your sensor when it tries to print payload.

1. Check what your controller is sending (advanced tab if your on vera). If I remember correctly the sensor requests last known value from controller at startup. is this garbled somehow? Sensor expects an long integer.
2. Turn off debug printing if that is causing hanging for some reason.

[epierre]

@hek sorry I'm not explicit enough...

original node gets always stuck at the same message, even if I flash it again.

a new node has no issue all along...

[epierre]

@hek not sending from a vera...

I recompiled the sketch without serial print and it works again... good lesson for later....