Sensor is not added

[DaTTcz]

Hello, I built a Sensor (mysensors v2.0 with NRF24L01 on arduino). In the log I see that it is communicating with SerialGateway. But nothing is not automatically added... Do I have to add myself sensor? What am I doing wrong ? I see this in the log:

Nov 03, 2016 19:09:30 Notice Node GW01 0:N01 Received Interní[Inclusion mode] 0
Nov 03, 2016 19:09:05 Notice Node GW01 0:N01 Received Interní [Log message] TSP:MSG:READ 10-10-0 s=3,c=1,t=16,pt=2,l=2,sg=0:1
Nov 03, 2016 19:09:04 Notice Node GW01 0:N01 Received Interní [Log message] TSP:MSG:READ 10-10-0 s=3,c=1,t=16,pt=2,l=2,sg=0:0
Nov 03, 2016 19:08:52 Notice Node GW01 0:N01 Received Interní [Log message] TSP:MSG:READ 10-10-0 s=4,c=1,t=16,pt=2,l=2,sg=0:1
Nov 03, 2016 19:08:51 Notice Node GW01 0:N01 Received Interní [Log message] TSP:MSG:READ 10-10-0 s=4,c=1,t=16,pt=2,l=2,sg=0:0
Nov 03, 2016 19:08:49 Notice Node GW01 0:N01 Received Interní [Log message] TSP:SANCHK:OK
Nov 03, 2016 19:08:46 Notice Node GW01 0:N01 Received Interní [Log message] TSP:MSG:READ 10-10-0 s=255,c=3,t=11,pt=0,l=13,sg=0:Binary Sensor
Nov 03, 2016 19:08:44 Notice Node GW01 0:N01 Received Interní [Log message] TSP:MSG:READ 10-10-0 s=255,c=3,t=24,pt=1,l=1,sg=0:1
Nov 03, 2016 19:08:42 Notice Node GW01 0:N01 Received Interní [Log message] TSP:MSG:SEND 0-0-10-10 s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=ok:0
Nov 03, 2016 19:08:42 Notice Node GW01 0:N01 Received Interní [Log message] TSP:MSG:READ 10-10-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
Nov 03, 2016 19:08:30 Notice Node GW01 0:N01 Received Interní [Inclusion mode] 1

[jkandasa]

@DaTTcz This log doesn't looks like MyController log. From where did you get this log? You have to add your serial gateway on MyControler.

[DaTTcz]

@jkandasa This log is from tab - status/resources logs. I'm sorry, I do not know why I did not look into Mycontroller server log. Here I found ERROR. My serial port (Arduino Nano NRF24L01) had an automatic driver to pi4j. So I changed it to jSerialComm and now everything works as it should.

[jkandasa]

@DaTTcz Thanks to narrow down the issue. I guess we have serious issue with pi4j driver. I will check it.