-
Notifications
You must be signed in to change notification settings - Fork 311
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 normalized payload in the Console #5758
Comments
Also good to atleast have the wireframes for this early in Q3. |
I've finished designing this feature as part of the general Console UX updates. Planning will follow. |
@kschiffer Do we have wireframes for this? If not, can we work on that with @pierrephz? @mjamescompton for the implementation. |
I was skimming through my files and only found two screendesigns based on an earlier revision of the Console redesign. I will discuss this with @pierrephz so he can pick this up and finalize the UX. |
I think this is a good place to do it and it stays clean. I think having a table like this is too limiting though. I think we should create sections for the high level objects that we have: battery, soil, air, wind, water, etc. |
I have gathered all our Here is the propriety element that I designed:Here is the updated panel with the normalized payload properties in use: |
Summary
Show normalized payload in the Console
References #5752 (review)
Current Situation
The new
normalized_payload
field inApplicationUplink
andApplicationNormalizedUplink
contain a known data schema: JSON Schema and documentation.There is now very basic support for showing
air
andwind
(425b41a), showing values as JSON.The payload code editor shows
normalized_payload{_warnings}
as returned fields, but not as prominently as decoded uplink data.Why do we need this? Who uses it, and when?
I think it would be good UX to show normalized payload if it's available.
Proposed Implementation
Low hanging fruit would be to show the normalized payload nicely in the payload editor. This would need its own code editor. If the normalized payload is present, it might be shown more prominent than decoded payload (but one does not replace the other).
What would be nice in the event view, is to show the values nicely. For example:
Air: 25.4 ℃, wind: 4 bft (NNE)
(if thenormalized_payload
were to contain{"air":{"temperature":25.4},"wind":{"speed":6.1,"direction":15}}
.Cherry on the pie would be to render temperature graphs based on historical data retrieved from the storage integration. We still don't want to be come an IoT platform, so this is a sliding edge, but it would be cool.
Contributing
Code of Conduct
The text was updated successfully, but these errors were encountered: