Hi

I'm looking for a long range (2.5-3 meters) barrier sensor and I can't find something interesting
Maybe you can help me ;-)

I need to detect the car position in my garage and turn on a light to not bump the other car.
My idea is to install 3 or 4 sensors on ceiling to detect which car is the first and with a little of intelligence turns on first or second light.
It's not a problem to install reflector on the ground.
The idea is similar to parking build but it can't be applied in my configuration.

Thanks for your help ;-)

Hi torehc

vcc (3.04v)-----arduino RAW pin
gnd------arduino GND
NRF vcc-----arduino VCC (regulated 3.3 in my case)

If you have problem with route i suppose it is a problem with your power supply. NRF seems to be really erratic.
Also you must add a capacitor on nrf too.

Hourra I found my problem !
I connected directly the NRF to RAW pin instead of regulated one (VCC).
Now everything is working fine

Thank you guys for your help ;-)

I forced the parent id as vil1driver suggested and I saw on my controller id request (give id 3) with no error

2015-Sep-01 22:16:47.793938 [DEBUG]  => RECEIVING: 255/255;INTERNAL;0;I_ID_REQUEST;
2015-Sep-01 22:16:47.794094 [DEBUG] Free id found: 3
2015-Sep-01 22:16:47.794176 [DEBUG]  => SENDINGv15: 255;255;3;0;4;3<NL>
2015-Sep-01 22:16:47.830373 [DEBUG]  => RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;send: 0-0-2-255 s=255,c=3,t=4,pt=0,l=1,sg=0,st=ok:3

But my sensor seems to have problem receiving the response

req id
255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
sensor started, id=255, parent=2, distance=1
req id
255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
req id
255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
req id
255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
req id
255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
req id
255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0

So do you think my problem is a circuit issue?
Is it possible to send successfully all packets and have problem receiving them?

No way to make it find a new route after 4 days.
I decided to clear eeprom and the sensor is still in bad state.
It always display

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

on my gateway i receive:

0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-255 s=255,c=3,t=8,pt=1,l=1,sg=0:1
0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-255 s=255,c=3,t=8,pt=1,l=1,sg=0:1
0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-255 s=255,c=3,t=8,pt=1,l=1,sg=0:1
0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-255 s=255,c=3,t=8,pt=1,l=1,sg=0:1

I tried with 2 differents NRF (with 4.7µf cap)
Before clearing eeprom, the sensors successfully sends its data directly to gateway (without passing though repeater) but gateway failed still failed to send command to sensor
Gateway and repeater have NFR with external antenna.

I don't know exactly where is the problem:

• is there a communication problem between gateway and controller ?
• is there a problem with my sensor ?

Near my new sensor (2 meters) i have an another sensor that is working fine but it's not an actuator.
I have another actuator that is out of gateway sensor and connected to repeater #2.

To sum up my configuration:
#111 (actuator) -> #2 (repeater) -> gateway ==> no pb (report state and receive command successfully)
#1(power sensor) -> #2 (repeater) -> gateway => no pb
#110 (temp sensor) -> #2 (repeater) -> gateway => no pb

Is someone have some clue to investigate?

I created a new sensor today and tested it near my gateway.
The sensor is supposed to be out of my gateway range (behind 3 thick walls), but installed in the place it was built for (open/close my garage door) it manages to send sometimes some messages :S
To handle my range problem a repeater is installed just behind the first wall and is repeating messages from 3 others sensors.
Seeing gateway messages, I saw messages from my new sensor are not using the repeater.
What is the event that forces sensor to change its route? And is there a way to force it manually (without clearing eeprom) ?
Thanks

@bjacobse said:

@Tang Perfect,
Let me know if I can do some testing/verification for you

I commited my stuff. You can make a try and tell me all bugs you found ;-)
Please use irc now. Thx

I thought i was using the latest 1.5 version but it seems not.
Uploading all my sketches with fresh downloaded version fixed my pb.

Thx sundberg84 ;)

I investigated more and found my actuator message seems to be lost by repeater:

2 is my repeater node
and 111 is my actuator sensor

<actuator started>
0;0;3;0;9;read: 111-111-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-111-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:0
111;1;1;0;2;0
0;0;3;0;9;read: 111-111-0 s=255,c=0,t=18,pt=0,l=3,sg=0:1.5
111;255;0;0;18;1.5
0;0;3;0;9;read: 111-111-0 s=255,c=3,t=6,pt=1,l=1,sg=0:0
111;255;3;0;6;0
0;0;3;0;9;read: 111-111-0 s=255,c=3,t=11,pt=0,l=14,sg=0:Relay & Butto
111;255;3;0;11;Relay & Button
0;0;3;0;9;read: 111-111-0 s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
111;255;3;0;12;1.0
0;0;3;0;9;read: 111-111-0 s=1,c=0,t=3,pt=0,l=0,sg=0:
111;1;0;0;3;
<actuator pressing button ok>
0;0;3;0;9;read: 111-111-0 s=1,c=1,t=2,pt=2,l=2,sg=0:1
0;0;3;0;9;send: 0-0-111-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:1
111;1;1;0;2;1
<actuator pressing button ok>
0;0;3;0;9;read: 111-111-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-111-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:0
111;1;1;0;2;0
<actuator pressing button ok>
0;0;3;0;9;read: 111-111-0 s=1,c=1,t=2,pt=2,l=2,sg=0:1
0;0;3;0;9;send: 0-0-111-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:1
111;1;1;0;2;1
<actuator pressing button failed>
0;0;3;0;9;read: 111-111-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-111-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=fail:0
111;1;1;0;2;0
<actuator pressing button failed>
0;0;3;0;9;read: 111-111-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-111-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=fail:0
111;1;1;0;2;0
<actuator pressing button failed>
0;0;3;0;9;read: 111-111-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;0;3;0;9;send: 0-0-111-111 s=255,c=3,t=8,pt=1,l=1,sg=0,st=fail:0
0;0;3;0;9;read: 111-2-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-2-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:0
111;1;1;0;2;0
0;0;3;0;9;read: 111-2-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-2-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:0
111;1;1;0;2;0
<actuator restarted>
0;0;3;0;9;read: 111-2-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-2-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:0
111;1;1;0;2;0
0;0;3;0;9;read: 111-2-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-2-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:0
111;1;1;0;2;0
0;0;3;0;9;read: 111-2-0 s=255,c=0,t=18,pt=0,l=3,sg=0:1.5
111;255;0;0;18;1.5
0;0;3;0;9;read: 111-2-0 s=255,c=3,t=6,pt=1,l=1,sg=0:2
111;255;3;0;6;2
0;0;3;0;9;read: 111-2-0 s=255,c=3,t=11,pt=0,l=14,sg=0:Relay & Button

111;255;3;0;11;Relay & Button
0;0;3;0;9;read: 111-2-0 s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
111;255;3;0;12;1.0
0;0;3;0;9;read: 111-2-0 s=1,c=0,t=3,pt=0,l=0,sg=0:
111;1;0;0;3;
0;0;3;0;9;read: 1-2-0 s=1,c=1,t=39,pt=1,l=1,sg=0:2
1;1;1;0;39;2
0;0;3;0;9;read: 111-2-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-2-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:0
111;1;1;0;2;0
0;0;3;0;9;read: 111-2-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-2-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:0
111;1;1;0;2;0
0;0;3;0;9;read: 111-2-0 s=1,c=1,t=2,pt=2,l=2,sg=0:0
0;0;3;0;9;send: 0-0-2-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:0
111;1;1;0;2;0

My gateway is on my office that have thick walls. For this reason i'm using a repeater with NRF with antenna (like my gateway)
So most of my sensors outside the office need to connect to repeater to access gateway.
In the sample below, the actuator succeed to connect to gateway at the beginning but after some button press, it doesn't handle to send its value. When i restarted the actuator, it connects to repeater and nothing works.

Gateway and actuator sketches are those i found on mysensors library examples, repeater node is based on library example but have a led that blinks periodically and each 10 minutes, repeater send its sketch name.

@bjacobse yes i'm working on it
I just need to fix some stuff on actuator and it should be good

Hi

I got trouble using actuator with button.
I'm using original "RelayWithButtonActuator" sketch from samples (I just replaced all V_LIGHT by V_STATUS and S_LIGHT by S_BINARY) and I can't set its value with command.
Pushing the button turn it on perfectly and I receive message on gateway but i'm unable to set its value using command.
Each time I pressed the button the same messages are received.

For my tests I didn't any controller, just arduino IDE (with NL+CR enabled).

Gateway output:

0;0;3;0;9;read: 111-2-0 s=255,c=0,t=18,pt=0,l=3,sg=0:1.5
111;255;0;0;18;1.5
0;0;3;0;9;read: 111-2-0 s=255,c=3,t=6,pt=1,l=1,sg=0:2
111;255;3;0;6;2
0;0;3;0;9;read: 111-2-0 s=255,c=3,t=11,pt=0,l=14,sg=0:Relay & Button

111;255;3;0;11;Relay & Button
0;0;3;0;9;read: 111-2-0 s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
111;255;3;0;12;1.0
0;0;3;0;9;read: 111-2-0 s=1,c=0,t=3,pt=0,l=0,sg=0:
111;1;0;0;3;
<press button>
0;0;3;0;9;read: 111-2-0 s=1,c=1,t=2,pt=2,l=2,sg=0:1
0;0;3;0;9;send: 0-0-2-111 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:1
111;1;1;0;2;1
<send command 111;1;1;0;2;1 (set value to 1)>
0;0;3;0;9;send: 0-0-2-111 s=1,c=1,t=2,pt=0,l=1,sg=0,st=ok:1
<send command 111;1;1;0;2;0 (set value to 0)>
0;0;3;0;9;send: 0-0-2-111 s=1,c=1,t=2,pt=0,l=1,sg=0,st=ok:0
<send command 111;1;2;0;2; (request value)>
0;0;3;0;9;send: 0-0-2-111 s=1,c=2,t=2,pt=0,l=0,sg=0,st=ok:

Sensor output

send: 111-111-2-0 s=255,c=0,t=18,pt=0,l=3,sg=0,st=ok:1.5
send: 111-111-2-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:2
repeater started, id=111, parent=2, distance=2
send: 111-111-2-0 s=255,c=3,t=11,pt=0,l=14,sg=0,st=ok:Relay & Button
send: 111-111-2-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:1.0
send: 111-111-2-0 s=1,c=0,t=3,pt=0,l=0,sg=0,st=ok:
<press button>
send: 111-111-2-0 s=1,c=1,t=2,pt=2,l=2,sg=0,st=ok:1
<send command 111;1;1;0;2;1 (set value to 1)>
<nothing>
<send command 111;1;1;0;2;0 (set value to 0)>
<nothing>
<send command 111;1;2;0;2; (request value)>
<nothing>

I added a log on the callback function "incomingMessage" (Serial.print("debug");) and it is never displayed.
It's like the callback is never called .

Any ideas?

Thanks;-)

Adding NL+CR to sent command fixed my problem.
Weird everything worked before 1.5. Anyway no problem now :D

Thank you for your help guys ;-)

I tryed with arduino IDE with "Both NL & CR" activated and the sensors received a new ID.

Here is full output of gateway:

0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
255;255;3;0;3;
0;0;3;0;9;send: 0-0-255-255 s=255,c=3,t=4,pt=0,l=1,st=fail:2
0;0;3;0;9;read: 2-2-0 s=255,c=0,t=17,pt=0,l=3:1.5
2;255;0;0;17;1.5
0;0;3;0;9;read: 2-2-0 s=255,c=3,t=6,pt=1,l=1:0
2;255;3;0;6;0
0;0;3;0;9;read: 2-2-0 s=255,c=0,t=17,pt=0,l=3:1.5
2;255;0;0;17;1.5
0;0;3;0;9;read: 2-2-0 s=255,c=3,t=6,pt=1,l=1:0
2;255;3;0;6;0
0;0;3;0;9;read: 2-2-0 s=255,c=3,t=11,pt=0,l=18:Temperature Sensor
2;255;3;0;11;Temperature Sensor
0;0;3;0;9;read: 2-2-0 s=255,c=3,t=12,pt=0,l=3:1.1
2;255;3;0;12;1.1
0;0;3;0;9;read: 2-2-0 s=0,c=0,t=6,pt=0,l=0:
2;0;0;0;6;
0;0;3;0;9;read: 2-2-0 s=0,c=1,t=0,pt=7,l=5:26.2
2;0;1;0;0;26.2

I will try tomorrow to update my controller sending \n\r at end of command.
Until now it seems my controller doesn't send it. Is it something new in 1.5 protocol to handle \n\r as end of command or it is a lack of my controller since the beginning?

@Sparkman I'm using agocontrol. I'm developping mysensors module.
The problem is my controller seems to have the good behaviour but the gateway does nothing.
Like Hek said it's like the frame is lost during serial transfer, but I have doubt about it.
A downgrade of my gateway to 1.4.2 version fixes the problem. My controller sends exactly the same frame (SENDING: 255;255;3;0;4;2)

015-Aug-19 11:22:48.806905 [DEBUG]  => 09:22:48 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0:
2015-Aug-19 11:22:48.808057 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:48.808084 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:48.808113 [DEBUG]  => 09:22:48 2015/08/19 RECEIVING: 255/255;INTERNAL;0;I_ID_REQUEST;
2015-Aug-19 11:22:48.808276 [DEBUG] Free id found: 2
2015-Aug-19 11:22:48.808354 [DEBUG]  => SENDING: 255;255;3;0;4;2
2015-Aug-19 11:22:48.853276 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:48.853309 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:48.853338 [DEBUG]  => 09:22:48 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;send: 0-0-255-255 s=255,c=3,t=4,pt=0,l=1,st=fail:2
2015-Aug-19 11:22:48.857694 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:48.857715 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:48.857745 [DEBUG]  => 09:22:48 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-0 s=255,c=0,t=17,pt=0,l=5:1.4.2
2015-Aug-19 11:22:48.859906 [TRACE] Use protocol version found in current message
2015-Aug-19 11:22:48.859925 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:48.859952 [DEBUG]  => 09:22:48 2015/08/19 RECEIVING: 2/255;PRESENTATION;0;S_ARDUINO_NODE;1.4.2
2015-Aug-19 11:22:48.859976 [WARNING] PRESENTATION subtype '17' not supported (protocol v1.4)
2015-Aug-19 11:22:48.864316 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:48.864316 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:48.864336 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:48.864363 [DEBUG]  => 09:22:48 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-0 s=255,c=3,t=6,pt=1,l=1:0
2015-Aug-19 11:22:48.864452 [TRACE] protocol found: 
2015-Aug-19 11:22:48.864480 [DEBUG]  => 09:22:48 2015/08/19 RECEIVING: 2/255;INTERNAL;0;I_CONFIG;0
2015-Aug-19 11:22:48.864499 [WARNING] Error: no protocol version found for this message, drop it
2015-Aug-19 11:22:50.814719 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:50.814794 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:50.814827 [DEBUG]  => 09:22:50 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-0 s=255,c=0,t=17,pt=0,l=5:1.4.2
2015-Aug-19 11:22:50.816996 [TRACE] Use protocol version found in current message
2015-Aug-19 11:22:50.817017 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:50.817044 [DEBUG]  => 09:22:50 2015/08/19 RECEIVING: 2/255;PRESENTATION;0;S_ARDUINO_NODE;1.4.2
2015-Aug-19 11:22:50.817067 [WARNING] PRESENTATION subtype '17' not supported (protocol v1.4)
2015-Aug-19 11:22:50.821411 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:50.821432 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:50.821460 [DEBUG]  => 09:22:50 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-0 s=255,c=3,t=6,pt=1,l=1:0
2015-Aug-19 11:22:50.822611 [TRACE] protocol found: 
2015-Aug-19 11:22:50.822640 [DEBUG]  => 09:22:50 2015/08/19 RECEIVING: 2/255;INTERNAL;0;I_CONFIG;0
2015-Aug-19 11:22:50.822660 [WARNING] Error: no protocol version found for this message, drop it
2015-Aug-19 11:22:52.827945 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:52.828028 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:52.828060 [DEBUG]  => 09:22:52 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-0 s=255,c=3,t=11,pt=0,l=18:Temperature Sensor
2015-Aug-19 11:22:52.830376 [TRACE] protocol found: 
2015-Aug-19 11:22:52.830412 [DEBUG]  => 09:22:52 2015/08/19 RECEIVING: 2/255;INTERNAL;0;I_SKETCH_NAME;Temperature Sensor
2015-Aug-19 11:22:52.830433 [WARNING] Error: no protocol version found for this message, drop it
2015-Aug-19 11:22:52.834780 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:52.834802 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:52.834830 [DEBUG]  => 09:22:52 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-0 s=255,c=3,t=12,pt=0,l=3:1.0
2015-Aug-19 11:22:52.837054 [TRACE] protocol found: 
2015-Aug-19 11:22:52.837086 [DEBUG]  => 09:22:52 2015/08/19 RECEIVING: 2/255;INTERNAL;0;I_SKETCH_VERSION;1.0
2015-Aug-19 11:22:52.837115 [WARNING] Error: no protocol version found for this message, drop it
2015-Aug-19 11:22:52.840755 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:52.840783 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:52.840811 [DEBUG]  => 09:22:52 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-0 s=0,c=0,t=6,pt=0,l=0:
2015-Aug-19 11:22:52.841915 [TRACE] protocol found: 
2015-Aug-19 11:22:52.841945 [DEBUG]  => 09:22:52 2015/08/19 RECEIVING: 2/0;PRESENTATION;0;S_TEMP;
2015-Aug-19 11:22:52.841965 [WARNING] Error: no protocol version found for this message, drop it
2015-Aug-19 11:22:53.729763 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:22:53.729837 [TRACE] protocol found: 1.4.2
2015-Aug-19 11:22:53.729869 [DEBUG]  => 09:22:53 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-0 s=0,c=1,t=0,pt=7,l=5:26.9
2015-Aug-19 11:22:53.731027 [TRACE] protocol found: 
2015-Aug-19 11:22:53.731058 [DEBUG]  => 09:22:53 2015/08/19 RECEIVING: 2/0;SET;0;V_TEMP;26.9

While I have it on 1.5

2015-Aug-19 11:17:24.437051 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:17:24.437124 [TRACE] protocol found: 1.5
2015-Aug-19 11:17:24.437157 [DEBUG]  => 09:17:24 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
2015-Aug-19 11:17:24.437250 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:17:24.437269 [TRACE] protocol found: 1.5
2015-Aug-19 11:17:24.437298 [DEBUG]  => 09:17:24 2015/08/19 RECEIVING: 255/255;INTERNAL;0;I_ID_REQUEST;
2015-Aug-19 11:17:24.437464 [DEBUG] Free id found: 2
2015-Aug-19 11:17:24.437540 [DEBUG]  => SENDING: 255;255;3;0;4;2
2015-Aug-19 11:17:26.448202 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:17:26.448284 [TRACE] protocol found: 1.5
2015-Aug-19 11:17:26.448316 [DEBUG]  => 09:17:26 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
2015-Aug-19 11:17:26.449473 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:17:26.449494 [TRACE] protocol found: 1.5
2015-Aug-19 11:17:26.449524 [DEBUG]  => 09:17:26 2015/08/19 RECEIVING: 255/255;INTERNAL;0;I_ID_REQUEST;
2015-Aug-19 11:17:26.449689 [DEBUG] Free id found: 2
2015-Aug-19 11:17:26.449765 [DEBUG]  => SENDING: 255;255;3;0;4;2
2015-Aug-19 11:17:28.455924 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:17:28.456006 [TRACE] protocol found: 1.5
2015-Aug-19 11:17:28.456039 [DEBUG]  => 09:17:28 2015/08/19 RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
2015-Aug-19 11:17:28.457196 [TRACE] Use protocol version of gateway (gateway or broadcast message)
2015-Aug-19 11:17:28.457217 [TRACE] protocol found: 1.5
2015-Aug-19 11:17:28.457245 [DEBUG]  => 09:17:28 2015/08/19 RECEIVING: 255/255;INTERNAL;0;I_ID_REQUEST;
2015-Aug-19 11:17:28.457409 [DEBUG] Free id found: 2
2015-Aug-19 11:17:28.457485 [DEBUG]  => SENDING: 255;255;3;0;4;2

As you can see on sample above, on 1.4.2 the id is requested only once ("Free id found...")and all other mysensors stuff is normal while on 1.5 the sensor always requesting an id.
The code is quite the same between 1.4.X and 1.5 protocol handling and there is absolutely no difference between ID_REQUEST on 1.4.X and 1.5. Both of functions are using the same code to send data to gateway.

In view of those outputs, I don't know how to investigate more on my controller side... but good to know it works on other controller ;)
Maybe somebody has a manual procedure using an external tool and tell me how to test it :p

I just tryed with new gateway and development branch and same result...

I reverted back to 1.4.2 without problem. The sensor sends its ID_REQUEST, my controller sends the reply and startup is complete.
I suppose there is something new in 1.5 that is not correct.

The ack set to 1 was just a test. I tryed first with 0
So no idea of my problem ... :S

@hek said:

How does the gateway log look like when id request comes in and being sent?

It looks like that

0;0;3;0;9;read: 255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;0;3;0;9;send: 0-0-255-255 s=255,c=3,t=8,pt=1,l=1,sg=0,st=bc:0
0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
255;255;3;0;3;
0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
255;255;3;0;3;
0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
255;255;3;0;3;
0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
255;255;3;0;3;
0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
255;255;3;0;3;

After sensor sends its ID_REQUEST command i send (within 2 seconds) this message 255;255;3;0;4;150 but no response from sensor.
I'm not familiar with cutecom, i suppose when i write something in input field and press enter, message is sent properly?

@sundberg84 said:

Did you clear the eeprom before reuploading the scetch?

Yep it's the first thing i did.

By the way, i have no problem if i force the sensor id using gw.begin(NULL, XXX) at startup.
I'm really lost about this issue :S

Same problem too. Sometimes sensors doesn't reconnect to network.
I experimented it mostly of the time with sensors connected to repeater.
I also added a status LED to check if repeater is still running (heartbeat) and it does.
It seems all my sensors are still running (i can check it with my actuator button, if sensor is not connected and i press the button sensor does nothing while if it is connected to repeater it switches relay properly) so i guess my sensors are still connected to repeater but repeater seems not to be connected to gateway.