@Jono,
The problem you are seeing is because the code in the measure has been update Ruby 2.5, which we started using with OpenStudio 3.0 and later, although we are getting ready to move to Ruby 2.7 with OpenStudio 3.2. For other measures impacted like OpenStudio results I updated the minimum version listed in the measure.xml which the OpenStudio Application uses to see if a measures is comparable with the installed version of OpenStudio.
I need to update the measure.xml to be 3.0 so the BCL won't update 2.9 OpenStudio installers. That doesn't directly help you. What I can do if you can't get it from our GitHub release for common measures is to give you a copy of the measure that was release alongside OpenStudio 2.9 which was version 0.1.2 of openstudio-common-measures. We do this for all of our measures collections for each major OpenStudio release, as well as sometimes interim releases. This allows users of Older installers to still have access for the measures. I can email you can copy if the link doesn't work. You can download zip file and look under lib/measures.
Have you tried deleting the measure from your project (not applicable if you are using apply measures now), throwing away the BCL directory under the user name on your computer, and re-downloading the measure from the BCL.
Looks to be the same problem as https://unmethours.com/question/53278...
It definitely looks like a bug, I posted an issue here: https://github.com/NREL/openstudio-co...
Thanks guys. I deleted the measure in my BCL library and redownloaded it. Seems I get the same issue. Was curious if it was just my pc or if everyone is encountering this issue. Sounds like it's not just me.
@Juno, I don't have a 2.x installer on my machine, but I didn't see this with OpenStudio 3.0.1 through OS Application. Can you try two more things. First, try to export your OSM file to an IDF using the file menu, I'm interested to know if that works. Next make a new empty OSM model and try to load the measure and see if you have the same problem. I'm trying to identify if the error is model specific or not.