Repository navigation
Etherlighting Evolved 0.6.0
This release removes API routes, saves schedules and port names in a format that 0.5.1 cannot read, keeps the fan mode for each switch in a new place, and moves the build to Python 3.14, Node.js 24.18.0 and .NET 10.
- LAN access lets phones and other computers on your network open EE at the Windows computer's address, without Tailscale. It is off by default; turn it on under LAN access in Settings → Remote. Each device pairs once with a code shown on the Windows computer and stays paired until you remove it or turn LAN access off. A browser keeps its access key for one year and then needs a new code. LAN access uses port 4280 by default and IPv4 only, and accepts only private network addresses. Its traffic is plain HTTP and is not encrypted, and Settings says so. Switch and UniFi Network passwords never cross it. An uninstall for one user deletes the LAN access setting and the paired devices.
- Tailscale is optional. Private access stays off until you turn it on, and EE runs no Tailscale command while it is off. The one exception is a route that EE added earlier and has not yet seen removed, including one from a setting turned off in 0.5.1: EE reads
tailscale serve statusat start, refresh and quit until a start or refresh sees the route gone. - As in 0.5.1, the first connection to a switch that has no saved SSH key, whether you sign in, connect with the saved login or EE connects at startup, signs in with the username and password and saves the switch's key. No SSH key is needed on the switch. Keys saved by earlier versions are used as they are.
- Settings → Connection shows the SSH key fingerprint and key type of the connected switch.
- When a switch presents a key that differs from the saved one, EE refuses the connection before it sends the username or password, and the Connect page shows the saved and the new fingerprints. The new key can be accepted only in EE on the computer that runs it, which also clears the lighting player record of the previous switch. Lighting, schedules and port names saved for the previous key stay on disk but are not used with the new key.
eectl probe --accept-host-key <fingerprint>accepts a changed key from the command line. - Devices on Tailscale and paired LAN devices can use only the requests listed for remote use: lighting, effects, automation, profiles, schedules, port names, fans, status, reconnecting to the saved switch and Handoff to UniFi. Logging in to a new switch, forgetting the saved login, UniFi Network setup, the Tailscale and LAN access settings and accepting a changed SSH key work only on the computer that runs EE. Clients on those devices leave out the controls they cannot use. Update macOS and Linux clients that connect by address.
- Changing the Tailscale or LAN access settings or closing the web session from a browser needs a key that EE creates at each start. Open the browser tab with Open in browser in the tray menu or in Settings → Connection. Tabs opened another way show these settings read-only. A source run prints a one-use administration link.
- EE removes its own Tailscale Serve route when it stops and adds it again when it starts with private access on. Uninstalling EE removes the route when EE was installed for you only. After uninstalling an installation for all users, run
tailscale serve statusand remove EE's port withtailscale serve --https=<port> off. - Fans saves the fan mode for each switch, and a switch that EE has not controlled before starts in Switch control. The mode chosen in 0.5.1 moves to the first USW-Pro-XG-8-PoE that EE connects to after the update.
- Handoff to UniFi also returns the fans of a USW-Pro-XG-8-PoE to the switch's own controller, and EE restores the switch's saved fan mode when you connect again. Uninstalling EE does not connect to the switch, so choose Handoff to UniFi for each switch before you uninstall.
- EE's fan control program on the switch changed. On the first switch that EE connects to after the update, the first check restarts the fan control that 0.5.1 started there once, with the same mode. On other switches, EE stops fan control that 0.5.1 started, on this or another computer, and the switch's own controller runs the fans until you choose a mode.
- When the fan mode saved for a switch cannot be read, Fans says so, and EE does not change fan control that is running on the switch until you choose a mode. Fan control that EE on another computer started with this or a later release also keeps running until you choose a mode. A fan setting that takes effect but cannot be saved is reported instead of failing with a server error.
- When EE's fan control on the switch stops, EE starts it again. If that fails, EE tries again every 60 seconds and shows that the fans are back on switch control.
- When the saved lighting for a switch cannot be read, EE renames the file with
.corrupt-and the time and offers to start a new lighting setup. If the switch plays that lighting from its memory, the login stops with a message and the file is kept. Saved lighting from a newer EE version is refused with a message to update EE. The desktop app and the browser show these messages instead of a general connection error. - Schedules, port names and saved SSH host keys are saved with a format version, and EE refuses files saved by a newer version instead of overwriting them. A login refused because the saved SSH host keys cannot be read or come from a newer version says so. EE 0.5.1 cannot read the schedules and port names saved by this version.
- When the EE service stops on its own, the desktop window says so and offers to start it again. The browser workspace's gateway stops as well, instead of answering every request with an error.
- Settings → About in the desktop app shows the app and service versions and the service's disclaimer. The browser workspace shows the same disclaimer.
- The desktop app no longer has Close web session in Settings, so a client connected by address cannot close the workspace of the computer it connects to.
--urlandEE_WORKSPACE_URLaccept only the addresses that the workspace address dialog accepts. - The desktop app keeps
desktop.login its data folder with the errors it could not show and why its service failed to start or stopped. The loading spinner no longer leaves a failed task in that log at every start. service-diagnostics.logalso records EE's fixed error codes and log message templates, still without hosts, names or passwords.- The local gateway and the engine refuse API requests (403
forbidden) and WebSocket connections that a browser marks as coming from another website, and request bodies over 1 MiB (413too_large). - API changes: the WebSocket accepts the token only in the
Authorizationheader.cors_origins = ["*"]requires a token of at least 32 characters.POST /api/presets/{name}/applywaits for SFP output and can return 409output_unconfirmedor 503offline_scene_unconfirmed.POST /api/rules/testrefuses the rules that the save routes refuse. Login fields have length limits (422invalid_credentials), zones are limited to 64 and rules to 256.GET /api/sessionaddsssh_host_key,ssh_host_key_typeandfan_handoff.GET /api/fansaddssettings_errorandhold, andPUT /api/fanscan return 500fan_settings_save_failed.GET /api/private-accessaddsadmin_requiredandlocal. New routes:POST /api/session/host-key/replace,POST /api/workspace/admin-linkand the LAN access routes under/api/lan-access. - Removed API routes:
POST /api/session/forget-host-key(usePOST /api/session/host-key/replaceoreectl forget-host), and, because no client used them,POST /api/session/switch-playback,POST /api/session/switch-playback/check,GETandPUT /api/session/switch-playback/effects,GET /api/controller/diagnosticsandPOST /api/presets/action, and thecan_save_to_switchsession field. etherlighting-evolved serveserves the API only. Its page at/links to the API documentation at/docs. The old standalone browser front end, the 0.4 desktop host and the separate WPF client are removed from the repository.- Updating EE replaces the whole application folder, so no file from an earlier version stays behind. The app keeps no data in that folder.
- The lighting engine is split into smaller parts for the command rate, the SFP indicators and port identification. Lighting, its timing and the API behave as before.
- The Windows package bundles Python 3.14 and Node.js 24.18.0, and the desktop apps use .NET 10. The macOS client needs macOS 12 or later.
- Releases are built by GitHub Actions from a version tag and published on GitHub with
SHA256SUMSand build provenance attestations. The Windows installer has no Authenticode signature yet, and the macOS app has an ad hoc signature but no Developer ID signature or notarization.
Downloads
The installer is not code-signed yet, so Windows SmartScreen may warn before it runs. SHA256SUMS lists the checksum of each file. Check a download's build provenance with: gh attestation verify --repo Views2k/etherlighting-evolved
Built from commit ff68d61.