Skip to content

Fludia - add FM432ir firmware 20 double mode (E_POS + E_NEG, header 0x35) - #1092

Open
Fludia-IoT wants to merge 2 commits into
TheThingsNetwork:masterfrom
Fludia-IoT:fm432ir-v20-double-mode-0x35
Open

Fludia-IoT wants to merge 2 commits into
TheThingsNetwork:masterfrom
Fludia-IoT:fm432ir-v20-double-mode-0x35

Conversation

@Fludia-IoT

Copy link
Copy Markdown
Contributor

Summary

Add decoding of the FM432ir firmware 20 double mode: T1 frame F0 35 (E-POS and E-NEG indexes and 8 values each), which was previously rejected as "Invalid payload". Also fix a ReferenceError in the T2 adjustable step decoder.

Changes

  • vendor/fludia/fm432ir-10-15mn-decode.js: new header 0x35 (T1_IR_DOUBLE_MODE), output fields identical to the firmware 21/22 double mode (index_solar, powers, time_step, type_of_measure)
  • T2 F0 2A: type_of_measure for the double mode (measure 3)
  • Fix undeclared "bytes" variable in decode_T2_mme_adjustable_step (negative E-SUM index)
  • No change for the other frame types (checked on 16,800 random frames)

Checklist for Reviewers

Notes for Reviewers

Release Notes

rflud and others added 2 commits November 10, 2026 16:07
…x35)

Decode the T1 frame F0 35 sent in double mode by the firmware 20
(E-POS and E-NEG indexes and 8 values each), with the same output fields
as the double mode of the firmware 21 and 22 (index_solar, powers,
time_step, type_of_measure). The T2 frame F0 2A now also gives
type_of_measure for the double mode (measure 3).
No change for the other frame types.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
decode_T2_mme_adjustable_step used "bytes" without declaring it when
the E-SUM index is negative (measure 1), which threw a ReferenceError
instead of returning the decoded index.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants