@jocke4u I run 2 RF gateways and it's not a problem. When you 'migrate' a node to a new gateway make sure to run the mysensors clear eeprom sketch first to get rid of the old routing table or you might have issues.
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.
@kimot No, it is an obvious mistake, I am very sorry. Maybe it is becouse the code in master branch is very old, the newest is not yet on github, but the developement branch is quite new. I am going to fix this soon.
@scalz said in HALO : ESP32 multi transport GW/Bridge for Mysensors:
the webapp was great, but I converted it to native crossplatform app for better versatility&perf, so I can use one app for my devices, like Ethernet for HALO etc, or Serial for my other Janus gw dongle, bluetooth..
To be honest, I've not updated anything yet for a few reasons, like very little spare time for a public release + support for such "big" project. (easier to handle local projects).
Sorry, still no eta for the moment..
It is clear that there is not enough time. But this project can become popular. That's what's missing MySensors. ...This void must be filled.
