If your board don't have embedded network communication, or if you don't want to use it in some specific use case, you can use SerialGateDevice library (see Arduino reference for more about Arduino libraries) in conjunction with GateHub started on machine your board is connected to. GateHub scans Serial Ports and - if SerialGateDevice is detected - GateHub opens WebSocket connection with Local Server for it and act as relay, passing messages from Serial Port to WebSocket and vice-versa.

Each Node.js process using Device or Controller library has built-in discovery service that allows it to find Local Server within local network basing on discovery messages broadcasted by Local Server. You can start multiple such processes on one physical machine, however, only one of them will be able to listen on discovery port at time. Therefore, it can take a while for all the processes to join Local Server (next process will wait until previous one releases discovery port). If your system is meant to run permanently it might not be a big problem, but if you want to launch your system periodically and it consists of many components running on one physical machine, it can take significant amount of time before all the components will get online. With GateHub running on such physical machine, all the processes will fetch discovery information from GateHub instead of using their built-in discovery services and won't block each other.

If your system contains several components meant to run on one physical machine, you can use Autostart functionality to start them all together with GateHub. To add components to Autostart list, you just need to modify autostart.js file under GateHub root directory, adding process working directory and start command for each process. Example: