Issue with Energy plus components in Ladybug and Rhino inside Revit 1.6

Hello all, this bug has been happening for a while apparently but it still hasn’t been resolved in Rhino Inside Revit 1.15.8522.
None of the energy plus components can be used with Revit at the monent. I know about the set_python_path.bat that could fix the problem but it didn’t help me. I tried to reinstall Ladybug 1.6 from Revit directly but also no luck there.


  1. Solution exception:
    Failed to import ladybug:
    No module named _sqlite3
1 Like

Hi @Alakelele
Maybe it is something wrong about running enviroment on you computer.You can use ladybug 1.6.0 only in grasshoppper to chech the componet. Then you connect rhino and revit for next simulation.

I know, but this bug has existed with Rhino inside Revit for a while now and it seems to come back when updates of Rhino inside Revit are installed. I will have to ask my it department for help.
Anybody tried ladybug 1.6 with Revit and has the same issue ?

Uninstall and reinstall from Revit didn’t solve the problem

There is no traction on this post, I tried to tell the folks at Rhino inside Revit about it, they are definitely more responsive. Issue Energy plus components Ladybug 1.6 and Rhino i Revit 1.5 - #7 by thomas.lagarde - Revit - McNeel Forum

1 Like

Sorry for the late response here, @Alakelele , but I think you surmised correctly that the bug is not something that we have the power to fix on the Ladybug Tools end.

The issue appears to be that whatever IronPython is being used inside Revit is old/broken in the sense that it does not have a working sqlite3 module. This is a native IronPython module that’s not something we have written for Ladybug Tools.

I know that McNeel has told me in the past that Rhino uses a different version of IronPython than Revit does and this has created conflicts in the past. So you were right to ask the McNeel people about this and that’s the correct place to have the conversation.

1 Like

Alright, well next step is to go at Autodesk, wish me luck

Hello, still having this exact issue! I reverted back to Rhino 7.25 and 7.26 and various older Rhino Inside Revit versions (all the way back to 1.13) but to no avail.
Anyone have any suggestions here?