Has anyone been successful connecting the M2 Data Only LoRaWAN Indoor Gateway to ChirpStack? If so, please let me know and how you did it!
Objective of the current project is to get the location data from the SenseCAP T1000-A LoRaWAN Tracker to TagoIO.
Hi Fernando.
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.
Hi Leo,
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?
It does not look like I can attach images here, so I have shared a google drive link:
https://drive.google.com/drive/folders/1K71XQAMd0mQWu2fEWO9fDUX_bsuo2lkw?usp=sharing
Additionally, if the gateway cannot be connected to ChirpStack, then can I ask about what the purpose of this documentation I have found is:
https://drive.google.com/drive/folders/1F74xdKUheCqcLyZKszG4WbzYlL-tuf96?usp=sharing
Hi there!
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.
Hi Leo,
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!
Just to confirm, can the SenseCAP M2 Multi-Platform LoRaWAN Indoor Gateway be connected to ChirpStack? I have followed the Instructions in the wiki but I don’t seem to be able to correctly configure the required settings. If available, is there an indepth setup that you can share, possibly for people new to ChirpStack?
Additionally, I found a link to a ChirpStack GUI under the Local Network Server mode, what is the purpose of it?
Lastly, can the SenseCAP T1000-A LoRaWAN Tracker for Indoor and Outdoor Positioning be used indepedantly of the gateway, for data visualization?
Thank you for your time!
The SenseCAP M2 Multi-Platform LoRaWAN Indoor Gateway can be connected to ChirpStack. They can connect to our built-in ChirpStack server or to an external ChirpStack server.
Connect to the built-in ChirpStack server, see SenseCAP M2 Multi-Platform Gateway LNS Configuration.(I recommend you to ignore the MQTT related content for now and go ahead and connect the gateway and devices to ChirpStack)
Connect to the external ChirpStack server, see Connecting to ChirpStack.
The ChirpStack GUI link is used to configure gateways and devices for ChirpStack. Just like The Things Network console (if you have used it before).
The T1000-A tracker cannot upload data to a LoRaWAN network server without being connected to a LoRaWAN gateway. So it can’t work independently for data visualisation.
Hi Leo, thank you for your response. I’ll test your suggestions and get back to you!
Hi Leo,
I am currently using the SenseCAP T1000 tracker for motion and shock detection. While I am able to configure the motion and shock thresholds and receive event notifications, I would like to know if it is possible to retrieve the raw acceleration data (X, Y, Z axis values) from the tracker.
Specifically, I am looking to:
Could you please confirm if the T1000 tracker supports this functionality? If so, could you provide guidance on how to configure the tracker or access this data?
Thank you for your assistance.
Hi Leo, Kind reminder on the above query.