cync_lan (Home Assistant custom_component) v2.6.3

Fixes the hub query sensors ("Hub Firmware", "Hub Clock") polling the mesh far
harder than intended.

These are diagnostic entities, disabled by default, and their class docstring
described the poll interval as "deliberately long". It was never actually set:
the class asked Home Assistant to poll it and no SCAN_INTERVAL existed
anywhere in the platform, so they ran on HA's 30-second default.

That matters because each poll puts a real command on the mesh and then blocks
for up to 10 seconds waiting for a reply. This command family's transport is
unconfirmed (see docs/mesh_opcodes.md), so on hardware where it simply does
not answer, every poll cost a timeout warning plus Home Assistant's own
"Update of sensor ... is taking over 10 seconds" - measured on a real system at
around 5,700 log lines a day, from a sensor that had never once produced a
value.

They now run on their own 15-minute timer rather than HA's polling, so the
other sensors on the platform - all cheap local reads - stay responsive.
Neither firmware version nor hub clock drifts meaningfully in that window.

If you enabled either of these and saw nothing but timeouts, that behaviour
itself is unchanged: the command may not be answerable on your hub. It is just
quiet about it now. The matching core-library fix stops the repeated warning
and stops waiting out the full timeout when there was no connection to send
the request on in the first place - relevant right after a restart, when Cync
devices can take many minutes to reconnect.

cync_lan (Home Assistant custom_component) v2.6.2

Reworks the logo variants added in 2.6.1. The LAN badge is now a smaller pill
tucked into the bottom-right, overlapping the tail of the wordmark, rather than
a full-size pill sitting beside it. Same idea as the icon's corner badge, so the
two read as one family.

cync_lan (Home Assistant custom_component) v2.6.1

Adds the wide logo brand variants, light and dark, alongside the square icons
that shipped in 2.4.x. Home Assistant uses the logo where a horizontal lockup
fits better than a square tile.

The icon takes its LAN badge as a corner overlay, which works because the mark
fills the tile. The same treatment on the wordmark lands on top of the final
"c" — it reads "Cyn" plus a sticker — so here the badge sits beside the
wordmark instead, which reads as "Cync LAN", the integration's actual name.

cync_lan (Home Assistant custom_component) v2.6.0

The indicator LED is no longer experimental. It has been confirmed working
on real hardware, so it is out from behind the opt-in.

The Select, Number and Switch entities for indicator-LED mode, colour,
brightness and blink-on-disconnect already appeared by default - that part was
already right. What changed is the action: it is now cync_lan.set_indicator_led
rather than cync_lan.experimental_set_indicator_led, and it is registered
whether or not experimental commands are enabled.

The old name still works. It was the only name for several releases, so it
is in people's automations, and renaming without an alias would break them
silently - the symptom being a light that does not respond, which nobody traces
back to a service rename. Calling the old name logs a warning asking you to
update, and otherwise behaves identically.

Everything else stays behind the opt-in. Of the 27 experimental commands this
integration implements, this is the only one confirmed against real hardware;
the other 26 still send a cmd_code predicted from a length formula, which is
exactly what the gate is there to protect people from.

cync_lan (Home Assistant custom_component) v2.5.3

Documentation only - no code change.

The comparison table on the repository's front page still said this integration
"is not on the default branch yet, which makes HACS installation more manual for
now". That stopped being true when feature/ha-custom-component became the
default branch; HACS installs work like any other custom repository. The
integration's own README and RELEASING.md were corrected at the time and this
line was missed.

Released rather than left to sit on the branch because HACS installs the latest
release, so until now the copy users actually got was the one still telling them
the install path was awkward.

cync_lan (Home Assistant custom_component) v2.5.2

Fixes every bridge button showing up as "Cync LAN Bridge" - the same fault
2.5.1 fixed for group power switches, which turned out to be more widespread
than that release assumed.

All six home-wide button types were affected: Query mesh credentials, Sync hub
clock, and the Delete buttons for scenes, schedules, automation bindings and
groups. Since there is one Delete button per scene, schedule and group, a
populated account produced a long list of buttons with the same name and no
way to tell which was which.

They all inherit from one base class that was missing has_entity_name, so
this is a one-line fix covering all six rather than six separate ones.

Also adds a test that scans the source for the general mistake - an entity
declaring a translated name without the flag that makes it apply - rather than
checking the eight classes known to have hit it. The same bug reaching a
release twice is what prompted it.

cync_lan (Home Assistant custom_component) v2.5.1

Fixes group power switches all showing up as "Cync LAN Bridge". Every one
of them fell back to the bridge's own device name instead of " power",
so a home with several groups got several identically-named switches with
nothing to tell them apart.

The cause: these switches declared a translated name but not
has_entity_name, and Home Assistant only applies translated entity names
when that is set. Every other bridge-attached entity in the integration either
sets it or sets a plain name; this one did neither.

Only affects the experimental group power switches - reported from a real
install.

cync_lan (Home Assistant custom_component) v2.5.0

Writes to a sleeping motion sensor are now refused instead of vanishing.

Battery devices - motion sensors, and the wireless switches and remotes that
share their behaviour - only join the mesh while awake. A settings or schedule
write aimed at a sleeping one never reaches it. Previously the two
experimental_set_motion_sensor_* actions and the "Experimental commands"
schedule form sent regardless, so the command disappeared and nothing said why.

All of them now check the device is awake first and refuse with an error asking
you to hold its off button for five seconds until the LED turns green. The
guided "Edit motion sensor settings" wizard already did this; the other three
paths did not, and now share the same check.

The check is the device's ordinary online status, which is what the real Cync
app uses too - its wake-up screen watches the same availability signal every
device type reports, and no separate "discoverable" state exists to detect.
Where this deliberately differs from the app: the app sends anyway and reports
success without transmitting. A silent no-op there is indistinguishable from a
wrong opcode, and would send you debugging the protocol instead of pressing a
button.

cync_lan (Home Assistant custom_component) v2.4.2

Corrects the installation instructions. Earlier versions told you HACS
installs would not work, because the integration lived on a branch that was not
the repository's default and HACS only ever tracks the default. That has since
changed - feature/ha-custom-component is the default branch now - so HACS
picks the integration up normally as a custom repository, and releases are
offered as updates to existing installs.

The old note stayed behind after the branch change and was actively steering
people to the manual-install path for no reason. Removed from the integration
README and the repository README; RELEASING.md now records why the default
branch matters, so it does not get moved back by accident.

Documentation only - no functional change.

cync_lan (Home Assistant custom_component) v2.4.1

A proper icon. The integration now uses the Cync mark from the Home
Assistant brands repository - the same one Home Assistant already shows for
Cync devices - with a blue "LAN" badge in the corner marking it as the
local-control integration rather than the official cloud one. The previous
icon was a generic bulb.

Dark-theme variants are included for the first time, so the mark stays
visible on a dark background instead of being a black glyph on black.

Where it shows up: Home Assistant serves brand images out of an integration's
own brand/ folder from 2026.3.0 onwards, so on that version or newer the
icon appears on the integrations page and in HACS once the integration is
installed. It will not appear in the HACS browse-and-download list before
installation - nothing is on disk to serve at that point, and that listing
falls back to the central brands CDN, which has no entry for this domain.
Getting it there needs a pull request against home-assistant/brands.

Icons are regenerated by scripts/make_brand_icons.py. Provenance and the
trademark notice that travels with the source art are recorded in
LICENSE-3RD-PARTY.

Cosmetic only - no functional change.