Iām working on live data tool to help with this - code named FireHose (as in, try drinking from one).
Iāll be needing some testers shortly, however they will have to be able read instructions and deal with a grumpy sarcastic old developer.
Iām working on live data tool to help with this - code named FireHose (as in, try drinking from one).
Iāll be needing some testers shortly, however they will have to be able read instructions and deal with a grumpy sarcastic old developer.
Unlike the current tester
But he does cope well with the grumpy sarcastic old developer!
Birds of a feather?
Hey everyone!
Note that filtering out verbose events by default is a feature coming up in the next release which will be deployed shortly thereafter. It is a first step towards improving the usability of the event views in the Console (as in taming the firehose ).
See also:
Cool - yourās is Lego Technic - mine is very much Lego Duplo.
@kschiffer, assuming you are at the heart of the Matrix, can you explain the correlation ids please - what are they, how might we use them and more importantly, particularly for mobile apps, can we turn them off?
Cool - yourās is Lego Technic - mine is very much Lego Duplo.
Not sure if that is good or bad. You mean that you would like to have even less data displayed (even more data filtered out)?
Correlation IDs are, as the name suggests, IDs that allow you to link an event to other event based on a specific topic. E.g. for gateways, youāll see a correlation ID for the connection, allowing you to identify all gateway events that are related to this particular gateway connection. Another topic would be e.g. an uplink. You will see that all gateway events relating to the same uplink will share the same correlation ID starting with gs:uplink:
.
In the future we will use these IDs in the Console to highlight related events.
Iām not exactly sure what you mean by āturning them offā. If you mean to make the event stream omit the correlation IDs (or any other event property), then yes, something like this is in consideration.
Both - I like yours for the detail but when Iām running round the garden pouring water on to sensors, Iād rather have a really simple display that just shows me that an uplink was triggered which means the alarm was triggered. Iāve got something that replicates the v2 traffic view without the expanding detail working, just needs a bit more tidy up before beta-testing.
Plus mobile needs the bare minimum unless you have an A2 side iPad Air.
But when it gets gritty, return to āThe Sourceā - the official console - what would be considered āThe Truthā.
Iād not worry about the many variants of live data that people could aspire to - the APIās are there for people to roll their own and it means the wife is happy because Iām fully occupied.
Understand the correlation idās now - very good - but mostly they are wasted bytes for the average console view - if I run out of things to do I could get some API feeds running and have different screens linking the entries via the correlation-ids - probably need to be a glass freestanding monitor with gesture control so I can swipe widgets around.
I see. Yeah indeed youāre always free to come up with your own interface that suits your specific needs (which is part of the power of TTS). Obviously though in the Console we try to come up with a design that suits as many needs as possible. As is known, weāre not quite there yet, but improvements will come in steadily now.
Btw, regarding mobile, the TTS Console is fully responsive and also the event views are optimized for mobile screensizes (obviously with some limitations). We will flesh this out further with the ability to hide columns as well, but it can already be used pretty smoothly (imho).
Please donāt try - @kersing or @Jeff-UK tell him - itās not possible.
I think all we need short term is a switch to only show join, uplink & downlinks.
Yes, aware itās all responsive - but again, use cases vary - try horizontal sleet with wind chill at -15ā - fingers too cold to swipe etc etc.
Iām very much aware of the trade-off. Still what I mean is a sane approximation that serves the most common use cases without sacrificing usability. Any choices there need to be made with careful consideration. Weāre not planing to bloat event streams with millions of options just to cover every last use case.
This is coming up.
That is the kind of āevery last use caseā use case I was thinking of .
Ok guys all sounds good but in last case please dont ask/expect me to be the tester (though British summer will likely be fitting environmental test! )
Standard Operational Procedure for flying gliders in the Peak District in winter - we log flights on computer.
Once you get up in the air, the flying greenhouse / canopy keeps you warm along with electric socks.
Hello, Iām sending data to my GW, I can see the activity counter change in TTN, but the LIVE DATA never shows anything?
As per many other posts asking similar, this is not updated in absolute real time due to the constraints / load on the servers ā¦
Thanks Nick
The thing is that I never see any ālive dataā. I understand that it canāt be realtime, just strange that nothing ever shows.
Erm, apologies, youād circled the thing most people ask about - if you mean you never get an entries in the log underneath, then there is something preventing the device from matching EUIās etc at the Network Server level so it canāt pass it on to the application console.
How are you joining, what is the device, the stack, itās version and can you check the EUIās / keys.
Hi Nick, below is a summary on the configuration :
RAK7268
Configuration Mode : Basics Station
Gateway EUI : AC1F09FFFE0606D0
Server setup : LNS Server wss://eu1.cloud.thethings.network
Firmware : WisGateOS 1.3.4
RAK3172
Firmware : 3.2.0-p2_22q1_final.87
Join mode : OTAA
Class A
DEVEUI=70B3D57ED00553C8
APPEUI=0000000000000000
APPKEY=D0ā¦74
AppEUI = 0000000000000000
DevEUI = 70B3D57ED00553C8
AppKey = D0ā¦74
LoRaWAN version : LoRaWAN Specification 1.0.3
I join network by sending AT command AT+JOIN=1:0:10:8, then after joined ack recevied I send test data AT+SEND=1:0167FFD7
Hi Nick, I see live data now showing in the console
Did you perhaps change anything? Awesome to see the data!
Your device and application keyās you need to be carful with, the gateway keyās are fine, that is public.
Did you perhaps change anything?
Nope, Iām just another volunteer forum person like everyone else with no access to the servers.