fix: decode special log records in ReadRange without status flags by Copilot · Pull Request #77 · bacnet-js/client

Copilot · 2026-03-17T08:39:33Z

Fixes ReadRange decoding when TREND_LOG contains special log records (e.g., log-interrupted, time-change) that don't have status flags.

Problem

When reading a TREND_LOG that contains a special log record, records after it were silently missing from the result. The issue was that decodeRange unconditionally consumed the status flags bytes after the log-datum value, but special records don't have status flags. This caused the decoder to read into the bytes of the next record and lose sync.

Solution

Updated decodeRange in src/lib/asn1.ts to:

Validate closing tag 1 before consuming it
Check for context tag 2 presence before decoding status flags (status flags are optional for ALL record types per ASHRAE 135 §12.25)
Add support for log-status choice (context tag 0 - special records like log-disabled, buffer-purged, log-interrupted)
Add support for time-change choice (context tag 9 - clock adjustment records)
Add isLogStatus, logStatus, and isTimeChange fields to differentiate special records

Type Changes

Extracted LogRecord, LogStatusFlags, LogRecordStatusFlags interfaces to types.ts
Updated ReadRangeAcknowledge.values to use LogRecord[] instead of any[]
Added LogRecordValue union type to narrow LogRecord.value
Added ASHRAE 135 §12.25 standard references to code comments

Testing

Added unit test for special log-status records without status flags (mixed with normal records)
Added unit test for time-change records without status flags
All 204 unit tests pass
Linting passes
Build passes
CodeQL security scan - no issues found

Original prompt

This section details on the original issue you should resolve

<issue_title>ReadRange bug when response contains a special log record</issue_title>
<issue_description>Hello

When reading a TREND_LOG that contains a special log record (e.g. log-interrupted), records after it are silently missing from the result — no error, no warning.

I spent some time debugging this with Wireshark and found that the raw UDP packet is perfectly valid and complete. The issue is in decodeRange.

What's happening

Special log records don't have status flags. A normal record ends with:
1f 2a 04 00   ← closing tag 1, opening tag 2, BIT_STRING, closing tag 2
A special record ends with just:
1f            ← closing tag 1, nothing after
But decodeRange unconditionally consumes 2 tags after the datum value without validating their tag numbers. So it reads into the bytes of the next record, shifts the offset by an unpredictable amount (depends on the byte values that follow), and loses sync for everything after.

The behavior is non-deterministic — sometimes records after the special one are silently dropped, sometimes the buffer appears truncated. Took a while to figure out why the same code would behave differently depending on which records were in the response.

Reproduction
const response = await client.readRange(
    { address: '10.x.x.x:47808' },
    { type: bacnet.ObjectType.TREND_LOG, instance: 100101 },
    startIndex, 20,
    {}
);
// response contains fewer records than expected
// no error thrown
// Wireshark shows the full response is received correctly

Thanks so much for the patch ;-)

Thomas</issue_description>

## Comments on the Issue (you are @copilot in this section)

<comments>
<comment_new><author>@robertsLando</author><body>
Hi Thomas and thanks for your issue! WOuld you like to submit a PR? </body></comment_new>
</comments>

Fixes ReadRange bug when response contains a special log record #76

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

Special log records (log-interrupted, buffer-purged, log-disabled) use the log-status choice which does NOT include status flags. The previous code unconditionally consumed the status flags bytes, causing it to read into subsequent records and lose sync. This fix: - Validates closing tag 1 before consuming it - Checks for context tag 2 (status flags) presence before decoding - Adds support for log-status choice (context tag 0) - Adds isLogStatus and logStatus fields to differentiate special records - Adds comprehensive test for mixed normal and special log records Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

- Extract LogRecord, LogStatusFlags, LogRecordStatusFlags interfaces - Update ReadRangeAcknowledge.values to use LogRecord[] instead of any[] - Update decodeRange to return Decode<LogRecord[]> - Use assert.strictEqual for undefined checks in tests Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

robertsLando

@copilot

ASHRAE 135 Standard Reference

This library implements ASHRAE Standard 135 (BACnet). Always consult the official specification and reference implementations when reviewing or implementing features:

[bacnet-stack](https://github.com/bacnet-stack/bacnet-stack) — The most widely used open-source BACnet implementation in C. Use as the primary source of truth for protocol behavior and packet formats.
[BACnet.org technical papers](https://bacnet.org/developer-resources/) — Free PDFs covering specific topics (foreign devices, BBMDs, routing, etc.)
[Wireshark BVLC dissector](https://github.com/wireshark/wireshark/blob/master/epan/dissectors/packet-bvlc.c) — Useful for verifying packet formats and field layouts

When implementing or modifying protocol features, reference the relevant standard section in a code comment. Example:

// Encode object identifier per ASHRAE 135-2024 §20.2.14
encodeApplicationObjectId(buffer, objectType, instance)

Copilot

Pull request overview

Adds typed support for decoding BACnet TREND_LOG “log-status” records in ReadRange acknowledgements, including handling records that omit status flags per ASHRAE 135.

Changes:

Extended baAsn1.decodeRange to decode the log-datum CHOICE [0] log-status and to tolerate missing status flags for log-status records.
Introduced LogRecord (and related flag interfaces) and updated ReadRangeAcknowledge.values to use it.
Added a unit test covering mixed normal + log-status log records in a single range buffer.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
test/unit/service-read-range.spec.ts	Adds coverage for decoding log-status records that omit status flags.
src/lib/types.ts	Introduces `LogRecord` typing and narrows `ReadRangeAcknowledge.values` to `LogRecord[]`.
src/lib/asn1.ts	Updates `decodeRange` to parse log-status records and make status flags optional when appropriate.
src/lib/services/WriteProperty.ts	Formatting-only changes (no behavioral change).

You can also share your feedback on Copilot code review. Take the survey.

Reference ASHRAE 135 Standard Section 12.25 for LogRecord structure in JSDoc comments for decodeRange function and LogRecord types. Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

Copilot · 2026-03-17T09:37:14Z

@copilot

ASHRAE 135 Standard Reference...

Added ASHRAE 135 §12.25 standard references to the decodeRange function JSDoc and LogRecord, LogStatusFlags, LogRecordStatusFlags type definitions in commit 5609612.

robertsLando · 2026-03-17T09:41:36Z

@copilot Address review comments please. Ignore the ones marked as RESOLVED

Address code review comments: - Use BACNetBitString for bitstring casts instead of { value: number[] } - Add LogRecordValue union type to narrow LogRecord.value from unknown Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

Copilot · 2026-03-17T09:44:55Z

@copilot Address review comments please. Ignore the ones marked as RESOLVED

Addressed the unresolved review comments in commit a33fbbb:

BACNetBitString casts: Changed bitstring casts from { value: number[] } to BACNetBitString to properly reflect the shape returned by decodeBitstring (includes bitsUsed property).
LogRecordValue type: Added a LogRecordValue union type to narrow LogRecord.value from unknown to a union of supported value types (number | boolean | BACNetBitString | null | string | BACNetObjectID).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

127.0.0.2
- Triggering command: REDACTED, pid is -1 (packet block)
255.255.255.255
- Triggering command: REDACTED, pid is -1 (packet block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Copilot

Pull request overview

This pull request extends the ReadRange ACK decoding path to properly handle BACnet TREND_LOG “log-status” records (which omit status-flags), and adds stronger typing around decoded log records.

Changes:

Add unit coverage for decoding log-status records without status flags in ReadRange acknowledgements.
Introduce LogRecord / related types and update ReadRangeAcknowledge.values typing accordingly.
Update decodeRange logic to decode log-status choice records and treat status-flags as optional for non-log-status records.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
test/unit/service-read-range.spec.ts	Adds a regression test for decoding mixed normal + log-status log records.
src/lib/types.ts	Adds `LogRecord`-related types and updates `ReadRangeAcknowledge.values` to `LogRecord[]`.
src/lib/asn1.ts	Updates `decodeRange` to support log-status choice records and optional status-flags.
src/lib/services/WriteProperty.ts	Formatting-only changes.

Comments suppressed due to low confidence (1)

src/lib/asn1.ts:2534

The comment lists multiple log-datum CHOICE alternatives, but the implementation currently only handles tag 0 (log-status), tag 2 (REAL), and some ENUMERATED cases. If other alternatives (e.g., boolean, unsigned, signed, null, string, object-id) appear, decodeRange will return undefined and ReadRangeAcknowledge.values will be omitted. Consider either decoding the remaining alternatives or making the supported subset explicit (and non-fatal) so mixed/other record types don't prevent returning parsed values for known records.

		// log-datum [1] CHOICE per ASHRAE 135 §12.25:
		// [0] log-status (BACnetLogStatus bitstring - special records)
		// [1] boolean-value
		// [2] real-value
		// [3] enum-value
		// [4] unsigned-value
		// ... and more
		tag = decodeTagNumberAndValue(buffer, offset + len)
		len += tag.len
		let value: ApplicationData | undefined
		let isLogStatus = false
		if (tag.tagNumber === 0) {
			// log-status choice: BACnetLogStatus bitstring per ASHRAE 135 §12.25
			// Special log records (log-disabled, buffer-purged, log-interrupted)
			// do NOT have statusFlags [2] after the log-datum
			value = bacappDecodeData(
				buffer,
				offset + len,
				maxOffset,
				ApplicationTag.BIT_STRING,
				tag.value,
			)
			isLogStatus = true
		} else if (tag.tagNumber === 2 && tag.value === 4) {
			value = bacappDecodeData(
				buffer,
				offset + len,
				maxOffset,
				ApplicationTag.REAL,
				tag.value,
			)
		} else if (tag.tagNumber === 4 && tag.value === 1) {
			value = bacappDecodeData(
				buffer,
				offset + len,
				maxOffset,
				ApplicationTag.ENUMERATED,
				tag.value,
			)
		} else if (tag.tagNumber === 3 && tag.value === 1) {
			value = bacappDecodeData(
				buffer,
				offset + len,
				maxOffset,
				ApplicationTag.ENUMERATED,
				tag.value,
			)
		}

You can also share your feedback on Copilot code review. Take the survey.

robertsLando · 2026-03-17T09:57:59Z

@copilot fix review

Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

Copilot · 2026-03-17T10:04:19Z

@copilot fix review

Fixed in f5bbc1f:

Changed all flag names to camelCase (logDisabled, bufferPurged, logInterrupted, outOfService, overridden, fault, inAlarm)
Narrowed LogRecordValue to number | BACNetBitString (the types actually decoded) and added JSDoc documenting which CHOICE alternatives are supported

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

127.0.0.2
- Triggering command: REDACTED, pid is -1 (packet block)
255.255.255.255
- Triggering command: REDACTED, pid is -1 (packet block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

robertsLando

@copilot Don't introduce unnecessary braking changes. Keep the previous property names in interfaces

Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

Copilot · 2026-03-17T10:13:05Z

@copilot Don't introduce unnecessary braking changes. Keep the previous property names in interfaces

Reverted in f1f7176. Restored the original snake_case property names (log_disabled, buffer_purged, log_interrupted, out_of_service, in_alarm) to avoid breaking changes.

thomasbertanier-prog · 2026-03-30T11:22:09Z

I tested this fix and it doesn't solve my issue. My original problem was actually triggered by a time-change record (TL_TYPE_DELTA, context tag 9), not a log-status record (context tag 0).

Here's what the special record looks like in Wireshark:

time change: 0.075000 (Real)
    Context Tag: 9, Length/Value/Type: 4

Raw bytes:

0e [date 4B] 09 01 b4 [time 4B] 0f 1e 9c [float 3B] 1f
                                              ^^
                                   context tag 9, no status flags after

This PR fixes the log-status case but the time-change case would still cause the same offset corruption.

robertsLando · 2026-03-30T12:08:42Z

@copilot Fix @thomasbertanier-prog comment #77 (comment)

…l record types Agent-Logs-Url: https://github.com/bacnet-js/client/sessions/e153eab8-5232-426b-92f5-4cecd29c35b7 Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

robertsLando · 2026-03-30T12:15:46Z

@thomasbertanier-prog Could you verify now please?

Agent-Logs-Url: https://github.com/bacnet-js/client/sessions/e153eab8-5232-426b-92f5-4cecd29c35b7 Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

Copilot · 2026-03-30T12:16:28Z

@copilot Fix @thomasbertanier-prog comment #77 (comment)

Fixed in a648ade. The changes:

Added support for time-change records (context tag 9) - now correctly decodes clock adjustment records as REAL values
Made status flags optional for ALL record types - the previous code only checked for context tag 2 when it wasn't a log-status record, but per ASHRAE 135 §12.25 and bacnet-stack, status flags are optional for all log records (the encoder only includes them when bit 7 of ucStatus is set)
Added isTimeChange field to LogRecord interface
Added unit test covering mixed records with time-change

The raw bytes from the issue (9c [float 3B] 1f = context tag 9 + REAL + closing tag 1 with no status flags) will now be decoded correctly.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

https://api.github.com/graphql
- Triggering command: /usr/bin/gh gh pr view 77 --comments --json comments (http block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Initial plan

b5ec00a

Copilot AI assigned Copilot and robertsLando Mar 17, 2026

Copilot started work on behalf of robertsLando March 17, 2026 08:39 View session

Copilot AI and others added 2 commits March 17, 2026 08:45

Copilot AI changed the title ~~[WIP] Fix ReadRange bug when response contains a special log record~~ fix: decode special log records in ReadRange without status flags Mar 17, 2026

Copilot AI requested a review from robertsLando March 17, 2026 08:50

Copilot finished work on behalf of robertsLando March 17, 2026 08:50

robertsLando marked this pull request as ready for review March 17, 2026 09:29

Copilot AI review requested due to automatic review settings March 17, 2026 09:29

Copilot started reviewing on behalf of robertsLando March 17, 2026 09:30 View session

robertsLando mentioned this pull request Mar 17, 2026

ReadRange bug when response contains a special log record #76

Closed

robertsLando reviewed Mar 17, 2026

View reviewed changes

Copilot started work on behalf of robertsLando March 17, 2026 09:35 View session

Copilot AI reviewed Mar 17, 2026

View reviewed changes

Comment thread src/lib/types.ts Outdated

Comment thread src/lib/types.ts

Comment thread src/lib/asn1.ts

docs: add ASHRAE 135 §12.25 standard references to LogRecord decoding

5609612

Reference ASHRAE 135 Standard Section 12.25 for LogRecord structure in JSDoc comments for decodeRange function and LogRecord types. Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

Copilot AI requested a review from robertsLando March 17, 2026 09:37

Copilot finished work on behalf of robertsLando March 17, 2026 09:37

Copilot started work on behalf of robertsLando March 17, 2026 09:41 View session

robertsLando requested a review from Copilot March 17, 2026 09:45

robertsLando approved these changes Mar 17, 2026

View reviewed changes

Copilot started reviewing on behalf of robertsLando March 17, 2026 09:46 View session

Copilot AI requested a review from robertsLando March 17, 2026 09:47

Copilot finished work on behalf of robertsLando March 17, 2026 09:47

Copilot AI reviewed Mar 17, 2026

View reviewed changes

Comment thread src/lib/types.ts

Comment thread src/lib/asn1.ts

Comment thread src/lib/types.ts

Copilot started work on behalf of robertsLando March 17, 2026 09:58 View session

refactor: use camelCase for flag names and narrow LogRecordValue type

f5bbc1f

Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

Copilot finished work on behalf of robertsLando March 17, 2026 10:07

robertsLando requested changes Mar 17, 2026

View reviewed changes

Comment thread src/lib/asn1.ts Outdated

Copilot started work on behalf of robertsLando March 17, 2026 10:08 View session

revert: keep snake_case property names to avoid breaking changes

f1f7176

Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

Copilot AI requested a review from robertsLando March 17, 2026 10:15

Copilot finished work on behalf of robertsLando March 17, 2026 10:15

Copilot started work on behalf of robertsLando March 30, 2026 12:08 View session

fix: handle time-change records and make status flags optional for al…

2125d03

…l record types Agent-Logs-Url: https://github.com/bacnet-js/client/sessions/e153eab8-5232-426b-92f5-4cecd29c35b7 Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

fix: use UNSIGNED_INTEGER for log-datum tag 4 per ASHRAE 135

a648ade

Agent-Logs-Url: https://github.com/bacnet-js/client/sessions/e153eab8-5232-426b-92f5-4cecd29c35b7 Co-authored-by: robertsLando <11502495+robertsLando@users.noreply.github.com>

Copilot finished work on behalf of robertsLando March 30, 2026 12:17

robertsLando merged commit 8074b54 into master Apr 1, 2026

robertsLando deleted the copilot/fix-readrange-bug-special-log-record branch April 1, 2026 08:32

Conversation

Copilot AI commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Solution

Type Changes

Testing

What's happening

Reproduction

Uh oh!

robertsLando left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI commented Mar 17, 2026

Uh oh!

robertsLando commented Mar 17, 2026

Uh oh!

Copilot AI commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

robertsLando commented Mar 17, 2026

Uh oh!

Copilot AI commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

robertsLando left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI commented Mar 17, 2026

Uh oh!

thomasbertanier-prog commented Mar 30, 2026

Uh oh!

robertsLando commented Mar 30, 2026

Uh oh!

robertsLando commented Mar 30, 2026

Uh oh!

Copilot AI commented Mar 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Copilot AI commented Mar 17, 2026 •

edited

Loading

Copilot AI commented Mar 17, 2026 •

edited

Loading

Copilot AI commented Mar 17, 2026 •

edited

Loading

Copilot AI commented Mar 30, 2026 •

edited

Loading