-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alarm Trigger = Only Once/Every Time #30
Comments
Hi @abtahizadeh! Thank you so much for the contribution and suggestion. I will definitely take this into account. I love this idea. Would you rather this be an optional parameter when creating each alert, or a global parameter that you can set in the config which applies to all alerts? |
Hello @hschickdevs I think both options are effective. /alarms expire 0 (never) or /newalert BTC/USDT PRICE ABOVE 35700 NoExpire |
This is great advice @abtahizadeh ! I will update the issue once this is implemented. Stay tuned! |
Thank you @hschickdevs |
@abtahizadeh yea, we can do it this way! There are many ways to handle this issue |
Hello @hschickdevs |
Hello again @abtahizadeh, I apologize as I've been very busy with my full-time work. I will try to add this feature this coming weekend (July 5-7). Thank you for your patience. |
Hello again @hschickdevs,Thank you |
Writing this here for notes, this issue has been raised by another user of the bot. Here are their ideas: for indicator alerts:
for simple price checks (percentage):
for simple price checks (absolut): you could also define a new parameter on alert creation like "trigger" to be able to set to:
|
@hschickdevs Thanks for this fantastic bot
Alarm is trigger once, It will be deleted after notification
Please add an option to make an alarm always used. (every time)
For example, when the price of Bitcoin reach 37500 to warn every time Until the alarm is removed.
(of course, to prevent spam, you can set a minute limit, if the price is still 37500 every x minutes)
can set an expiration date like TradingView for Alarms.
The text was updated successfully, but these errors were encountered: