Yes, devices often needs to be reset before inclusion, since exclusion success rate is random.
When it comes to Fibaro motion sensors, remember they are battery powered. So the only time they can be configured is when they are awake. You set the wake up interval. Or, better, make sure they are awake while configuring (press button so that they light up blue). Alternatively, wait a couple of days, and they will be configured finally. Just don’t expect anything to be immediate with Vera in general, or battery powered devices in particular. Because if one config fails during wake up (very likely), Vera has to wait until next wake up. What is default wake up, 4 hours? I have mine on 12 hours to conserve battery. Time to complete a config could be days.
What are you trying to achieve with associations? My advise: stay away from it if you can, it is extremely flaky. Not well documented, not well implemented. Very limited in functionality. Example: I have a room where a Fibaro motion sensor is associated with a Fibaro dimmer. So it will turn on the light when motion is detected, and turn it off after motion is “undetected”. A fixed timer. In the mean time, no more motion is detected, you are blind. If you turn lights off manually, they won’t come on again until set time of “undetected”. Pretty lame. On top of that, the time stamp for motion detected is fixed, it won’t change if motion continues. So it is like this: Motion detected, lights on, timer starts, timer ends, lights off. That’s it. Stupid. And to add insult to injury, associations aren’t any faster than firing off a controller scene based on the same event. You would expect associations to be fast, right? They are not.
What you want to do is to create a scene, like this: If motion detected, turn lights on. If no motion is detected after set time, turn lights off. If motion reoccurred during set time, add time before shut off. If light are manually shut off during set time, end process and listen for new motion event immediately. Few lines of LUA to make it a lot better in every way.
A comment on GUI. I have lived with and cried over Vera for a decade. I have several installations, my main one has more than 120 devices and thousands of lines of LUA code. I have now started a slow migration to HomeSeer. Mainly because of stability. I just can’t live with they way Vera has become an unstable, unpredictable, time consuming hack any more. Still, Vera GUI is decades ahead of HomeSeer when it comes to user friendliness and intuitivity. HomeSeer is highly regarded in the industry as one of the most production ready, stable and reliable platforms. Might be, but their UI is as bad as they come. I am really, really amazed by how completely, utterly pathetic it is. There should be laws against making something that horrible! Vera is fantastic in comparison. Yes, that says a lot…
Just an example I just spent hours on debugging today: HomeSeer GUI did not reflect the fact that a dimmer or switch status or load level was manually changed using a physical switch. Like, never. Say what? That is of course default in Vera. In HomeSeer? You need to configure each device and child to send status changes back to the controller using undocumented black magic (also known as associations), it is not default behavior. How unbelievable stupid is that? So the simple task of telling the controller the changed status of a device has to be configured for each device, or by polling in set intervals.
No, I am not in a hurry to move it all to HomeSeer, I will continue to try my use cases in a test environment for a while. Vera is in fact pretty powerful after all. I just wish it was reliable and stable as well.