Adding Your First Device and Gateway in The Things Stack
HTML-код
- Опубликовано: 5 фев 2025
- Try The Things Stack before subscribing: accounts.theth...
Start building LoRaWAN solutions with The Things Network: www.thethingsn...
Scale with The Things Industries: www.thethingsi...
Join The Things Conference: www.thethingsn...
Thanks for watching!
Hi there how do I know the EUI for a third party gateway?
What I didn't see anywhere so far is how I can get the data from my device.
That smart plug pushes them to TTN, can my application poll them from TTN or are they pushed to my connected application?
For a full end to end walk through please check out this video: ruclips.net/video/HSh5QAd8jvM/видео.html
@@TheThingsIndustries Yes, thank you! That is very helpful.
I followed the steps, but at the live data it says: Console:stream reconneceted The stream connection has been re-established. But I didn't achive the join request. What can I do? what I missed?
I have the LoraWan MKR WON 1310, its not in the LoraWan device repository. How do I find it there?
Arduino has to add it! The repository is here, with instructions -> github.com/TheThingsNetwork/lorawan-devices/tree/master
So say I have a device that I'm programming myself. I'm using a public gateway, it's not getting a response, I'm at a loss.
try one you own first. get familiar. easier to troubleshoot when you know what is going on before trying to just cross your fingers plug it in and wish. ya know? that's what half the people do with this stuff. First, check gateway map. If not one close enough, or even if there is one, you may not be able to use it. It's a mesh network - so it's ideal to be in range of multiple gateways. sounds like you need to be the change you wish to see in the world and drop $100 on one for your neighborhood and then tell your friends.
@@bjmurrey Hi, It's been 3 months. I am and have been aware of the limitations you're telling me. This was my bachelor's graduation project which in the mean time has been completed. After the fact, what you're telling me, definetely was not the issue.
@@JustRosa14 so, definitely for a fact, tell us what was. Instead of telling us nothing .
@@bjmurrey didn't think you'd be interested but here I go then.
I was writing my own software for different purposes including a sensor, then analyzing data and sending that, hence the custom software since the analytics were quite complex.
I used a public available library with some comments that it worked for them so decided to give it a go. I had a hackRF to validate that something was indeed being sent. With no way of knowing exactly what I had sent over I had to assume the library was working (since it had worked for other people, too).
When it didn't I dove even more into the datasheet checking every single register with the library and found a few faults, still nothing.
Decided to purchase another device to rule out hardware defects. Still nothing. Used the secondary device to receive the message sent to ensure the join request was sent correctly, which it was. The format was also correct after having validated every piece of the LoRaWAN specification. I posted on the things forum and got condescending people attacking me for modifying the library because they "like to keep THEIR network nice and stable" which seemed absurd to me since I'm in a different continent.
In the end I'm not quite sure why it didn't work but I'm left to speculate there was something not quite right with the chip settings. Something I wasn't willing to figure out any longer.
Since I now had two chips at hand, based on ESP32's I decided to use P2P LoRa communication and then use Wi-Fi for eventually sending it to the database that I needed to send to in the first place.
I have now passed the project at school and I'm happy for it. I'm still at a loss and have looked with teachers and colleagues what could be the issue but none were found unfortunately.
Oh and yes - I have used the stock firmware the device came with which worked perfectly. Considering it only joined the network and sent arbitrary numbers I couldn't use it directly. I contacted the manufacturer for the firmware and they gave me the runaround and then a manual containing all and only dead links. I therefore wasn't able - given the short timeframe - to reverse engineer the original firmware it came with unfortunately.