This page lists the values that Hermetry uses when you do not set one: what a new device profile, alarm rule, command or flow starts with, and the defaults of organisation settings. Each table links to the page that explains the setting and its range. Limits that cannot be changed are in Limits and quotas .
Device profiles
Setting Default Range Page Plain MQTT TLS only (port 8883) Device profiles Allowed networks Empty: any network Up to 64 same Commands allowed without TLS Empty Up to 32 same Telemetry messages 10:1,300:60same Telemetry points 200:1,6000:60same Attribute updates, attribute requests, RPC messages 5:1,60:60same Certificate requests 1:3600same Connects 6:60same Replay messages per second Half the per-second telemetry count 1 to 10,000 same Max message payload (bytes) 65,536 1,024 to 65,536 same Max downlink payload (bytes) 65,536 (4 KiB for licensed devices) 1,024 to 65,536 same Max raw payload (bytes) 4,096 256 to 65,536 Telemetry keys Max unacknowledged messages (MQTT) 20 1 to 1,000 Device profiles Inactivity timeout (seconds) 600 10 to 604,800 same Max children of a gateway 500 0 to 10,000 same Profile of new children Generic child profile same Default RPC timeout (seconds) 10 1 to 300 same Device certificate lifetime 365 days 30 to 825 The device certificate authority Poll interval of a polled profile 300 s (60 s for built-in SNMP templates, 300 s for printers and cameras) 30 s to 1 day Polling intervals, back-off and quota
Firmware updates (profile’s Firmware tab)
Setting Default Range Allow firmware updates for this profile Off Allow unsigned images Off Allow updates over LTE (mobile data) Off Download may take (minutes) 60 5 to 1,440 Installing may take (minutes) 20 2 to 240 Tries per update 3 1 to 10
The usual rollout plan: waves of 1 % (1 to 10 devices), 10 %, 50 % and the rest; waits of 30, 30 and 15 minutes; each wave needs 90 % of its finished devices updated, pauses above 5 % failed and closes after 240 minutes. See Firmware updates (OTA) and Rolling out firmware in waves .
Commands
Option Default Do not wait for an answer (one-way) Off (two-way) Answer timeout (seconds) The command’s default, else 10 Deliver when the device comes back (persistent) The command’s default Give up after (minutes) 24 hours Ask before running on a board controlOn
See Sending commands to devices and Control cards .
Alarm rules
Field Default Range debounce.modecount (Readings in a row )count, durationdebounce.raise, debounce.clear1 1 to 86,400 dampening.maxTransitions4 2 to 100 dampening.windowSec600 10 to 86,400 dampening.holdSec300 1 to 86,400 Clear condition None: the alarm clears when no severity condition is true Offline rule: Open after (seconds offline) 600 10 to 604,800 Offline rule: Severity Warning Offline rule: Alarm title {{device.name}} is offline
See Alarm rules on device profiles and Debounce, hysteresis and dampening .
Alarm settings (Alarms > Alarm settings)
Setting Default Range Critical alarms ignore notification preferences On Repeat window (seconds) 300 60 to 86,400 Storm threshold (per minute) 20 1 to 10,000 Critical alarms sent during a storm (per minute) 60 1 to 10,000 Keep resolved alarms (days) 365 0 (forever) to 36,500
See Alarm notifications in depth .
Flows
Protection Default Bounds Runs of one flow a minute before it pauses 6,000 60 to 600,000 Failed runs in a row before it pauses 100 5 to 100,000 Runs of one flow at once 16 1 to 1,024 Messages one block sends for one input 100 1 to 10,000 Repeated device message window 60 s 1 to 3,600 s Message time-to-live 5 min 10 s to 24 h Commands and settings from flows to one device 30 a minute 1 to 600 Same notification to the same person Once per 10 min 1 min to 24 h Shortest Inject repeat 60 s 1 to 3,600 s Failed messages kept 10,000 100 to 100,000 Script CPU per message 50 ms up to 200 ms by plan HTTP request / MQTT out timeout 10 s, 3 attempts 1 to 30 s, at most 5 attempts Unsaved drafts kept 30 days Versions kept The newest 100 and those younger than 90 days
See Flow limits .
LoRaWAN device profiles
Setting Default Range RX1 delay 5 s 1 to 15 s RX1 data-rate offset 0 0 to 5 RX2 869.525 MHz, DR0 DR0 to DR7 ADR On Installation margin (ADR) 10 dB 0 to 30 dB De-duplication window 200 ms 50 to 1,000 ms Device status request interval 24 h 0 (never) to 720 h Confirmed downlink sends 3 0 to 10 Class C reachable after the last uplink 900 s 60 to 86,400 s Class C acknowledgement wait 60 s 5 to 3,600 s
See LoRaWAN device profiles .
Telemetry settings (Settings > Telemetry)
Setting Default Range Future timestamp tolerance (minutes) 10 1 to 1,440 Oldest accepted reading (days) 0 (any age) 0 to 36,500
See Timestamps, late and duplicate readings .
Notifications
Dashboards
Setting Default Grouping interval auto : by the minute up to 1 hour, 5 minutes up to 1 day, the hour up to 7 days, the day beyondAggregate of a series avgTime zone of a window The viewer’s browser A card’s “still watching?” question (video) Every 5 minutes Status key of site views status
See Data sources and parameters and Site status and the status key .
Organisation and security settings
