Admin

@ruben_gr thanks for explaining. Your strategy makes sense, at least to me If you find migration of the entire MySensors library too cumbersome, you could probably make do with just migrating the transport protocol parts.

@ruben_gr the technical reason is that the default mode is that the gateway listens for incoming connections from a controller. Since you've configured your controller to connect to the gateway, the default mode is what you need.

Some controllers accept (expect?) the gateway to connect to the controller instead. That's when my-controller-ip-address is used.

About rs485: I don't know. I have never used rs485. But MySensors expects to talk to other Mysensors nodes, you can't add stuff that doesn't speak the mysensors protocol. Mysensors uses node ID for addressing. https://www.mysensors.org/about/overview might be useful.

@ruben_gr are you still using —my-controller-ip-address in the configure command? In that case remove it, your controller will connect to the gateway.

@ruben_gr because the gateway fails to init the nrf24 radio.

Add --my-transport=none to the configure command and go back to the make step if you don't want to use the default setting of nrf24.

@ruben_gr yes, in the form of rs485.

Maybe the info in https://forum.mysensors.org/topic/5668/mysensors-gateway-on-orangepi-zero-opi can help. I have no idea how the spidev stuff works, but I imagine it can be different on beagle compared to raspberry.

@ruben_gr since all the errors mention an ip address, my guess is that --my-controller-ip-address=<IP> needs to be given an ip address. Try removing :8123 and see if the compilation works. If it does, the error is with the configuration and not with the code or the beaglebone.

@garubi yes, you got it right

We were all noobs at some point

@garubi they’ll need common ground to be able to communicate.

Connect gnd on the Arduino to gnd on the nrf24 (in addition to the existing connections).

@garubi is gnd on the nrf24 connected to gnd on the Arduino?