Fix: /homekit/accessories returns null when characteristic metadata contains NaN or Infinity

[DarkStarDS9]

Problem

GET /homekit/accessories silently returns null instead of the expected JSON array, causing casa devices to fail with "The data couldn't be read because it isn't in the correct format."

Root Cause

JSONEncoder throws EncodingError.invalidValue when encoding Double.nan or Double.infinity — both of which can appear in HomeKit characteristic metadata (e.g. minValue, maxValue, stepValue). The encodedData() method used try? which silently swallowed the error and fell back to Data("null".utf8).

Fix

In HomeKitMapper.jsonValue(_:), check for NaN/Infinity before returning .number(...) and map them to .null instead:

let d = number.doubleValue
if d.isNaN || d.isInfinite { return .null }
return .number(d)

Testing

• GET /homekit/accessories now returns a valid JSON envelope with the full accessories array
• casa devices works correctly
• Verified with a real HomeKit setup containing Philips Hue and Tado devices across multiple homes

🤖 Generated with Claude Code