A little more use of âresponsive designâ would also be welcome.
Only 40% of my browser width is used (when I maximize it) for showing traffic which is a lot of unused screen estate.
Using more width would also allow to add RSSI and SNR to the first line so they can be read at a glance without having to unfold the contents first.
When using an extension for that, one could also use some Greasemonkey script to find the elements, without TTN making any changes. But then oneâd still need to configure the list of DevAddrâs oneâs interested in. (Assuming thatâs what the âaha momentâ was about?)
As an aside: note that the search box on top already allows for filtering a single DevAddr.
Then youâre using OTAA, which is good but indeed the address will change.
I doubt TTN will do that, as the gateway does not know anything about that. So far, the gatewayâs Traffic page merely shows the unencrypted parts of the LoRaWAN packet, and gateway meta data, just like a gatewayâs log could show you. (Plus debug info in the traceâŚ)