I have checked this as well, what I found is below…
Sending using the Selection method:
You would need to actually “TAB” and select the nested shared families individually for them to be sent through Speckle. (It would be great to have the nested shared families sent through when having the parent family selected)
Sending using Visible in View method:
Nested shared families get sent without any issues.
I sent you a message containing a Revit project with placed families (having nested shared families)… I am not facing the issue mentioned above by Thomas, so maybe he can share his findings as well.
For my case, whenever I send the objects visible in view to a stream and try to receive it back, speckle creates duplicate elements because it is treating the nested shared families as separate elements.
Output after receiving the stream:
1- The parent family (which includes the nested shared families).
2- A duplicate instance for each shared family created separately from the parent family.
3 (bonus)- One of the nested shared STR. Framing elements fails to be created separately in its position, so maybe that would something to check as well.