The latest articles on DEV Community by 咻咻咻 (@_eaeba623341235aac75ac). https://dev.to/_eaeba623341235aac75ac https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4109154%2F6f720e2a-2afd-47e0-9844-f8e9bd4f5c6b.jpg https://dev.to/_eaeba623341235aac75ac en 咻咻咻 Fri, 04 Sep 2026 06:29:50 +0000 https://dev.to/_eaeba623341235aac75ac/how-we-keep-story-beats-and-device-actuators-in-sync-over-ble-1ob3 https://dev.to/_eaeba623341235aac75ac/how-we-keep-story-beats-and-device-actuators-in-sync-over-ble-1ob3 <p>Connected narrative hardware is easy to demo on the happy path. The interesting cases are mid-scene disconnect and what you put on the wire.</p> <h2> Event bus, not amplitude </h2> <p>We treat the story engine as a publisher of discrete events (beat reached, route chosen, voice line completed). Firmware maps each event to an actuation profile with start/shape/end. That avoids chasing a 20ms audio analysis loop across BLE jitter.</p> <h2> Mid-scene dropout defaults </h2> <ol> <li>Link lost → actuator idle (never hold last intensity)</li> <li>Story clock holds at a beat boundary</li> <li>Reconnect does not auto-resume physical output; the scene asks again</li> <li>Telemetry stays counters, not a session transcript</li> </ol> <h2> Why this belongs on DEV </h2> <p>This is a protocol/product-safety writeup for makers wiring interactive fiction to peripherals. Product context: <a href="https://www.creviatech.com/" rel="noopener noreferrer">Crevia Tech / CRAVE AI</a> (18+ hardware; this post is about the failure path).</p> iot bluetooth ai hardware