New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show latest uplink message and up- & downlink fcount #2167
Comments
I'm not sure if this is the same, but quickly checking the NS's @rvolosatovs are we keeping a "last seen" timestamp in NS? |
No, but it can be derived from |
That's what I did, but I figured that for the complete functionality, we'd need to hook into the event stream to keep the numbers updated in real time. |
Before I go ahead and implement it this way, @htdvisser do you think that approach is thorough enough? The uplink downlink events do not contain the current frame count, so I'd have to increment them based on the initial value that I got from the session prop inside the end device. |
That’s not the way to go I’m afraid. Are we not sending the frame counters along? That would be the real issue then. |
Unfortunately, it's not as simple as it seems at first sight.
All of this is handled by NS (and 2. in part by AS), and I certainly do not think console shall do the same. I think the way forward is to add events for (1.) - |
Blocked until we arrive to a conclusion on NS events to drive this and that is implemented in NS. |
Ok I get that this is indeed not feasible then at the moment. What about the |
Yes, |
For downlinks we currently do not have similar functionality, but that's also not the focus of this issue, let's start with just the uplink FCnt and then add downlinks at a later stage(Note, that depending on LoRaWAN version we may actually have 2 distinct downlink frame counters - one for NS and one for AS, so it's much less trivial that uplink frame counter as well.) |
It would definitely be nice to show that information globally for the application, but doing so would mean that the console needs to probe all end devices associated with the application one after the other, to be able to show the initial last seen status. I don't think this is viable when we have to assume applications with potentially hundreds or thousands of end devices. Two things I could think of:
@htdvisser @rvolosatovs Do I maybe overlook something? Alternatively, can you think of any way of aggregating that data and making it available through an API endpoint? |
https://github.com/TheThingsNetwork/lorawan-stack/blob/develop/api/applicationserver.proto#L56-L69 |
Closed via #2585 |
MOVED ISSUE FROM https://github.com/TheThingsIndustries/lorawan-stack/issues/1971 original from @laurensslats
Summary
I love this feature of the V2 console, currently missing in V3.
...
Why do we need this?
Easy debugging as it gives insights on whether the device is operational and data is picked up by the network.
...
What is already there? What do you see now?
...
What is missing? What do you want to see?
What about something like this? Maybe with some magic UI sauce from Kevin
...
Environment
Chrome
...
How do you propose to implement this?
Add some fields in the console
...
Can you do this yourself and submit a Pull Request?
I need pure brainpower from @kschiffer
...
The text was updated successfully, but these errors were encountered: