I’ve buyed a RAK7249 gateway. It has OpenWRT and it seems to work fine, but I’ve found an issue when trying to conect it to our Loraserver instance.
The stat package is quite different so I get invalid stats:
Looking for MQTT packets, I can see the difference… this gateway uses JSON to send the packages:
AFAIK you can build a software stack for the gateway from source, if you want to badly enough. I’m not sure if they released instructions for that fully integrated model, but they have for earlier MT7628 based kits, and the concentrator card doesn’t really change apart from their newer ones having the silly design mistake requiring that you use a low SPI clock speed. You can probably also replace part of the stack without rebuilding everything - ie, if they have a distinct gateway bridge component, just replace that and not touch the packet forwarder. Their configuration interface might be custom, but you probably don’t have to continue using it for everything.
That said it’s kind of too bad if LoRaServer introduced a new protocol version and promptly removed the old one, rather than supporting it for a few generations as a legacy option, replying in kind to gateways using it.
In theory you could probably whip up a translator fairly quickly, though for cleanliness you might want a distinct MQTT broker for the untranslated vs. translated version, and it would add some latency (though not that much if co-located with the rest of the server stack). Latency is not a gradual thing - you either get the reply back to the gateway in time to make the downlink window, or you don’t - though edge cases could have statistical failure rates.
So far so good, I installed this release and I can confirmed that it is working with LORA Gateway MQTT bridge option loraserver 3.x.
On the LORA server side:
I’m getting into the LIVE LORAWAN FRAMES an error saying “ns out of range [0, 1000000000)” at the botton of the screen with the flashing message “not connected websocket API”, after 2 or 3 secs those messages disappear…???
Can one of you can validate it ?
Error messages from lora-app-server:
level=error msg=“parse timestamp error” dev_eui=70b3d5499abd3c72
error=“timestamp: seconds:1568845150 nanos:-783383680 : nanos not in range [0, 1e9)”