Mondays are perfect for making videos.
On Saturdays though, you find the right problems to solve.
Last Saturday, at around noon, I asked my friend Konrad Sobon in New York City if he had ever considered looking at the old Door Swing problem in Revit with Python, API and Dynamo eyes. Later the same day (I think it was Labor Day in the US) he uploaded a small Custom Node to his website archi-lab (archi-lab.net). I’ve been waiting since then to test and break it, but apart from a small bug that prevents me from using the Categories node in Dynamo (this is not Konrad’s fault), it works fantastically well! Hard as stone – impossible to break!
Until we can bake Dynamo definitions inside Revit families, the way to use this is the same as most other addins: Run before you QA your documentation. (Striking double meaning there.)
Documenting Door Swing and Handing Direction has been a lacking OTB functionality in Revit for a very long time. Architects who needed to handle this had two choices: Do it manually (suicide!!!) or buy addins. Many of these addins have worked extremely well, but now you can do it yourself. For free.
This is another example of how building designers, with a little help from people with programming skills, can start designing their own software, and share it with the rest of the world.
Håvard Vasshaug 
I have done according to your design Door Swing Direction in Revit, Dynamo just like you but the result is incorrect, Yellow boxes.
If only it were possible, and you could send light model of Revit project with the code works, so I could see what settings I am missing on their own project.
And, if you will, but also the Dynamo code if I’m in the doing something wrong.!
Sorry for my bad english but I hope you understand.
Erkki
Hi. Check my update: Door Handing in Revit with Dynamo update
I am getting the same result as zcgt21 and Tapani. The problem seems to be linked to the value in the code block. I am entering “Left”; and it doesn’t seem to like it it goes yellow with a warning: Warning: Dereferencing a non-pointer.
Hi. You could try using a String node instead. Also, there’s a Package called “DanEDU Dynamo” that has a Door Handing node you could give a shot.
Check out my update: https://vasshaug.net/2015/04/23/door-handing-in-revit-with-dynamo-update/
Did you find a solution to zcgt21´s problem? Could you post it over here?
Hi. No I didn’t. I don’t know if zcgt21 posted the problem to the community forum. It’s pretty hard to see what’s going on without imagery.
No yet, I still searching, but probably is a language problem, my Revit is in spanish, and Dynamo in english.
Hello:
I’m a spanish speaker, so my english es very bad, I hope you understand.
I’m following the instructions of the video, but my code doesn’t work, I don’t know what is happening, when I do the last part, (Element.SetParameterByName) and apply “run” the node it’s turn yellow and show me the Warning: Dereferencing a non-pointer. I no have idea.
Even edit my family door and create a new parameter called “Abatimiento”.
Thanks for your time.
Could you post a description and screen shot on the community at dynamobim dot org? And notify me with a link so i can respond there? Thanks:)
OK, thanks for your anwser.
Gracias por su respuesta.
What is your thought on the real world use of this app? Maybe run Dynamo just before printing or at specific stages to make sure your plans are updated? Or have it running in the background as the user makes the changes that day?
Matt
Hi Matt:) On a general basis I would say that data is best updated as often as possible. Live data = less errors. In this case that is practically impossible, and I think you would look at updates every time someone is to review the model documentation. Which basically means before issues. I can’t have one def running in the background as I use dynamo for many things. This problem relating to updating data will be irrelevant when we can start baking dynamo definitions inside Revit families.
Pingback: Door Set Handing | archi-lab