@spanners I told you it would make a big difference :-) Thanks for reporting back!

@kduino I think you need to define MY_RS485_SWSERIAL as well

@kduino the debug output will probably provide useful information.

Hi Kisse66, thank you very much for this advice. Most of the forum writers are pointing on the terminating resistors, but in my experience they are not the key. I put two 680R from B to GND and A to 5V and the reliability I experienced has improved tremendously! Thank you for the hint. Another question I have: The gateway is receiving the messages now but there is no ACK. How can I ask for an ack for security relevant messages? Thank you By kduino

Hi PJR, now it is working with this code in the MyTransportRS485 without any changes on MySensors.h: #if defined(MY_RS485_SWSERIAL) SoftwareSerial& _dev = MY_RS485_SWSERIAL; #elif defined(__linux__) SerialPort _dev = SerialPort(MY_RS485_HWSERIAL); #elif defined(MY_RS485_HWSERIAL) HardwareSerial& _dev = MY_RS485_HWSERIAL; #else AltSoftSerial _dev; #endif As far as I can interpret the peace of code, the #include "hal/transport/MyTransportRS485.cpp" is active as soon as the MY_RS485 layer is defined. This is a great step, I can use all my nodes from now on! Thank you very much for your support! By Kduino

By the way I have done this with the icsc lib from majenko, if anyone is interested. The rs485 input is directly sent via udp and v v. Additionally I extended the icsc with an ack funtionality to keep track on lost messages on the bus. It runs currently with 57600 baud.