Open fatalerrortan opened 7 years ago
"walk_max": 13.16, "walk_min": 3.16,
test change values on min
@Jcolomar thanks for your advice . I have adjusted the walk_limit to 2.16. So far there is no problem, but the strange thing is that the robot seems to move faster than usual
closed
@Jcolomar sorry, it happens again. is something wrong with the moveToFort config?
Ok, look how many pokestops are around ur default location. { "type": "MoveToFort", "config": { "enabled": true, "lure_attraction": true, "lure_max_distance": 2000, "walker": "StepWalker", "log_interval": 5 } },
Movetofort force bot to move to closest fort in distance from ur position. Ill try this:
"walk_max": 10 "walk_min": 4, "lure_max_distance": 1000,
And choose a good location with a lot of pokestops (like green gardens, beachs, etc..)
@Jcolomar I really appreciate your help. : )
by "lure_max_distance": 1000 the problem happens still.
by changing to 3000 it happens relatively less but I got often "Possibly searching too often, take a rest."
Try follow spiral to FALSE and test
"walk_max" really shouldn't be too much higher than 2. using 2.15 is fine, 2.25 or higher causes mine to miss spins and get "Possibly searching too often". I set mine to just 2 and rarely have spinning issues now.
@Jcolomar @crvfts thanks for your help. Sorry, I'can give a quick test reply because I got 2 whole days of "Server busy or offline, reconnecting in 723 seconds". But I can still login using my phone and the hash key is not expired. I would like to know, did it happen also to you? Or I'm the lucky man : )
server hashing has a lot of issues, it happens to all.
the "server busy" message you're getting is due to hashing server instability. tons of people getting it, you're not alone on that one. it should be fixed fairly soon. worth the wait, your hash key expiration date will be extended to compensate for the lost time.
I'm getting this same problem (never making progress towards the next Pokestop) for the last couple days, with the default config.
@kranzrm I set walk_max: 9 walk_min: 2 and disable the location_cache although still happening but obviously better than before. One or two times a day
I'm seeing this issue as well with a clean install of python and the repo. Runs for about 5-10 minutes then hangs while walking to a fort.
my "frankenbot" of pokemongof running just fine, though. doesn't seem to be related to hashing.
@crvfts I suggest you to use path config instead of MoveToFort. It happens no more after using custom geolocation
Have we gotten to the bottom of whats causing this? Is it config?
My config is:
"location_cache": false,
"type": "MoveToFort",
"config": {
"enabled": true,
"lure_attraction": true,
"lure_max_distance": 2000,
"walker": "StepWalker",
"log_interval": 5
"walk_max": 4.16,
"walk_min": 2.16,
Has anyone got a set of working config that reliably works? Clearing out the account files created in ../data/ seems to fix it for a short period, but not a long term solution
The problem is after the recent update!In the forward but never to the destination!
[2017-06-29 13:34:20] [MoveToFort] [INFO] Moving towards pokestop Eingangswächter Schillstraße - 0.13km [2017-06-29 13:34:25] [MoveToFort] [INFO] Moving towards pokestop Eingangswächter Schillstraße - 0.13km [2017-06-29 13:34:31] [MoveToFort] [INFO] Moving towards pokestop Eingangswächter Schillstraße - 0.12km [2017-06-29 13:34:36] [MoveToFort] [INFO] Moving towards pokestop Eingangswächter Schillstraße - 0.13km [2017-06-29 13:34:49] [MoveToFort] [INFO] Moving towards pokestop Eingangswächter Schillstraße - 0.12km [2017-06-29 13:34:58] [MoveToFort] [INFO] Moving towards pokestop Eingangswächter Schillstraße - 0.13km [2017-06-29 13:35:06] [MoveToFort] [INFO] Moving towards pokestop Eingangswächter Schillstraße - 0.12km [2017-06-29 13:35:14] [MoveToFort] [INFO] Moving towards pokestop Eingangswächter Schillstraße - 0.12km
config.json