Include Room property on FamilyInstance conversion

Hey guys!

Would it be possible to include the FamilyInstance.Room property during the conversion from Revit to Speckle?

We are building PowerBi dashboards for a clients where the relationship between furniture, for example, and to which room they belong would make them happy :slight_smile:

Sure thing - would you need the Room Name or ElementId?

1 Like

I think the ElementId would be more useful, since we need to construct the relationship.

Yes, definitely useful. This info can also be used for Power BI dashboards, Room data sheets.

2 Likes

Done, it’s coming!

We’ve also added:

  • roomFromId: for doors and windows
  • roomToId: for doors and windows
  • worksetId
  • all the parameters of type ElementId and of value null (which were previously excluded)

image

5 Likes

Sweet!!! We’ll try to comeback with a demo :wink:

1 Like

Hi, I see that new connectors don’t have “roomIds” attached to the instances, anymore. Why were they removed? Or are they moved somewhere?

On the same note, the logical connecter list is also missing from the new Revit connector. Example lighting fixtures have electrical connectors added to circuit them. In V2 Revit connector the list of these Revit logical connectors were showing up and had application IDs.

1 Like

Hey @trish25 ,

Thanks for flagging this! We’ve made some changes to how properties are structured in our latest connectors, and roomIds got caught up in that refactor. We’re definitely looking at how to bring them back in a more organized way.

In V2 Revit connector the list of these Revit logical connectors were showing up and had application IDs.

What do you mean by “logical connector” is missing. Are they not published? If you can share a screenshot explaining the issue, it would help us understand the problem.

Thank you for the quick response, @gokermu.

Please see two images attached. The one named V2 connector will have a Revit “connector list” highlighted in blue. This is the logical connector added in Revit to a lighting fixture (in this case).

The second image is an export from new connector for the same lighting fixture, but the connector list is missing.


Hey @trish25 ,

I see what you mean. Assuming, that’s an electrical fixture, how do you want to use Connectors info? And are you loading this data into another system (like PowerBI), or working with it directly in Speckle? Understanding your full workflow will help us determine how to address this.

(@trish25 's colleague here)

In general, we’re using the data to create building models (in another form). The Connectors create the electrical relationships in an overall electrical system. These can be used for a variety of checks and applications.

So, we could use things that show up in the Revit Snoop but not in Speckle.

@gokermu just following up on this. Thanks!

Hey @trish25 ,
We added roomId property to FamilyInstances and it has been released as part of the latest release. Get it from Connectors | Speckle

2 Likes

Thanks for the addition @gokermu.

I also noticed that the id and speckle_type is missing from the new connector.

I am adding two images with this reply: Wattage parameter in new and legacy connector for a lighting fixture.

We do see id and speckle_type in the legacy connector but not in the new connector?


Hey @trish25 ,

We don’t send parameter objects anymore. Hence no need for an id or speckle_type in parameters. They are simple dictionaries.

1 Like