Hi Monty,
Just so you know, I couldn't get the speed reporting working properly with BFGminer either. I tried all sorts of combinations of port numbers and whatever, but it seems it just doesn't like the API commands. I'm using gridseeds too, so a similar setup I would imagine. Once I switched back to CGminer everything was fine. Also, I noted that when running BFG miner with 20 gridseeds, a few of the gridseeds either didn't hash properly, or not at all. The effect seemed random it was different gridseed units each time (I checked the serial numbers). All in all, CGminer seems to be better (although you have to turn off the damn USB hubs before you run it, which is a pain).
The API commands seem to work fine with the gridseed version of CGminer. Not had a problem since I switched back.
Tested CGminer for a few hours now and it seems stable regarding to speed reports. PLUS I didn't even need to deactivate the USB hubs.
Had to hotplug the Gridseeds though after starting CGminer to be recognised so I am a little worried what happens if the rig goes down for some reason and I am not around. Any idea how to solve this?
@SlipperySlope
ipominer.com is one of the pools I am using in times my rig is not leased. You have to keep an eye on the multipool though as it sometimes is not the most profitable solution but ipominer.com is - in general - better than most other multipools you find on poolpicker.eu.
No, I haven't figured out how to hotplug the gridseeds remotely yet (in case of some unexpected error that requires a restart). In Windows 7, you can disable the hubs from the device manager, and then re-enable them again, but this doesn't seem to work fantastically well. Last time I did this only 14/20 gridseeds were discovered. I then tried again and only 8 were discovered. Seems the only reliable way is to physically disconnect the hubs, which obviously requires you to be there.
What is really required is a USB hub that can be activated or deactivated via an IP-switch. I suppose that might do the trick.
AS A SEPARATE ISSUE...
Can we PLEASE have some kind of tolerance (-+ 5% perhaps) on what the site thinks is an underperforming rig?
For example, my rigs operate at 7.23 almost constantly. I've however put the rated speed at 7.2 to make sure it's nearly always reported at running okay. BUT, occasionally a pool goes down and it drops the rate down a bit, even though the rig is working fine. Right now the site is telling me my rig is underperforming because it's reported at 7.18 not 7.2!! Seems a bit harsh to me! Especially as you get that damn annoying pop-up saying "are you really sure you want to hire an underperforming rig?". It's only 0.02 off it's speed FFS!