LHT65N Temperature Alarms: Verify Which Probe the Threshold Watches
An LHT65N can report two different temperatures: one at its housing and another at a connected probe. If the housing sits outside a cabinet while the probe sits inside, those readings answer different questions. Before adjusting an alarm limit, establish which channel the device’s alarm mode watches. A sensible limit attached to the wrong sensing point can leave the intended condition unmonitored.

Key takeaways |
Verify the sensing channel before adjusting the threshold. Record the housing and probe locations, confirm the exact firmware and working mode, then prove the channel with an isolated test. |
1. Start with the physical sensing point
Mark the enclosure and probe locations on the commissioning record. Give each channel a descriptive name such as “cabinet air, external probe” and “ambient at sensor housing”. Avoid a single dashboard label called “temperature” when the installation contains two sensing points.
The photograph below shows the LHT65N housing from ProSense Instruments’ external-probe product listing. Check the supplied probe and ordered variant separately; the photograph does not establish its installed firmware or the selected radio band.

2. Match the alarm format to the firmware
Dragino’s LHT65N/S manual separates legacy alarm commands from newer WMOD formats. Its newer mode descriptions identify modes 1 and 2 with external DS18B20 or TMP117 probes. Mode 3 selects DS18B20, TMP117 or the internal sensor using a separate parameter. The legacy section describes an onboard-temperature alarm. A saved command from an older installation therefore needs checking against the actual firmware before reuse.
Do not infer the configuration from a successful network join or a plausible graph. Obtain the firmware identity and current settings through the manufacturer’s supported procedure. Record the manual section used, the intended probe type and the complete configuration response. Where the firmware and documentation disagree, stop the change and seek clarification rather than testing successive guessed commands.
3. Distinguish a limit alarm from a change alarm
In the documented newer format, mode 1 compares external temperature with lower and upper limits. Mode 2 compares the current sample with the last uploaded temperature. Mode 3 combines multiple samples in an uplink and has its own alarm-enable setting. These functions should not be treated as interchangeable.
Write the requirement in ordinary language first. “Warn when cabinet air leaves the agreed band” describes a threshold function. “Warn when temperature changes sharply from the previous uploaded value” describes a different test. A slow drift can matter to the first requirement without meeting the second. Choose the function from that requirement, then confirm its behaviour on the specific device.

4. Prove the channel before proving the limit
Use a spare sensor or an authorised test arrangement that cannot disturb stock or a process. Establish a stable baseline for both displayed channels and note their locations. Then use a safe, manufacturer-permitted temperature stimulus on the intended sensing point while keeping the other as stable as practicable. Allow the sensing assembly to respond; do not judge the result from the first displayed value.
Record which measured channel changed and which device event was received.
Repeat with a controlled change at the other sensing point to check for an unintended trigger.
Compare the device configuration, received event and dashboard rule; retain evidence for all three.
Restore the agreed operating configuration and confirm the final state before handover.
These are proposed acceptance checks, not a manufacturer-certified test method. Do not expose electronics to unsuitable temperatures, wet the housing, damage a probe cable or create an out-of-range condition in operating equipment. Arrange the test with the person responsible for the application.
5. A hypothetical cabinet investigation
Suppose an external probe measures cabinet air at 8 °C while the housing remains at 23 °C. The team expects an alert above an application-approved 10 °C limit. On an isolated bench arrangement, the external channel is raised to 12 °C while the housing reading remains near its baseline. The acceptance question is whether that specific channel produces the expected device event and downstream indication.
Next, the external probe returns to its baseline and only the housing temperature is changed safely. An unexpected event now points to a channel or configuration issue worth investigating. These numbers are illustrative; they are not recommended storage limits, accuracy tolerances or a guarantee about alarm response time.
6. Avoid a correct command with an unverified outcome
Common mistakes include copying a legacy WMOD example, selecting the wrong sensor in mode 3, and assuming a dashboard threshold configures the device itself. Keep device settings and application rules separately documented. Dragino documents an A5 FF configuration request with a reply on FPort 8; interpret that response using the matching firmware documentation.
A configuration reply is useful evidence, but it does not replace the controlled channel test. Similarly, a device alarm uplink does not establish that a receiving application will notify the intended person. Agree on the complete response path and any missing-data handling separately. This monitoring arrangement is not, by itself, a certified protective control.
For a useful technical enquiry, provide the exact model, firmware version, connected probe, sensing locations, current settings and a sanitised event sample. Leave device security keys out of ordinary correspondence.
Need help with your application?
ProSense Instruments - explore instruments, sensors, data loggers and test equipment.
ProSense Solutions - discuss complete monitoring and automation systems.
ProSight Software - explore cloud dashboards, alarms and reporting. Device integration must be confirmed for your application.
Instrument enquiries: sales@prosenseinstruments.com.au | 1800 560 854
Project enquiries: sales@prosense.com.au. Software enquiries: info@prosightsoftware.com.




Comments