@iobroker/gui-components 10.3.3 → 10.3.5

package/README.md

@@ -36,7 +36,7 @@ npm create vite@latest src -- --template react-ts
     "dependencies": {
         "@emotion/react": "^11.14.0",
         "@emotion/styled": "^11.14.1",
-        "@iobroker/gui-components": "^10.3.3",
+        "@iobroker/gui-components": "^10.3.5",
         "@mui/icons-material": "^9.0.1",
         "@mui/material": "^9.0.1",
         "react": "^19.2.5",
@@ -877,6 +877,14 @@ You can find the migration instructions:
 -->
 
 ## Changelog
+### 10.3.5 (2026-09-25)
+
+- (@GermanBluefox) Added function `findObjectIcon`
+
+### 10.3.4 (2026-09-23)
+
+- (@GermanBluefox) Fixed: the schedule wizard threw the time of day away. A schedule with an exact time was saved as `{"time":{"exactTime":true}}` without the time itself, so it ran at 00:00 and the dialog showed `--:--` and "every day at undefined" when it was opened again (ioBroker.javascript#2386). A saved schedule that lacks a setting now also falls back to the default of that setting instead of `undefined`
+
 ### 10.3.3 (2026-09-23)
 
 - (@krobipd) Improved: the object browser renders the rows around the visible area instead of every open row of the tree. Selecting a row, applying a filter or folding a node rebuilt every open row, and that cost grows with the size of the tree: measured with 4003 rows open, one click on a row blocked the main thread for 3.9 seconds and a filter for 2.6 seconds - with 603 rows it was 0.4 seconds each. Now it is 0 ms in both cases, and the table holds 38 rows instead of 4003 (1985 instead of 164652 DOM nodes). Scrolling, scrolling to a row and the keyboard navigation reach every row as before

package/build/Components/Schedule.d.ts

@@ -3,6 +3,8 @@ import type { IobTheme } from '../types';
 export interface ScheduleConfigSaved {
     time?: {
         exactTime: boolean;
+        /** The time of the day as "HH:MM" or the name of an astro event, like "sunrise" */
+        start: string;
     } | {
         start: string;
         end: string;

package/build/Components/Schedule.js

@@ -304,7 +304,13 @@ export class Schedule extends Component {
             setTimeout(() => this.onChange(this.state.schedule, true), 200);
             schedule = DEFAULT;
         }
-        schedule = { ...DEFAULT, ...schedule };
+        // Only the settings of the chosen mode are saved, so everything else comes from the defaults. The parts are
+        // merged one by one, as a saved schedule has e.g. only the time of day in `time` and nothing else.
+        schedule = {
+            time: { ...DEFAULT.time, ...schedule.time },
+            period: { ...DEFAULT.period, ...schedule.period },
+            valid: { ...DEFAULT.valid, ...schedule.valid },
+        };
         schedule.valid.from ||= Schedule.now2string();
         this.refFrom = React.createRef();
         this.refTo = React.createRef();
@@ -381,13 +387,15 @@ export class Schedule extends Component {
                     copy.period.yearMonth = yearMonth;
                 }
             }
-            if (copy.time?.exactTime) {
+            const _time = copy.time;
+            if (_time?.exactTime) {
+                // The time of the day belongs to the exact time too, without it the schedule would run at 00:00
                 copy.time = {
-                    exactTime: copy.time?.exactTime,
+                    exactTime: _time.exactTime,
+                    start: _time.start,
                 };
             }
             else {
-                const _time = copy.time;
                 copy.time = {
                     start: _time.start,
                     end: _time.end,