Start here: reporting what your hardware actually does

[Proxy-alt]

Most of what this integration can send has never been confirmed to work. Of the
27 experimental commands, one — set_indicator_led — has been verified on
real hardware. The other 26 were reconstructed from the decompiled Cync Android
app, and their outer envelope byte is predicted from a length formula rather
than observed on the wire.

Nobody owns every Cync device. Support for a model generally arrives because
someone with that model reported what it did. That is the bottleneck — not code.

Please report either outcome

A command that did nothing is as useful as one that worked. More useful,
sometimes: a silent no-op is the expected failure when an opcode is wrong, so
"I pressed it and nothing happened" narrows things down in a way that no amount
of reading the decompiled app can.

There is no need to debug anything first. Just say what you saw.

What to include

• Device model — as printed on the device, or as the Cync app names it
• What you ran — which entity, action or button
• What happened, including "nothing at all"
• experimental_features.log — every experimental command is recorded there
  automatically, alongside your other cync-lan files. No flag to enable
• Debug logs if you have them: set cync_lan to debug level and it prints the
  outgoing packet hex. Please redact anything identifying before pasting

Where things currently stand

Confirmed on hardware	set_indicator_led
Everything else	predicted cmd_code, unverified
Hub commands (scenes, schedules, groups, hub queries)	send, but no reply has ever been observed

The hub family is the most interesting open question. Both candidate envelope
shapes have now been tested and neither produces a reply, which rules out
the routing prefix as the cause and points at either the reply channel or the
op codes themselves. A hub-family write with a visible physical outcome —
deleting a scene, toggling a schedule — is the next thing that would settle it.
If you try one, that result is worth a lot.

Details, with the evidence behind each claim, are in
docs/hardware_verification.md
and docs/hub_envelope_ab_test.md.

Two standing cautions

• Don't contact GE or Savant about this project. They didn't write it and
  can't support it.
• Don't firmware-upgrade Cync devices once you rely on local control. It
  would be trivial for the vendor to disable this method.