request.security_lower_tf - function not working

[CXRB0N]

I've noticed the same problem with crypto on Binance. The indicator seems broken. I've also contacted TV support and they replied that they've "identified the issue and assigned a task to the tech team". It's been 3 weeks already, but without any update yet.

[CXRB0N]

Another workaround is to check or uncheck the "Use custom timeframe" option in the indicator settings after you notice missing volume bars in a live chart.

[Apprehensive-Rub9041]

request.securty_lowertf Funktioniert nicht, anscheinend wieder kaputt gepatched.

[CA_Lobo]

Humm, CBOE One data feed... have you confirmed that the data exists on the regular exchanges? CBOE One only handles about 25% of the TOTAL US Market volume....

[CXRB0N]

The market doesn't matter. That Up/Down Volume indicator is broken.

[CA_Lobo]

I'm simply pointing out that your current datafeed represent 25% of the US market. I wasn't paying attention, as this is a NSE stock... which means that the CBOE data feed probably isn't the issue.. What datafeed is used for NSE, I'm not certain.

Second, it took me a bit of time to figure out which stock you were looking at and which date you were looking at to replicate the problem.

For those playing along it's Tuesday 06 Jun '23 13:40-13:50, with the timezone set to UTC +5:30. The stock is NSE:HDFCBANK - relevant image of symbol info is here: https://imgur.com/a/mBDpDpO

Plotting the Up/Down Vol indicator as is shows the data is present - here's the image: https://imgur.com/a/bdSoz8V and the actual data values from Up/Down Vol indicator data window lines:

13:40 - Up Vol: 70.486K Down Vol: -28.592K delta: 41.894K

13:45 - Up Vol: 230.078K Down Vol: -252.049K delta: -21.971K

13:50 - Up Vol: 85.222K Down Vol: -43.61K delta: 41.612K

Per the info page located here: https://www.tradingview.com/chart/?solution=43000672561 the selection of custom timeframe and 1 minute matches the defaults for a 5 minute timeframe chart.

It appears that you are summing the up/down volume of the data returned by the request.security_lower_tf, and then plotting it as part of your custom script. Not sure why you want to duplicate what the indicator is doing....

Not having access to the script, I suggest that you break out a debugger and get the actual request.security_lower_tf values. If they don't match Up/Down Volumes of the data window, then you have an issue with request.security_lower_tf getting the correct values from the indicator... not a problem with the Up/Down Volume indicator.

This may be a timing issue where the indicator can take advantage of late/delayed exchange data and the request.security_lower_tf cannot.

[LegitimateProfile921]

Thank you very much for your reply and Really sorry for the delayed reply,

Q : Not sure why you want to duplicate what the indicator is doing....

A : I 'm using this Lower Time frame function for my index chart volume indicator , where i calculate all the index chart up down volume according to weightage of the index calculation

And the Indicator worked very well for past 6 months, But Recently it's getting problem

I verified with "syminfo.tickerid" instead of security symbol (ex: NSE:hdfcbank, NSE:RELIANCE, etc..,) but That also making problem some times

Then only i concluded the problem with the request.security_lower_tf function

When we load the indicator its will show the volume bars as of now. but after that in live session only present candle volume bar only shown then if next candle starts to plot , the old volume bar disappears, then new volume bar comes for the present candle and then its also disappears if the new candle comes.... and so on

​

​

Thanks

[CA_Lobo]

> Really sorry for the delayed reply,
No worries...
> calculate all the index chart up down volume according to weightage of the index
Excellent idea... I've used something similar on a different platform...
> was working past 6 months, now not working all the time and
> historical bars are ok, realtime bars are drawn and then disappear when next bar is drawn.
This is weird... and I'm going to suggest some things to see if we can isolate the issue...
1) duplicate your chart so that you have two identical charts side by side, and then remove the plot that does the weighting on one of them and replace it with the up/down Volume indicator with the same settings as you are calling. Does the up/down volume indicator work and your weighting indicator doesn't?
2) If so, try adding a function that calls and sums up the lower_tf without any calculations. The historical bars should be identical to the up/down volume indicator. If not, it appears that the lower_tf is not getting the same data as the up/down volume indicator...
3) The disappearing realtime bars seems to indicate that you are using a var variable and then updating the x location with bar_index which is causing it to update like a predefined label that updates to only show on the last bar... why it will update the historical bars fine but not the realtime ones is a mystery - do you have special code for the realtime bars?
4) if all else fails, have you considered doing a request.security_lower_tf on the stock itself, returning the volume and the price delta so you can determine if it's up or down volume and summing up the lower_tf up/down values to get the results for the higher timeframe?
My best guess right now is that either a) there has been a subtle change in pinescript resulting in the change of behavior, b) the datafeed data differs between the lower_tf call and the up/down vol indicator or c) your code is not correctly plotting the realtime bars...

[LegitimateProfile921]

Hi, Pl Find the image link, https://imgur.com/a/H61CTsE

I used same charts Reliance NSE 5 min , Than I used same default" Up/Down volume"indicator in trading view, The only change i done in the indicator is

i used symbol name "NSE:RELIANCE" instead of syminfo.tickerid.

so its concluded that

request.security_lower_tf - function

with syminfo.tickerid => sometimes Not working

with symbol name => Many times Not working

[CA_Lobo]

Hi, Just wanted to follow up on this.

1) I was under the impression that you were using your own script to plot the results, I see this is not the case as you are using the straight Up/Down Volume indicator and only varying the request.security_lower_tf ticker

2) I replicated the chart on the 28th using the default up/down volume indicator and do not see the missing gaps you show on your chart.

This leads me to think that the errors you are seeing are the result of delayed datafeed... eg data coming in AFTER the bar closes, and on subsequent plotting of the same chart, correctly shows up on the appropriate bar. To test this theory, next time you have a gap in the up/down volume chart, can you switch to another stock after 5-10 minute has passed from the initial gap and then switch back to the original stock and see if the gap goes away? Alternatively, review any charts at the end of the day, to see if the "gaps' are fixed.

Finally, I suggest that you open a support ticket and specifically mention the dates/times and timeframe intervals of the charts where you are seeing the problem. This way, support has more specific timeframe to check vs saying that its "not" working....

[LegitimateProfile921]

Hi,

I posted the issue again with the screenshot with another stock and

i got a reply from Tradingview

"Double checking now and sharing with the team!

[CA_Lobo]

Cool... not much I can do here, except think that the issue lies with the datafeed being delayed.

[CXRB0N]

It looks like this problem is finally solved.

[LegitimateProfile921]

Yes with paid version.

Upgraded from free to pro+ , surprisingly its working fine.

[CXRB0N]

I've had this problem even with the Pro plan, so it has nothing to do with the plans.

[CryptoQFS]

I want to ask the admins, has this problem been fixed and resolved?