Ladybug Tools 1.2 and Rhino Inside Revit issue

Hi there

I’ve been having some issues with the new ladybug tools. So far, everything seems to be running fine in Rhino 7, but when I try using LB 1.2 in Rhino Inside Revit, all components turn red and display the following error.

Not sure if this is a RIR issue or on LB’s end?
Any suggestion will be greatly appreciated.


I’m having the same issue using Ladybug/Honeybee v1.2.0 with Rhino Inside Revit. Scott Davidson from Rhino passed the issue over to this Discourse when someone posted the issue:

Problems with Rhino.Inside.Revit and python-based plugins (Honeybee) - Rhino.Inside / Revit - McNeel Forum

1 Like

same issue here. Has anyone found a solution to this?

I had this issue but managed to fix it. LBT in Rhino7 (standalone) was working fine, but not in Rhino Inside Revit.

I ran the installer from within RIR and if fixed my issue. Basically, the problem was that it could find the Python libraries, which is now resolved.

I am pretty sure that this issue results from the fact that McNeel doesn’t create the User settings file that sets the Rhino IronPython path until the very first time that you open Rhino Inside Revit. So opening Rhino Inside Revit after you installed Ladybug Tools causes this import error.

Rerunning the whole installer after the first time you open Rhino Inside Revit should fix it (as @PaulWintour suggests). But a quicker fix is just to rerun the set_python_path.bat file inside your ladybug_tools installation folder.


I had it HB working on Rhino 7 but when opening through Rhino Inside Revit it wasn’t working, I was getting the error “module not found”.

Running the set_python_path.bat fixed it immediately. Thanks for the suggestion Chris!

1 Like

I also had the same issue

I have the same problem with Ladybug/Honeybee v. 1.6.0. When I use HB nodes, I get the message e.g: “1. Solution exception:
Failed to import honeybee:
No module named honeybee.boundarycondition”

I followed the procedure:

  • rerun the set_python_path.bat file inside your ladybug_tools installation folder.
  • open Rhino/GH through the RhinoInside Revit plugin

I also tried to inverse this procedure.
In both cases, it doesn’t work.

Do you have any suggestion how I could fix it? Maybe in that case i should keep Revit and RiR plugin open and reinstall Ladybug Tools?

Many thanks!

Best regards,


1 Like

Hi… I also have the same issue… did you find the solution?

I tried to re install ladybug 1.6 by opening grasshopper using rhino inside… you are right it was solved… Thanks for your suggestion

1 Like

Could there be a hotfix for that routing problem, it seems to have come back after an update of Rhino Inside Revit

1 Like

Reviving this issue on Dec 4, 2023. I followed the steps listed above and I am still running into this issue using Rhino 7, Revit 2023, and LBT v1.7.
With RIR open, I ran the .bat file. In the terminal window, I saw that it set a path successfully for Revit 2023. I also confirmed the path is set and unblocked in the folder: C:\Users(name)\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings

Yet, I am seeing the same error in GH. I tried closing Revit and restarting after this too.

Perhaps its a new version of RIR as @Alakelele suggested?

So, this morning the issue is resolved but I cannot report anything definitely that resulted in the fix. I restarted my computer and re-ran the .bat file. Of course, when consulting a colleague on the issue, it was fixed when I went to open Revit 2023 and RIR. Hopefully you all can have similar luck. When in doubt, restart?

1 Like

Hello, I still have issues, even when reverting back to a version that once did work (RH 7.25, RiR v1.12 and LB 1.6.0). So sadly this issue is still not solved :frowning:

Hello Chris, I would like to run this, but when I do, it does not help. Can you explain to me when I should run the set_python_path.bat? Or run it multiple times, etc?

Hi everyone, here is an additional solution that worked for my by uninstalling a Revit plugin/add-on that was also working with Python and Ironpython, see my post here: