dosync 0.4.2__tar.gz → 0.5.0__tar.gz

{dosync-0.4.2 → dosync-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dosync
-Version: 0.4.2
+Version: 0.5.0
 Summary: The semantic layer between AI agents and physical devices
 Author-email: Rodrigo Giuliani <rgiuliani@dosync.dev>
 License-Expression: Apache-2.0
@@ -24,10 +24,11 @@ Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: fastapi<1.0,>=0.115.0
-Requires-Dist: uvicorn<1.0,>=0.23.0
+Requires-Dist: uvicorn[standard]<1.0,>=0.23.0
 Requires-Dist: pydantic<3.0,>=2.7.0
 Requires-Dist: jsonschema<5.0,>=4.18
 Requires-Dist: bleak>=0.21
+Requires-Dist: zeroconf>=0.130
 Requires-Dist: pyyaml>=6.0.1
 Requires-Dist: aiohttp>=3.9.0
 Requires-Dist: paho-mqtt>=2.0.0
@@ -210,7 +211,7 @@ DoSync earns its place in specific situations — and honestly gets in the way i
 ```
 User / AI says:  "there is an emergency at home"
                           │
-                    DoSync Hub v0.3.0
+                       DoSync Hub
                           │
           ┌───────────────┼───────────────┐
           ▼               ▼               ▼
@@ -257,6 +258,50 @@ pipx install dosync      # recommended
 dosync-hub
 ```
 
+<details>
+<summary><b>On Windows</b> — pipx is not installed with Python there</summary>
+
+Every step below was found by running it on a clean Windows machine. None of it
+is exotic; it is simply what Windows needs and what this page used to omit.
+
+```powershell
+python -m pip install --user pipx
+python -m pipx ensurepath
+```
+
+**Close PowerShell and open it again.** `ensurepath` edits your PATH and the
+session you are in cannot see the change. Then:
+
+```powershell
+pipx install dosync
+dosync-hub
+```
+
+Two things the rest of this page assumes that PowerShell does not provide:
+`export VAR=value` is `$env:VAR = "value"`, and `curl` is an alias for
+`Invoke-WebRequest`, which is a different program with a different syntax — use
+`curl.exe`, or the PowerShell examples further down. `setup_pki.sh` is a shell
+script and needs Git Bash or WSL.
+
+</details>
+
+### Then open the dashboard
+
+```
+http://localhost:47200
+```
+
+Paste the API key the hub printed on startup, press **Scan**, and the hub
+searches every transport it can reach — WiFi broadcast, mDNS, SSDP, Bluetooth —
+and shows what answered. Name anything you want to keep and it is adopted.
+
+**Start here.** Discovering and adopting a device needs no terminal and no
+JSON: a 3D printer, a television and a Bluetooth sensor were adopted this way
+on the reference deployment without a line being typed. The API calls below are
+for building against DoSync, not for setting it up — they came first on this
+page for a long time, which told people who do not write code that the project
+was not for them, while a button that did the same job sat one section lower.
+
 <details>
 <summary><b>"error: externally-managed-environment"?</b> — Raspberry Pi OS, Debian 12+, Ubuntu 23.04+</summary>
 
@@ -294,11 +339,28 @@ That is a working hub on `http://127.0.0.1:47200`. It starts with a simulated
 executor, so you can drive the whole protocol — register devices, fire intents,
 read the audit chain — before you own a single smart device.
 
+### Or drive it from the API
+
+Everything the dashboard does is an HTTP call, and this is the part to read if
+you are building against DoSync rather than setting it up.
+
+The hub prints an API key on that first start and stores only a hash of it, so
+it is shown once. Save it — every command below needs it:
+
+```bash
+export DOSYNC_TOKEN=<the key printed on first start>
+```
+
+```powershell
+$env:DOSYNC_TOKEN = "<the key printed on first start>"
+```
+
 Register something and give it a goal:
 
 ```bash
 # 1. A device declares what it CAN DO (not what commands it takes)
 curl -X POST http://127.0.0.1:47200/v1/devices/register \
+  -H "Authorization: Bearer $DOSYNC_TOKEN" \
   -H 'Content-Type: application/json' -d '{
     "device_id": "siren-hall", "device_name": "Hall Siren",
     "manufacturer": "acme", "model": "S1", "firmware": "1.0",
@@ -309,14 +371,50 @@ curl -X POST http://127.0.0.1:47200/v1/devices/register \
 
 # 2. An AI expresses a GOAL — not a command, and it names no device
 curl -X POST http://127.0.0.1:47200/v1/intent/async \
+  -H "Authorization: Bearer $DOSYNC_TOKEN" \
   -H 'Content-Type: application/json' \
   -d '{"intent": "ensure_safety", "urgency": "emergency", "context": {}}'
 
 # 3. Ask WHY those devices were chosen
-curl http://127.0.0.1:47200/v1/intents/ensure_safety/explain
+curl http://127.0.0.1:47200/v1/intents/ensure_safety/explain \
+  -H "Authorization: Bearer $DOSYNC_TOKEN"
 
 # 4. Read the tamper-evident record of what happened
-curl http://127.0.0.1:47200/v1/audit?limit=10
+curl "http://127.0.0.1:47200/v1/audit?limit=10" \
+  -H "Authorization: Bearer $DOSYNC_TOKEN"
+```
+
+<details>
+<summary><b>The same calls in PowerShell</b></summary>
+
+`curl` in PowerShell is an alias for `Invoke-WebRequest`, and quoting JSON for
+`curl.exe` is impractical — a clean Windows machine following the commands above
+verbatim gets `JSON decode error`, because PowerShell passes the escaped quotes
+through literally. Build the body as an object instead:
+
+```powershell
+$body = @{
+  device_id = "siren-hall"; device_name = "Hall Siren"
+  manufacturer = "acme"; model = "S1"; firmware = "1.0"
+  category = "actuator"; tags = @("alarm","emergency")
+  emergency_capable = $true; cert_tier = "basic"
+  capabilities = @{ sensors = @(); actuators = @(@{ id="alarm"; type="alarm"; description="sound" }) }
+} | ConvertTo-Json -Depth 6
+
+$headers = @{ Authorization = "Bearer $env:DOSYNC_TOKEN" }
+
+Invoke-RestMethod -Method Post -Uri http://127.0.0.1:47200/v1/devices/register `
+  -Headers $headers -ContentType "application/json" -Body $body
+
+Invoke-RestMethod -Method Post -Uri http://127.0.0.1:47200/v1/intent/async `
+  -Headers $headers -ContentType "application/json" `
+  -Body (@{ intent = "ensure_safety"; urgency = "emergency"; context = @{} } | ConvertTo-Json)
+
+Invoke-RestMethod -Uri http://127.0.0.1:47200/v1/intents/ensure_safety/explain -Headers $headers
+Invoke-RestMethod -Uri "http://127.0.0.1:47200/v1/audit?limit=10" -Headers $headers
+```
+
+</details>
 ```
 
 Step 3 is the one worth pausing on: the hub tells you which devices it
@@ -338,7 +436,13 @@ Matter, BLE, MAVLink, and the Home Assistant bridge, which is the widest door of
 all: anything HA already integrates, DoSync can reach. **Reference** adapters
 (WiZ, Shelly) implement one vendor's product and ship as worked examples of how
 an adapter is written — not as endorsement, partnership, or a promise to track
-anyone's firmware. **Infrastructure** is notifications.
+anyone's firmware. **They register only when their vendor library is installed,
+and say nothing when it is not.** A hub whose operator owns nothing from that
+vendor should never be told to install anything: the protocol does not presume
+your hardware, and a reference adapter that nagged for `pip install pywizlight`
+on every start was presuming it. If you do register a device that names an
+adapter the hub cannot load, the startup check names that device and tells you
+its actions will be simulated. **Infrastructure** is notifications.
 
 **If your device is not covered, describe it in a file.** A declarative adapter
 is YAML or JSON — no code, no release of DoSync to wait for:
@@ -419,35 +523,6 @@ pip install 'dosync[mqtt]'     # MQTT devices
 pip install 'dosync[all]'      # everything
 ```
 
-### Access: token, your own password, or none
-
-The hub prints an API token the first time it starts and stores only a hash of
-it, so it cannot show you that one again. Three ways to deal with that,
-depending on who you are:
-
-```bash
-# 1. Choose your own, like a password — for a person who has to type it
-dosync-manage keys create --token "my-house-2026-kitchen" --label dashboard
-
-# 2. Let it generate one — for a program that will store it
-dosync-manage keys create --label my-integration
-
-# 3. Turn authentication off entirely
-DOSYNC_AUTH=false dosync-hub
-```
-
-**Option 3 is legitimate and not a trap door.** On a home network, behind a
-router, with no port forwarding, requiring a token protects against nobody who
-is not already inside your house. It is the wrong default for a clinic and a
-reasonable choice for a workshop, so DoSync provides it plainly instead of
-pretending everyone has the same threat model. What it is not suitable for is
-any hub reachable from outside its own network.
-
-Tokens are checked without rate limiting or lockout, so a chosen one must be at
-least 12 characters and a passphrase of several words is better than a short
-clever string. Existing keys: `dosync-manage keys list` (previews only — they
-are hashed), `dosync-manage keys revoke <preview>`, `dosync-manage keys reset`.
-
 ### Access: a password you choose, or none at all
 
 The hub prints a token on first start and stores only a hash of it, so it cannot
@@ -575,7 +650,7 @@ git clone https://github.com/giulianireg-spec/dosync-protocol
 cd dosync-protocol
 python3 -m venv venv && source venv/bin/activate
 pip install -e '.[dev]'
-pytest                                  # 667 tests
+pytest                                  # runs the full suite
 dosync-hub --reload
 ```
 
@@ -585,7 +660,7 @@ dosync-hub --reload
 
 | Component | Status |
 |---|---|
-| REST API (12+ endpoints) | ✅ |
+| REST API (40+ endpoints) | ✅ |
 | WebSocket real-time events | ✅ |
 | Web dashboard | ✅ |
 | API key authentication + SHA-256 audit log | ✅ |
@@ -644,7 +719,7 @@ python3 certify.py --host <hub-ip> --port 47200 --tier standard
 | Language | Location | Author | Certification |
 |---|---|---|---|
 | Python (reference) | `server.py` | this project | Standard 33/33 · Emergency 44/44 ✅ |
-| Node.js (companion) | [giulianireg-spec/dosync-node](https://github.com/giulianireg-spec/dosync-node) | this project | 33/33 Standard ✅ |
+| Node.js (companion) | [giulianireg-spec/dosync-node](https://github.com/giulianireg-spec/dosync-node) | this project | Standard 33/33, against the v0.3 suite — re-validation against the current 56-test suite pending |
 
 The Node.js implementation is a **companion** port that validates the protocol
 is implementable in a second language against the same certification suite —
@@ -692,4 +767,4 @@ Apache 2.0 — free to implement, free to extend, no royalties.
 
 ---
 
-*DoSync Protocol v0.3.0 · © 2026 Rodrigo Giuliani · rgiuliani@dosync.dev*
+*DoSync Protocol · © 2026 Rodrigo Giuliani · rgiuliani@dosync.dev*

{dosync-0.4.2 → dosync-0.5.0}/README.md

@@ -149,7 +149,7 @@ DoSync earns its place in specific situations — and honestly gets in the way i
 ```
 User / AI says:  "there is an emergency at home"
                           │
-                    DoSync Hub v0.3.0
+                       DoSync Hub
                           │
           ┌───────────────┼───────────────┐
           ▼               ▼               ▼
@@ -196,6 +196,50 @@ pipx install dosync      # recommended
 dosync-hub
 ```
 
+<details>
+<summary><b>On Windows</b> — pipx is not installed with Python there</summary>
+
+Every step below was found by running it on a clean Windows machine. None of it
+is exotic; it is simply what Windows needs and what this page used to omit.
+
+```powershell
+python -m pip install --user pipx
+python -m pipx ensurepath
+```
+
+**Close PowerShell and open it again.** `ensurepath` edits your PATH and the
+session you are in cannot see the change. Then:
+
+```powershell
+pipx install dosync
+dosync-hub
+```
+
+Two things the rest of this page assumes that PowerShell does not provide:
+`export VAR=value` is `$env:VAR = "value"`, and `curl` is an alias for
+`Invoke-WebRequest`, which is a different program with a different syntax — use
+`curl.exe`, or the PowerShell examples further down. `setup_pki.sh` is a shell
+script and needs Git Bash or WSL.
+
+</details>
+
+### Then open the dashboard
+
+```
+http://localhost:47200
+```
+
+Paste the API key the hub printed on startup, press **Scan**, and the hub
+searches every transport it can reach — WiFi broadcast, mDNS, SSDP, Bluetooth —
+and shows what answered. Name anything you want to keep and it is adopted.
+
+**Start here.** Discovering and adopting a device needs no terminal and no
+JSON: a 3D printer, a television and a Bluetooth sensor were adopted this way
+on the reference deployment without a line being typed. The API calls below are
+for building against DoSync, not for setting it up — they came first on this
+page for a long time, which told people who do not write code that the project
+was not for them, while a button that did the same job sat one section lower.
+
 <details>
 <summary><b>"error: externally-managed-environment"?</b> — Raspberry Pi OS, Debian 12+, Ubuntu 23.04+</summary>
 
@@ -233,11 +277,28 @@ That is a working hub on `http://127.0.0.1:47200`. It starts with a simulated
 executor, so you can drive the whole protocol — register devices, fire intents,
 read the audit chain — before you own a single smart device.
 
+### Or drive it from the API
+
+Everything the dashboard does is an HTTP call, and this is the part to read if
+you are building against DoSync rather than setting it up.
+
+The hub prints an API key on that first start and stores only a hash of it, so
+it is shown once. Save it — every command below needs it:
+
+```bash
+export DOSYNC_TOKEN=<the key printed on first start>
+```
+
+```powershell
+$env:DOSYNC_TOKEN = "<the key printed on first start>"
+```
+
 Register something and give it a goal:
 
 ```bash
 # 1. A device declares what it CAN DO (not what commands it takes)
 curl -X POST http://127.0.0.1:47200/v1/devices/register \
+  -H "Authorization: Bearer $DOSYNC_TOKEN" \
   -H 'Content-Type: application/json' -d '{
     "device_id": "siren-hall", "device_name": "Hall Siren",
     "manufacturer": "acme", "model": "S1", "firmware": "1.0",
@@ -248,14 +309,50 @@ curl -X POST http://127.0.0.1:47200/v1/devices/register \
 
 # 2. An AI expresses a GOAL — not a command, and it names no device
 curl -X POST http://127.0.0.1:47200/v1/intent/async \
+  -H "Authorization: Bearer $DOSYNC_TOKEN" \
   -H 'Content-Type: application/json' \
   -d '{"intent": "ensure_safety", "urgency": "emergency", "context": {}}'
 
 # 3. Ask WHY those devices were chosen
-curl http://127.0.0.1:47200/v1/intents/ensure_safety/explain
+curl http://127.0.0.1:47200/v1/intents/ensure_safety/explain \
+  -H "Authorization: Bearer $DOSYNC_TOKEN"
 
 # 4. Read the tamper-evident record of what happened
-curl http://127.0.0.1:47200/v1/audit?limit=10
+curl "http://127.0.0.1:47200/v1/audit?limit=10" \
+  -H "Authorization: Bearer $DOSYNC_TOKEN"
+```
+
+<details>
+<summary><b>The same calls in PowerShell</b></summary>
+
+`curl` in PowerShell is an alias for `Invoke-WebRequest`, and quoting JSON for
+`curl.exe` is impractical — a clean Windows machine following the commands above
+verbatim gets `JSON decode error`, because PowerShell passes the escaped quotes
+through literally. Build the body as an object instead:
+
+```powershell
+$body = @{
+  device_id = "siren-hall"; device_name = "Hall Siren"
+  manufacturer = "acme"; model = "S1"; firmware = "1.0"
+  category = "actuator"; tags = @("alarm","emergency")
+  emergency_capable = $true; cert_tier = "basic"
+  capabilities = @{ sensors = @(); actuators = @(@{ id="alarm"; type="alarm"; description="sound" }) }
+} | ConvertTo-Json -Depth 6
+
+$headers = @{ Authorization = "Bearer $env:DOSYNC_TOKEN" }
+
+Invoke-RestMethod -Method Post -Uri http://127.0.0.1:47200/v1/devices/register `
+  -Headers $headers -ContentType "application/json" -Body $body
+
+Invoke-RestMethod -Method Post -Uri http://127.0.0.1:47200/v1/intent/async `
+  -Headers $headers -ContentType "application/json" `
+  -Body (@{ intent = "ensure_safety"; urgency = "emergency"; context = @{} } | ConvertTo-Json)
+
+Invoke-RestMethod -Uri http://127.0.0.1:47200/v1/intents/ensure_safety/explain -Headers $headers
+Invoke-RestMethod -Uri "http://127.0.0.1:47200/v1/audit?limit=10" -Headers $headers
+```
+
+</details>
 ```
 
 Step 3 is the one worth pausing on: the hub tells you which devices it
@@ -277,7 +374,13 @@ Matter, BLE, MAVLink, and the Home Assistant bridge, which is the widest door of
 all: anything HA already integrates, DoSync can reach. **Reference** adapters
 (WiZ, Shelly) implement one vendor's product and ship as worked examples of how
 an adapter is written — not as endorsement, partnership, or a promise to track
-anyone's firmware. **Infrastructure** is notifications.
+anyone's firmware. **They register only when their vendor library is installed,
+and say nothing when it is not.** A hub whose operator owns nothing from that
+vendor should never be told to install anything: the protocol does not presume
+your hardware, and a reference adapter that nagged for `pip install pywizlight`
+on every start was presuming it. If you do register a device that names an
+adapter the hub cannot load, the startup check names that device and tells you
+its actions will be simulated. **Infrastructure** is notifications.
 
 **If your device is not covered, describe it in a file.** A declarative adapter
 is YAML or JSON — no code, no release of DoSync to wait for:
@@ -358,35 +461,6 @@ pip install 'dosync[mqtt]'     # MQTT devices
 pip install 'dosync[all]'      # everything
 ```
 
-### Access: token, your own password, or none
-
-The hub prints an API token the first time it starts and stores only a hash of
-it, so it cannot show you that one again. Three ways to deal with that,
-depending on who you are:
-
-```bash
-# 1. Choose your own, like a password — for a person who has to type it
-dosync-manage keys create --token "my-house-2026-kitchen" --label dashboard
-
-# 2. Let it generate one — for a program that will store it
-dosync-manage keys create --label my-integration
-
-# 3. Turn authentication off entirely
-DOSYNC_AUTH=false dosync-hub
-```
-
-**Option 3 is legitimate and not a trap door.** On a home network, behind a
-router, with no port forwarding, requiring a token protects against nobody who
-is not already inside your house. It is the wrong default for a clinic and a
-reasonable choice for a workshop, so DoSync provides it plainly instead of
-pretending everyone has the same threat model. What it is not suitable for is
-any hub reachable from outside its own network.
-
-Tokens are checked without rate limiting or lockout, so a chosen one must be at
-least 12 characters and a passphrase of several words is better than a short
-clever string. Existing keys: `dosync-manage keys list` (previews only — they
-are hashed), `dosync-manage keys revoke <preview>`, `dosync-manage keys reset`.
-
 ### Access: a password you choose, or none at all
 
 The hub prints a token on first start and stores only a hash of it, so it cannot
@@ -514,7 +588,7 @@ git clone https://github.com/giulianireg-spec/dosync-protocol
 cd dosync-protocol
 python3 -m venv venv && source venv/bin/activate
 pip install -e '.[dev]'
-pytest                                  # 667 tests
+pytest                                  # runs the full suite
 dosync-hub --reload
 ```
 
@@ -524,7 +598,7 @@ dosync-hub --reload
 
 | Component | Status |
 |---|---|
-| REST API (12+ endpoints) | ✅ |
+| REST API (40+ endpoints) | ✅ |
 | WebSocket real-time events | ✅ |
 | Web dashboard | ✅ |
 | API key authentication + SHA-256 audit log | ✅ |
@@ -583,7 +657,7 @@ python3 certify.py --host <hub-ip> --port 47200 --tier standard
 | Language | Location | Author | Certification |
 |---|---|---|---|
 | Python (reference) | `server.py` | this project | Standard 33/33 · Emergency 44/44 ✅ |
-| Node.js (companion) | [giulianireg-spec/dosync-node](https://github.com/giulianireg-spec/dosync-node) | this project | 33/33 Standard ✅ |
+| Node.js (companion) | [giulianireg-spec/dosync-node](https://github.com/giulianireg-spec/dosync-node) | this project | Standard 33/33, against the v0.3 suite — re-validation against the current 56-test suite pending |
 
 The Node.js implementation is a **companion** port that validates the protocol
 is implementable in a second language against the same certification suite —
@@ -631,4 +705,4 @@ Apache 2.0 — free to implement, free to extend, no royalties.
 
 ---
 
-*DoSync Protocol v0.3.0 · © 2026 Rodrigo Giuliani · rgiuliani@dosync.dev*
+*DoSync Protocol · © 2026 Rodrigo Giuliani · rgiuliani@dosync.dev*

{dosync-0.4.2 → dosync-0.5.0}/dosync/__init__.py

@@ -13,5 +13,5 @@ The two numbers move independently on purpose:
   __version__           this implementation of the hub  (semver)
   __protocol_version__  the wire contract other implementations must match
 """
-__version__ = "0.4.2"
+__version__ = "0.5.0"
 __protocol_version__ = "0.4"

{dosync-0.4.2 → dosync-0.5.0}/dosync/adapters/__init__.py

@@ -1,17 +1,17 @@
 """
 DoSync — Adapter Layer
 ======================
-Capa de traducción entre el protocolo DoSync y dispositivos físicos reales.
+Translation layer between the DoSync protocol and real physical devices.
 
 Modelo:
     DoSync Hub → AdapterExecutor → [WiZAdapter | GPIOAdapter | ShellyAdapter | ...]
 
 Para agregar un nuevo dispositivo:
     1. Crear adapters/mi_marca.py implementando DoSyncAdapter
-    2. Registrar el dispositivo con adapter="mi_marca" en su CapabilityManifest
-    3. El hub lo maneja igual que cualquier otro dispositivo — sin cambios al núcleo
+    2. Register the device with adapter="my_brand" in its CapabilityManifest
+    3. The hub treats it like any other device — no core changes needed
 
-Publicación de adapters de terceros:
+Publishing third-party adapters:
     pip install dosync-adapter-philipshue
     pip install dosync-adapter-shelly
     pip install dosync-adapter-matter
@@ -27,11 +27,11 @@ from ..models import ActionResult, DeviceAction, Urgency
 log = logging.getLogger("dosync.adapters")
 
 
-# ── Interfaz base que todo adapter debe implementar ───────────────────────────
+# ── Base interface every adapter must implement ───────────────────────────────
 
 class DoSyncAdapter(ABC):
     """
-    Interfaz base para adapters de dispositivos físicos.
+    Base interface for physical device adapters.
 
     Cada adapter traduce acciones DoSync al protocolo nativo
     del dispositivo (UDP, HTTP, GPIO, BLE, etc.).
@@ -160,16 +160,16 @@ class DoSyncAdapter(ABC):
 class AdapterExecutor:
     """
     Ejecutor central que delega acciones al adapter correcto
-    según el campo 'adapter' del CapabilityManifest del dispositivo.
+    based on the 'adapter' field of the device's CapabilityManifest.
 
-    Si un dispositivo no tiene adapter registrado, cae al SimulatedExecutor.
+    A device with no registered adapter falls back to the SimulatedExecutor.
 
     Uso:
         executor = AdapterExecutor(hub)
         executor.register(WiZAdapter())
         executor.register(GPIOAdapter())
 
-        # El hub usa este executor en lugar del SimulatedExecutor
+        # The hub uses this executor instead of the SimulatedExecutor
         result = await hub.execute_intent(intent, executor)
     """
 
@@ -191,7 +191,7 @@ class AdapterExecutor:
             self._simulated = None
 
     def register(self, adapter: DoSyncAdapter) -> None:
-        """Registra un adapter por su nombre."""
+        """Register an adapter under its name."""
         self._adapters[adapter.adapter_name] = adapter
         log.info("Adapter registered: %s", adapter.adapter_name)
 
@@ -206,8 +206,8 @@ class AdapterExecutor:
 
     async def execute(self, action: DeviceAction, urgency: Urgency) -> ActionResult:
         """
-        Ejecuta una acción buscando el adapter correcto para el dispositivo.
-        Fallback al SimulatedExecutor si el dispositivo no tiene adapter.
+        Execute an action, looking up the right adapter for the device.
+        Falls back to the SimulatedExecutor when the device has no adapter.
         """
         device = self._hub.registry.get(action.device_id)
 
@@ -250,7 +250,7 @@ class AdapterExecutor:
                 result = await self._adapters[adapter_name].execute(action, urgency)
                 if result.success:
                     self._update_resolver_state(action)
-                # Device Health Monitor — registrar resultado
+                # Device Health Monitor — record the outcome
                 self._record_health(action, result)
                 return result
             except Exception as e:
@@ -267,13 +267,19 @@ class AdapterExecutor:
                 self._record_health(action, err_result)
                 return err_result
 
-        # Fallback
+        # Fallback. WARNING, not INFO, and the result says it was simulated:
+        # this branch is how a device that declares actuators nobody can execute
+        # still reports success. The reference deployment ran an SMS notifier
+        # here for an unknown length of time, and every log line read like an
+        # execution.
         if self._simulated:
-            log.info(
-                "No adapter for '%s' (device %s) — using SimulatedExecutor",
-                adapter_name or "none", action.device_id,
+            reason = ("no_adapter_declared" if not adapter_name
+                      else "adapter_unavailable")
+            log.warning(
+                "Simulating %s.%s — %s (adapter=%s). Nothing was sent to the device.",
+                action.device_id, action.action, reason, adapter_name or "none",
             )
-            return await self._simulated.execute(action, urgency)
+            return await self._simulated.execute(action, urgency, reason=reason)
 
         return ActionResult(
             device_id=action.device_id,
@@ -283,7 +289,7 @@ class AdapterExecutor:
         )
 
     def _record_health(self, action: DeviceAction, result) -> None:
-        """Registra el resultado en el Device Health Monitor."""
+        """Record the outcome in the Device Health Monitor."""
         try:
             db = getattr(self._hub, 'db', None)
             if db:
@@ -298,7 +304,7 @@ class AdapterExecutor:
                         action.device_id, _e)
 
     def _update_resolver_state(self, action: DeviceAction) -> None:
-        """Notifica al StateAwareResolver el nuevo estado tras una accion exitosa."""
+        """Tell the StateAwareResolver the new state after a successful action."""
         from ..hub import StateAwareResolver
         resolver = getattr(self._hub, 'resolver', None)
         if not isinstance(resolver, StateAwareResolver):