smart-home-engine 1.53.0 → 1.53.2

package/dist/web/assets/{tsMode-BIGdBOAo.js → tsMode-DDvVFMm4.js}

@@ -1,4 +1,4 @@
-import{m as O}from"./monaco-langs-DKJI_o9J.js";import{t as I}from"./index-COKTfw7g.js";/*!-----------------------------------------------------------------------------
+import{m as O}from"./monaco-langs-DKJI_o9J.js";import{t as I}from"./index-lCqN_GjH.js";/*!-----------------------------------------------------------------------------
  * Copyright (c) Microsoft Corporation. All rights reserved.
  * Version: 0.52.2(404545bded1df6ffa41ea0af4e8ddb219018c6c1)
  * Released under the MIT license

package/dist/web/index.html

@@ -175,10 +175,10 @@
                 }
             })();
         </script>
-      <script type="module" crossorigin src="/assets/index-COKTfw7g.js"></script>
+      <script type="module" crossorigin src="/assets/index-lCqN_GjH.js"></script>
       <link rel="modulepreload" crossorigin href="/assets/monaco-langs-DKJI_o9J.js">
       <link rel="stylesheet" crossorigin href="/assets/monaco-langs-DyX1CsEw.css">
-      <link rel="stylesheet" crossorigin href="/assets/index-x3Sn9IKo.css">
+      <link rel="stylesheet" crossorigin href="/assets/index-BsO7OQRT.css">
     </head>
     <body>
         <div id="app"></div>

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "smart-home-engine",
-    "version": "1.53.0",
+    "version": "1.53.2",
     "description": "Node.js based script runner for use in MQTT based Smart Home environments",
     "main": "src/index.js",
     "scripts": {

package/src/index.js

@@ -691,6 +691,9 @@ if (config.url) {
             state.lc = state.val === oldState.val ? oldState.lc : ts;
             store.setObject('mqtt::' + topic, state);
             store.setObject('var::' + varName, state);
+            // dispatch now, as setVariable() does: the broker's echo of the status publish below finds the store
+            // already updated, so a { change: true } subscription would never see the change (B-22)
+            stateChange(topic, state, oldState, msg);
             mqtt.publish(topic, JSON.stringify(state), { retain: true });
         } else {
             if (!state) {
@@ -701,6 +704,18 @@ if (config.url) {
                 state.ts = new Date().getTime();
             }
             oldState = store.getObject('mqtt::' + topic) || {};
+            // our own echo: she publishes <prefix>/status/<name> retained after a var/set or she.var.set(), and the
+            // broker delivers it back (we subscribe to #). The subscriptions were dispatched at set time; the
+            // echo carries the stored state verbatim (same ts and lc), so it is stored again but not dispatched.
+            if (
+                topicArr[0] === config.variablePrefix &&
+                topicArr[1] === 'status' &&
+                oldState.ts === state.ts &&
+                oldState.lc === state.lc &&
+                JSON.stringify(oldState.val) === JSON.stringify(state.val)
+            ) {
+                return;
+            }
             // lc (last change): prefer a payload-provided value; otherwise set it
             // on value change and carry the previous lc over when the value is
             // unchanged. Previously the old lc was simply lost on repeated
@@ -1688,6 +1703,9 @@ function loadDir(dir) {
             }
 
             const fileLabel = makeLabel(filePath);
+            // the Scripts page reloads an open tab of this file (U12): every file, also libraries, disabled
+            // scripts and non-.js files, since any of them may be open in a tab
+            if (event === 'change') broadcast({ type: 'script:changed', path: fileLabel.slice(0, -1) });
             if (event === 'change' && filePath.endsWith('.js')) {
                 if (isLibFile(filePath, dir)) {
                     log.warn(fileLabel, 'is a library file - scripts that require() it will see the old version until they or the daemon are restarted');

package/src/web/ai-tools.js

@@ -1350,7 +1350,7 @@ function analysisLoaders(ctx) {
             } catch {
                 /* module missing */
             }
-            if (!client) throw new Error('no Elasticsearch integration is configured in she (config "elastic")');
+            if (!client) throw new Error('no Elasticsearch integration is configured in she (config "elastic"); use data.history (InfluxDB) for values over time instead');
             const fromMs = needTime(from, 'from');
             const toMs = needTime(to, 'to');
             const cap = Math.min(Math.max(1, Number(limit) || 1000), 5000);

package/src/web/prompts/tools.md

@@ -2,12 +2,12 @@
 Use the tools; they read the running daemon. Where to start:
 - a room ("the light in the workshop", "presence in the bathroom"): describe_room first — every device, variable, script and discovery device of the room in one call; then narrow with describe_device (several names at once), get_timeline or get_topic_history
 - one device: describe_device; the current value of a topic: get_mqtt_topic; topics by pattern or value: search_mqtt_topics
-- anything about the past — "why", "when", "how often", "since when": get_timeline (the changes of several topics merged in time order; the tool for "what happened"), get_topic_history (the values of one or several topics over time), get_topic_messages (the raw messages of one topic)
+- anything about the past — "why", "when", "how often", "since when": get_timeline (the changes of several topics merged in time order; the tool for "what happened"), get_topic_history (the values of one or several topics over time), get_topic_messages (the raw messages of one topic; needs Elasticsearch — without it use the history)
+- a question that needs counting, correlating or comparing more than two topics over time ("did the light go off while the echo kept playing", "how often per evening", "what else changed in the minute before"): run_analysis first — one call with the computation in JavaScript beats a dozen history calls, and the user sees the code
 - which script does what: read_script (the source with its subscriptions, publishes and the scripts wired to it), list_scripts, who_publishes
 - what a script did or logged: get_script_logs with a time window; what is still pending: list_timers
 - "nothing happens": get_health first, then list_services for the adapters
 - Matter: list_matter_devices (with state), get_matter_attribute; sheDB: list_shedb_docs, get_shedb_doc
-- research that would take many calls or arithmetic over long lists (counts per hour, correlations, durations): run_analysis — write the computation in JavaScript over `data.topics`, `data.history`, `data.messages`, `data.log` and return a small result; the user sees the code and the result
 How to call them:
 - ask for every independent tool in the same turn — the calls of a turn run concurrently, and each turn costs a round trip
 - use MQTT filters (`radar-x/status/#`, `zigbee2mqtt/+_workshop/#`) where the topic tree is known; a substring search is for an unknown name