I know the Trust State in general has been a mixed success depending on the user / environment in which Bond is integrated.
I get around some of the challenges by (a) never using original remotes for things which are controlled via Bond or Harmony, (b) using Bond’s Trust State tracking for lights, and (c) leveraging my own ISY programs/integrations for any voice assistants.
I don’t use the native Bond (nor really any device’s native) voice assistant integration - it all goes through my ISY so I can programmatically track what is happening in my entire home ecosystem and only send “Power Toggle” commands to devices which I have tracked to be opposite of what I intend in the moment to turn on / off via voice.
I am able to rely partially on Bond for any controlled lights via Trust State, but I have smart keypads set up with programmatically discrete Light On and Light Off buttons, where a single tap sends the Bond “Light On” or “Light Off” command, per Trust State. A double tap sends the Bond “Light Power Toggle” command AND patches / updates the Bond’s Trust State to the opposite of whatever it thinks it currently was.
Same basic idea for “Fan On” or “Fan Off” - I just have to track the fan power state through my ISY and if voice command = “Turn On”, only issue the Bond “Fan Power Toggle” command if my ISY-tracked fan power state is OFF / 0 (and vice versa).
Not 100% perfect, but nearly so. Now, if Bond offered a Bond-Bridge-pairable universal remote and/or hardwired keypad that could be set to handle the majority of fans (with or without light kits), then I think there’s a more consumer friendly option available at that point in time.
As it stands, using original remotes, having original receivers without the ability for discrete ON/OFF commands (be they for lights or fan), and mixing of voice assistant routines / whole home setups / third party integrations without a central, customized-per-home controller continues to have a mixed bag of success for most folks. 