Oh, so you want to distribute a dashboard to a few devices :) What a marvelous idea! So, let's play with it, I'm already enjoying this!
I'd say your key data structure is a "Car". It has a few "sensors", a "PIN", and a list of connected "display devices".
If it has devices (phones) connected, it will, in order of priority, send each of them just one specific type of sensor output. It will also tell that device which output it is.
Example: no phones - no output. Then a single phone connects to the server, and gives this car PIN. (Could be a password, token, QR code, whatever, I'm simplifying here).
When the server sees this PIN, it starts sending to this device the most important output (engine/coolant temperature, let's say). And if you're using something like websockets, or server-sent events, or push or by simple long-polling, it updates this data frequently or in real time, depending on your sensor inputs.
Then the second phone connects, with the same PIN. The server sees the second device, it sends it the _second_ type of sensor output, and starts pushing data - in our case, speedometer.
And so on - as new devices connect, they are assigned a different sensor output and they start showing it.
Devices, ideally, should know how to display all of the outputs, but only show the selected one, the one they receive (because you can't control the order of devices connecting). Alternatively, devices can ask for just specific sensor (e.g. RPM or signal lights) and the server will still keep track of which output to show to which device. You can connect more then 5 phones, and server tells the extra ones to be on "stand-by" - if one of the busy phones disconnects (e.g. battery empty), server tells one of the stand-by ones to chime in.
I mean, you can go way less than that, for a basic functionality, or much more complex, depending on what you need.
But yes, you can definitely do it and node could be the best tool for the job.