docs(device-state): document profile-level inactivity timeout#426
Open
zzzeebra wants to merge 1 commit into
Open
docs(device-state): document profile-level inactivity timeout#426zzzeebra wants to merge 1 commit into
zzzeebra wants to merge 1 commit into
Conversation
Adds documentation for the new Device Profile "Device inactivity timeout" field introduced by thingsboard/thingsboard#15527, and updates existing inactivity timeout references to reflect the three-tier resolution: per-device server attribute → device profile → global default. - user-guide/device-profiles: new "Device inactivity timeout" section with unit selector, resolution order, and propagation behavior. - user-guide/connectivity-status: expand Aside to the three-tier hierarchy; rewrite Inactivity Detection paragraph; fix TB_TRANSPORT_SESSIONS_INACTIVITY_TIMEOUT default 300000 -> 600000 to match thingsboard.yml. - recipes/device-inactivity-alarm: replace yml-property reference with env var; split Step 1 into Option A (device profile, recommended) and Option B (per-device override). - edge/reference/configuration/rule-engine-config: tighten the defaultInactivityTimeoutInSec description and mention the new three-tier resolution. Note: core-rule-engine-config.mdx (CE+PE) is auto-generated from application/src/main/resources/thingsboard.yml comments by scripts/generate_config_pages.py, so it is updated in the platform yml as part of the matching CE PR rather than edited here.
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new Device inactivity timeout field on the Device Profile Details page (introduced by thingsboard/thingsboard#15527) and updates existing inactivity timeout references to reflect the three-tier resolution.
Effective inactivity timeout per device, in priority order:
inactivityTimeoutserver-side attribute (milliseconds)DEFAULT_INACTIVITY_TIMEOUTfallback (seconds, default 600)Files changed
user-guide/device-profiles.mdx— new "Device inactivity timeout" section (unit selector, resolution order, profile-update propagation). Profile Details table row updated with anchor link.user-guide/connectivity-status.mdx— Aside expanded from per-device-only override to the full three-tier hierarchy with link to the new profile section. "Inactivity Detection" paragraph rewritten to mention all three sources. Drive-by bug fix:TB_TRANSPORT_SESSIONS_INACTIVITY_TIMEOUTdefault300000→600000to matchthingsboard.yml.recipes/device-inactivity-alarm.mdx— "Step 1. Set inactivity timeout" split into Option A (Device profile, recommended) and Option B (per-device override). Replacedstate.defaultInactivityTimeoutInSecyml-property withDEFAULT_INACTIVITY_TIMEOUTenv name per style guide.edge/reference/configuration/rule-engine-config.mdx— tightened the description ofstate.defaultInactivityTimeoutInSec; mentions the three-tier resolution.Test plan
Pairing
Pair with thingsboard/thingsboard#15527. If the field name or UX changes during code review on that PR, this PR will need to follow.