Hello,

two months ago, I tried to start with MySensors, without the tiniest success I tried to get some help here, without any reaction. Quite sad. But now I tried it almost from scratch - still without success, but maybe now someone can help me?

I bought new NRF24+ modules from itead. The forum somewhere claimed that they would most likely not send faked modules. Did cost a good bit more than the ones from E-Bay... who knows?

The gateway NRF24 is powered using an LM317. The oscilloscope shows no ripple at all.

The node has a 22µF Capacitor across VCC/Gnd and is configured as a pure Repeater. No additional hardware.

I updated to MySensors 2.2.0. The gateway is found in FHEM and I start the inclusion (using FHEM). The FHEM log tells me:

2018.01.28 15:16:52 1: 192.168.178.3:5003 disconnected, waiting to reappear (MySensors.Gateway)
2018.01.28 15:16:57 1: 192.168.178.3:5003 reappeared (MySensors.Gateway)

The gateway log Logparser:

0 MCO:BGN:INIT GW,CP=RNNGA---,VER=2.2.0
3 TSM:INIT
4 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
12 TSM:INIT:GW MODE
14 TSM:READY:ID=0,PAR=0,DIS=0
17 MCO:REG:NOT NEEDED
319 GWT:TIN:IP=192.168.178.3
1323 MCO:BGN:STP
1324 MCO:BGN:INIT OK,TSP=1
27586 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
27592 TSF:MSG:BC
27593 TSF:MSG:FPAR REQ,ID=255
27596 TSF:PNG:SEND,TO=0
27598 TSF:CKU:OK
27600 TSF:MSG:GWL OK
28616 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
30430 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
30435 TSF:MSG:BC
30437 TSF:MSG:FPAR REQ,ID=255
30439 TSF:CKU:OK,FCTRL
30442 TSF:MSG:GWL OK
31226 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
32441 TSF:MSG:READ,255-255-0,s=1,c=3,t=3,pt=0,l=0,sg=0:
34450 TSF:MSG:READ,255-255-0,s=220,c=3,t=3,pt=0,l=0,sg=0:
36460 TSF:MSG:READ,255-255-0,s=183,c=3,t=3,pt=0,l=0,sg=0:
38469 TSF:MSG:READ,255-255-0,s=146,c=3,t=3,pt=0,l=0,sg=0:
50488 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
50493 TSF:MSG:BC
50495 TSF:MSG:FPAR REQ,ID=255
50498 TSF:PNG:SEND,TO=0
50500 TSF:CKU:OK
50501 TSF:MSG:GWL OK
50867 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
52499 TSF:MSG:READ,255-255-0,s=107,c=3,t=3,pt=0,l=0,sg=0:
54509 TSF:MSG:READ,255-255-0,s=71,c=3,t=3,pt=0,l=0,sg=0:
56518 TSF:MSG:READ,255-255-0,s=34,c=3,t=3,pt=0,l=0,sg=0:
58529 TSF:MSG:READ,255-255-0,s=254,c=3,t=3,pt=0,l=0,sg=0:
70549 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
70554 TSF:MSG:BC
70556 TSF:MSG:FPAR REQ,ID=255
70558 TSF:PNG:SEND,TO=0
70560 TSF:CKU:OK
70562 TSF:MSG:GWL OK
71532 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
72560 TSF:MSG:READ,255-255-0,s=217,c=3,t=3,pt=0,l=0,sg=0:
74570 TSF:MSG:READ,255-255-0,s=181,c=3,t=3,pt=0,l=0,sg=0:
76579 TSF:MSG:READ,255-255-0,s=144,c=3,t=3,pt=0,l=0,sg=0:
78589 TSF:MSG:READ,255-255-0,s=107,c=3,t=3,pt=0,l=0,sg=0:
90607 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
90613 TSF:MSG:BC
90614 TSF:MSG:FPAR REQ,ID=255
90617 TSF:PNG:SEND,TO=0
90619 TSF:CKU:OK
90621 TSF:MSG:GWL OK
91171 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
92619 TSF:MSG:READ,255-255-0,s=69,c=3,t=3,pt=0,l=0,sg=0:

The repeater log logparser:

16 MCO:BGN:INIT REPEATER,CP=RNNRA---,VER=2.2.0
26 TSM:INIT
27 TSF:WUR:MS=0
34 TSM:INIT:TSP OK
35 TSM:FPAR
37 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
801 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0
806 TSF:MSG:FPAR OK,ID=0,D=1
2046 TSM:FPAR:OK
2048 TSM:ID
2049 TSM:ID:REQ
2052 TSF:MSG:SEND,255-255-0-0,s=1,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
4059 TSM:ID
4060 TSM:ID:REQ
4062 TSF:MSG:SEND,255-255-0-0,s=220,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
6070 TSM:ID
6071 TSM:ID:REQ
6073 TSF:MSG:SEND,255-255-0-0,s=183,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
8081 TSM:ID
8082 TSM:ID:REQ
8084 TSF:MSG:SEND,255-255-0-0,s=146,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
10092 !TSM:ID:FAIL
10093 TSM:FAIL:CNT=1
10095 TSM:FAIL:DIS
10097 TSF:TDI:TSL
20100 TSM:FAIL:RE-INIT
20102 TSM:INIT
20109 TSM:INIT:TSP OK
20111 TSM:FPAR
20113 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20458 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0
20463 TSF:MSG:FPAR OK,ID=0,D=1
22121 TSM:FPAR:OK
22122 TSM:ID
22124 TSM:ID:REQ
22126 TSF:MSG:SEND,255-255-0-0,s=107,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
24134 TSM:ID
24135 TSM:ID:REQ
24138 TSF:MSG:SEND,255-255-0-0,s=71,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
26145 TSM:ID
26146 TSM:ID:REQ
26149 TSF:MSG:SEND,255-255-0-0,s=34,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
28157 TSM:ID
28158 TSM:ID:REQ
28162 TSF:MSG:SEND,255-255-0-0,s=254,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
30169 !TSM:ID:FAIL
30170 TSM:FAIL:CNT=2
30172 TSM:FAIL:DIS
30174 TSF:TDI:TSL
40177 TSM:FAIL:RE-INIT

A look at the repeaters log and I'm completely puzzled:
806 TSF:MSG:FPAR OK,ID=0,D=1 Find parent response from node 0 is valid, distance 1 to GW

\o/ Party! Finally it works! ... but wait. A few (successful) messages later:

   10092 !TSM:ID:FAIL	
   10093 TSM:FAIL:CNT=1	Transition to Failure state, consecutive failure counter is 1

I could v*mit, excuse my language. To me it seems that the communication is ok, but there's still some error that I don't understand. Isn't there anybody who could help me? Pretty, pretty please?
I have a photo of the system attached. In the background, you see the gateway, in the foreground the repeater:

Any help will be very much appreciated, as you can imagine after two months without success...

cu
Markus

Hello @Technovation,

as embarrassing as it is: you are completely right . For more than 30 years, I've either used elkos (where I know they have a polarity) or ceramic capacitors (which don't have one) or used the correct polarity by accident and was completely baffled when I learned that tantalum capacitors have a polarity. It doesn't help that the only indication is so non-descript...

Well, you never stop learning. I'm looking forward to much more stable mysensors

And I apologize for blaming the NRF24 modules and the shops for my ignorance.

Hello @Technovation,

as embarrassing as it is: you are completely right . For more than 30 years, I've either used elkos (where I know they have a polarity) or ceramic capacitors (which don't have one) or used the correct polarity by accident and was completely baffled when I learned that tantalum capacitors have a polarity. It doesn't help that the only indication is so non-descript...

Well, you never stop learning. I'm looking forward to much more stable mysensors

And I apologize for blaming the NRF24 modules and the shops for my ignorance.

The Culprit seems to be the yellow capacitor next to the gray 100nF Capacitor. Should be 10uF, I think. If I cool that one with ice spray, power consumption normalizes immediately.

It seems to be really hard to buy high quality components, even at shops that have a good name.

@Yveaux Yes. I measured 0.2Ω.

Hello,

I built the board from scratch and am none the wiser

To recap: I have built a mysensors sensor to read the wind speed of an Adafruit Anemometer. That sensor literally burned Nrf24l01+ modules and I have no idea why.

The only special thing about this sensor is that I connected the AREF pin of the Arduino to 3.3V because the Aneometers output is 0.4..2V and I didn't want to waste a ADC bit because of the standard 5V reference voltage. I did this by connecting AREF directly to 3.3V and I let the capacitor from AREF to GND in place.

I connected the new module to a 2 channel lab power supply: 9V to the RAW input (because the Anemometer needs 7 to 12V power supply) with a maximum current of ~100mA. 0.4V to A0 with barely some current flowing to simulate the Anemometer. I powered up the module and everything worked. The module consumed about 23mA which is the value that I expected from earlier tries. Yay!

About 15 minutes later: Communication was broken again. The Arduino LED that indicates SPDIF clock was dark, the Power supply showed >110mA power consumption. Sh*t.

I lowered the Supply voltage to 5V (maybe to cause less damage...) and power cycled the module. It started with 35mA and was working (presentation to the controller and sends wind speed). And then... the consumed current rises! The longer, the faster. I let it run for about 1.5 minutes and the consumed current doubled to more than 60mA.

I'm running out of NRF modules and out of ideas. I attach some pictures that show my module and really hope that you have some new ideas. Did I mess up the AREF?

Ah, what? The forum doesn't allow uploading source code? Well, then as code block:

/**
 * The MySensors Arduino library handles the wireless radio link and protocol
 * between your home built sensors/actuators and HA controller of choice.
 * The sensors forms a self healing radio network with optional repeaters. Each
 * repeater and gateway builds a routing tables in EEPROM which keeps track of the
 * network topology allowing messages to be routed to nodes.
 *
 *******************************
 *
 * DESCRIPTION
 * This sketch reads wind speed information from an Adafruit Wind Speed Sensor 1733
 *
 * Specifications
 *
 *  Output: 0.4V to 2V
 *  Testing Range: 0.5m/s to 50m/s
 *  Start wind speed: 0.2 m/s
 *  Resolution: 0.1m/s
 *  Accuracy: Worst case 1 meter/s
 *  Max Wind Speed: 70m/s
 *  Connector details: Pin 1 - Power (brown wire),
 *                     Pin 2 - Ground (black wire),
 *                     Pin 3 - Signal (blue wire),
 *                     Pin 4 not connected
 *
 */

// Enable debug prints
#undef MY_DEBUG

// Enable and select radio type attached
#define MY_RADIO_NRF24

// Enabled repeater feature for this node
#define MY_REPEATER_FEATURE

/**
 * @def MY_NODE_ID
 * @brief Node id defaults to AUTO (tries to fetch id from controller).
 */
#define MY_NODE_ID 105

/**
 * @def MY_PARENT_NODE_ID
 * @brief Node parent defaults to AUTO (tries to find a parent automatically).
 */
#define MY_PARENT_NODE_ID 0

#include <MySensors.h>
#include <limits.h>

// (External) Reference voltage in Volts
// We use the external 3.3V because it's closer to the 2V maximum of the sensor.
// This way we loose less of the ADC range
#define U_REF_V (3.3)

// Set this to the pin you connected the DHT's data pin to
#define WIND_ANLOG_PIN A0

#define SECOND (1000)  // seconds to milliseconds

// Sleep time between sensor updates (in milliseconds)
static const uint64_t UPDATE_INTERVAL_MS = 10 * SECOND;

// Force sending an update of the temperature after n sensor reads, so a controller showing the
// timestamp of the last update doesn't show something like 3 hours in the likely case, that
// the value didn't change since;
// i.e. the sensor would force sending an update every UPDATE_INTERVAL*FORCE_UPDATE_N_READS [ms]
static const uint8_t FORCE_UPDATE_N_READS = 6 * 5;  // each 5 minutes

#define CHILD_ID_WIND 0

#define LSB_TO_VOLT (U_REF_V/1024)   // V/LSB
#define V_MAX_mps   (70)             // Maximum wind speed in m/s
#define U_MIN_V     (0.4)            // Minimum voltage in V
#define U_MAX_V     (2.0)            // Maximum voltage in V
#define SENSOR_PRECISION_MPS (0.1)   // precision of the sensor in m/s

// m=70/(2-0.4)   m/(sV)
// t=-0.4*m       m/s
// v=m*u+t

#define M (V_MAX_mps/(U_MAX_V-U_MIN_V))    //  m/(sV)
#define T (-U_MIN_V*M)                     //  m/s

float lastWindSpeed_mps;
uint8_t noUpdates;

MyMessage msgWindSpeed(CHILD_ID_WIND, V_WIND);

float lsbToWindSpeed(const float lsb)  {
  const float u_V = lsb * LSB_TO_VOLT;
  float speed_mps = M * u_V + T;
  if( speed_mps <0 ) {
    speed_mps = 0;
  }
  return speed_mps;
}

void presentation()
{
  // Send the sketch version information to the gateway
  sendSketchInfo("WindSpeed", "1.1");

  // Register all sensors to gw (they will be created as child devices)
  present(CHILD_ID_WIND, S_WIND);
}


void setup()
{
  analogReference(EXTERNAL);         // use the external reference voltage
  pinMode(WIND_ANLOG_PIN, INPUT);
  lastWindSpeed_mps = -1;
  noUpdates = 0;
}


void loop()
{
  int adcValue = analogRead(WIND_ANLOG_PIN);
  float windSpeed_mps = lsbToWindSpeed(adcValue);


#ifdef MY_DEBUG
  Serial.print("ADC: ");
  Serial.println(adcValue);
  Serial.print("SP1: ");
  Serial.println(windSpeed_mps);
#endif



  if ( abs(lastWindSpeed_mps - windSpeed_mps) >= SENSOR_PRECISION_MPS || noUpdates== FORCE_UPDATE_N_READS ) {
    lastWindSpeed_mps = windSpeed_mps;
    noUpdates = 0;

    send(msgWindSpeed.set(windSpeed_mps, 1));

#ifdef MY_DEBUG
    Serial.print("SP2: ");
    Serial.println(windSpeed_mps);
#endif
  }
  else {
    ++noUpdates;
  }

  // Sleep for a while to save energy
  sleep(UPDATE_INTERVAL_MS);
}

Here you can see a video with the rising power consumption:
https://youtu.be/7o4FYRTkRLA

Next days I'll remove the 3.3V modification and try it with the default. The extra bit resolution is not really necessary. But I can't imagine that's the reason.

Hello, thanks for all your feedback!

I'll send pictures soon. But since I'm using @sundberg84 's easy PCB, I rule out bad wiring. I haven't seen any solder bridges, but I'll have a closer look.

The PCB is only connected to a 9V power supply

Maybe it's realy a bad batch... I thought itead.com is the preferred supplier - are there better ones?

And by the way: the sensor stopped working again ;( I'll have a real close look over the weekend.

cu
Markus

This is a phenomenon that I've had two or three times already:

• NRF24+ Module from itead.com
• PCB from @sundberg84 Easy PCB because it's awesome

Built a new sensor, works perfectly. Put the sensor into a housing, let it run for a few (last time: less than one) hours and the sensor stops working. Opened the housing that was already warm. The PCB is hot and I burnt my finger on the 3.3v regulator.The NRF24+ is even hotter.

I checked the PCB and saw no problem. Checked my software: all ok. Dared to blow up another NRF24+ ... that worked. Has been working without a flaw since three days.

As I said, this is about the third time that happened. Do you experience that problem too? I rule out a hardware problem on the easypcb and the software, because with another NRF24+ module all is fine...

Could it be an ESD problem? I have no ESD protected setup at home...

Looking forward to your answers

P.S.: the 5A are not measured. I just invented that number.

cu
Markus

Logparser is really a helpful tool. But is there a version that I can run offline on my computer?

• It is annoying to be forced to be online, just to interpret logs
• If I had it on my computer, I coult pipe the debug output through the parser and see the results life

Hello,

thanks for your input! In the FHEM-Forum, it turned out that I erased the arduinos EEPROM using the ClearEEPROMConfig - sketch, which overwrites everything with 0, not with 0xFF. That disabled the automatig setting of the node id...

I used a sketch that overwrites with 0xFF and all is fine

Hello mfalkvidd!

At last, some good news Thanks for the information. I think the FHEM guys will be able to help with the node id question. I'll be back when there's some news. Unfortunately, this could be next weekend.

Thanks again,
Markus

Hello,

two months ago, I tried to start with MySensors, without the tiniest success I tried to get some help here, without any reaction. Quite sad. But now I tried it almost from scratch - still without success, but maybe now someone can help me?

I bought new NRF24+ modules from itead. The forum somewhere claimed that they would most likely not send faked modules. Did cost a good bit more than the ones from E-Bay... who knows?

The gateway NRF24 is powered using an LM317. The oscilloscope shows no ripple at all.

The node has a 22µF Capacitor across VCC/Gnd and is configured as a pure Repeater. No additional hardware.

I updated to MySensors 2.2.0. The gateway is found in FHEM and I start the inclusion (using FHEM). The FHEM log tells me:

2018.01.28 15:16:52 1: 192.168.178.3:5003 disconnected, waiting to reappear (MySensors.Gateway)
2018.01.28 15:16:57 1: 192.168.178.3:5003 reappeared (MySensors.Gateway)

The gateway log Logparser:

0 MCO:BGN:INIT GW,CP=RNNGA---,VER=2.2.0
3 TSM:INIT
4 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
12 TSM:INIT:GW MODE
14 TSM:READY:ID=0,PAR=0,DIS=0
17 MCO:REG:NOT NEEDED
319 GWT:TIN:IP=192.168.178.3
1323 MCO:BGN:STP
1324 MCO:BGN:INIT OK,TSP=1
27586 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
27592 TSF:MSG:BC
27593 TSF:MSG:FPAR REQ,ID=255
27596 TSF:PNG:SEND,TO=0
27598 TSF:CKU:OK
27600 TSF:MSG:GWL OK
28616 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
30430 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
30435 TSF:MSG:BC
30437 TSF:MSG:FPAR REQ,ID=255
30439 TSF:CKU:OK,FCTRL
30442 TSF:MSG:GWL OK
31226 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
32441 TSF:MSG:READ,255-255-0,s=1,c=3,t=3,pt=0,l=0,sg=0:
34450 TSF:MSG:READ,255-255-0,s=220,c=3,t=3,pt=0,l=0,sg=0:
36460 TSF:MSG:READ,255-255-0,s=183,c=3,t=3,pt=0,l=0,sg=0:
38469 TSF:MSG:READ,255-255-0,s=146,c=3,t=3,pt=0,l=0,sg=0:
50488 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
50493 TSF:MSG:BC
50495 TSF:MSG:FPAR REQ,ID=255
50498 TSF:PNG:SEND,TO=0
50500 TSF:CKU:OK
50501 TSF:MSG:GWL OK
50867 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
52499 TSF:MSG:READ,255-255-0,s=107,c=3,t=3,pt=0,l=0,sg=0:
54509 TSF:MSG:READ,255-255-0,s=71,c=3,t=3,pt=0,l=0,sg=0:
56518 TSF:MSG:READ,255-255-0,s=34,c=3,t=3,pt=0,l=0,sg=0:
58529 TSF:MSG:READ,255-255-0,s=254,c=3,t=3,pt=0,l=0,sg=0:
70549 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
70554 TSF:MSG:BC
70556 TSF:MSG:FPAR REQ,ID=255
70558 TSF:PNG:SEND,TO=0
70560 TSF:CKU:OK
70562 TSF:MSG:GWL OK
71532 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
72560 TSF:MSG:READ,255-255-0,s=217,c=3,t=3,pt=0,l=0,sg=0:
74570 TSF:MSG:READ,255-255-0,s=181,c=3,t=3,pt=0,l=0,sg=0:
76579 TSF:MSG:READ,255-255-0,s=144,c=3,t=3,pt=0,l=0,sg=0:
78589 TSF:MSG:READ,255-255-0,s=107,c=3,t=3,pt=0,l=0,sg=0:
90607 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
90613 TSF:MSG:BC
90614 TSF:MSG:FPAR REQ,ID=255
90617 TSF:PNG:SEND,TO=0
90619 TSF:CKU:OK
90621 TSF:MSG:GWL OK
91171 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
92619 TSF:MSG:READ,255-255-0,s=69,c=3,t=3,pt=0,l=0,sg=0:

The repeater log logparser:

16 MCO:BGN:INIT REPEATER,CP=RNNRA---,VER=2.2.0
26 TSM:INIT
27 TSF:WUR:MS=0
34 TSM:INIT:TSP OK
35 TSM:FPAR
37 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
801 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0
806 TSF:MSG:FPAR OK,ID=0,D=1
2046 TSM:FPAR:OK
2048 TSM:ID
2049 TSM:ID:REQ
2052 TSF:MSG:SEND,255-255-0-0,s=1,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
4059 TSM:ID
4060 TSM:ID:REQ
4062 TSF:MSG:SEND,255-255-0-0,s=220,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
6070 TSM:ID
6071 TSM:ID:REQ
6073 TSF:MSG:SEND,255-255-0-0,s=183,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
8081 TSM:ID
8082 TSM:ID:REQ
8084 TSF:MSG:SEND,255-255-0-0,s=146,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
10092 !TSM:ID:FAIL
10093 TSM:FAIL:CNT=1
10095 TSM:FAIL:DIS
10097 TSF:TDI:TSL
20100 TSM:FAIL:RE-INIT
20102 TSM:INIT
20109 TSM:INIT:TSP OK
20111 TSM:FPAR
20113 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20458 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0
20463 TSF:MSG:FPAR OK,ID=0,D=1
22121 TSM:FPAR:OK
22122 TSM:ID
22124 TSM:ID:REQ
22126 TSF:MSG:SEND,255-255-0-0,s=107,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
24134 TSM:ID
24135 TSM:ID:REQ
24138 TSF:MSG:SEND,255-255-0-0,s=71,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
26145 TSM:ID
26146 TSM:ID:REQ
26149 TSF:MSG:SEND,255-255-0-0,s=34,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
28157 TSM:ID
28158 TSM:ID:REQ
28162 TSF:MSG:SEND,255-255-0-0,s=254,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
30169 !TSM:ID:FAIL
30170 TSM:FAIL:CNT=2
30172 TSM:FAIL:DIS
30174 TSF:TDI:TSL
40177 TSM:FAIL:RE-INIT

A look at the repeaters log and I'm completely puzzled:
806 TSF:MSG:FPAR OK,ID=0,D=1 Find parent response from node 0 is valid, distance 1 to GW

\o/ Party! Finally it works! ... but wait. A few (successful) messages later:

   10092 !TSM:ID:FAIL	
   10093 TSM:FAIL:CNT=1	Transition to Failure state, consecutive failure counter is 1

I could v*mit, excuse my language. To me it seems that the communication is ok, but there's still some error that I don't understand. Isn't there anybody who could help me? Pretty, pretty please?
I have a photo of the system attached. In the background, you see the gateway, in the foreground the repeater:

Any help will be very much appreciated, as you can imagine after two months without success...

cu
Markus