You must be registered and logged in to post to this forum.
So...initially I had little problem getting my Spykee on my home network, and remote working just a couple hours after that.
After about 9 months of use (2 years ago)...I switch networks about the same time I received the replacement charger. I don't know what happened but the replacement charger suddenly would not charge my Spykee!
So, about 3 months later, I received a replacement battery found on ebay, larger Ah rating. I replaced the battery, it worked as soon as I plugged it in, then needed charging within 15 mins. So I put it on the replacement charger....and nothing. I tried the original battery, and briefly tried the original charger...nothing seemed to work.
Not being more patient, and having him sitting around for months (about 9 months!!) I packed him up and sent him home to France with a letting.
Now, 3 months later he's BACK! I believe all they did was replace the battery, not much info, but he works! I made sure to use the original charger this time, and he recharges! BUT, getting him back on my network is not working well.
My U-Verse router refuses to see him. And, he won't save my admin password change. As soon as I put my router and password information in, he just blinks and blinks, nary a connect to be. I see him broadcasting if I reset him to factory settings. As soon as I put in router information, he disappears from my scans.
Local Ad-Hoc via laptop works fine. And video on YouTube showed he prefers WEP to WPA, so a couple questions;
My router name is long with spaces, does this cause a problem?
My newer router was on WPA, and I set it to WEP, still no go. Should WPA or WPA2 work?
Also, I tried to use the Android app, but that does not seem to connect.
Thanks in advance for any tips...and I will keep searching....
LONG story short, it only took me a couple days to reconfigure and get Spykee back on my network. Here are some steps that HELPED!
1) I took the space out of my router name , as I have heard that Spykee firmware may have an issue with that. It seemed to help get spykee on my home network. Before that it seems that Spykee did not like my network and I did not see him on my router.
2) I DID NOT have use WEP. The 3800HGV-B wireless router that AT&T uses works fine in the default setting with Spykee (WPA).
3) I DID have to use a fixed IP (for external access)! Once I got that through my head and set my router to assign him an IP, he worked fine across the net. Before that, he would work only in local mode.