4 Commits

Include renames

Author	SHA1	Message	Date
Josh HawkinsandGitHub	812e5308a3	fix notification suspend state lost on page reload (#23989) ... <camera>/notifications/suspended arrives as a string over the live connection but as a number in the camera_activity snapshot, and the truthiness guard dropped the numeric 0, so a camera with notifications off rendered as active after a reload. Normalize to a string and derive isSuspended instead of storing it.	2026-08-13 16:51:44 -06:00
Josh HawkinsandGitHub	729ee86043	Miscellaneous fixes (#23619) ... * fix stale active object indicators on the live dashboard The camera_activity/<camera> snapshot cache is only written when a client sends onConnect, and object "end" events only update the local state of mounted useCameraActivity hooks, never the cache. As a result, a hook that seeded from a stale cache or missed an "end" event while disconnected showed objects that had already left, with no path to correct itself short of a full page reload. This change will re-request the snapshot on hook mount (collapsed to one onConnect per task across camera cards), and always re-notify camera_activity topics so hooks reconcile against their own local state instead of relying on snapshot-vs-snapshot comparison, and clear the payload dedup cache on reconnect and resync so byte-identical snapshots still apply. * docs tweaks * fix mqtt log message * use consistent values for lpr debug frame filenames with millisecond resolution * apply object events through a functional updater to prevent lost updates The events effect derived a new objects list from the value captured at render time and wrote the whole list back. When events arrived close together, a run derived from a stale list erased a concurrent run's removal; the resurrected object then had no remaining "end" event to clear it, and the add branch could mint a duplicate entry that no splice could ever remove, leaving the live dashboard showing active objects the backend had already cleared, until a page reload. The fix is to apply each event inside setObjects so it operates on the true current list exactly once. Unchanged results return the same reference so React bails out of re-rendering, and the label rewrite is hoisted so added objects get the sub_label/verified label directly instead of relying on the effect re-running against its own state update.	2026-07-04 00:25:22 -06:00
Josh HawkinsandGitHub	74fcd720d3	Add step + percent progress for exports (#22915) ... * backend * improve frontend Job typing * progress frontend * i18n * tests	2026-04-17 12:18:12 -06:00
Josh HawkinsandGitHub	192aba901a	Replace react-tracked and react-use-websocket with useSyncExternalStore (#22386) ... * refactor websockets to remove react-tracked react 19 removed useReducer eager bailout, which broke react-tracked. react-tracked works by wrapping state in a JavaScript Proxy. When a component reads state.someField, the proxy records that access. On the next state update, it compares only the fields each component actually touched and skips re-renders if those fields are unchanged. Under the hood, this relies on useReducer — and in React 18, useReducer had an "eager bail-out" that short-circuited rendering when the new state was === to the old state. React 19 removed that optimization, so every dispatch now schedules a render regardless, and the proxy comparison runs too late to prevent it. useSyncExternalStore is a React primitive (added in 18, stable in 19) designed for exactly this pattern: subscribing to an external store: useSyncExternalStore( subscribe, // (listener) => unsubscribe — called when the store changes getSnapshot // () => value — returns the current value for this subscriber ) React calls getSnapshot during render and compares the result with Object.is. If the value is the same reference, the component bails out — no re-render. The key difference from react-tracked is that this bail-out is built into React's reconciler, not bolted on via proxy tricks and useReducer. The per-topic subscription model makes this efficient. Instead of one global store where every subscriber has to check if their fields changed, each useWs("some/topic", ...) call subscribes only to that topic's listener set. When a message arrives for front_door/detect/state, only components subscribed to that exact topic get their listener fired → React calls their getSnapshot → Object.is compares the value → bail-out if unchanged. Components watching back_yard/detect/state are never even notified. * remove react-tracked and react-use-websocket * refactor usePolygonStates to use ws topic subscription * fix TimeAgo refresh interval always returning 1s due to unit mismatch (seconds vs milliseconds) older events now correctly refresh every minute/hour instead of every second * simplify * clean up * don't resend onconnect * clean up * remove patch	2026-03-11 09:02:51 -05:00