I am so dam confused.
There will be a fix for this in 3.0.3. It will still require some physical work though from the user.
The problem is that, in order for MultiMiner to detect both SHA and Scrypt ASICs, it must run BFGMiner twice. When the Bigpic (BF1 / Red Fury / Blue Fury) is probed as virtually anything but Bigpic, it stops responding.
This is not really a "bug" that can be fixed in BFGMiner. It's a known limitation. Some ASICs just do not provide a way to say "hey, what are you??". In that case you have to go through devices and say "are you A? no, are you B? no, are you C?".
And some devices, like Bigpic, just stop responding if you do this. And by adding a scan for devices with the --scrypt argument (necessary to pick up Scrypt ASICs) in one of the 3.0 previews, this effectively disables the BF1.
So, 3.0.3 will scan for SHA devices first, then Scrypt. This means (in my tests) all devices should be recognized by Scan Hardware.
But that scan also effectively disables some of you ASICs - namely your BF1 devices. You now need to physically walk over to them and press the RST button them. Then you can start mining.
The RST button must only be pressed once after Scan Hardware. I'm also looking into some more effective solutions for a future update but that will have to be for BFGMiner, not MultiMiner.