New beta version of Bet Angel v1.55.0 - now on general release

[jimibt]

V.1.55.0 is a NIGHTMARE!! So many things now do not work and I want to go back to the previous version. Every attempt so far just re-loads V1.55 ........... any ideas??

i've not experienced any issues tbh. maybe as Dallas mentions, just pop a list of the issues into a message and maybe it will shed light on a potential fix (if it exists).

I found that i had to perform a reboot on one of the previous installs as it actually couldn'r get it to update.

[Vovsen]

There seems to be an issue when storing the VWAP Book % of a selection, it does not return correct values when using "ANY":

VWAP.PNG

I have not used it before this version of BA.

In this rule I am already storing the back and lay book %, for every selection row, which is working as it should.

But if I try to store the VWAP%, it gives the same value for every selection, instead of just one value for a certain row, that I have defined for the stored values.

If I use "EVERY" selection the other prices do not work, but they do work when I use "ANY", VWAP however does not.

[Dallas]

There seems to be an issue when storing the VWAP Book % of a selection, it does not return correct values when using "ANY":

VWAP.PNG

I have not used it before this version of BA.

In this rule I am already storing the back and lay book %, for every selection row, which is working as it should.

But if I try to store the VWAP%, it gives the same value for every selection, instead of just one value for a certain row, that I have defined for the stored values.

If I use "EVERY" selection the other prices do not work, but they do work when I use "ANY", VWAP however does not.

Can you post the rule file or log from it if its set up correctly there should be no problems?

There are several example rules i put on the forum in the last few weeks that use applied to 'EVERY' selection and even some also store the VWAP% so know I thats always worked exactly as it should, but just ran a test rule to show it below anyway.

When applying a rule to ANY selection it will always start by looking at the selection in betfair row 1, then row 2, then row 3, and so on, and will always trigger on the first selection to meet its criteria,so if using no conditions it will just continullly trigger on Row1
Again thats the way applying a rule to 'ANY' selection should and always has worked.

Log.jpg

[Vovsen]

There seems to be an issue when storing the VWAP Book % of a selection, it does not return correct values when using "ANY":

VWAP.PNG

I have not used it before this version of BA.

In this rule I am already storing the back and lay book %, for every selection row, which is working as it should.

But if I try to store the VWAP%, it gives the same value for every selection, instead of just one value for a certain row, that I have defined for the stored values.

If I use "EVERY" selection the other prices do not work, but they do work when I use "ANY", VWAP however does not.

Can you post the rule file or log from it if its set up correctly there should be no problems?

There are several example rules i put on the forum in the last few weeks that use applied to 'EVERY' selection and even some also store the VWAP% so know I thats always worked exactly as it should, but just ran a test rule to show it below anyway.

When applying a rule to ANY selection it will always start by looking at the selection in betfair row 1, then row 2, then row 3, and so on, and will always trigger on the first selection to meet its criteria,so if using no conditions it will just continullly trigger on Row1
Again thats the way applying a rule to 'ANY' selection should and always has worked.


Log.jpg

Thanks Dallas for the quick response. I will try to upload more info going forward instead of typing so much as I am not very good with words.

Here is the log where you can see that Lay and Back % is working fine, but VWAP is not.

VWAPnotWorking.PNG

And here is example rule file, it uses the Condition of text "Match Odds":

VWAPtest.baf

[Dallas]

There seems to be an issue when storing the VWAP Book % of a selection, it does not return correct values when using "ANY":

VWAP.PNG

I have not used it before this version of BA.

In this rule I am already storing the back and lay book %, for every selection row, which is working as it should.

But if I try to store the VWAP%, it gives the same value for every selection, instead of just one value for a certain row, that I have defined for the stored values.

If I use "EVERY" selection the other prices do not work, but they do work when I use "ANY", VWAP however does not.

Can you post the rule file or log from it if its set up correctly there should be no problems?

There are several example rules i put on the forum in the last few weeks that use applied to 'EVERY' selection and even some also store the VWAP% so know I thats always worked exactly as it should, but just ran a test rule to show it below anyway.

When applying a rule to ANY selection it will always start by looking at the selection in betfair row 1, then row 2, then row 3, and so on, and will always trigger on the first selection to meet its criteria,so if using no conditions it will just continullly trigger on Row1
Again thats the way applying a rule to 'ANY' selection should and always has worked.


Log.jpg

Thanks Dallas for the quick response. I will try to upload more info going forward instead of typing so much as I am not very good with words.

Here is the log where you can see that Lay and Back % is working fine, but VWAP is not.
VWAPnotWorking.PNG

And here is example rule file, it uses the Condition of text "Match Odds":
VWAPtest.baf

Thanks for the rules file, and for flagging this up.

After looking into we can confirm that is a genuine bug you've found caused when using the combination of applying a rule to 'ANY' selection, and using 'Nominated' selection on the SV tab, to store the VWAP%, we also found it also the same when storing just the VWAP (all others work fine).

The build is due to go on general release shortly so we'll get that fixed before then.

In the mean time using the 'Every' selection you should be able to work around what you need to do, if not if you start a new thread we details of exactly what you want to achieve i'll take a look and see what can be advised

[StevieB]

V.1.55.0 is a NIGHTMARE!! So many things now do not work and I want to go back to the previous version. Every attempt so far just re-loads V1.55 ........... any ideas??

What specifcally isn't working?

It been working fine for everyone else using it apart from the two minor bug fixes below both found and fixed several weeks ago
ladder cells were not changing colour as mouse tracked over them
matched bets not showing in Guardian if you navigate the markets in a certain way

For Example:
In Guardian / Used to be able to select various markets.....then hit apply auotmation rule to the selected selected markets (doesn't work on V1.55). ////// Same issue when trying to delete selected markets.

There are more examples but I want to see your response (maybe its just me!) - thanks

[Dallas]

V.1.55.0 is a NIGHTMARE!! So many things now do not work and I want to go back to the previous version. Every attempt so far just re-loads V1.55 ........... any ideas??

What specifcally isn't working?

It been working fine for everyone else using it apart from the two minor bug fixes below both found and fixed several weeks ago
ladder cells were not changing colour as mouse tracked over them
matched bets not showing in Guardian if you navigate the markets in a certain way

For Example:
In Guardian / Used to be able to select various markets.....then hit apply auotmation rule to the selected selected markets (doesn't work on V1.55). ////// Same issue when trying to delete selected markets.

There are more examples but I want to see your response (maybe its just me!) - thanks

Theres nothing changed in respect to selecting multiple markets in Guardian, with the CTRL key held down you just left click the markets you want to select.

Another method is to select one market then with your left mouse button held down move your cursor over other markets to automatically select them.
To do this you need to ensure you have the 'Allow drag and drop' option in your behaviour settings unticked (as two actions can't be performed at the same time)
Thats been this way since the drag and drop option was added a few versions ago so doubt thats what you'll be refering to?

Can you post a screenshot of your Guardian with some markets added so i can see how it looks? I suspect you may just have a corrupted settings file

[firlandsfarm]

Hi, could I ask for a confirmation of how the "Every Selection" trigger works. If I select for the rule to trigger 1 time (and let's assume the default for rearming is left at 5 seconds) how will things play out …

1. Is the rule applied just the once to each selection and is triggered for any that meet the Conditions at that time but if the Conditions are not met on that one occasion - tough, it fails forever? So the "1" applies to a single application of the rule to each selection, or
2. Does the rule continue to be applied to each selection until the selection meets the Conditions once. So the "1" applies to each selection individually, and
3. If it's 1. then the 5 second rearm default is irrelevant but if 2. would the 5 second rearm delay be applied before re-testing those that failed the Conditions first time or does the rule constantly re-test those that failed the conditions previously?

[Dallas]

Hi, could I ask for a confirmation of how the "Every Selection" trigger works. If I select for the rule to trigger 1 time (and let's assume the default for rearming is left at 5 seconds) how will things play out …

1. Is the rule applied just the once to each selection and is triggered for any that meet the Conditions at that time but if the Conditions are not met on that one occasion - tough, it fails forever? So the "1" applies to a single application of the rule to each selection, or
2. Does the rule continue to be applied to each selection until the selection meets the Conditions once. So the "1" applies to each selection individually, and
3. If it's 1. then the 5 second rearm default is irrelevant but if 2. would the 5 second rearm delay be applied before re-testing those that failed the Conditions first time or does the rule constantly re-test those that failed the conditions previously?

When it triggers it does so on every selection that meets your conditions, it then won't trigger on any of them again until it rearms.

It will then try and trigger on every selection again (both those it triggered on the previous time and those it never) unless you are using a condition/s like matched/unmatched bets to prevent it triggering on selections more than 'X' times

[convoysur-2]

Hi.I placed some trades just after a goal was scored ,then it was cancelled 1-2 -3 mins later. Betfair cancelled the bets and my full balance became available again, BUT on the betangel 3.5 it never corrected itself, so i waited for some time ,but its still the same 25 mins later .

[Vovsen]

Can you post the rule file or log from it if its set up correctly there should be no problems?

There are several example rules i put on the forum in the last few weeks that use applied to 'EVERY' selection and even some also store the VWAP% so know I thats always worked exactly as it should, but just ran a test rule to show it below anyway.

When applying a rule to ANY selection it will always start by looking at the selection in betfair row 1, then row 2, then row 3, and so on, and will always trigger on the first selection to meet its criteria,so if using no conditions it will just continullly trigger on Row1
Again thats the way applying a rule to 'ANY' selection should and always has worked.


Log.jpg

Thanks Dallas for the quick response. I will try to upload more info going forward instead of typing so much as I am not very good with words.

Here is the log where you can see that Lay and Back % is working fine, but VWAP is not.
VWAPnotWorking.PNG

And here is example rule file, it uses the Condition of text "Match Odds":
VWAPtest.baf

Thanks for the rules file, and for flagging this up.

After looking into we can confirm that is a genuine bug you've found caused when using the combination of applying a rule to 'ANY' selection, and using 'Nominated' selection on the SV tab, to store the VWAP%, we also found it also the same when storing just the VWAP (all others work fine).

The build is due to go on general release shortly so we'll get that fixed before then.

In the mean time using the 'Every' selection you should be able to work around what you need to do, if not if you start a new thread we details of exactly what you want to achieve i'll take a look and see what can be advised

Thanks again Dallas,

I have been trying to come up with a way to use the every selection as a temporary work around, but have been unable to, so I will just wait for the fix.

Is there perhaps a reason why the VWAP% is there to store as a value, however High% and Low% is not?

[Anbell]

Here's a couple of lines from my log:

9/2/2020 07:29:47: [G_Auto] : Unable to : Store: 'Liability' for current selection. First value invalid.
9/2/2020 07:29:48: [G_Auto] : Store Value for 11. Mozzie Monster: NewLiability = 1000 - 0

For debugging purposes it would be handy if the first line (the error line) included the name of the selection (in the same manner as the 2nd line), rather than just " for current selection"

[Bet Angel]

Hi.I placed some trades just after a goal was scored ,then it was cancelled 1-2 -3 mins later. Betfair cancelled the bets and my full balance became available again, BUT on the betangel 3.5 it never corrected itself, so i waited for some time ,but its still the same 25 mins later .

It's to do with the way betfair void the matched bets and sometimes reinstate the matched bets as unmatched ones. We've flagged it to betfair development and they are looking into adding extra messaging on the API to cater for such situations. It can also occasionally happen with false starts in horse racing & greyhounds.

[Bet Angel]

9/2/2020 07:29:47: [G_Auto] : Unable to : Store: 'Liability' for current selection. First value invalid.

The 'first value invalid' message occurs when you lookup something that doesn't exist. e.g. A stored value that has never been initialised or using an invalid price.

We'll make a note to look into the use of 'current selection' to see if it knows enough at that point in the code to specifically log which selection by name.

[Anbell]

9/2/2020 07:29:47: [G_Auto] : Unable to : Store: 'Liability' for current selection. First value invalid.

The 'first value invalid' message occurs when you lookup something that doesn't exist. e.g. A stored value that has never been initialised or using an invalid price.

We'll make a note to look into the use of 'current selection' to see if it knows enough at that point in the code to specifically log which selection by name.

Cheers.

Yeah, I understand why *I* caused an error. I'm not complaining about that at all.

It would be handy to specify the specific 'current selection' if you could. I'd be surprised if you couldn't, but I don't know a whole lot.