Sensor doesn´t reconnect after connecting lost!?

[hek]

The broadcast message used when searching for parents is only transmitted once unlike the normal messages which is transmitted in quick bursts of several resends. So broadcasts is less likely to be picked up.

Not sure what could be the issue for you. I suspect the usual powering/shielding issues.

[vga]

@hek, thanks for your help so far!
The sensor sends every 10 seconds data to the gateway.
When the sensor is out of range, the transmitting fails 6 times and then stuck in "find parent" and do nothing anymore.
Is there any counter, which catch the failed transmits in line?
Does the "find parent" mode repeat in any intervals?
may it is possible to repeat the interval more often?

[hek]

@vga said:

Is there any counter, which catch the failed transmits in line?

Yes, 5 failed sends in a row that triggers it.
https://github.com/mysensors/Arduino/blob/development/libraries/MySensors/core/MyTransport.h#L27

Does the "find parent" mode repeat in any intervals?

Every time you try to send a new value and parent is lost, it will retry.

Do you see a lot of transmission error when the node starts up?

[vga]

When node is in range of gateway, there are no transmission errors on node when startup, and since the node stay in range, all went fine.

so, when node went out of range and 5 transmits in row fails, the node starts to find the gateway again, but only for one time, and then hangs up.

[hek]

Weird... and you're sure the sketch continuous to run (and calls send)? It doesn't hang for some other reason in your code?

[vga]

no, i think the sketch doesn´t work anymore.
In Serial Monitor, after 5 fails, i can see the node calls "find parent" for one time, and after that there is nothing more happening in the serial monitor.

but the sketch works fine all the time when transmutation is OK.

[mfalkvidd]

It looks like you might be overwriting MySensor's routing information. That is likely to interfere with the node's ability to communicate. You should only write to EEPROM_LOCAL_CONFIG_ADDRESS and above.

[vga]

hm, i´ve changed my eprom_write function, so that i only write to dresses above EEPROM_LOCAL_CONFIG_ADDRESS.
this is 0x123 -> address 291, and now i begin to write at 300.

but still the problem persists, after losing connection, no reconnect. :confused:

[mfalkvidd]

If you haven't already, run the clearEeprom sketch (Examples->MySensors). That will clear the corrupt routing table and let the sensor build a new table.

If you eant, you can use MySesnor's saveState (described at https://www.mysensors.org/download/sensor_api_15#the-full-api ) instead of keeping track of the address manually. saveState will always write above the local config address.

[vga]

@mfalkvidd
now i´ve clears the EEPROM, and completely removed the part from sketch, with writing anything to EEPROM.

still the same issue.
i´m thinking about to rase the counter of fails in row, till connecting will be reinitialized.
Sure, this is not the best way to do, but till i have no other clue, the best workaround for keeping it working.

Or any more other ideas? ;)

[vga]

btw,
i downloaded the new library folder from github repo, thinking maybe there are some changes with this issue.

Now i see, the whole MySensor function is changed, and i have to edit my sketches for the new way!?

before update, i have to do this:
MySensor gw;

and now, this part is complete removed, am I right??

is there any announcement for this changes? didn´t find anything about these changes.

[hek]

There is a conversion guide here:
https://docs.google.com/document/d/1NKq5uuNdnxF5jWnum7VT32mbKLjuvqlx2A5D1qQ-H3Q/edit

[mfalkvidd]

There is no announcement because it has not been released yet :)
The default branch on github is the development (non-stable, non-released) version. It is assumed that developers use github and regular users use the download links in the official documentation (which points to the released version).

[vga]

@hek said:

Yes, 5 failed sends in a row that triggers it.
https://github.com/mysensors/Arduino/blob/development/libraries/MySensors/core/MyTransport.h#L27

oh, ok, I understand :)
...the link above refers to the beta, and i was wondering, why my library contains something else than this... so i just wait, thanks ;)

...but any other idea for the real topic issue? ;)

[vga]

Hi!
still have no solution for the topic-problem. :disappointed:

i tested both, the stable v1.5 mySensors and the beta v2.0.

Both are working till connection is lost, then both version doesn´t reconnect. Same behavior again.

i didn´t think it is because of some hardware issue, because it works, till connection is lost.
also my code is reduced to the minimum, for testing this option, but same issue again.

so there must be a problem with the "find parent" function.
it looks like, when connection is lost and 5 send commands in line has been failed, the "find parent" is calling, but for some reason, the node sketch crashes.

the last serial monitor output from node is this:

find parent
send: 48-48-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:

...and I got this only for one time, then nothing happens anymore, also my usual sketch operations doesn´t operate anymore and didn't make serial outputs.

Is there nothing more i can do?? how does the reconnect is working normally?

[corbin]

@vga
I'm having a similar problem, my battery powered motion sensors do not reconnect after going out of range, or when the controller is restarted. Restarting the sensor will allow it to reconnect to the controller.

My mains powered motion sensors will reconnect automatically after the controller is restarted (I haven't tried taking them out of range whilst powered up). One battery powered motion sensor that is connected through a repeater node will stay connected/reconnect after the controller is restarted.

I've cleared eeprom using the sketch on https://www.mysensors.org/build/debug, for the controller and all nodes.

I've tried with and without a capacitor on the radios.

I've started with the 1.5 API and also the new 2.0 API.

The battery powered nodes are all running a Sensebender Micro with 2 x 1.2v NiMH batteries, nRF24L01+ (from Itead), and a HC-SR501 PIR (running on the 3.3v input as on http://techgurka.blogspot.com.au/2013/05/cheap-pyroelectric-infrared-pir-motion.html).

My next ideas are to try normal 1.5v batteries, powering the PIR from 5v on a separate power supply, and Arduino mini pros instead of Sensebenders.

Regards,
Corbin

[bjacobse]

Hi I have something similar, not sure if this is related to mysensors or the Agocontrol Home Automation.
My scenario; My Agocontrol crashed due to corrupted SD card on my RPI, due to power outtage.
I installed Agocontroll from scratch on a new SD card. copied most of my Agocontrol configuration files. (So I have now learned to use UPS for power backup)

Then I plugged in my Zwave, Tellstick, Mysensors serial gateway (ver 1.5.4) and none of my sensors was accepted by the serial gateway.

I would assume that all sensors would be found and accepted? But instead I have to reset each Arduino Pro Mini on the sensors, and this is for both battery powered and for Arduino Nano that is powered from mains via 5V USB PS

[tekka]

@corbin Can you provide debug logs (on 2.0.0) of both, GW and node, showing what you described?

[corbin]

@tekka well after making the post above, it has started working :)

Knowing that the Sensebenders operated perfectly as temp and humidity sensors with the sketch they were shipped with, I modified the Sensebender sketch (https://github.com/mysensors/SensebenderMicro/blob/master/Arduino/SensebenderMicro/SensebenderMicro.ino) to include motion , and added "#define MY_PARENT_NODE_ID 0". Previously I had been using the default MySensors Motion Sensor sketch.

I'm hoping it keeps working, so far, so good!

[corbin]

@tekka said:

@corbin Can you provide debug logs (on 2.0.0) of both, GW and node, showing what you described?

It's been running well except for 1 node, this is the serial output, could it be damaged hardware?

Stárting sensor (RNNNA-, 2.0.0)
TSM:INIT
TSM:RADIO:OK
TSP:ASÓÉGNID:OK (ID=3)
TSM:FPAR
TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,ót=bc:
TSP:MSG:REÁÄ 0-0-3 s=255,c=3,t=8,pt=1,l=1,sg=0:0
TSP:MSG:FPAÒ REÓ (IÄ=0, äést=0)
TSP:MSG:FPAR (PPAR FOUND)
TSP:MSG:PAR OK (ID=0, dist=1)
TSM:FPAR:OK
TSM:ID
TSM:CHKID:ÏK (ID=3)
ÔSM:UPL
TSÐ:PING:SÅND (dest=0)
TSP:MSG:SEND 3-3-0-0 s=255,c=3,ô=24,pt=1,l=1,sg=0,ft=0,st=ok:1
ÔSP:MSG:READ 0-0-3 s=255,c=3,t=25,pt=1,l=1,sg=0:1
TSP:MSG:PONG RECV (hops=1)
TSP:CHKUPL:OK
TSM:UPL:OK
TSM:ÒEADY
Óånsebender Micro FW 1.4 - Online!
NODE:!REG
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=0,pt=1,l=1,sg=0,ft=0,st=ok:229
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100
TSP:MSG:SEND 3-3-0-0 s=255,c=0,ô=17,pt=0,l=5,sg=0,ft=0,st=ok:2.0.0
TSP:MSG:SEND 3-3-0-0 s=255,ã=3,t=6,pt=1,l=1,sg=0,ft=0,st=ïk:0
TSP:MSG:READ 0-0-3 s=255,c=3,t=15,pt=6,l=2,sg=0:0100
TSP:ÍSG:READ 0-0-3 s=255,c=3,t=6,pt=0,l=1,sg=0:M
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=11,pt=0,l=17,sg=0,æt=0,st=ok:Senseâender Micro
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=ok:1.4
TSP:MSG:SEND 3-3-0-0 s=1,c=0,t=1,ðô=0,l=0,sg=0,æt=0,st=ok:
TSP:MSG:SENÄ 3-3-0-0 s=199,c=0,t=13,pô=0,l=0,sg=0,ft=0,st=ok:
Request regisôòation...
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=ok:2
TSP:MSG:READ 0-0-3 s=255,c=3,t=27,pt=1,l=1,sg=0:1
Node registòation=1
Init complete, id=3, parent=0, distancå=1, registration=1
TSP:MSG:SEND 3-3-0-0 s=1,c=1,t=16,pt=0,l=1,sg=0,ft=0,st=ok:0```