You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FB_29 (Temperature Interval Metering) has no defined rule for which data it grants in the Data Custodian's resource API, so the DC cannot gate temperature data on it.
FunctionBlock.FB_29 is a COMMODITY Function Block with no service kind, unlike FB_5–FB_9 (electricity), FB_10 (gas) and FB_11 (water).
ServiceCategory has no temperature value, so a temperature UsagePoint cannot be identified by its ServiceCategory.
Identification: how temperature data is recognised: ReadingType commodity, ReadingType uom (e.g. degrees Celsius or Fahrenheit), a UsagePoint ServiceCategory, or a combination. Cite the REQ.21 v4.1 FB_29 text and the GBA certification test expectations.
Granularity: whether missing FB_29 removes whole UsagePoints or only the temperature MeterReadings (with their ReadingTypes and IntervalBlocks) under a UsagePoint of another commodity.
Combination with FB_4: whether FB_29 alone (with FB_4) is enough for Batch/Subscription and the per-resource endpoints, and what a token with FB_29 but no other commodity FB receives.
Activity
feat(datacustodian): Batch/Subscription UsagePoints by commodity Func…
fix(datacustodian): Batch/Subscription requires FB_4 plus an electric…