Hi ! I am an architecture student and Im struggling with making aperture shadows. I wanted to make shades (something like roller blinds) that will activate only at night or when my buildings is closed. I wanted to use “HB Window Construction Shade” along with Shade Material, but every time I plug it into HB Apertures an error occurs in “ModeltoOSM” right before Energy Simulations. I tried a lot of diffrent possisiblities and I ran out of ideas, could anybody help me? Unfortunately im a new user so I cannot upload the gh file :(( or more than 1 picture
Hello !! I have also been facing this issue very recently, especially after moving from 1.8 to 1.9 or 1.10.
I think there is a similar discussion about this before
Bug: incorrect referencing of window construction - grasshopper / honeybee - Ladybug Tools | Forum
In my case, I have made a construction. hbjson that I refer to for about 10k simulations, and then only change the window material in the hbjson with roller blinds. So my process also looks like this
As you can see in my base construction.hbjson: the window material is Window_U164_G06_T06. I then add the shade material BuitenzonWindowMat U164 G06 T06, reapply it using windowconstructionshd and applywindowconstr components, but this results in an error about not finding the new window material I created.
So I am not sure if this is a bug where the model-to-OSM component gets confused between the two materials.
Anyway, how I solved this is to deconstruct my base material. hbjson and create a new base construction set without any windows in it. It solved my issue.
I am not sure if this helps you, but I hope it does because the frustration is very real 
Prateek
The official answer to this issue right now is to either install Ladybug Tools via the Pollination single-click installer, which already has a version of Ladybug Tools with the fix in it (recommended for all Windows users), or use the LB Versioner to go the the latest development version of the plugin (recommended only for Mac users or advanced users keeping up with the latest development).
If you are still experiencing issue with this after updating, please post a minimal Grasshopper sample file that recreates the issue and I will investigate further.