That is the price we pay for behaviour of TTN/TTI.
↧
TTN Console not working properly all the time [console] [gateway] [not connected] [no traffic] [application] [no data]
↧
Heltec CubeCell - part 2
Hello, I was missing telling you that the Gateway UG87 is less than 2m away from the CubeCell HTCC AB-01 module. I also did the test with the other two CubeCell HTCC AB-01 modules that I have but still can’t get the connection, so it’s not a problem of a specific module, it must be wrong module or gateway configuration maybe.
↧
↧
Having trouble sending downlink with HTTP Integration
Thanks for the answer!
I used curl with -i and -v and used the url that came with my uplink. It still doesn’t work and I get a http 400 Bad Request error. I also tried using -H "Content-Type: application/json" because to my understanding the data is encoded in json?
My output log in terminal is as follows:
HTTP/1.1 400 Bad Request
Server: nginx/1.13.7
Date: Fri, 03 Jul 2020 15:21:13 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 0
Connection: keep-alive
My curl command:
curl.exe -i -v -X POST -d ‘{“dev_id”:“td00”, “port”:1, “payload_raw”:“AQIDBA==”}’ https://integrations.thethingsnetwork.org/ttn-eu/api/v2/down/idt00/request_bin_test?key=(APP ACCES KEY)
I also tried it without any “payload_raw” and it didn’t work. Could you also elaborate your last point about not sending text for my payload?
Thanks!
↧
Having trouble sending downlink with HTTP Integration
↧
Graphing data
As far as I know, the only system that support “natively” TTN is Thingsboard PE (https://thingsboard.io/docs/user-guide/integrations/ttn/).
↧
↧
868Mhz -138 km! it is possible!
Apprently because of the way the bands are allocated in the UK, the frequency of transmissions were engineered so that they were spread across the TTN channels so that in effect you could extend the legal limit on duty cycle from 1% to circa 3%.
↧
TTN Console stopped showing downlinks for TTIG
The Magic did not last for long, downlinks are down again, restarts do not help this time either.
I use OTAA / frame counter is disabled. Empty message comes from ESP32/LMIC (LMIC_setLinkCheckMode(0); LMIC_disableTracking(); LMIC_setAdrMode(1)) I guess, that’s by default then, right after ‘confirmed ack’. ACK in my screenshot, was just example of successful / confirmed downlink, with my gateway id and superb RSSI. I’m clueless, what to do now. Have to get rid of that TTIG. and get gateway with options to check logs and change configuration.
↧
TTN Console stopped showing downlinks for TTIG
Aside:
(More details in that post.)
For OTAA, disabling frame counters is not needed. (But won’t cause the problems you’re seeing either.)
Beware: to avoid crosstalk, don’t be too close to the gateway!
↧
TTN Console stopped showing downlinks for TTIG
thank you, I’ll try out that UART port.
yes, devices should be at least 4x Lambda apart. in my case distance to the station is about 180m.
↧
↧
TTN Console stopped showing downlinks for TTIG
Also, ttnctl gateway status <gateway id> may show some details. (That status is not listed on https://www.thethingsnetwork.org/docs/network/cli/)
↧
868Mhz -138 km! it is possible!
Where do you get 3% from? I thought it aggregated to 2%.
↧
Heltec CubeCell - part 2
I don’t use ABP much but I’m trying to work out why you have three different ones - sketch, serial monitor and TTN.
Have you tried OTAA? (just re-check your app key if you change back to OTAA)
Can you also show us your radio channels settings in the gateway please
↧
Graphing data
Well that’s another 2 hours lost forever - spent it trying to get Influx DB working but it goes down one rabbit hole after another with endless plug ins and what not with almost no documentation nor ever any sight of an obvious path. Can it really be this hard to draw a simple graph?..asking myself really…Is the Grafana mySQL plugin a reasonable way to resolve this perhaps?
↧
↧
Heltec CubeCell - part 2
Hi, I did the test with OTAA but still can’t get it.
She means “I’m trying to work out why you have three different ones - sketch, serial monitor and TTN”.
I attach the requested screenshots. Thank you.
↧
My application's downlink is always queued for next uplink
Hi, doesn’t the MQTT Data API run from the same Azure hosted VMs in Ireland just like the HTTP end-point? I am just trying to wrap my head around how MQTT Data API could produce a better latency compared to HTTP calls? Thanks
↧
Heltec CubeCell - part 2
OK, looks like you are using sub band 1 - you can see your TX frequencies are below where your first gateway channel starts.
You need sub band 2 to be set by your channel mask in your sketch
/*LoraWan channelsmask, default channels 0-7 - 0xFF00 sets to sub band 2 */
uint16_t userChannelsMask[6]={ 0xFF00, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000};↧
868Mhz -138 km! it is possible!
Your right, 2% was the stated figure, however it would have been possible on the same basis to exceed 2% a bit since there are other TTN channels that fall into a faily wide 0.1% duty cycle band.
↧
↧
My application's downlink is always queued for next uplink
A mqtt connection is persistent. For a https request, there must first be the three-way TCP handshake, then the TLS handshake, before the request can be sent.
Since mqtt performs the tcp and tls handshakes once (when establishing the connection), the connection is available for sending data immediately when data comes in from the device.
Cloudflare has a good description:
https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/
↧
Graphing data
Hi @Qmick, Ubidots is very good for fast, easy and simple graphing, etc. It’s not free but there are free trial periods. The TTN integration works well.
https://www.ubidots.com/
↧
Using community gateways for a commercial product
I’m suffering a failure of imagination regarding how this community and business thing works.
If sessions are between back-end servers and nodes, and gateways will pick up any packet at least for analysis to see if it needs to pass it on to the server, isn’t a DDoS trivial? Even the fair use policy could only be implemented by the servers and I assume gateways can’t selectively listen for nodes because they don’t know who’s talking until they’ve received and examined the message.
It sounds like a risk setting up a network of commercial gateways that can easily be flooded even if they’re not forwarding the uplinks to a server. I assume LoRaWAN is pretty rare still so this isn’t an immediate problem but I can’t wrap my head around how it’s supposed to work in future.
And what is the impact of people breaking the rules using these RF bands? Do other technologies suffer?
↧