Hello @Fabiana_Ilari,
Thank you for reporting this issue to us! It really helps us to make Speckle better. We’ve found the bug that was causing this behavior and have fixed it.
Speckle Revit connector version 2.8.3
Speckle Revit connector version 2.9.0
Go into the Manager for Speckle application and upgrade your Revit connector to version 2.9.0 and everything should work. Let me know if that fixes your issue and please don’t hesitate to report any other issues that you experience!
Hi support team, additional objects missing
I’ll send you a portion of the file privately, thanks 
my Revit connector is 2.9.0
Thank you for the additional stress testing of the Revit connector! I received your PM and I’ll see what can be done. Hopefully we can push out a better version in the next couple days
additional stress for you! I am sorry 
I am going to build my new scan-to-bim portfolio on Speckle!
a lot of models to upload…
That sounds great!
When your lots of models are ready, we have examples around how you might present them!
wow, that sound really great! can’t wait to see those examples
Hello,
Just wanted to give you an update on the progress of this issue. As you can see here I’ve been able to get everything except the detail lines on the door to send to Speckle. Currently, Speckle doesn’t have very good support for in-place families such as that door, and I think implementing that will be a longer task that I’ll have to work on in the future.
I don’t like to implement sending of an object to Speckle without also implementing the receive functionality of those same object back into Revit, so that is what I am working on now. Specifically receiving the glazed roof is a bit tricky. I will continue to work on it and keep you updated on the progress.
In the meantime let me know if you’ve found any more objects that don’t send to Speckle
thank you for your work @connor!
as you may have noticed, there are some in-place families, in fact
In this case, I confirm that the entry door is an in-place family, the glazed roof is a built-in (system) component, and the chimney caps are common (parametric) generic model components.
But, in general, you may find strange things in historical building models: sometimes it is not worth making parametric families if a component does not have a critical impact on the bim process, for example unique decorative elements.
In some other cases, I confess I do strange things: ( 
) like transforming an in-place family into a loadable one (tricks of the trade)?! and other similar creative workflows, I think that in my models you may find a complete collection of Revit components, so once fixed them, you’ll be all set! (maybe)
Can I send you other pieces of models?!
ahhhh, my beautiful objects in the Random Garbage?!
they might be worth a fortune after my death!
Hahaha the stream title is not a comment on the objects themselves. It’s more of a comment on my many failed attempts to properly send those objects
Absolutely! On behalf of @connor, we’d love to to test them out in his stream (that’s now aptly called Random Treasure) 
ahahhahah, I love this new name!
@dimitrie, I’ll send you a pcloud link to a folder where I’ll drop my precious ‘treasures’
It’s awesome to see how much progress this connector is making! Sorry for the slow response to my original post. We will be getting stuck back in soon
It took quite a while, but I’ve submitted the fix for the objects that you brought up. The curtain roof is a bit limited when receiving back into Revit, but there isn’t a ton more I can do about this. I had to hack my way around some Revit API limitations. Seems like you are mostly interested in sending to Speckle so that should work fine for you (except the door… I haven’t forgot, it’s still on my list).
If it is of any interest to you, you can see the changes I made to the code base as well as a description of the changes that I made at this link. These changes will be availible in the next release, 2.10, of Speckle which will happen in a couple weeks. Hopefully I can get your other unsupported objects fixed in 2.10 as well.
Thank you again for your error report and sharing the model with me to help make our platform better. Please continue to do so.
Hi @connor! Thanks for your work!
keep fighting mate!
Don’t forget the beam systems, too
and, yes, actually ‘sending’ is mainly relevant to me. I’ll read your post about the changes but I am afraid I won’t understand much, no coding skills, unfortunately 
(But I always wanted to learn at least Dynamo, and probably I will)
Please continue to do so.
Sure ;D
columns were previously assumed to be always based on two levels, but appearently they can be one-level based with a fixed height.
→ Actually, in general, the category is not a guarantee of how a family behaves, in this case, the column was made as an in-place family then turned to loadable, in-place families do not use families templates, or I could have made it starting from a generic model template, then switched to the Columns category. So, you might find a variety of situations. Regarding ‘slope arrows’, they can be applied to roofs, floors, ceilings, pads…
Hi guys, other items to append to the list:
I’ll drop a sample file in the pCloud folder
thank you!
Hello @Fabiana_Ilari,
Sorry for taking so long, but I’ve finally gotten around to supporting all of the objects that you’ve provided us. You can see a few before and after screenshots here. I know I’m not showing all the models that you sent, but several of the issues overlapped and I think that I’ve fixed all of them. The changes will make it into our next release, 2.11, which should happen in the next couple days. Once it gets released (I’ll ping you here again) give it a shot and let me know if I missed anything.
Thanks again for your many contributions!
Hi Connor! No worries for the time, I am so happy you fixed those issues
These days I am pretty busy but I can’t wait to see the improvements on Speckle 2.11!
It’s great to have beams, braces, and columns converted
