Simple Heiken Ashi Candle Condition problem
-
I am unsure whether this is user error.
I wish to write a log message with a simple (bullish) signal:
- Previous HA H4 candle has no bottom wick
- Current price breaks above previous H4 candle high
Same with bearish signal:
- Previous HA H4 candle has no top wick
- Current price breaks below previous H4 candle low
So the below would be a bullish signal and I would like to write a message to log file.

But I am having problems with the conditional statement which is not working as expected.
I am checking the HA open is the same as the low. This would mean bottom of candle has no wick. But the conditional statement seems to provide incorrect output in some scenarios. For example, the prev H4 in this instance definitely has a bottom wick. And you can see values in data window, but my EA is not functioning correctly, it should simply output 'Has Bottom Wick' to log:

Here is shared project, can anyone advise on what I'm doing wrong? I have tried numerous combinations in the 'chosen candle type'/'previous candle type' as well. Can't get it to work.
(Ignore the blocks to the right, they are turned off anyway):
https://fxdreema.com/shared/IvP3gqDbb -
You are nor selecting any kind of candle type in blocks 18 and 32. IIRC, those locks don't work correctly unless candle types are specified.
-
Even when I specify candle types I am getting some very strange behaviour that is unexpected.
Find a pair that has current/previous HA candles that are different and I always get flase positives.
I've even tried simply detecting whether current/previous candle are both same direction, again, false positives. The way the block works is confusing in the documentation, or there is some kind of bug.
For example:

If you leave '--' in the dropdown for 'previous candle type', is previous candle ignored? Is that allowed? Clarity from admin would be great on this! -
And if the block does not pass, how do you control behaviour if it's in a loop? Does current loop just stop? And you can't process blocks afterwards to output error messages to trace bug etc?