r35157/com_r35157_nenjim-hubd-impl_ref
0
0
Fork 0
Code Issues 8 Pull Requests Actions Packages Projects Releases Wiki Activity

37: Add re-armable CROSSING alarm trigger

Browse Source
This commit is contained in:
minimons
2026-08-05 10:12:38 +02:00
parent e59aff95b8
commit d2f28af1bc
4 changed files with 39 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README_alarm.md
+19 -2
View File
@@ -140,7 +140,7 @@ Supported column values:
- `ID`: integer alarm identifier. IDs should be unique. Action files use this ID to select alarms.
- `ASSET`: `SOL`, `ETH`, or `BTC`.
- `CONDITION`: a comparison or range expression. It must be one token with no whitespace.
- `TRIGGER`: `ONETIME`, `PERSISTENT`, or `PERSISTENT:<seconds>`.
- `TRIGGER`: `ONETIME`, `CROSSING`, `PERSISTENT`, or `PERSISTENT:<seconds>`.
A trailing comment is allowed after a variable value or trigger.
@@ -210,7 +210,7 @@ At exactly `LIQ+1%`, only the first condition matches. The corresponding short-p
## Trigger behavior
On the first accepted oracle price after startup or reconnect, an already-satisfied alarm can trigger immediately.
On the first accepted oracle price after startup, an already-satisfied `ONETIME` or `PERSISTENT` alarm can trigger immediately. A `CROSSING` alarm only establishes its initial state.
### `ONETIME`
@@ -219,6 +219,23 @@ On the first accepted oracle price after startup or reconnect, an already-satisf
- Leaving and re-entering the condition does not re-arm it.
- Restarting the application re-arms it because alarm state is held only in memory.
### `CROSSING`
- Triggers when the condition changes from not satisfied to satisfied.
- The first accepted price establishes the initial state and never triggers the alarm.
- Remaining inside the condition does not trigger again.
- Leaving the condition re-arms the alarm, so the next entry triggers again.
- A grace period is not supported; `CROSSING:<seconds>` is rejected.
The condition determines the crossing direction. For example:
```text
19 SOL >={{SOL_LONG_ENTRY_PRICE}} CROSSING
20 SOL <{{SOL_LONG_ENTRY_PRICE}} CROSSING
```
Alarm 19 triggers when the price enters the profitable side from below. Alarm 20 triggers when it enters the losing side from above. With a range condition, `CROSSING` triggers whenever the price enters the range from either side.
### `PERSISTENT`
- Triggers immediately on the first accepted matching price.