@electrik Thanks, I think I can do the same with the MQTT integration (not MySensors MQTT) OSD

@mfalkvidd thank you very much for your quick answer! I'll look into that.

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.

@scalz in the second test i used that getting started code to test the radio modules with a library other than mysensors. and they worked. (That code is not mine, i suppose it use the maniacbug library). So i did investigate to find the differences between mysensors and that library. Only after replacing, in mysensors, the enablefeatures with that code, i got the communication gw-node.