alleyway / add-tradingview-alerts-tool

Automated entry of TradingView alerts for bot trading tools such as 3Commas, Alertatron, CryptoHopper, etc.
MIT License
636 stars 141 forks source link

Issue with tertiaryRight condition #51

Closed zerocomte closed 3 years ago

zerocomte commented 3 years ago

Hello guy,

I try this: alert: condition: primaryLeft: MA Emperor insiliconot primaryRight: P secondary: Croisement vers le haut tertiaryLeft: MA Emperor insiliconot tertiaryRight: MA 2 quaternaryLeft: quaternaryRight:

Step Primary is ok Step Secondary is ok Step tertiaryLeft is ok Step tertiaryRight is ko

This last one can't be change, it could not open the dropdown menu.

Error: ERROR waiting for XPath (//div[contains(@class, 'tv-alert-dialog__group-item--right ')]/div[contains(@class, 'js-number-input')]/input)[1] failed: timeout 3000ms exceeded

I am using the version 1.8.0.

Kind regards, Thomas

ramnite commented 3 years ago

I am using:

After being able to upgrade to ATAT latest version (https://github.com/alleyway/add-tradingview-alerts-tool/issues/54), I am experiencing the same issue as @zerocomte with the tertiaryRigh condition. In my case, my alert is very simple, nothing fancy. Just a MACD Line crossing up the MACD Signal.

The alert creation process seems to work fine until it reaches the tertiaryRigh condition ("Signal", in my case), which triggers the following error:

 ERROR  waiting for XPath (//div[contains(@class, 'tv-alert-dialog__group-item--right ')]/div[contains(@class, 'js-number-input')]/input)[1] failed: timeout 3000ms exceeded

  at new WaitTask (/usr/local/lib/node_modules/@alleyway/add-tradingview-alerts-tool/node_modules/puppeteer/src/common/DOMWorld.ts:780:28)
  at DOMWorld.waitForXPath (/usr/local/lib/node_modules/@alleyway/add-tradingview-alerts-tool/node_modules/puppeteer/src/common/DOMWorld.ts:675:22)
  at Frame.waitForXPath (/usr/local/lib/node_modules/@alleyway/add-tradingview-alerts-tool/node_modules/puppeteer/src/common/FrameManager.ts:1193:47)
  at Page.waitForXPath (/usr/local/lib/node_modules/@alleyway/add-tradingview-alerts-tool/node_modules/puppeteer/src/common/Page.ts:2111:29)
  at fetchFirstXPath (/usr/local/lib/node_modules/@alleyway/add-tradingview-alerts-tool/src/service/tv-page-actions.ts:15:20)
  at performActualEntry (/usr/local/lib/node_modules/@alleyway/add-tradingview-alerts-tool/src/service/tv-page-actions.ts:208:50)
  at configureSingleAlertSettings (/usr/local/lib/node_modules/@alleyway/add-tradingview-alerts-tool/src/service/tv-page-actions.ts:238:5)
  at addAlert (/usr/local/lib/node_modules/@alleyway/add-tradingview-alerts-tool/src/service/tv-page-actions.ts:331:5)
  at addAlertsMain (/usr/local/lib/node_modules/@alleyway/add-tradingview-alerts-tool/src/add-alerts.ts:209:9)
  at Command.<anonymous> (/usr/local/lib/node_modules/@alleyway/add-tradingview-alerts-tool/src/cli.ts:67:13)

Could this be related to the puppeteer-related errors I get when I try to update my tradingview-alerts-home?

Screen Shot 2021-05-10 at 13 32 35

mlake commented 3 years ago

Could each of you try installing a beta release and confirm the fix?

npm install @alleyway/add-tradingview-alerts-tool@beta

@ramnite looks like you have a permissions issue from all the sudo commands... You could try the following:

sudo chown -R $(whoami) .

To avoid permissions hell, you might want to think about installing NVM: https://github.com/nvm-sh/nvm

zerocomte commented 3 years ago

image

I installed. I tried. But same resultat. It can't found the dropdown list.

failed

mlake commented 3 years ago

@zerocomte I should have mentioned that you should run that command in the same directory your config files are located..

lools like you're doing everything in "C:/Users/thomas/Documents/TV/" so that's where you should run the command

the ATAT Version should end being 1.8.4-beta.0

zerocomte commented 3 years ago

Oh sorry, my mistake!

zerocomte commented 3 years ago

Now, with update into the good repository, That is working great:

image

mlake commented 3 years ago

ça roule...i will close this issue then! Happy alerting!

zerocomte commented 3 years ago

Merci!

Have a nice day!

ramnite commented 3 years ago

Thanks for the tip about permissions. I will look into it later, unless you think that it is related to my current issue.

Unlike zerocomte, the issue persists for me. As you can see, I have installed the beta version but still receiving the same error:

Screen Shot 2021-05-10 at 14 56 17