Hello, everyone!
I get this error when I want to add a Sensor Grid to a model. This error occurs both for one room and for the whole building. Could you please tell me what the problem might be and how to solve it?
Hello, everyone!
I get this error when I want to add a Sensor Grid to a model. This error occurs both for one room and for the whole building. Could you please tell me what the problem might be and how to solve it?
Hi @maksym,
Thank you for reporting this. This is a bug that we are aware of and will be fixed in the upcoming release.
One workaround is to use the LBT Grasshopper plugin to add the sensor grids and add the sensor grids back to Rhino. Do you know how to use Grasshopper?
@mingbo, can we create a release and share it with @maksym to unblock his workflow?
Thank you @mostapha .
Yes, I know how to use Grasshopper. I would appreciate it if you could show me how to add sensor grids with Grasshopper.
Hi @maksym, I tried a couple of solutions to fix the issue without renaming the rooms and failed. I’ll assign this to @chriswmackey to see if he has a better suggestion.
It’s a bug that resulted from the Rhino plugin starting to enforce honeybee-schema rules, which had a typo in them that we never found before as we had never enforced them.
I fixed the bug in schema rules here:
… but it won’t be in the rhino plugin until @mingbo gets the chance to rebuild the rules used by the plugin and make a new release. So I’m now reassigning the issue to him.
Unfortunately, there’s no way to resolve it except to not use the Rhino plugin once sensor grids are added (adding the grids in Grasshopper and keeping the model there from there forwards). Or you could divorce the grids from the rooms completely (replacing room_identifier with None), which might be ok for simpler radiance studies like direct sun but not ok for LEED or daylight or thermal comfort studies.
1 Like
Hi @maksym, I shared a link with you to download the latest version that resolves this issue.
We can’t release it publicly yet because it has a minor conflict with the latest version of Rhino 8. The McNeel team and @eirannejad are helping us to resolve the issue. We can mark this topic as resolved once we make it publicly available.
Let us know how it goes.
Hi @mostapha.
Thank you, everything is working correctly now.
1 Like