Ok. Below is a list of a few of the things I have found that seem to help...

I am running Mac Powerbook - OSX 10.5.6 - 1 gig ram - on Airport Express

Some of this may apply to everyone though...

1. Spykee WON'T connect to your network if it is NOT one word, no spaces...
2. Video will LAG severely over time if the console is not the ONLY program running at the time...
3. The 'name' of your Spykee should be one word, no spaces or special characters - same with the passwords... - Mine is - ModBot - and that works fine...
4. Renewing your DHCP lease (in network prefs - TCP/IP) may be required to force a new I.P address (if it has gone blank)
5. Apparently Spykee can only handle WEP - I chose NONE, it's just easier... (my network is out of range of potential piggy-backers)
6. The Good Quality video (fast network) is WAAAAY better, even in low light, than the Low Quality (slow) setting... I set my Mbps to 5.5 from 2.2 and it's lovely... (for a web cam)
7. For remote connections I have found Port-Mapping crucial - I selected the option in the console prefs and entered port 9050 - then in the AirPort Utility program - I selected Manual configure, then under the Advanced Menu button I selected Port Mapping. I then ADDED a new one and filled in the Public Port Number to 9000 and the Private Port Number to 9050. Then APPLY and allow AirPort to Update. Turn Spykee off, wait, then on - hope for your 3 beeps :)
8. Sometimes I have had a "Spykee not Available" or "Internal Connection Error"... Even though he beeped 3 times at start-up - I could NOT connect remotely and would get those errors - but I COULD, for some reason (even with my open Internet connection and NOT the ad-hoc wi-fi selected) connect to it locally - with no such error. The solution seemed to be - turn off Spykee and wait a few moments. Turn it back on - wait for your 3 beeps - then try again. It would then work for me - no idea why... It seems if you can connect locally when you think it should be set to access remotely, you will get one of those errors... If it will NOT connect locally - you will probably then be ok for the remote... ughhh - I know...
9. The software seems to indicate the battery level is lower than it really is... Once conditioned a few times and left to fully charge - the battery seems to be fine for as much as a few hours of 'stand-by' (on but not connected to or moving) time...
10. The Auto-Park battery feature works best at about 3-4 feet from the charger base with it's back facing the charger... closer seems to make it less reliable... I turn the bot to face the charger 3-4 feet out - then do a 180 degrre turn - square on to start seems best as well...

I may think of some more to add later - but that's some of what I have found so far - and NOT from the official manuals etc. It was learned through lots of trial and error troubleshooting and from various posts on various forums (thank you)... thought it might be useful to collect some of it in a more singular way/place...

Hope some of this helps. I woulda liked a list like this before I went totally grey... lol