Skip to content

History

Revisions

  • Name the pages the way GitHub titles them Wiki page titles come from filenames, so install.md rendered as a page called "install" and debugging_setup.md as "debugging setup". Renamed to Installation, Troubleshooting, Tips, Debugging Setup and Firmware Versions. DNS was already right. Updated every internal link, including two in Home.md whose display text still read debugging_setup and firmware_version even though the targets were fine, and one in Troubleshooting.md pointing at ./install, which the first pass missed because it matched neither the (install) nor the ./install.md form.

    @Proxy-alt Proxy-alt committed Jul 28, 2026
    3576096
  • Correct inherited claims that this fork has since made false The motion/ambient section in tips.md said motion data 'is not available in the Cync cloud API or to cync-lan' and advised asking Cync support to expose it. Motion sensors have worked here for a while - they surface as Home Assistant motion binary sensors, read off the mesh directly, so the cloud never needed to expose anything. Ambient light is genuinely still config-only, and now says so rather than being lumped in. install.md only ever documented the Docker/MQTT path, from when that was the only one. The Home Assistant integration is the primary way to run this now and was missing entirely; added it, kept Docker, and scoped the cync_mesh.yaml tip to Docker since the integration has no such file. Fixed one link that broke in the move to the wiki (../docker/example.env resolved relative to docs/, which no longer exists here), and retargeted debugging_setup.md's request for socat logs - it asked readers to send them to an unspecified 'me'.

    @Proxy-alt Proxy-alt committed Jul 27, 2026
    089f649
  • Move the user-facing setup guides here from docs/ DNS, install, troubleshooting, tips, debugging_setup and firmware_version are guides that benefit from being edited by the people hitting the problem - router UIs change and nobody owns every model. The protocol and reverse-engineering docs deliberately stay in the repository: they are cited from source comments over a hundred times, mirrored across three release branches by a CI check that fails on drift, and their claims carry evidence tiers that are worth reviewing in a pull request rather than editing in place.

    @Proxy-alt Proxy-alt committed Jul 27, 2026
    31f1afa
  • Initial Home page

    @Proxy-alt Proxy-alt committed Jul 27, 2026
    f9dc027
  • Footer

    @Proxy-alt Proxy-alt committed Jul 27, 2026
    0393ddc