Skip to content
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

Open
3 of 4 tasks
johanstokking opened this issue Sep 1, 2022 · 2 comments
Open
3 of 4 tasks

Show normalized payload in the Console #5758

johanstokking opened this issue Sep 1, 2022 · 2 comments
Assignees
Labels
c/console This is related to the Console in progress We're working on it needs/ux This needs UX design / approval
Milestone

Comments

@johanstokking
Copy link
Member

johanstokking commented Sep 1, 2022

Summary

Show normalized payload in the Console

References #5752 (review)

Current Situation

The new normalized_payload field in ApplicationUplink and ApplicationNormalizedUplink contain a known data schema: JSON Schema and documentation.

There is now very basic support for showing air and wind (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 the normalized_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

  • I can help by doing more research.
  • I can help by implementing the feature after the proposal above is approved.
  • I can help by testing the feature before it's released.

Code of Conduct

@johanstokking johanstokking added the needs/triage We still need to triage this label Sep 1, 2022
@NicolasMrad NicolasMrad added c/console This is related to the Console needs/ux This needs UX design / approval labels Sep 13, 2022
@NicolasMrad NicolasMrad removed the needs/triage We still need to triage this label Sep 13, 2022
@NicolasMrad NicolasMrad added this to the v3.22.2 milestone Sep 13, 2022
@NicolasMrad NicolasMrad modified the milestones: v3.22.2, 2022 Q4 Oct 25, 2022
@NicolasMrad NicolasMrad modified the milestones: 2022 Q4, 2023 Q1 Jan 2, 2023
@NicolasMrad NicolasMrad modified the milestones: 2023 Q1, 2023 Q2 Apr 12, 2023
@adriansmares adriansmares added the needs/triage We still need to triage this label May 23, 2023
@NicolasMrad NicolasMrad removed the needs/triage We still need to triage this label Jun 27, 2023
@KrishnaIyer KrishnaIyer modified the milestones: 2023 Q2, Q3 2023 Jul 4, 2023
@KrishnaIyer
Copy link
Member

Also good to atleast have the wireframes for this early in Q3.

@KrishnaIyer KrishnaIyer modified the milestones: Q3 2023, v3.27.0 Jul 4, 2023
@johanstokking johanstokking modified the milestones: v3.27.0, v3.27.1 Jul 19, 2023
@kschiffer kschiffer added the in progress We're working on it label Aug 16, 2023
@KrishnaIyer KrishnaIyer removed this from the v3.27.1 milestone Aug 24, 2023
@kschiffer
Copy link
Member

I've finished designing this feature as part of the general Console UX updates. Planning will follow.

@KrishnaIyer KrishnaIyer added this to the pipeline milestone Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c/console This is related to the Console in progress We're working on it needs/ux This needs UX design / approval
Projects
None yet
Development

No branches or pull requests

5 participants