Assistance Needed for Mapping KNX Points from MQTT Explorer to Brick Classes

[Sabin Dahal]

Hello Everyone,

I’m currently working on a project where I’ve extracted several KNX points using MQTT Explorer, as shown in the attached image. These points represent various actuators and weather unit statuses, among others. I aim to map these KNX points to the appropriate Brick classes accurately.

Here’s a brief overview of what I’ve gathered:

• Actuators.DimLight: Covering various lighting statuses, dimming commands, and values for different rooms.
• Actuators.Weather unit: Representing different weather parameters such as rain, temperature, wind speed, etc.

I understand that Brick provides a structured way to represent building data, but I’m facing challenges in correctly identifying the right Brick classes for these points. For instance:

• ON/OFF Status: Should this be mapped to brick:On_Off_Status or something else?
• Dim Commands: What is the best Brick class to represent dimming actions?
• Sensor Values: How do I represent real-time weather readings, such as temperature and wind speed, within the Brick schema?

Could anyone guide me on how to approach this mapping? Are there specific best practices or resources within the Brick community that I should be aware of?

Any help or pointers would be greatly appreciated!

Thanks in advance for your support.

Sabin

[Gabriel Fierro]

Hi Sabin:

 

Here are some answers!

• ON/OFF Status: Should this be mapped to brick:On_Off_Status or something else?

Yes, On_Off_Status is the best fit here

• Dim Commands: What is the best Brick class to represent dimming actions?

I would look at https://ontology.brickschema.org/brick/Luminance_Command.html

• Sensor Values: How do I represent real-time weather readings, such as temperature and wind speed, within the Brick schema?

Brick does not represent real-time weather readings, or any real-time sensor values. You can use https://ontology.brickschema.org/brick/lastKnownValue.html to point to a recent reading, but if you want to refer to the history, you should refer to https://docs.brickschema.org/metadata/timeseries-storage.html or https://docs.brickschema.org/metadata/external-representations.html for pointing to external data. We do have some weather-related points like https://ontology.brickschema.org/brick/Wind_Speed_Sensor.html and https://ontology.brickschema.org/brick/Outside_Air_Temperature_Sensor.html

 

For establishing this mapping, you can look at the ontology docs at https://ontology.brickschema.org or the developer docs at https://docs.brickschema.org/intro.html. In the past, I’ve used embeddings to find “similar” matches between a set of keywords and the Brick points/classes

 

Best,

Gabe

 

From: brick...@googlegroups.com <brick...@googlegroups.com> on behalf of Sabin Dahal <sabin...@gmail.com>
Date: Monday, August 26, 2024 at 8:10 AM
To: Brick User Forum (Unified Building Metadata Schema) <brick...@googlegroups.com>
Subject: [Brick] Assistance Needed for Mapping KNX Points from MQTT Explorer to Brick Classes

--
You received this message because you are subscribed to the Google Groups "Brick User Forum (Unified Building Metadata Schema)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brickschema...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/brickschema/849b6d51-ff0b-4ad3-a633-e2cee5d35b60n%40googlegroups.com.