Nested generic annoation - put on sub-category

[HVAC-Novice]

I have a lighting device with a nested generic annotation family. to control visibility of the annotation i want to put it on a sub-category of "Lighting Devices". but there doesn't seem to be a way to put the nested family on that sab-category.

The only workaround seems to be to edit the annotation family, and create a sub-category to "Generic Annoations". One problem is, I would prefer to control visibility of lighting devices under lighting devices. But the other problem is that the annotation family also has a "label", which seems to not be possible to be assigned to a sub-category. 

what other options do I have? What I ultimately want to accomplish is to show a switch symbol ("$"for example) only on lighting plans, but not on all other views. those other views only should show the actual switch (without symbol). So just making the entire Lighting Device category invisible wouldn't work. Fr example, I need to coordinate thermostat locations with light switch locations. 

I attached the family in question in R2021 version (My current is 2022, but i figured more people can open 2021)

[barthbradley]

How about Nesting one into the other as a Shared Family under a different Category?

[HVAC-Novice]

it seems the generic annotation family can only get changed into a lot of tag categories. when I change it to a lighting device tag (to be somewhat consistent) it gives me an error saying it only can nest certain categories. 

I actually kind of resolved my problem and decided to try to get rid of the symbol entirely (I use tags for switches anyway). But still curious how to do that in case I want a symbol. 

[barthbradley]

I meant to nest it the other way around. You can't nest shared annotations.  

[syman2000 · Accepted solution]

Typically I would set the generic annotation to show up in fine.

That way you can control the plan as course/medium and make it show up on RCP with fine detail.

[HVAC-Novice · Accepted solution]

thanks. but if i use the fine/coarse to make things visible, that also will apply to all other categories if i make a view fine/coarse. Or?

Like in my example, if I have a mechanical plan, and want to show the annotation of some mechanical families, but not electrical, lighting, architectural etc. Using the fine/coarse would be a too wide net to differentiate. 

What I do now to close this thread is to just get rid of these annotations and only use a tag. My original example was a light switch, and even where I wanted the symbol being shown, it cluttered up the view when I had multiple switches next to each other. BTW, the ne wR2022 feature lets me tag multiple items (if they are the same) with a single tag. so that works even better.

I'll accept this as solution. Didn't really solve my original question, but A-desk keeps bugging me if I don't accept a solution and my new solution is acceptable to me 🙂

[syman2000 · Accepted solution]

You can control each category detail level thru graphics override. So if this applies to electrical, you can set it to fine while the rest will be by view.

[HVAC-Novice]

Thanks. I hadn't realized i can change that per category. 

Learn something new every day.