Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
faq [2019/04/05 09:23] profitview |
faq [2019/04/05 16:06] profitview |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| <accordion> | <accordion> | ||
| + | |||
| <panel title="1) - Once I have paid for PV, when do I receive my registration code?"> | <panel title="1) - Once I have paid for PV, when do I receive my registration code?"> | ||
| Once you have received at least two confirmations on the blockchain, you will receive an email containing your registration code. (Please let us know if you haven't received a registration code within 24hr) | Once you have received at least two confirmations on the blockchain, you will receive an email containing your registration code. (Please let us know if you haven't received a registration code within 24hr) | ||
| Line 9: | Line 10: | ||
| <panel title="2) - How do I request a trial for your indicators?"> | <panel title="2) - How do I request a trial for your indicators?"> | ||
| - | Trials were being abused and are thus no longer offered for indicators. Please join our [[https://discord.profitview.app/|Discord]] Server and see the #results-only channel where you'll find numerous examples showing their effectiveness. | + | Trials were being abused and are thus no longer offered for indicators. |
| + | |||
| + | Please join our [[https://discord.profitview.app/|Discord]] Server and see the ''#results-only'' channel where you'll find numerous examples showing their effectiveness. | ||
| </panel> | </panel> | ||
| Line 16: | Line 19: | ||
| </panel> | </panel> | ||
| - | <panel title="4) - How much do the OCC & Multipass Indicators cost?"> | + | <panel title="4) - How much do the OCC & Multipass Indicators cost?"> |
| OCC & Multipass are each offered at an annual cost of 0.1 BTC per year. | OCC & Multipass are each offered at an annual cost of 0.1 BTC per year. | ||
| </panel> | </panel> | ||
| Line 25: | Line 28: | ||
| <panel title="6) - After I buy ProfitView or an indicator, how do I get help or support?"> | <panel title="6) - After I buy ProfitView or an indicator, how do I get help or support?"> | ||
| - | Once you have bought ProfitView or one of our indicators, use the ''!register'' command in the #bot-commands channel to have our Discord bot guide you through the registration process (make sure you can receive PMs from "non-friends"!). | + | Once you have bought ProfitView or one of our indicators, please join our [[https://discord.profitview.app/|Discord]] Server and use the ''!register'' command in the ''#bot-commands'' channel to have our Discord bot guide you through the registration process (make sure you can receive PMs from "non-friends"!). |
| Just use the same email address you used to buy our product and the license code you got via email, for our indicators use ''occ'' or ''mp'' instead of the license code. | Just use the same email address you used to buy our product and the license code you got via email, for our indicators use ''occ'' or ''mp'' instead of the license code. | ||
| + | \\ | ||
| After you have registered you will have access to all our additional support channels on Discord including channels with different indicator settings ready to use! | After you have registered you will have access to all our additional support channels on Discord including channels with different indicator settings ready to use! | ||
| </panel> | </panel> | ||
| <panel title="7) - Does ProfitView only support OCC/MP or do OCC/MP only work with ProfitView?"> | <panel title="7) - Does ProfitView only support OCC/MP or do OCC/MP only work with ProfitView?"> | ||
| - | Short answer: No! | + | Short answer: **No!** |
| - | ProfitView supports all indicators (not strategies!) available on TradingView that provide alert conditions. The other way around our indicators can also be used with other automation products. | + | \\ |
| + | ProfitView supports **all indicators** (not strategies!) available on TradingView that provide alert conditions. The other way around our indicators can also be used with other automation products. | ||
| Although this is not recommended as ProfitView is currently the best TradingView automation solution available and you would not benefit from its additional features such as advanced alert filtering, monitoring and notifications via Email, Discord, Telegram and more. | Although this is not recommended as ProfitView is currently the best TradingView automation solution available and you would not benefit from its additional features such as advanced alert filtering, monitoring and notifications via Email, Discord, Telegram and more. | ||
| </panel> | </panel> | ||
| Line 38: | Line 45: | ||
| <panel title="8) - How can I backtest the OCC or MP Indicator?"> | <panel title="8) - How can I backtest the OCC or MP Indicator?"> | ||
| While TradingView backtesting is quite limited and not really useful for crypto trading, backtester versions of OCC and MP are still in the works. | While TradingView backtesting is quite limited and not really useful for crypto trading, backtester versions of OCC and MP are still in the works. | ||
| - | Until then you have to manually backtest (count the signals) on the chart and use our Google Sheet to compare the profatibility of different setups: <https://profitview.app/strateval> | + | \\ |
| + | Until then you have to manually backtest (count the signals) on the chart and use our Google Sheet to compare the profatibility of different setups: https://profitview.app/strateval | ||
| + | \\ | ||
| (we are also working on a TradingView addon to quickly export/save the signals from the active chart to make this much easier) | (we are also working on a TradingView addon to quickly export/save the signals from the active chart to make this much easier) | ||
| </panel> | </panel> | ||
| <panel title="9) - Can I setup ProfitView on a VPS? (virtual private server)"> | <panel title="9) - Can I setup ProfitView on a VPS? (virtual private server)"> | ||
| - | Yes, for information on our own VPS service please join our [[https://discord.profitview.app/|Discord]] Server and see the #vps-hosting channel. | + | Yes, for information on our own VPS service please join our [[https://discord.profitview.app/|Discord]] Server and see the ''#vps-hosting'' channel. |
| </panel> | </panel> | ||
| <panel title="10) - In TradingView alerts, what do I have to select?"> | <panel title="10) - In TradingView alerts, what do I have to select?"> | ||
| Under ''Condition'' you have to select your indicator with the settings that you are using on your chart or that you want to run, then in the **wide** dropdown **below** it you select the alert condition (Long/Short etc.). | Under ''Condition'' you have to select your indicator with the settings that you are using on your chart or that you want to run, then in the **wide** dropdown **below** it you select the alert condition (Long/Short etc.). | ||
| + | \\ | ||
| The narrow dropdown right next to the indicator selection only contains the graphs of the indicator which don't influence the main trigger condition and can usually be ignored! | The narrow dropdown right next to the indicator selection only contains the graphs of the indicator which don't influence the main trigger condition and can usually be ignored! | ||
| We also highly recommend that you uncheck all options under ''Alert Actions'', otherwise this can lead to a delay in the alert being picked up by ProfitView. | We also highly recommend that you uncheck all options under ''Alert Actions'', otherwise this can lead to a delay in the alert being picked up by ProfitView. | ||
| + | \\ | ||
| Further make sure you have ''Play Sound'' and general sound notifications in TradingView disabled especially if you use ProfitView on a VPS as this can lead to missed alerts! | Further make sure you have ''Play Sound'' and general sound notifications in TradingView disabled especially if you use ProfitView on a VPS as this can lead to missed alerts! | ||
| + | |||
| + | (Alternatively see the next entry below for information on how to run without any TradingView tabs open) | ||
| </panel> | </panel> | ||
| Line 59: | Line 72: | ||
| If you are still experiencing similar issues, please open the following link in Chrome and change the setting in the dropdown menu on the right to ''Disabled'': | If you are still experiencing similar issues, please open the following link in Chrome and change the setting in the dropdown menu on the right to ''Disabled'': | ||
| <file>chrome://flags/#expensive-background-timer-throttling</file> | <file>chrome://flags/#expensive-background-timer-throttling</file> | ||
| - | Alternatively run Chrome with the command line option ''--disable-background-timer-throttling'' | + | Alternatively run Chrome with the command line option: ''--disable-background-timer-throttling'' |
| The most common causes for this issue are: | The most common causes for this issue are: | ||
| + | \\ | ||
| ➣ Chrome throttling or unloading of background tabs/processes (see above) | ➣ Chrome throttling or unloading of background tabs/processes (see above) | ||
| + | \\ | ||
| ➣ Low resources/memory especially on a VPS | ➣ Low resources/memory especially on a VPS | ||
| + | \\ | ||
| ➣ Using a normal TradingView account on more than one device (eg. your VPS and at home or a mobile device etc.) | ➣ Using a normal TradingView account on more than one device (eg. your VPS and at home or a mobile device etc.) | ||
| + | \\ | ||
| ➣ Saving your chart in a different tab or having unsaved chart changes | ➣ Saving your chart in a different tab or having unsaved chart changes | ||
| + | \\ | ||
| For some of these there are remedies available under ''General Options'' in ProfitView, but they are safety nets and should only be used if the listed causes cannot be resolved! | For some of these there are remedies available under ''General Options'' in ProfitView, but they are safety nets and should only be used if the listed causes cannot be resolved! | ||
| Another possible solution is to close all TV tabs and make ProfitView use the TradingView EventStream only to listen to alerts: | Another possible solution is to close all TV tabs and make ProfitView use the TradingView EventStream only to listen to alerts: | ||
| + | \\ | ||
| Make sure you have ''Auto open TradingView'' **disabled** and **BOTH** ''Reload TradingView'' options **enabled** under ''General Options'', also enabling ''Always keep ProfitView options page open'' is recommended. | Make sure you have ''Auto open TradingView'' **disabled** and **BOTH** ''Reload TradingView'' options **enabled** under ''General Options'', also enabling ''Always keep ProfitView options page open'' is recommended. | ||
| - | (Note: still the same TradingView max devices etc. connection limits apply!) | + | \\ |
| + | (Note: Your TradingView account limits regarding max devices, connection limits etc. still apply!) | ||
| </panel> | </panel> | ||
| <panel title="12) - I have everything set up, do I need to leave a TradingView tab open at all times for each asset I want to trade?"> | <panel title="12) - I have everything set up, do I need to leave a TradingView tab open at all times for each asset I want to trade?"> | ||
| No, one TradingView tab is perfectly fine for ProfitView to receive events from all your active alerts even from different chart timeframes and assets. | No, one TradingView tab is perfectly fine for ProfitView to receive events from all your active alerts even from different chart timeframes and assets. | ||
| + | \\ | ||
| Alternatively you can also run ProfitView without any TradingView tab open, for more on that see the previous entry above. | Alternatively you can also run ProfitView without any TradingView tab open, for more on that see the previous entry above. | ||
| </panel> | </panel> | ||
| Line 80: | Line 101: | ||
| <panel title="13) - TradingView Alerts have fired but I can't see them on the chart?"> | <panel title="13) - TradingView Alerts have fired but I can't see them on the chart?"> | ||
| Depending on how your indicator calculates its trigger condition (moving averages etc.) it is possible for a signal condition to be met during candle formation but not met at candle close. | Depending on how your indicator calculates its trigger condition (moving averages etc.) it is possible for a signal condition to be met during candle formation but not met at candle close. | ||
| + | \\ | ||
| Make sure your alerts are set to fire ''Once Per Bar Close''. On timeframes over 15-30min it is also possible to use ''Once Per Minute'' and set the filter options in your ProfitView alerts accordingly: | Make sure your alerts are set to fire ''Once Per Bar Close''. On timeframes over 15-30min it is also possible to use ''Once Per Minute'' and set the filter options in your ProfitView alerts accordingly: | ||
| + | \\ | ||
| **Disable** at least ''Bar Open'' and ''Start'', make sure ''Once per Bar'' and ''Filter Repeats'' are both checked with ''Reset Repeat'' set to 2-3 times your chart resolution. | **Disable** at least ''Bar Open'' and ''Start'', make sure ''Once per Bar'' and ''Filter Repeats'' are both checked with ''Reset Repeat'' set to 2-3 times your chart resolution. | ||
| Another reason for signals to disappear after having fired is if your indicator combines multiple timeframes (different to the timeframe of your original chart). | Another reason for signals to disappear after having fired is if your indicator combines multiple timeframes (different to the timeframe of your original chart). | ||
| - | In OCC for example this happens when you use a ''Resolution Multiplier'' greater than the default of 1 or select certain longer timeframes for ''Trend Confirmation Resolution''. | + | \\ |
| + | In OCC for example this happens when you use a ''Resolution Multiplier'' greater than the default of 1 or select longer timeframes for ''Trend Confirmation Resolution'' different to your charts native timeframe. | ||
| + | \\ | ||
| Both features are still very useful, they just require more live testing and experimentation and you have to be aware of this behaviour. | Both features are still very useful, they just require more live testing and experimentation and you have to be aware of this behaviour. | ||
| + | |||
| + | **Please also note:** The new warning message Tradingview shows when creating or changing alerts is triggered just by the **possibility** of these occurences, because certain functions are used in the indicator. | ||
| + | \\ | ||
| + | For all setups that don't use a resolution multiplier >1 or a non-native trend confirmation resolution **the warning does not apply and is not true**! | ||
| </panel> | </panel> | ||
| - | <panel title="14) - My TradingView Alerts are set to "Once Per Bar Close" but I'm not getting alerts that correspond to my chart."> | + | <panel title="14) - My TradingView Alerts are set to "Once Per Bar Close" but I'm not getting alerts that correspond to my chart."> |
| TradingView alerts are linked to instances of chart/resolution + indicator settings. Each time you edit the settings of an indicator on your chart, a new instance is created. | TradingView alerts are linked to instances of chart/resolution + indicator settings. Each time you edit the settings of an indicator on your chart, a new instance is created. | ||
| + | \\ | ||
| Thus your alerts still link to the old settings until they are edited (updated) or recreated. | Thus your alerts still link to the old settings until they are edited (updated) or recreated. | ||
| To change existing alerts, best do a reload of the TradingView tab first (Ctrl + Shift + R). Then select ''Edit'' on the alert and select the new version of the indicator settings in the ''Condition'' dropdown. | To change existing alerts, best do a reload of the TradingView tab first (Ctrl + Shift + R). Then select ''Edit'' on the alert and select the new version of the indicator settings in the ''Condition'' dropdown. | ||
| + | \\ | ||
| Ensure triggers are correct and the expiration time well into the future and hit save, best wait a few seconds before editing the next alert. | Ensure triggers are correct and the expiration time well into the future and hit save, best wait a few seconds before editing the next alert. | ||
| + | \\ | ||
| Once you are done, reload your TradingView tab again and double check your alerts. | Once you are done, reload your TradingView tab again and double check your alerts. | ||
| </panel> | </panel> | ||
| - | <panel title="15) - Sometimes I get error messages saying "expires is in the past" or "Your computer's clock is too far into the future" etc., what can I do?"> | + | <panel title="15) - Sometimes I get error messages saying "expires is in the past" or "Your computer's clock is too far into the future" etc., what can I do?"> |
| - | Please make sure that your computers clock is synced and has the exact current time. You can check this by visiting the following site: <https://time.is/> | + | Please make sure that your computers clock is synced and has the exact current time. You can check this by visiting the following site: https://time.is/ |
| - | It is also highly recommended that you enable auto clock syncing by installing NetTime (<http://www.timesynctool.com/>) for Windows. | + | It is also highly recommended that you enable auto clock syncing by installing NetTime (http://www.timesynctool.com/) for Windows. |
| - | For OS-X follow the instructions under <http://www.macinstruct.com/node/92> to set up time syncing! | + | \\ |
| + | For OS-X follow the instructions under http://www.macinstruct.com/node/92 to set up time syncing! | ||
| </panel> | </panel> | ||
| Line 108: | Line 141: | ||
| It is also highly advisable to set those really high (lots of retries with enough timeout inbetween) to ensure SL and TP orders are placed, which usually are the most important orders in your syntax. | It is also highly advisable to set those really high (lots of retries with enough timeout inbetween) to ensure SL and TP orders are placed, which usually are the most important orders in your syntax. | ||
| + | \\ | ||
| At the same time you should then specify LESS number or retries (3-4) for your main position order by adding ''retries=<number>'' only to that line of your syntax. | At the same time you should then specify LESS number or retries (3-4) for your main position order by adding ''retries=<number>'' only to that line of your syntax. | ||
| + | |||
| + | **Note:** According to the [[https://www.bitmex.com/api/explorer/#!/Order/Order_new|BitMEX API documentation]] position closing orders are considered "reduce only" by default, so for ''c=position'' commands there is **no need** to specify ''r=1'' – with the added benefit of normal closing orders being exempt from load shedding while "reduce only" orders can fail! | ||
| </panel> | </panel> | ||
| Line 123: | Line 159: | ||
| <panel title="19) - How do I check my ProfitView VPS Status and Subscription?"> | <panel title="19) - How do I check my ProfitView VPS Status and Subscription?"> | ||
| - | Use the ''!vpsinfo'' command and the ProfitView bot will send you a DM. | + | Use the ''!vpsinfo'' command ([[https://discord.profitview.app/|Discord]]) and the ProfitView bot will send you a DM. |
| </panel> | </panel> | ||
| <panel title="20) - Can I restart my ProfitView VPS?"> | <panel title="20) - Can I restart my ProfitView VPS?"> | ||
| - | Sure! Just run ''!restartvps'' in a channel or a DM to the ProfitView Bot. | + | Sure! Just run ''!restartvps'' in a channel ([[https://discord.profitview.app/|Discord]]) or a DM to the ProfitView Bot. |
| </panel> | </panel> | ||