github dmellok/tesserae v0.514.0

26 minutes ago

Security

  • Home Assistant App: the admin no longer opens to anyone on the network who sends an X-Ingress-Path header. The app trusted that header as proof that Home Assistant had signed the visitor in, and it also publishes port 8765 on the host for displays, so any device on the LAN could add the header and skip the password. The header now counts only when the request comes from the Supervisor's ingress proxy (172.30.32.2), or from a proxy listed in TESSERAE_TRUSTED_PROXIES. Opening Tesserae from the Home Assistant sidebar works as before. Thanks to hillmar for the report. (GHSA-v8q4-3m6w-r576)
  • First-run setup: while no password is set, /setup asks a visitor from outside the local network for a setup token. Before, the first request from any address could set the password, so an install reachable from the internet could be claimed before its owner set one. A browser on the same machine, a private network or a trusted network sets the password with no extra step. The token is printed in the server log while no password is set, or set it yourself with TESSERAE_SETUP_TOKEN. Thanks to Shravan Kumbhar for the report.
  • Reverse proxies: a visitor from outside is no longer treated as local on an install with the password turned off. The server dropped the proxy's forwarded headers before Tesserae saw them, so every visitor carried the proxy's private address and the admin opened without a sign-in. If the password is off and Tesserae is reachable through a proxy or tunnel, outside visitors now get a 403; turn the password on to use it remotely. Installs with a password set are not affected. Thanks to Shravan Kumbhar for the report.
  • Zero-touch pairing: a display that has collected its token stays closed to its MAC after the server restarts or the display's settings are saved. The marker was written to the display's file and not read back, so either one let the MAC collect the token again until the display's next request. (#515)
  • Zero-touch pairing: a display's MAC address collects its access token only once. Before, any request to /api/v1/device/discover carrying the MAC of a registered display was given that display's token, and a MAC can be read by anything on the network. Now the match stops working after the display's first request with its token. A display that is re-flashed or factory reset shows This display is asking to pair again on its page and on Settings › Devices, and Allow re-pair lets it collect its token again with its pages and history kept. Displays you already have are not affected until they lose their token. (#515)

Added

  • Export displays to a file and import them on another server, from Settings › Devices. The file holds each display's type, panel, orientation, quiet hours and settings. Access tokens are left out unless you tick Include access tokens, which lets a display move between two of your own servers by changing only the address it connects to; such a file works like a password, and the export and import pages say so. Importing adds a display, or updates one with the same id and keeps the token it has here. (#541)
  • Add Meural cloud sign-in and single-image delivery with a per-device delivery interval. A frame added for local previews before this keeps local delivery. Adding a cloud frame before signing in returns to the Devices page with the reason. Deleting a cloud frame frees it for another display. Local previews renew every 15 seconds by default, as before.
  • Export dashboards and lineups to a file and import them on another server. An export leaves out displays, passwords and keys; an import shows what it will add or replace before anything changes, and replacing keeps the displays already assigned. (#541)
  • Offer optional conditions when adding a dashboard to a lineup.
  • Add Netgear Meural local-network previews and quiet-hours sleep control.
  • Widget choices can be shown as unavailable in the editors, with a reason, and can depend on saved cell options. The flag guides the editors only; saves are not checked against it.
  • Let unreadable Home Assistant conditions count as not met when requested.
  • The lineup editor shows display wake times and warns about renders between wakes.
  • Choose a test display panel type and preview each display at exact pixel sizes.
  • Choose which displays keep a dashboard when binding it; keep all by default.
  • Pick dashboards in a popup with previews shaped for the display.
  • Add dashboards to a new lineup in one click.
  • Lineups on phones start collapsed, with a filter toggle and compact rows.
  • Add kie.ai as a selectable image service, with saved tasks and shared spending limits.
  • Add dashboard duplication from lineup tiles.
  • Add a dashboard editor with guided steps, live preview and widget option examples. Switch back to classic from its help menu.

Fixed

  • Priority lineups follow Home Assistant state changes through a shared event subscription, within about a second. Events for entities no lineup watches cost nothing on disk, and a subscription that cannot connect leaves the regular state polling in charge.

  • Pause the Meural slideshow timer during cloud delivery and restore it on release. If the restore cannot reach Netgear, the device page says to turn gallery rotation back on in the Meural app.

  • Fix lineup binding races and warnings, and load picker previews on demand with an inline fallback.

  • Sync painting budgets and spending records to disk, serialize charges across server processes, and let Repaint recover a failed picture's saved payload.

  • Touch switches, sliders and steppers read the right way up on a panel mounted a quarter turn from its native orientation, such as a reTerminal Sticky set to landscape. The server now tells the panel how far the page was turned. Needs panel firmware that draws turned controls (tesserae-device-firmware#73); older firmware ignores it and draws as before.

  • A cell's Flat dithering setting now works on CircuitPython and Pico displays, including the status bar. Before, those displays dithered every cell whatever the setting said. The setting's first choice is now called Display setting, since it follows the display's Calibration tab; the old Use dashboard and Smooth choices did the same thing. (#572)

  • Duplicating a dashboard with a status bar keeps the copy's status bar under its own control. The copy pointed at the original's bar, so switching it off on the copy left it in place.

  • Home Assistant: entity and service widgets no longer drop out for five minutes in every fifteen when the access token belongs to a user who is not an administrator. The OpenDisplay check asked Home Assistant an admin-only question every 15 minutes, even with no OpenDisplay tags set up, and the refusal was treated as a rejected token. With no tags linked it now asks nothing, and a refusal from an admin-only request no longer holds back the requests the token is allowed to make. (#553)

  • Priority lineups recheck when a display wakes, and a lineup step or refresh of a dashboard the lineup no longer picks is dropped instead of painting over the new pick. Schedules, webhooks, Home Assistant commands and unbound dashboards are sent as before.

  • Lineup thumbnail files close before transmission, so disconnected browsers cannot leave them open.

  • Font atlases for touch and overlay displays build in about a second instead of 25. Each build waited out a timeout and logged composer mount wait timed out, which on a fresh start looked like the server had hung.

  • Windows: the server starts again. The kie.ai image service used a file lock that only exists on Linux and macOS, so run.ps1 stopped with ModuleNotFoundError: No module named 'fcntl'.

  • Keep lineup tiles level when a NEXT or QUEUED tag appears.

  • Fraimic closes HTTP error responses after reading the frame error.

  • Windows installer: a failed check (git or Python missing) now shows its message and leaves the PowerShell window open. Before, the window closed before the message could be read.

  • Show calibrated panel previews in their measured inks.

  • Lineups show the delivered, queued and waiting states, with separate lanes for overlapping windows.

  • The dashboard editor warns when a Home Assistant theme overrides the dashboard appearance.

  • Smart sync: button wakes no longer reset wake-time trust.

  • Pre-renders and warm-ahead runs are skipped for a display that is paused, in quiet hours, or whose lineup conditions for that dashboard fail, so background renders no longer spend money nobody can see. A dashboard on the glass keeps its refreshes and edits as before. An automated follow-up is dropped once a newer frame has reached the display, and a display coming back from a pause gets a fresh render instead of a frame drawn before it. (#535)

  • Unreadable painting budgets block new paid requests instead of resetting the daily allowance.

  • Hiding or closing the dashboard editor tab keeps the latest edit: an earlier autosave still on its way can no longer overwrite it, and closing the tab sends the edit at once.

  • Show when a held update will land in the next refresh tooltip.

  • Home Assistant dashboard captures refresh again after serving a stale picture.

  • Buttons: a press on a lineup starts from the dashboard the lineup is showing, not its first one. Refresh re-sends that dashboard and Next goes to the one after it. This applies to every lineup that runs on a schedule, with or without conditions. Next and Previous also skip dashboards whose conditions fail, and History says where the press landed. A button set to a fixed step still goes to that step.

  • Device page: a display's Own hours switch under Quiet hours can be turned off again. Saving with it off left it on, because the page sent nothing for that section. The window you set is kept for when you switch it back on. (#523)

  • Fix wake estimates after quiet hours to follow the interval sent to the display.

  • Lineup editor: a dashboard switched from canvas to grid lists its items again (its leftover canvas data counted as a second widget).

  • New dashboard editor: adding a dashboard to a rotating lineup, or removing it, shows the right dashboard on the next tick instead of at the next boundary. A lineup is deleted by leaving it only when the request confirms it, and a lineup whose times can't be described no longer stops the editor from opening.

  • The dashboard editor skips Look when every widget draws its own appearance, and updates the step when widgets change.

  • News, Wikipedia On This Day: the date follows your timezone setting. It used UTC, so west of Greenwich it showed tomorrow's entries from the early evening until local midnight.

  • GTFS: when the agency publishes a new timetable, a pushed board now updates once the rebuild lands instead of keeping the old times. The stop list and the timetable also no longer download the same feed twice at once.

  • The classic editor can refresh widget data without saving and inspect previews at their native size.

Don't miss a new tesserae release

NewReleases is sending notifications on new releases.