In this release
Edge Management functionality was migrated to a separate service. The Edge Management API can now be accessed at the path ‘https://proptechos.com/edge’, or if you are running a dedicated instance‘https://<p8s_api_host>/edge’. New median and native observation functions are introduced.
New functionality
Median Function – Consolidate Observation from N sensors
MedianObservationFunction – MedianObservationFunction calculates the median value over the observed sensors’ values over a configurable period. If during the configured period any of the observed sensors did not provide any observation, the median value will not be calculated. (Sensors with MedianObservationFunction should observe at least 2 sensors).
MedianObservationFunction json schema:
In order to set up ‘recalculationPeriod’ ISO 8606 Duration format should be used, the example above is for a period of 1 hour.
Native Observation Function
In this release we introduce a list of predefined Observation Functions, that can be used for conversion from one measurement unit to another. Native functions have no relation to the Property Owner.
All new functions available by GET /json/observationfunction
The initial set of Native Functions:
- hPa To Pascal
- kPa To Pascal
- Liters To Gallons
- Square Meters To Square Feet
- Inches To Cm
- Cm To Inches
- Meters To Feet
- Celsius To Fahrenheit
- Fahrenheit To Celsius
- kGal To Cubic Meters
- Gal To Cubic Meters
- Therms To Wh
- Bar To Pascal
- m³/h To l/s
- Hour To Seconds
- Minute To Seconds
Breaking changes
- None
Fixes and minor upgrades
New connectors:
- NordPool
- Support of weather forecast values for SMHI
Added edge management support for the connector types:
- WebCTRL
Improvements:
- Added new endpoint to fetch collection of sensors using specified ObservationFunction (PLAT-4586)
- GET /json/observationfunction/{id}/performedby
- Added opportunity to grant RPPs to agents by OrgAdmin (PLAT-4667)
- Added new filter to observation function endpoint – observation_function_classes
- GET /json/observationfunction?observation_function_classes=Native ObservationFunction&twin_statuses= Valid&page=0&size=50
- For “RealEstateCore individuals”, such as roomtype, quantitykind, placementcontext, measurementunit, devicefunction, buildingcomponentclass responses, a new field “labels” was added to save translations for different languages. Currently, there are translations for English and Swedish languages. For example:
- GET json/roomtype
- Sensor object extended with new property ‘observationCharacteristics’ that accepts array of enum values:
- CumulativeReading – the sensor represents a running count. Meaning that the numerical quantity represents the accumulated value or consumption since the last reset (when the value starts from zero or the beginning). Metering devices (e.g. for electricity or water) is commonly generating cumulative readings.
- CalculatedValue – the sensor represents a quantity that is not directly observed, but a value that is based on a calculation, estimation or model which likely includes one or more directly observed quantities.
- PeriodObservation – the sensor value is related to a time period, rather than an instant in time. This means that the observed value of a period start time and a period end time is involved. Typically applicable when observing consumptions rather than state. E.g. volume of water over an hour (period), which the flow rate is an instant observation.
Defect fixes:
Per Karlberg
Per Karlberg, a distinguished technology executive, demonstrates deep expertise in the nexus of real estate, technology, and ESG. Holding advanced degrees from Lund University, and with key roles as CEO of our company and Co-Founder of ProptechOS, he has shaped the proptech field through significant contributions to real estate technology advancements. His instrumental work in co-authoring “The realestatecore ontology” has facilitated digital transformation and ESG breakthroughs in the real estate sector.
Read his full bio and information here.
