-
Notifications
You must be signed in to change notification settings - Fork 160
Description
We are encountering an issue where the Telemetry Validator reports missing points for entities even though data is present in the subscription. The data output from the subscription indicates that all required points are being published, but the validator still flags these as missing.
Steps to Reproduce:
-
Run the following command:
python toolkit.py -i path/test.yaml -v -s projects/x-y-z/subscriptions/x-y-z-subscription -d /path --udmi -t 400000
-
Verify data availability in the subscription by manually subscribing. Confirmed output:
{
"timestamp": "2025-01-06T13:31:37Z",
"version": "1.4.2",
"points": {
"supply_fan_energy_accumulator_1": {"present_value": "4843.0"},
"supply_fan_energy_accumulator_3": {"present_value": "4578.0"},
...
}
} -
Despite data availability, the Telemetry Validator reports the following error:
{ "entityCode": "AHU-14", "expectedPoints": [...], "telemetryMessageErrors": { "missingPoints": [ "chilled_water_valve_percentage_command", "supply_fan_energy_accumulator_1", ... ], "missing_present_values": [], "invalid_dimensional_values": {} }, "telemetryMessageWarnings": { "extraPoints": [], "unmapped_states": {} }, "timestamp": "2025-01-17T04:14:58Z", "version": "1.4.2" }
Observations:
- The points flagged as missing (e.g.,
chilled_water_valve_percentage_command,supply_fan_energy_accumulator_1, etc.) are available in the subscription output. - There are no extra points or unmapped states in the warnings.
Expected Behavior:
The Telemetry Validator should successfully validate entities and their points if all required data is present in the subscription.
Please help us identify the cause of this discrepancy and provide guidance on resolving the issue to ensure successful validation.