Include ioBroker. We support mySensors over MQTT protocol.
ioBroker has over 80 adapters/drivers and all of them developed with Javascript (node.js)

@hek said:

Introducing a wait(50) between each presentation message could resolve the problem.

I do not understand, should ioBorker use wait(50) or Sketch? (I guess sketch, but to be sure)

@hek said:

Ok, it sends 9 presentations in a row....
Where can you see that?
It is really strange I have my answer ready and wait for 2 minutes to send it out. In this time you answer on my previous question and my answers looks silly because the it is old.

I have this one log from him:

0;255;3;0;9;TSP:MSG:READ 2-2-0 s=2,c=1,t=1,pt=2,l=2,sg=0:0
2;1;1;0;0;23.5
0;255;3;0;9;TSP:MSG:READ 2-2-0 s=1,c=1,t=0,pt=7,l=5,sg=0:23.5
1;8;1;0;2;0
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=8,c=1,t=2,pt=1,l=1,sg=0:0
1;7;1;0;39;-12.17
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=7,c=1,t=39,pt=7,l=5,sg=0:-12.17
1;255;3;0;0;75
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=255,c=3,t=0,pt=1,l=1,sg=0:75
1;5;1;0;36;1
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=5,c=1,t=36,pt=2,l=2,sg=0:1
1;2;1;0;1;63.38
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=2,c=1,t=1,pt=7,l=5,sg=0:63.38
1;2;1;0;0;12.87
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=2,c=1,t=0,pt=7,l=5,sg=0:12.87
1;2;1;0;38;12.56
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=2,c=1,t=38,pt=7,l=5,sg=0:12.56
1;2;1;0;39;-43.80
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=2,c=1,t=39,pt=7,l=5,sg=0:-43.80
1;1;1;0;23;17.69
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=1,c=1,t=23,pt=7,l=5,sg=0:17.69
1;255;3;1;0;1475773988
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=255,c=3,t=0,pt=0,l=10,sg=0:1475773988
0;255;3;0;9;TSP:MSG:SEND 0-0-1-1 s=255,c=3,t=0,pt=0,l=10,sg=0,ft=0,st=ok:1475773988
0;255;3;0;9;TSP:MSG:READ 1-1-0 s=255,c=3,t=1,pt=0,l=0,sg=0:
0;255;0;0;18;2.0.0
0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1
0;255;3;0;9;No registration required
0;255;0;0;18;2.0.0
0;255;3;0;14;Gateway startup complete.
0;255;3;0;9;TSM:READY
0;255;3;0;9;TSM:GW MODE
0;255;3;0;9;TSM:RADIO:OK
0;255;3;0;9;TSM:INIT
0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0)

Is the information you required there?

And this one must be a sketch: http://forum.iobroker.net/viewtopic.php?f=12&t=3577&start=20#p36212

Accordingly to http://forum.iobroker.net/viewtopic.php?f=12&t=3577&start=20#p36227 he has 2.0 Serial with
Seeeduino for the gateway (serial)
Seeeduino for the chicken shed
Sensebende for the temperature sensor
Raspberry pi 2 and 3 for the controller

BTW, is it not the good idea to print the version out in log? What is this? 0;255;0;0;18;2.0.0

@hek Hello, I am the developer of ioBroker and adapter of mySensors for ioBroker. One of the user has a Problem with the sketch. And I automatically too. Accordingly to log output:

2;1;1;0;0;23.5
1;8;1;0;2;0
1;7;1;0;39;-12.17
1;255;3;0;0;75
1;5;1;0;36;1
1;2;1;0;1;63.38
1;2;1;0;0;12.87
1;2;1;0;38;12.56
1;2;1;0;39;-43.80
1;1;1;0;23;17.69
1;255;3;1;0;1475773988
0;255;0;0;18;2.0.0
0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1
0;255;3;0;9;No registration required
0;255;0;0;18;2.0.0
0;255;3;0;14;Gateway startup complete.

(from bottom to top) there is no representation messages about datapoints. And I thought, that this information is required to describe the received information. In my driver I send "'0;0;3;0;19;force presentation'" message to receive the representation information jsut after connection esteblishment.
Why the sketch do not send representation info? There is no use on data without to know the name and configuration for that.

@hek I assume, that you need something like that. Ok. I will prepare info.
How can I send it to you?

Include ioBroker. We support mySensors over MQTT protocol.
ioBroker has over 80 adapters/drivers and all of them developed with Javascript (node.js)