Hi, for everyone who reads all of this, forget about the last few posts. I don't know why it works even when the Interrups are masked out on the radio, but it works now. The error I had occured because of the config of the OrangePi-Gateway. I removed: --extra-cxxflags="-DMY_RF24_DATARATE=\(RF24_250KBPS\) -DMY_RF24_BASE_RADIO_ID=\(0x00,0xFC,0xE1,0xA8,0xA8\) -DMY_DEBUG_VERBOSE_RF24" and wrote: --extra-cxxflags="-DMY_RF24_DATARATE=\(RF24_250KBPS\) -DMY_DEBUG_VERBOSE_RF24" Now I think I have an working OrangePi-Gateway without signing but with interrupt enabled. If there are new problems I will come back here. The next step for me is to activate signing again and bring the node into homeassistant.

ok, thanks for reminder.

@alowhum thank you

Just one final question... is the approach to MQTT correct or should I stick with simple Ethernet? I was planning on using OpenHab or Home Assistant. Thank You all

Please provide the required documentation for the CERN license. See here if anything is unclear.

@Technovation Welcome to the MySensors forum! This is an awesome first post! Hope to see a lot more in the future!

@rusg323 said in [Solved] Building RPi Gateway - No Support for nRF24 radio on this platform: nfiguration chang actually this is the only way, every configure launch will overwrite previous settings. Thats how configure wokrs. You can do ./configure --help to see all the options

very impressive work. Can´t wait to give it a try. So many things in one project, looks very useful. I think that alone through the intgrations like snips this could become a stand-alone, closed mysensors/mqtt hub, where almost everything is integrated what you need. Can´t wait to hear more of this project.

@mfalkvidd oké, clear! Unfortunate. Guess a couple esp8266 couldn't hurt.

@GertSanders No, you have to update manually...