Help with a tennis bot

[captainbang]

I have a bot that i am testing and has been working fine up until this afternoon.

the bot is pretty much the same as Dallas's alert for a dominant server but instead of an alert it places a back bet.

But i have noticed in the challenger matches that started in the USA at 4pm today that it seems to just place a back bet straight away. for example the in the match couacaud v ignatik the favourite is 0-3 behind now so how did a back bet get placed if he hasnt even won a game?

when i check the log, there is no record of the back bet, details below

10/01/2019 18:08:37: Guardian has detected that the market is in-play
10/01/2019 18:08:37: Guardian has detected that the market is suspended
10/01/2019 18:08:43: [G_Auto] : Automation Signal for Enzo Couacaud: fav = 1
10/01/2019 18:08:43: [G_Auto] : Automation Signal for Uladzimir Ignatik: 2nd = 1
10/01/2019 18:08:43: Guardian has detected that the market is now unsuspended
10/01/2019 18:13:26: [G_Auto] : Automation Signal for Enzo Couacaud: dom = 1
10/01/2019 18:13:26: [G_Auto] : Automation Signal for Enzo Couacaud: dom - Cleared
10/01/2019 18:13:40: [G_Auto] : APING Exception: TIMEOUT, ,
10/01/2019 18:14:30: [G_Auto] : Automation Signal for Enzo Couacaud: dom = 1
10/01/2019 18:16:40: [G_Auto] : Automation Signal for Enzo Couacaud: dom - Cleared

I noticed in a previous match that a second back bet went in on the favourite after he won the 1st set, but i have the bot to only trigger once. The second bet was captured in the log file but the first one again wasnt.

As said this bot was working fine untill 4pm today. Any ideas anyone?

thanks

[captainbang]

looking at the time my bet was placed on betfair which was at 18:13:41 it seems it may have something to do with APING Exception: TIMEOUT, listed below. What does this mean?

10/01/2019 18:13:40: [G_Auto] : APING Exception: TIMEOUT,

[captainbang]

I have observed a further two matches with the same issue.

It seems whatever this APING is a bet is being paced into betfair either 1 or 2 seconds later but again no record of the bet in the guardian log.

image below shows the bet matched times from betfair
https://www.photobox.co.uk/my/photo/ful ... 1566547969

Logs from guardian below, and in each no record of any bets

10/01/2019 18:09:45: Guardian has detected that the market is in-play
10/01/2019 18:09:45: Guardian has detected that the market is suspended
10/01/2019 18:09:51: [G_Auto] : Automation Signal for Lucas Miedler: fav = 1
10/01/2019 18:09:51: [G_Auto] : Automation Signal for Mario Vilella Martinez: 2nd = 1
10/01/2019 18:09:51: Guardian has detected that the market is now unsuspended
10/01/2019 18:12:12: [G_Auto] : Automation Signal for Lucas Miedler: dom = 1
10/01/2019 18:12:12: [G_Auto] : Automation Signal for Lucas Miedler: dom - Cleared
10/01/2019 18:12:26: [G_Auto] : APING Exception: TIMEOUT, ,
10/01/2019 18:13:17: [G_Auto] : Automation Signal for Lucas Miedler: dom = 1
10/01/2019 18:44:23: [G_Auto] : Automation Signal for Lucas Miedler: dom - Cleared
10/01/2019 18:57:31: [G_Auto] : Automation Signal for Lucas Miedler: dom = 1
10/01/2019 19:17:13: [G_Auto] : Automation Signal for Lucas Miedler: dom - Cleared
10/01/2019 19:28:52: [G_Auto] : Automation Signal for Lucas Miedler: dom = 1
10/01/2019 19:31:45: [G_Auto] : Automation Signal for Lucas Miedler: dom - Cleared
10/01/2019 19:33:01: Guardian has detected that the market is suspended
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

10/01/2019 18:08:37: Guardian has detected that the market is in-play
10/01/2019 18:08:37: Guardian has detected that the market is suspended
10/01/2019 18:08:43: [G_Auto] : Automation Signal for Enzo Couacaud: fav = 1
10/01/2019 18:08:43: [G_Auto] : Automation Signal for Uladzimir Ignatik: 2nd = 1
10/01/2019 18:08:43: Guardian has detected that the market is now unsuspended
10/01/2019 18:13:26: [G_Auto] : Automation Signal for Enzo Couacaud: dom = 1
10/01/2019 18:13:26: [G_Auto] : Automation Signal for Enzo Couacaud: dom - Cleared
10/01/2019 18:13:40: [G_Auto] : APING Exception: TIMEOUT, ,
10/01/2019 18:14:30: [G_Auto] : Automation Signal for Enzo Couacaud: dom = 1
10/01/2019 18:16:40: [G_Auto] : Automation Signal for Enzo Couacaud: dom - Cleared
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

10/01/2019 18:03:24: Guardian has detected that the market is in-play
10/01/2019 18:03:24: Guardian has detected that the market is suspended
10/01/2019 18:03:29: [G_Auto] : Automation Signal for Marcos Giron: fav = 1
10/01/2019 18:03:29: [G_Auto] : Automation Signal for Bernabe Zapata Miralles: 2nd = 1
10/01/2019 18:03:29: Guardian has detected that the market is now unsuspended
10/01/2019 18:08:01: [G_Auto] : Automation Signal for Marcos Giron: dom = 1
10/01/2019 18:32:25: [G_Auto] : Automation Signal for Marcos Giron: dom - Cleared
10/01/2019 18:38:50: [G_Auto] : Automation Signal for Marcos Giron: dom = 1
10/01/2019 18:38:50: [G_Auto] : Automation Signal for Marcos Giron: dom - Cleared
10/01/2019 18:39:04: [G_Auto] : APING Exception: TIMEOUT, ,
10/01/2019 18:39:52: [G_Auto] : Automation Signal for Marcos Giron: dom = 1
10/01/2019 18:41:26: [G_Auto] : Automation Signal for Marcos Giron: dom - Cleared

[Dallas]

An 'APING Exception: TIMEOUT' means Betfair didn't respond in a reasonable amount of time, perhaps if you're using WiFi or you've had a poor/intermittent loss of connection occurring today
If it persists you could try increasing the setting of your 'Dynamic Connection tuner' to make it less sensitive to a slow response, you can do this by clicking;
Settings > Edit Settings > Communications

[captainbang]

Thanks Dallas, I will try that.

[captainbang]

hopefully its sorted now. A bet just got placed at 1-1 and the bet is showing in the log now.

I have betangel refreshing at 200ms and changed the Dynamic Connection tuner from 6 to 9

log below.

Thanks again Dallas, you're a gent

10/01/2019 22:25:59: Guardian has detected that the market is in-play
10/01/2019 22:25:59: Guardian has detected that the market is suspended
10/01/2019 22:26:03: [G_Auto] : Automation Signal for Laurynas Grigelis: fav = 1
10/01/2019 22:26:03: [G_Auto] : Automation Signal for Jan Choinski: 2nd = 1
10/01/2019 22:26:03: Guardian has detected that the market is now unsuspended
10/01/2019 22:29:57: [G_Auto] : Automation Signal for Laurynas Grigelis: dom = 1
10/01/2019 22:29:57: [G_Auto] : Automation Signal for Laurynas Grigelis: dom - Cleared
10/01/2019 22:30:02: [G_Auto] : € 2.00 Back bet placed on Laurynas Grigelis at 1.7. Fully matched at 1.74. Ref: 150380844127 ( Offsetting by 50% [A] with greening. )
10/01/2019 22:30:07: [G_Auto] : € 3.45 Lay bet placed on Laurynas Grigelis at 1.01. Entirely unmatched when it initially reached the market. Ref: 150380845739

[captainbang]

An 'APING Exception: TIMEOUT' means Betfair didn't respond in a reasonable amount of time, perhaps if you're using WiFi or you've had a poor/intermittent loss of connection occurring today
If it persists you could try increasing the setting of your 'Dynamic Connection tuner' to make it less sensitive to a slow response, you can do this by clicking;
Settings > Edit Settings > Communications

Hi Dallas, It seems this problem persists even after connecting a LAN cable to the router. I thought that using the cable would stop this as I have 200MB broadband?

Today I was running 2 instances of betangel as I was testing a slightly altered version of the bot I am using in live mode.
Apart from noticing that both my bots are not working as designed I noticed that this APING exception only occurs in live mode. All practice bets had no error.

The problem with this APING exception error is that it still places the back bet but not the lay bet, so I have to watch what I can otherwise its just a straight bet. But if I manually place a lay bet and its matched and there is another occassion in the match that fits the criteria and because the initial bet is not captured in the log file betangel places another back bet in as it doesnt know there was already one. The second bet will mostly be recognised the second time.

Id appreciate any further advice.