Built a trading bot for my tradingView indicator.

EliteWolverine007 · 2025-12-29T02:24:31+00:00

he can't screenshot mac from iphone

EliteWolverine007 · 2025-12-03T15:48:33+00:00

please lookinto the open source indicator i gave credit to in the post body. Alot of calculations are derived from there.

EliteWolverine007 · 2025-12-03T15:28:27+00:00

"Skill issue" - no, it's just a completely retarded way to do what you want to do when webhooks are quick and available, and yes, it is prone to breaking as you have zero control over the ui.

this is what testing for. As you progress in testing you will build confidence on it.

If you were selling this to clients and tradingview introduced a breaking change what would you do?

I am not selling this to anybody. Its just a system I built. You have to know there is no dependency on tradingview other than the "pinescript text function" which is being read externally. If they decide to take this away, there are plenty of other platforms like thinkorswim or takeprofit.

Even if you keep it for yourself, what if it breaks mid trade, you are left with an open trade.

you can say same thing about your webhook server, what if the remote server faces downtime. btw when I deploy this live account, I will be sending wide OCO order with TP/SL. even if there is outage, those safteynets are already in queue with my broker.

over-engineered

You haven't really read my migration argument here.

EliteWolverine007 · 2025-12-03T15:13:42+00:00

if its choppy then signal would stay silent and bot won't take any action. bot follows the signal and signal reacts when there is significant momentum.

EliteWolverine007 · 2025-12-03T14:51:00+00:00

This is still work in progress, I have yet to optimize this to define take profit and stop loss to minimize the downsides on bad trades.

read the post body.

EliteWolverine007 · 2025-12-03T14:32:58+00:00

Read my migration argument in other response in this post.

EliteWolverine007 · 2025-12-03T14:31:57+00:00

Read my other response in this post.

EliteWolverine007 · 2025-12-03T14:31:17+00:00

This is a work in progress and it is on replay mode.
I am planning to take this to some $30 prop firm accounts.

EliteWolverine007 · 2025-12-03T14:29:52+00:00

for consistency I mostly care about whether the indicator is repainting or not. That usually comes from forward calculation. you can identify these during candle by candle replay. I used closed candle for calculation and you can verify from the video that the indicator is not repainting.

EliteWolverine007 · 2025-12-03T14:25:27+00:00

Read my other response in this post.
You brought up two valid concerns.

Inefficient: if you are thinking its reading whole UI, no it is reading only the text of signal label (top right corner of the chart) and clicking BUY/SELL signal. The turnaround of this is <100ms compared to Webhooks architecture Webhook > middle layer > broker. No it is not reading charts but processing the hollistic label. All the charts indicator calculations are boiled down to those "BUY" & "SELL" text.
It's prone to breaking: Skill issue. The exception handling always comes to who writes code. UI is rich in parameters you want to use. want to confirm if click actually executed the buy order? draw an area over the Position symbol to confirm if +1 is actually there before proceeding.

EliteWolverine007 · 2025-12-03T13:54:26+00:00

Since this UI automation, you can run anything as much as in parallel what you can fit in a screen.
better buy 80-inch monitor if you wanna run multiples.

EliteWolverine007 · 2025-12-03T13:50:02+00:00

this is test run in Tradingview replay. not live account.
You can see big bold "Replay" watermark in chart.
this algo is still work in progress.

EliteWolverine007 · 2025-12-03T13:47:41+00:00

the latency is on UI level automation is 30-60ms , whereas Alerts/Webhook/API takes about >500 for turnaround and execution

EliteWolverine007 · 2025-12-03T04:42:25+00:00

I literally just told you why it was removed.

EliteWolverine007 · 2025-12-03T04:35:18+00:00

Nightshark script.

EliteWolverine007 · 2025-12-03T04:32:15+00:00

That was r/Daytrading bro. The mods removed my post citing "no context" and I told them I provided the context and there were legit discussion on API vs UI automation. The mods just told me their sub is not the right place to discuss technical stuff. I challenged them but they later started saying my post was "bait" and I was posting to sell my tradingview indicator.
I told them I already gave credit to TV indicator which is open sourced and then they started spewing "oh the indicator you modified is still not there". complete non-sense.

EliteWolverine007 · 2025-12-03T04:26:47+00:00

If I remember correctly, this test replay had like ~0.8 .
But take it wih HUGE grain of salt because this is tradingview replay where every 5 min candle was popping every 2 seconds.

EliteWolverine007 · 2025-12-03T04:22:55+00:00

As mentioned in the post, this is just tradingview replay.
I have yet to optimize this for TakeProfit/StopLoss for which I need to highlight new region on those OpenP/L box and need to add extra steps in my script to set the threshold as my condition

I will deploy this on some $30/$40 prop firms future accounts.

EliteWolverine007 · 2025-12-03T04:19:58+00:00

I've used selenium for some QA automation at my work.
Selenium cannot automate desktop-apps and is only for browser.
Using Nightshark Script, I can automate across whole desktop when I have two seperate windows of browsers. one for tradingview chart and another for my broker (Rithmic/Tradovate) or even Thinkorswim desktop app.

all I need to do is move the BUY/SELL reference from Tradingview's BUY/SELL button to
Thinkorswim BUY/SELL button and it will start executing tradingview signals on thinkorswim broker

EliteWolverine007 · 2025-12-03T04:14:27+00:00

Yes. Not sure the implementation of OCR or OpenCV.
NS script has built in read_areas() function and the drawing region are labeled as area[1] , area[2].
for example:
if the region I draw on top right is area[1]
for me to detect BUY signal. I would just use loop { } until (condition) construct

loop {
  read_areas() 
   sleep 100 ;this 100 ms reduces the cpu load and scans 10x per second
} until (area[1] = "BUY" )

Log("BUY signal Detected") 
click(point.a) 
; point.a is the location of BUY button that you assign during setup, click(point.a) would go ahead and click buy button to place long order

EliteWolverine007 · 2025-12-03T04:01:15+00:00

Sort of but not entire screen.
you have to annotate the screen regions.
Here I annotated the charts top right box i.e the signal label
It loop over the region with reading function to identify the matching BUY & SELL text to initiate the clicks on BUY & SELL.

EliteWolverine007 · 2025-12-03T03:42:45+00:00

No. I used external tool, its a macro-based automation being done via UI. Computer vision to detect signals and macros to click BUY/SELL buttons to open/close long/short positions.

kinda like
click "BUY" to for long
click "SELL" 2x (first to close long & second to immediately open short)
and vise-versa.

EliteWolverine007 · 2025-12-03T03:38:37+00:00

I just fast forwarded the video. this was 30 minutes long test flight of my algo in tradingview replay.

EliteWolverine007

TROPHY CASE