Fastk value is not used correctly about freqtrade

[xmatthias]

Freqtrade only cares about the signal columns (enter_long, enter_short, ...).
How you get to that is completely up to the strategy (author).
So there's no "known issue" here - if fastk is ignored - it's your strategy ignoring that.

Now to some degree, we can assist with that - but not with the information you've shared.
with one partial line of a strategy, all we can say is "this compares fastk < 25".
Maybe you combine it wrongly with other indicators, maybe you're looking at the wrong strategy ...

Feel free to provide sufficient information to actually have a look at this - otherwise will close this tomorrow as this is not something that contains even remotely enough information to try to assist further.

[QgitM05]

[QgitM05]

Those are the indicators I am using. Now when I set the fastk value to something crazy like <1, it does not enter any trades. So that means it is using the line in my code. Yet when I set the value to 25, it enters trades even when the %k value at that moment is for exmaple 50 or 60 or whatever. The rest of the indicators are used correctly.

[QgitM05]

Let me know if this is sufficient info and if you need anything else

[xmatthias]

well this tells me that this part is using fastk to check if it's below 25.

if there's other conditions - we don't know. how it's calculated, we don't know.

From what you shared - i can't see anything wrong - though i also can't see what you think is wrong. (maybe you can share a screenshot from freqUI showing that it's > 25 and showing an entry signal ... ?

[QgitM05]

Alright I figured something out. 2 things:

1:
Previously I checked the actual fastk value with cryptowatch.net which is not exactly the same as the data presented and used by freqtrade (UI).

2:
The freqUI shows that indeed the bot bought when the fastk was 39.3 (see image). Yet that's understandable as the bot confirms the signal in a certain candle (the previous candle had fastk 24.8 therefore <25) so it proceeds to buy but the actual entry happens in the following candle.

So in the end it makes sense that the actual value during the entry isn't always <25. And on top of that it's not fair to try to match the freq data with cryptowatch.net

[xmatthias]

well as most indicators - there's parameters for the calculation (iirc, in STOCHF's case, it's several).

i don't know what cryptowatch is using for their calculation - neither do i know what the default for ta-lib is.
Usually, using the default does help - though it's not always guaranteed to yield identical results.

Freqtrade can't / won't really determine "this is the correct value for your strategy to use" - it's your strategy calling a library with (usually sensible) defaults.
if that's not what you want (the defaults) - then simply configure them the way you need them to align with your expectations.

if it still doesn't align - it might be a bug in the library you use - but that's usually not freqtrade - but either ta-lib, pandas_ta, or some other technical indicator library - making it hard for us to help you in this.