I get the error “expected str, got bytes” on the Honeybee/Honeybee component when trying to run it using Rhino.Inside.Revit. It works fine just running it in Rhino 7 WIP. Also, I get an error message, including the same error “expected str, got bytes”, from a ghpython component in the DecodingSpaces Grasshopper-plugin when Grasshopper starts up inside Revit. Why can this be?
and thanks for posting the question at Ladybug Tools, too.
The error in the image above, from DecodingSpaces, didn’t appear when I first started to use Rhino.Inside.Revit, either. I think it started to appear maybe 2-3 months ago.
Just had the same problem and neither @parametricmonkey1’s solution nor running set_python_path.bat worked (although the latter actually added the correct paths to the xml files).
I managed to fix it by adding the path manually to the path options of Python Editor in Rhino.Inside Revit:
Start Rhino.Inside Revit
Open Python Editor from the tab and then go to ‘Tools > Options’
Add the correct path to the ‘Model Search Path’ area and that’s it
Hello Japhy thank you, my issue is also posted earlier on the Ladybug forum, see link below. It is an issue with Rhino Inside Revit, which is not connecting properly to python causing the Honeybee Energy components to not work (_sqlite3 to be specific). Chris Mackey is referring back to the McNeel forum. So in short there is no solution yet. We used to have it working before, but an update in rhino or rhino inside revit (we did not update Ladybug Tools) has messed up the Python referral.
Forum:
All posted solutions so far did not work for me (running set_python bat file, reverting to older thino inside revit, adding location to ironpyhton referral manually).
I will now try to revert Rhino back to v7.25, since that is the version that is listed in the compatability matrix for Ladybug Tools. I will let you know if that works, now we have 7.36 running.
Hello, I’ve found an additional solution that did work for my by uninstalling a Revit plugin/add-on that was also working with Python and Ironpython, see my post here: