Hi guys, I may found the issue.

GW was powered from the NAS (for month) and I switched for a wall adapter. Now I'm able to ping GW without timeout...sorry (I see you guys coming....obviously it's a power issue :D !). GW has been running for one days now.

Note: I'm using AVR 1.6.16 now, but i'm pretty sure, power was the real issue.

Thank for the hint, I was able to invested the issue more. Here the result:

@gohan

Sketch uses 19560 bytes (60%) of program storage space. Maximum is 32256 bytes.
Global variables use 981 bytes (47%) of dynamic memory, leaving 1067 bytes for local variables. Maximum is 2048 bytes.

@webstor No it's pingable but their some timeout.

Request timeout for icmp_seq 115
Request timeout for icmp_seq 116
64 bytes from 1.1.0.130: icmp_seq=117 ttl=128 time=0.693 ms
64 bytes from 1.1.0.130: icmp_seq=118 ttl=128 time=0.694 ms
64 bytes from 1.1.0.130: icmp_seq=119 ttl=128 time=0.656 ms
64 bytes from 1.1.0.130: icmp_seq=120 ttl=128 time=3.135 ms
64 bytes from 1.1.0.130: icmp_seq=121 ttl=128 time=0.641 ms
64 bytes from 1.1.0.130: icmp_seq=122 ttl=128 time=0.618 ms
64 bytes from 1.1.0.130: icmp_seq=123 ttl=128 time=0.861 ms
64 bytes from 1.1.0.130: icmp_seq=124 ttl=128 time=3.536 ms
Request timeout for icmp_seq 125
Request timeout for icmp_seq 126
Request timeout for icmp_seq 127
Request timeout for icmp_seq 128
64 bytes from 1.1.0.130: icmp_seq=129 ttl=128 time=0.494 ms
64 bytes from 1.1.0.130: icmp_seq=130 ttl=128 time=0.563 ms
64 bytes from 1.1.0.130: icmp_seq=131 ttl=128 time=0.622 ms
64 bytes from 1.1.0.130: icmp_seq=132 ttl=128 time=0.643 ms
Request timeout for icmp_seq 133
Request timeout for icmp_seq 134
Request timeout for icmp_seq 135
Request timeout for icmp_seq 136
Request timeout for icmp_seq 137
64 bytes from 1.1.0.130: icmp_seq=138 ttl=128 time=0.828 ms
64 bytes from 1.1.0.130: icmp_seq=139 ttl=128 time=0.570 ms
64 bytes from 1.1.0.130: icmp_seq=140 ttl=128 time=0.766 ms
64 bytes from 1.1.0.130: icmp_seq=141 ttl=128 time=0.673 ms
64 bytes from 1.1.0.130: icmp_seq=142 ttl=128 time=3.274 ms
64 bytes from 1.1.0.130: icmp_seq=143 ttl=128 time=0.662 ms
64 bytes from 1.1.0.130: icmp_seq=144 ttl=128 time=0.714 ms
Request timeout for icmp_seq 145
Request timeout for icmp_seq 146
64 bytes from 1.1.0.130: icmp_seq=147 ttl=128 time=0.663 ms
64 bytes from 1.1.0.130: icmp_seq=148 ttl=128 time=3.395 ms
64 bytes from 1.1.0.130: icmp_seq=149 ttl=128 time=0.660 ms
64 bytes from 1.1.0.130: icmp_seq=150 ttl=128 time=3.527 ms
64 bytes from 1.1.0.130: icmp_seq=151 ttl=128 time=0.650 ms
64 bytes from 1.1.0.130: icmp_seq=152 ttl=128 time=0.629 ms
64 bytes from 1.1.0.130: icmp_seq=153 ttl=128 time=0.565 ms
64 bytes from 1.1.0.130: icmp_seq=154 ttl=128 time=0.639 ms

Same test after reset, GW keep dropping but this time with max of 2 drop per ten ping. Other devices (phone, bridge etc...) can be pinged without timeout and I'm on the same network.

For the communication testing, I'm sending payload to my tv sensor, and I made a video showing the GW status led when he doesn't work:
and
After reset

Look like it's a reset on the first video?

Next test, new sketch with debug on, sending same payload, GW always receive something like:

0;255;3;0;9;Eth: 2;3;1;0;32;10
0;255;3;0;9;TSF:MSG:SEND,0-0-2-2,s=3,c=1,t=32,pt=0,l=2,sg=0,ft=0,st=OK:10

Some time even when payload is received, TV doesn't turn on, also tested with a simple light sensor. GW and TV are in the same room.

So look like GW is dropping some message, I'll try tomorrow to get back to previous AVR, if their no hint.

Hi,
I have the same issue, W5100 gateway freeze, seen my update to MySensor 2.1.1.
I use a static IP otherway it's the same code as @webstor I did removed both line and still gateway freeze (one day max ). Unlike @websor if I reset, gateway doesn't come back. I have to unplug the usb power.

I only have five sensor, with only one battery powered. I used IDE 1.8.2 and AVR 1.6.18. Everything was working well with MySensor 2.0.0, IDE 1.6.9 , AVR 1.6.15. Any idea what could I look at ?

@gohan Just did it ! everything is up to date and work thank you :D.

@rejoe2 roll back to MySensor 2.0.0 and AVR to (1.6.15 then 1.6.10 then 1.6.11). Cleer eeprom of both GW and node each time. Also restart IDE each time. And still can't connect.

But I get back to AVR 1.6.18 and it's working now! Only for node with MS 2.0.0. So everything is back to normal except that I can't upgrade to MS 2.1.1 :(

@gohan No customization and I'm using version 1.6.9.
FYI error was: CRC doesn't match. File is corrupted. java.lang.RuntimeException: java.lang.Exception: CRC doesn't match. File is corrupted. at cc.arduino.contributions.libraries.ui.LibraryManagerUI.lambda$onInstallPressed$12(LibraryManagerUI.java:231) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.Exception: CRC doesn't match. File is corrupted. at cc.arduino.contributions.DownloadableContributionsDownloader.download(DownloadableContributionsDownloader.java:77) at cc.arduino.contributions.libraries.LibraryInstaller.install(LibraryInstaller.java:97) at cc.arduino.contributions.libraries.ui.LibraryManagerUI.lambda$onInstallPressed$12(LibraryManagerUI.java:227) ... 1 more

@gohan I did roll back but doesn't work. And by the way I can't downgrade to 2.0.0 from library manager. I'll post the error later but it's like the 2.0.0 does not exist, because I can downgrade to 2.1.0. Anyway I did it by downloading the package from mysensor download page.

@rejoe2 You may got it! I was using version 1.6.15 but I can't find it anymore in library manager. So can't downgrade, I'll search more carefully tonight.

Hello, I also had the same issue, unfortunately I can't fix it.
I using socket adapter and everything is usb powered. This configuration has been working well since september 2016.

Last week I decided to update to version 2.1.1 because I need to create a new door sensor. Seen that upgrade I can’t get anything working anymore. I have been try ClearEepromConfig, without success. Verify many time my wiring (Yes many time!). I also force MY_NODE_ID and MY_PARENT_NODE_ID.

So today I decide to get back to version 2.0.0 and still can’t connect. Luckyly I kept one sensor from being upgraded and this one worked. Look like all sensor that have been upgraded is likely of broken.

I have been searching and I’m not the only one, mostly the issue is because of power issue. Log parser also say "Finding parent failed","Power-down transport" but why people get power issue after updating to 2.1.* ?
If someone can tell what should I look for now, at least how to roll back to the 2.0.0.

GW: Arduino uno W5100-NRF24-L01+PA+LNA
NODE: Arduino nano-5v NRF24
Log:

720991 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
722998 !TSM:FPAR:NO REPLY
723000 TSM:FPAR
723003 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
725010 !TSM:FPAR:NO REPLY
725012 TSM:FPAR
725015 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
727022 !TSM:FPAR:NO REPLY
727024 TSM:FPAR
727027 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
729034 !TSM:FPAR:FAIL
729036 TSM:FAIL:CNT=7
729038 TSM:FAIL:PDT

@alexsh1 said:

FTDI
Ohh thank you @alexsh1 , and my bad, you made me realize that Ceech's board as the ATMega. Now that make more sense the A7 is the analog pin 7 that is linked with the CHRG of LTC4067. Anyway Thanks :D !

Hi everyone, I'm new to arduino, and I bougth Ceech board.
Can someone please let me know how to upload sketch on this board? I read it's compatible with arduino but I can't find any wiring schema.
Also where is A7/CHRG ? Because my board go from analog A0 to A5.
And I bought the following one :
http://www.ebay.com/itm/331838940273?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

I just want a solar/battery powered sensor. And I have anduino nano.
Thank