TELEMETRY VALIDATOR SHOWING MISSING POINTS FOR POINTS PRESENT ON CLOUD

Question

TELEMETRY VALIDATOR SHOWING MISSING POINTS FOR POINTS PRESENT ON CLOUD

darshanjain12 opened this issue 2 years ago · 8 comments

IMPORTANT
DO NOT INCLUDE ANY PROJECT-SPECIFIC INFORMATION IN THIS TICKET!
ANY PROJECT-SPECIFIC CONTEXT (E.G. BUILDING CONFIG INPUTS) SHOULD BE
EMAILED DIRECTLY TO: digitalbuildings-support@googlegroups.com

PLEASE REFERENCE THIS ISSUE LINK IN YOUR EMAIL TO THAT GROUP

Describe the bug
The telemetry validator is showing missing points for the points actually present.

To Reproduce
Steps to reproduce the behavior:

Run the command: python3 toolkit.py -i filename -v -d folderpath -s subscription
Check the telemetry validation report
Scroll down to the telemetryMessageErrors inside that look in missing points.

Expected behavior
All expected points should be validated as all points present in UDMI.

Screenshots

Additional context
We have set up our site model as per UDMI standard

Answer 1 · 2023-05-18T04:37:15.000Z

Hello @darshanjain12,

Thank you for all the information :).
It appears that three of the five points in the payload have a name mismatch with the building config used.
That doesn't explain why why the remaining 2 points were not picked up.

Could you please provide the full telemetry report json block containing the snippet in the middle image and its entity block in the building config?

Best,
shane

Answer 2 · 2023-05-18T05:13:24.000Z

Hi Please find the attached the full telemetry validation report.
I hope this will help in finding the root cause and solve it.

2023_05_12T12_42_39Z_telemetry_validation_report.zip

Answer 3 · 2023-05-19T22:51:31.000Z

Hi @darshanjain12

Have you tried running the validator again recently? I can't seem to reproduce the error. Our source code for the validator appears to be correct so I don't think this is a bug in our application.

Answer 4 · 2023-05-20T05:17:51.000Z

Hi @trav3711 i tried running the validator again but i am getting the same issue. Please suggest what we can do to get clean reports.

Answer 5 · 2023-05-22T16:28:20.000Z

@darshanjain12 one thing is a lot of fields for the LGRP types in your building config don't seem to have units. For fields that have no units, the proper notation is no-units: no_units

should look something like:

counter:
      present_value: "counter.present_value"
      units:
        no-units: "no_units"

Answer 6 · 2023-05-25T06:42:00.000Z

Hi @trav371

@darshanjain12 one thing is a lot of fields for the LGRP types in your building config don't seem to have units. For fields that have no units, the proper notation is no-units: no_units

should look something like:
counter:
      present_value: "counter.present_value"
      units:
        no-units: "no_units"

Hi @trav3711 we now did the required changes still we are facing the same issue

Answer 7 · 2023-05-27T05:12:56.000Z

Hi @trav3711 i did run git pull on a copy of my local master branch. Still I am facing the same issue. Can you share your generated reports with me?

Answer 8 · 2023-05-30T22:43:21.000Z

Closing this issue as it is a problem with the subscription messages rather than tooling source code.