iobroker.time-tracker 0.3.0 → 0.3.2

package/README.md

@@ -353,6 +353,23 @@ local SQLite file, access is role-based, and every correction is written to an a
 
 ### **WORK IN PROGRESS**
 
+### 0.3.2 (2026-09-22)
+
+- (Alex) fix: the automation rules are a **list** now — one row per rule with its caption, kind, time, target and
+  weekdays, plus the buttons for *active*, *edit* and *delete* on the right. The form only opens in a dialog, for a
+  new or an edited rule, so the list stays readable. The save button of the card says “**Regeln speichern**” (it
+  carried the caption of the break rules before). New texts in all 11 languages, and an end-to-end test keeps both
+  findings
+
+### 0.3.1 (2026-09-22)
+
+- (Alex) fix: the presence board shows the **real running** time of the day now. Two things kept it frozen:
+  `/terminal/users` answered with the stored day aggregate, which only changes on a punch (it counts finished
+  pairs), and the tile “ticker” measured the seconds since the last server answer — a refresh every 60 s never let
+  it grow beyond 0. The API adds the minutes of an open punch to its answer now, the tile shows that value directly,
+  and the board refreshes every 20 s (was 60 s). The API test moves the clock ten minutes and expects the open punch
+  in the answer
+
 ### 0.3.0 (2026-09-22)
 
 - (Alex) new: the presence board can show the working time of today on the employee tiles — `1:23` next to
@@ -379,21 +396,6 @@ local SQLite file, access is role-based, and every correction is written to an a
   up in `events.*` (`lastType`, `lastUser`, `lastDirection`, `lastSource`) and reaches the web app live. The punch was
   stored in the database but never sent to the event bus, so the event states kept the previous punch
 
-### 0.2.5 (2026-09-21)
-
-- (Alex) docs: the installation chapter leads with the normal way now — install the npm package (`iobroker install
-  iobroker.time-tracker` or the admin’s “Install from custom URL”), which creates the instance `time-tracker.0`
-  automatically. Building from a checkout is only the developer path, and the chapter explains why a Git install
-  reports `cannot find start file!` (`build/` and `www/` are not part of the repository)
-
-### 0.2.4 (2026-09-21)
-
-- (Alex) `commands.punchUserId` does what it promises now: writing an employee id selects the employee the punch
-  buttons apply to (`0` = the only employee again), and the adapter mirrors the current choice back into the state.
-  For the user the README has a new *Commands (states)* section and `docs/erste-schritte.md` explains all six command
-  states — both with copy-ready examples and the two traps (buttons act on `true` only, a wrong period answers in the
-  log)
-
 Older entries are kept in [`CHANGELOG_OLD.md`](CHANGELOG_OLD.md).
 
 ## Provenance

package/build/lib/web/api.js

@@ -1961,13 +1961,16 @@ function createApi(deps) {
       return (0, import_router.json)(200, {
         users: visible.map((user) => {
           var _a3, _b2;
-          const day = aggregation.day(user.id, (0, import_time.localDate)(timestamp, user.timezone));
+          const date = (0, import_time.localDate)(timestamp, user.timezone);
+          const day = aggregation.recalculateDay(user.id, date, { now: timestamp });
+          const open = (day == null ? void 0 : day.hasOpenEntry) ? entries.listByDate(user.id, date).at(-1) : void 0;
+          const runningMin = open ? Math.max(0, Math.floor((timestamp - open.tsUtc) / 60)) : 0;
           const showWorkedTime = ((_a3 = users.getWorkProfile(user.id)) == null ? void 0 : _a3.showWorkedTime) === true;
           return {
             id: user.id,
             displayName: user.displayName,
             present: (day == null ? void 0 : day.hasOpenEntry) === true,
-            workedMin: showWorkedTime ? (_b2 = day == null ? void 0 : day.workedMin) != null ? _b2 : 0 : void 0,
+            workedMin: showWorkedTime ? ((_b2 = day == null ? void 0 : day.workedMin) != null ? _b2 : 0) + runningMin : void 0,
             // the picture is fetched by the browser from its own route; the session of this device travels
             // in the query, so a plain `<img>` can load it
             avatarUrl: user.avatar ? `/api/users/${user.id}/avatar?terminalSession=${encodeURIComponent(terminalSession)}&v=${user.updatedAt}` : null