Device: TG-LR82 (dev_eui 0016c001f017e9aa), LoRaWAN 1.0.x, OTAA, EU868, ChirpStack v4 network server. Firmware version: querying now, will post in a reply (device confirms version frame contents).
What I'm trying to do
Use the 6 configuration profiles to implement a simple "fast reporting after an event, slow reporting at rest" pattern, driven entirely by data set-rule + switch-profile, without any extra downlink round-trip:
- Profile 0 ("rest"):
current-state+device-orientationframes every 3600s. - Profile 1 ("alert"): same two frames every 1800s (originally tried 300s, see below).
data orient-cfg 3,1,10,60,1,3,127— reference vector set once,profile-mask=3so it applies to both profiles (soangle_1keeps being computed no matter which profile is active).- Rule 18:
angle_1 > 25→switch-profile=1, sendcurrent-state,device-orientation. - Rule 20:
mag_sw_etm < 15→switch-profile=1, sendcurrent-state,device-orientation.
(I originally also had exit rules — angle_1 < 20 / mag_sw_etm > 900 → switch-profile=0 — but deleted both after realizing their test-expr is permanently true while the device is at rest, i.e. not a real edge. I now switch back to profile 0 via an explicit downlink instead. Mentioning this in case it's relevant to the behavior below — happy to be told this reasoning is wrong.)
Encoding verified correct: every hex payload below was independently re-generated with tg-lrx2-encode against the official tg-lrx2-2.0-desc.yml and matches byte-for-byte what was actually sent (so this isn't an encoding mistake on my end, as far as I can tell).
cfg-state CRCs (cfg_data_crc, cfg_rules_crc, cfg_frames_crc) confirm each of these configuration changes was actually received and stored by the device (each change produced the expected CRC delta).
What I'm seeing
After a real, sustained tilt (>40° off the reference vector, held for well over a minute), the device:
- Took ~54 minutes to report the new orientation at all (no sign of an "immediate" uplink independent of the normal cadence — the report arrived right around when the next regular cycle was due anyway).
- After that, instead of settling into a 1800s (30 min) cadence for
current-state/device-orientation, the actual gaps I measured were 60 / 120 / 274 minutes — no clean relationship to either 3600s (profile 0) or 1800s (profile 1).
This is independent of signal quality — I moved the device much closer to the gateway (RSSI improved from -93 to -62 dBm) and the irregular cadence persisted.
Separately: the device's gateway is intentionally restricted to a single enabled uplink channel (enabled_channels=[0] in every LinkADRReq I've seen). I don't know if that's related, but it's the only "scarce resource" factor I can point to.
Questions
- Does
switch-profile(as a rule action) actually change whichul-period-sis used for the next scheduled uplink immediately, or does the frame-group's internal timer keep running from whenever it last fired under the previous profile (i.e. could the first post-switch interval legitimately be "whatever was left" rather than the new period)? - Does
send-frame(as a rule action) force an uplink independent of the configuredul-period-s/duty-cycle scheduling for that frame group, or does it just mark the frame to be included in the next transmission that was going to happen anyway? The behavior I'm seeing looks a lot like the latter, but I can't confirm it from the docs. - Is there any internal duty-cycle/airtime self-throttling that would silently extend the actual interval beyond what's configured in
frame set-cfg, especially relevant on a single-channel gateway? - Does switching the active profile (via
switch-profileorapp profile) reset the edge-detection ("previous value") state used by other rules? Concretely: if rule A just switched to profile 1, and rule B's test-expr happens to already be true at that moment, can rule B fire on the very next evaluation even though its condition didn't actually just become true?
Any pointers — official documentation, firmware changelog, or just "this is a known limitation" — would save me a lot more trial-and-error. Happy to post more config details, decoded frame dumps, or try specific test commands if that helps.
