Thanks for the tip.
I will try that in the future. But I don't think it was a problem of not receiving on the sensor part. I think it was a problem with not sending on the Serial Gateway part.
But I got it working now!
Got it working, but my solution is not very satisfying.
I swapt the sketches on my 2 arduino's.
Original arduino setup was:
SerialGatway - Arduino pro mini 3.3v (including Decoupling-Capacitor)
Motion Sensor - Arduino Uno (including Decoupling-Capacitor)
Now the sketches are switched and it works.
Eventually I will be working with only Arduino pro mini's but still the original setup should have worked.
I'm trying to create my own controller in Node-Red.
My setup is as followed:
Motion Sensor arduino with standard example sketch <--> SerialGateway arduino with standard example sketch <--> USB <--> Node-Red (installed on Raspberry PI)
My SerialGateway receives the request for a node ID (255;255;3;0;3;)
I then return a serial command: 255;255;3;0;4;1
You can see my Node-Red output below:
For some reason my SerialGateway is not broadcasting my command. It's only repeating the above commands sevral times;
Am i using the correct protocol values or is there something else I should do?
I'm aware of the superiority of 1.4. Because I just started with building my custom controller I will go with the development branch for now. I really like the new protocol so far.
I'm using very basic arduino sketches at the moment. The only thing I'm worried about is my custom controller that I'm building in Node-Red. Hopefully the feature changes will not have to much impact on that part.