We regret to inform you that the built-in firmware of the M2 Data Only LoRaWAN Indoor Gateway only supports Helium. So at the moment you can’t configure your gateway to connect to the ChirpStack server.
However, we plan to release open source firmware for the M2 Gateway in the next quarter that may solve your problem.
If there’s any progress, I’ll let you know as soon as possible.
Thank you for your reply and I would very much appreicate any progress on that front.
Additionally, in the challenge of getting the data from the Tracker onto a local network server and then to a data visualizer, I have been investigating the MQTT capabilties of the Gateway, by establishing a broker on Node-red and sending the data to that broker, but I keep getting the attached error. Could you provide any assistance on that front?
Just wanted to let you know that our M2 Data Only Gateway doesn’t support local network server. From the image you sent, it looks like your gateway can be configured with a local network server. I’m not quite sure if your gateway is an M2 Data Only Gateway or if you’ve flashed the open source firmware I mentioned earlier.
But now you can go ahead and configure your gateway like that documentation you found, which shouldn’t make a difference.
Many apologies, just noted that the gateway is a SenseCAP M2 Multi-Platform LoRaWAN Indoor Gateway, and not Data only. In this case, would your answers remain the same?
Yeah for sure. We have a number of tutorials on the M2 Multi-Platform Gateway. You can check them on our wiki SenseCAP Gateway.
For the problem you encountered with the local web server MQTT data forwarding error to Node-red, I will do some tests, if there is a solution or suggestion will continue to communicate with you!