My Somfy devices are drapes and sheers, so I likely can not comment about the awnings.
If you asked me last week, all was well, and you will do well by using Bond. It behaved well handing 10-100 commands a day as issued by my SmartThings automation, closing when light sensors said it was too bright, or when the temperature was too low outside at night using the drapes as insulation, opening when the day is fresh and the sky was blue, or when the door behind it was sensed to be open so the drapes would move out of the way.
Alas this week we had some server problems (apparently Bond uses AWS) and after all was said and done, and with a fairly lengthy service ticket, my Bond cycled heavily, crashed, and other things, after a couple of days, blinking close commands out all night and waking us up, it eventually settled down. However it lost its pairing with all the drape and sheer motors as it exceeded some rolling counter in the RTS protocol and every attempt to retrain it resulted in failure.
Since my Bond is part of my SmartThings automation, and I have 100s of devices, and more than double that in automation scripts, I can not just do a factory reset and start over, because when the devices unregister and disappear, all the associated automations disappear and need to be reloaded. I am manually saving all my automations in a spread sheet as SmartThings does not have a save or restore backup function. So I also have to rewrite some of my automations to speak to virtual switches so that they hang around in preparation for the great reset so I can re-pair my Bond.
Lesson one is I might have been better off with a ‘local’ device like the Somfy ZIRTSI-II Z-Wave Bridge in the same price range that had no server-side dependency. As Bond development support matures, especially since they recently open sourced their protocol, they too can be a local device with carefully crafted built-in SmartThings Device Handler that does a Wifi connection inside my network to the Bond rather than bouncing off of AWS.
Another lesson I learned, I bought my Bond from a reputable eBay dealer with a high satisfaction count at only a few dollars cheaper than from Home Depot because I did not have to pay sales tax. The Warranty clearly states, but not apparent to me at the time of purchase, that Bond will not support or service devices bought from eBay or Amazon (and yet they use AWS for their services), so I got effectively abandoned in the middle of the service process and am now on my own. They suspect that part of the problem may be that my Bond’s wifi chip is from a problematic production run they had, and that replacement is the only option to truly fix it. That option is no longer available to me even though my device is only a few months old. This of course violates the Magnussen Moss Act (both the seller for not providing clear information that the warranty on a new product is void, and the manufacturer for requiring a tie-in provision), but for a $100 it just barely exceeds the lower price limit set up by the Magnussen Moss Act, certainly below the point to retain a lawyer, and may even be too much trouble for small claims court. So pray for me that it was not hardware, but in fact just a series of bad things that can all be fixed by a complete set of device resets (including the Somfy motors perhaps)