[Highsteads]

Summary

This adds new contract tests from a code review, and fixes the two Z-Wave code tables that the tests showed were wrong. The expected values come from the zwave-js project's definitions (BinarySensorType in packages/cc/src/lib/_Types.ts and packages/core/src/registries/Sensors.ts), fetched on 01-11-2026.

Tests

• tests/conftest.py reuses the bundle's own test_plugin.py indigo stand-in rather than adding a second one.
• test_xml_callbacks_and_changelog.py checks that:
  • every CallbackMethod and List method= named in the XML exists
  • every state written by name is declared
  • the newest docs/changelog.md entry matches Info.plist
• test_zwave_code_tables.py checks both tables against the standard, every mapped code, codes with no matching state, scales and conversions, and the notification codes.

5.16: code tables (the plugin change)

• BINARY_SENSOR_TYPES:
  • 0x06 Water now sets waterLeak (it set tamper)
  • 0x08 Tamper now sets tamper (it set motion)
  • 0x04 CO2, 0x09 Aux and 0x0B Tilt no longer set waterLeak or motion; like any type with no state of its own, they set only onOffState
• SENSOR_TYPES:
  • correct up to 0x09 before, wrong from 0x0B; for example 0x10 Current was written to watts, 0x0F Voltage to co2Level, and 0x11 CO2 to uvIndex
  • now follows the standard; velocity, loudness, target temperature, PM2.5 and VOC are at their real codes
  • codes with no matching state are logged as unknown instead of being written to an unrelated state
• SENSOR_SCALES: the unit follows the scale the sensor sends. mV and mA are converted to V and A. Target temperature (0x22) is converted to °C/°F like temperature.
• Tests that checked the old codes: one self-test sample and six existing bundle tests used the old codes. They now use the standard ones.
• Version 5.16 in Info.plist, the plugin.py header, the README and docs/changelog.md.

Not fixed (still xfail(strict))

A Home Security "idle" notification clears motion and tamper on every idle. It also writes onOffState=False whatever the device type, so a contact device can show closed when a tamper clears. I'm fairly, but not fully, confident that the standard's idle event names the event that ended in its first event parameter.

Test plan

• pytest: 264 passed, 2 xfailed. Ruff and compileall are clean.
• Before the fix, each table test failed for the stated reason (checked with --runxfail).
• Run Parser Self-Test: 14 passed, 0 failed.
• Not yet run on the Indigo Mac. If a sensor uses the older binary report, or sends current, voltage or CO2 as a multilevel report, check that its states now read correctly. Check any triggers built on Tamper, Motion, Water Leak, CO2, Voltage, Current or UV.

---

Generated by Claude Code