[Leggin]

A rewrite of the README, modelled on what well-regarded projects do (requests, httpx, python-kasa, lpgera/dirigera): a runnable example first, a supported devices table, the same layout for every device section, and collapsible troubleshooting.

Rendered on this branch

What changed

• Start: a short description and a runnable example right below the badges. The badges now link to their targets and have correct alt text.
• Getting started: finding the hub (also via its gw2-<id>.local name), generating a token and connecting, without the huge fake token.
• Supported devices: a table with the getter and the models known to work, plus how to request support for other devices.
• Finding devices: by name, id or list, a note that the hub doesn't return devices in a stable order, the errors raised, and a complete getter reference in a collapsible table.
• Working with devices: the common fields, snake_case attribute names, how setters validate, reload() and relation_id.
• Every device type is documented with attribute tables and examples that include their imports. Water, occupancy and light sensors had no section before.
• Scenes: examples for a device action, a shortcut button trigger, and a daily time trigger that ends after a duration. Also a note on the camelCase names used when creating scene models.
• Event listener: a complete example (the old one used an undefined bed_light), the message format and event types, how to stop it, and reconnecting.
• New sections: raw API access, Troubleshooting (MTU timeouts, tokens, ValidationErrors, unsupported attributes, listener disconnects, certificate) and Related projects.
• Links: all absolute, so they also work on PyPI.
• Removed: the outdated Motivation section, whose own text said the feature is now in the IKEA app.
• pyproject.toml: the classifiers now list Python 3.8–3.14, the versions CI tests, so the Python versions badge is correct.

How it was checked

• A script parsed all 19 Python examples and checked every method, argument, import, enum value and scene model field against the code.
• All internal links resolve to headings.
• Checked on a real hub:
  • The three scene examples were created, read back and deleted.
  • The event message format and event types come from a live listener, which was stopped from another thread.
  • The models in the devices table include what's paired with that hub.