[github-actions]

Automated Profile evidence

• Issue: [Profile Request] Eddy Solutions - H20 V3 #41
• Issue body SHA: e9ddff537637fca42a8a5cc375e63d9ff209538b82486da199859eb1e0555475
• Provider/model: openai / gpt-5.6-terra
• Evidence level: documentation-only
• fPort policy: {"mode":"fixed","ports":[3],"citation":"Issue #41 supplies all uplink examples on fPort 3; the documented Set Report and Read Time Period downlink is on fPort 5."}
• Clean validation: passed
• Hardware verified: no

Evidence matrix

Field	Official document	Decoder	Known payload	Resolution	Value	Rationale
Leak Alert	official-document.txt, pp. 7-8, §6.2: Sensor Status bit 0 is Leak (0/1).	—	request.json issue.uplinkExamples: Alert 0201185A215A08 has status 0x01, yielding bit 0 = 1; Report 010015241E640A15162424 has status 0x00, yielding 0.	payload-verified	status bit 0 (0/1)	Official status definition and raw Issue payloads independently recompute the binary leak-alert channel.
Leak Clear	official-document.txt, pp. 7-8, §6.2: Sensor Status bit 3 is Leak Cleared (0/1).	—	request.json issue.uplinkExamples: Acknowledgement 0318040F27FE286E000097 has status 0x18, yielding bit 3 = 1; Alert 0201185A215A08 has 0.	payload-verified	status bit 3 (0/1)	The official bit definition and acknowledgement status 0x18 resolve the Issue text's ambiguous bit-0 wording for Leak Clear.
Temperature	official-document.txt, pp. 8-9, §§6.3-6.6: byte 2 is Temperature in °C.	—	Report 010015241E640A15162424 => byte 2 = 0x15 = 21; Alert 0201185A215A08 => 0x18 = 24.	payload-verified	unsigned byte, degreesCelsius	Byte position and unit are explicit; Issue payloads provide reproducible values.
Humidity	official-document.txt, pp. 8-9, §§6.3-6.6: byte 3 is Humidity in %RH.	—	Report 010015241E640A15162424 => byte 3 = 0x24 = 36; Alert 0201185A215A08 => 0x5A = 90.	payload-verified	unsigned byte, percentRelativeHumidity	Byte position and unit are explicit; Issue payloads provide reproducible values.
Get Report Period	official-document.txt, pp. 7 and 9, §§6.1 and 6.5: Describe/Acknowledgement byte 2 is Report Period in hours.	—	Describe 0000040F27E3286E000097 and Acknowledgement 0318040F27FE286E000097 => byte 2 = 0x04 = 4 hours.	payload-verified	unsigned byte, hours	Official uplink structures identify the report-period byte and Issue payloads verify its position/value.
Firmware Version	official-document.txt, pp. 7-8, §6.1: Describe byte 10 is packed firmware version, bits 5-7 major, 2-4 minor, 0-1 revision.	—	Describe 0000040F27E3286E000097 => byte 10 = 0x97 (151).	payload-verified	packed byte 0x97 (151)	The profile preserves the documented packed numeric code rather than inventing a formatted string.
Set Report Period	official-document.txt, p. 5, §5.1: downlink type 0x10, byte 1 Report Period (hours), byte 2 Read Period (minutes).	—	request.json downlinkEvidenceText: fPort 5, report period 20 (0x14), expected bytes 10 14 0F.	payload-verified	channel 7; finite integer hours 0-255; bytes [0x10,value,0x0F]; fPort 5	The complete prepared downlink vector verifies command selector, value byte, fixed read period, and transmit port.

Agent summary

Generated and candidate-validated the H20-V3 Profile and strict fixture.

Warnings

• No complete expected BACnet output was supplied in the Issue; expected outputs are recomputed from the official specification and raw Issue payloads.
• Leak Clear is decoded from official Sensor Status bit 3 (Leak Cleared), while the Issue mapping text mentions bit 0 for both leak channels; the acknowledgement payload 0x18 verifies bit 3 as the clear indication.

The automation will never mark this PR ready, approve it, or merge it.

Closes #41