Thanks @reinder !
Sorry dont know 
But will try set it up in the next days. Is there any log i could attach / send to you to help with it?
Thanks, love to hear the results.
First thing I like to know is: does the communication work.
If it does, could you try to control locomotives and accessories.
On the Märklin CAN tab of the interface settings is a log all communication setting, Please enable that.
When you use a development build it has a create diagnostic report function in the help menu. That will collect the world info, system info and log etc. That will help me if something doesn’t work as it should.
Many thanks in advance for making time to test it.
Greetings,
Reinder
@Zasig I just read the CC-Schitte 2.x interface protocol description, it uses the same format as what is used for the CS2/3+ on the network and … I also made a serial port version back then, so I think communication should work.
I think these settings will work:
If that works I’ll add CC-Schnitte to the type list and hide the fixed baudrate and flow control settings, that will make it easier to setup 
Greetings,
Reinder
A post was merged into an existing topic: Märklin CAN CS2/3/3+/Gleisbox hardware support
In theory there is possible to implement Homie specification which allow to operate with different types of devices and vehicles without any hard specification for jsons or xml files. concept “value per topic” allow to exchange data between clients extremly fast. of course it there is possible to add alternatives for compatibilty layers with jmri and railcom. But exactly Homie is very friendly with microcontrollers such like esp32 and allow to implement communication ower LAN/WiFi very easily
Hi @TamiasSibiricus,
Welcome to the forum! 
I didn’t know Homie yet, I think this could be useful in both directions. Traintastic could read stuff, but also publish stuff. I’ve a few other things I need to develop first, but I put this on the list, thanks.
Greetings,
Reinder
Homie specification has been designed for IoT devices in mind. In my opinion scaled models are completely fit IoT paradigm and which is more important messaging with devices could bidirectional(as you mentioned previously). Device can publish current state, publish telemetry such like voltage, also topic could contain persistent value. it is helpful while disconnects happens for example. “Last will” topic allow to monitoring which device is connected to server. also you do not need to write own mqtt server. there is a lot of easy to configure and run servers such like mosquitto available. so there is a lot of benefits for everyone who want to make own DIY controllers over TCP/IP protocol. Unfortunately i’m not C++ developer and can’t help you to implement Homie over MQTT but ready to help with tests if implementation happened.