Sensor manager device not responding

[securitycopper]

On windows setting this up using the beta binary, getting an error:

What I've done:
systemctl disable --now swupdate-progress swupdate defibrillator
cd /opt/opensleep
chmod +x opensleep
RUST_LOG=debug,rumqttc=info ./opensleep

Side note:

• For instructions, consider adding after connected to wifi, back out of setup on the app, then remove the pod from the account before doing the ssh commands to disable the update service. Ended up bricking the app because it's handshake got corrupted, fixed the app issue by reinstalling it, clear app data and cache didn't fix the issue.

RUST_LOG=debug,rumqttc=info ./opensleep
[2025-10-26T20:05:32Z INFO opensleep] Starting opensleep...
[2025-10-26T20:05:32Z INFO opensleep] config.ron loaded
[2025-10-26T20:05:32Z INFO opensleep] Using timezone: America/New_York
[2025-10-26T20:05:32Z INFO opensleep::reset] Resetting Subsystems...
[2025-10-26T20:05:32Z INFO opensleep::mqtt] Initializing MQTT...
[2025-10-26T20:05:32Z INFO opensleep::mqtt] Connecting to MQTT broker at ****** as user '******'
[2025-10-26T20:05:32Z INFO opensleep::mqtt] MQTT broker connected
[2025-10-26T20:05:32Z INFO opensleep::sensor::manager] Initializing Sensor Subsystem...
[2025-10-26T20:05:32Z DEBUG opensleep::mqtt] Subscribing to opensleep/actions/calibrate
[2025-10-26T20:05:32Z WARN opensleep::sensor::presence] No presence config found. Please calibrate using 'opensleep/command/calibrate' endpoint.
[2025-10-26T20:05:32Z DEBUG mio_serial] opening serial port in synchronous blocking mode
[2025-10-26T20:05:32Z DEBUG opensleep::mqtt] Subscribed to opensleep/actions/calibrate
[2025-10-26T20:05:32Z DEBUG opensleep::mqtt] Subscribing to opensleep/actions/set_away_mode
[2025-10-26T20:05:32Z DEBUG opensleep::mqtt] Subscribed to opensleep/actions/set_away_mode
[2025-10-26T20:05:32Z DEBUG opensleep::mqtt] Subscribing to opensleep/actions/set_prime
[2025-10-26T20:05:32Z DEBUG opensleep::mqtt] Subscribed to opensleep/actions/set_prime
[2025-10-26T20:05:32Z DEBUG opensleep::mqtt] Subscribing to opensleep/actions/set_profile
[2025-10-26T20:05:32Z DEBUG opensleep::mqtt] Subscribed to opensleep/actions/set_profile
[2025-10-26T20:05:32Z DEBUG mio_serial] setting O_NONBLOCK for /dev/ttymxc0
[2025-10-26T20:05:32Z DEBUG opensleep::mqtt] Subscribing to opensleep/actions/set_presence_config
[2025-10-26T20:05:32Z DEBUG opensleep::mqtt] Subscribed to opensleep/actions/set_presence_config
[2025-10-26T20:05:32Z DEBUG opensleep::config::mqtt] Publishing config..
[2025-10-26T20:05:32Z DEBUG opensleep::config::mqtt] Published config
[2025-10-26T20:05:32Z INFO opensleep::frozen::manager] Initializing Frozen Subsystem...
[2025-10-26T20:05:32Z DEBUG mio_serial] opening serial port in synchronous blocking mode
[2025-10-26T20:05:32Z DEBUG mio_serial] setting O_NONBLOCK for /dev/ttymxc2
[2025-10-26T20:05:32Z DEBUG opensleep::frozen::manager] -> Ping
[2025-10-26T20:05:32Z DEBUG opensleep::frozen::manager] -> GetHardwareInfo

[2025-10-26T20:05:32Z INFO opensleep::frozen::state] Hardware info: SN ******** PN 20500 SKU 2 HWREV 0502 FACTORYFLAG 1 DATECODE 16091d
[2025-10-26T20:05:34Z INFO opensleep::sensor::manager] Trying Firmware mode
[2025-10-26T20:05:34Z DEBUG mio_serial] opening serial port in synchronous blocking mode
[2025-10-26T20:05:34Z DEBUG mio_serial] setting O_NONBLOCK for /dev/ttymxc0

thread 'main' panicked at src/sensor/manager.rs:56:83:
called Result::unwrap() on an Err value: Io(Custom { kind: NotFound, error: "Device not responding" })
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

[securitycopper]

Got passed this error:
The frankenfirmware was running so opensleep couldn't use /dev/ttymxc0, by killing it, opensleep was able to get past the above error.

command: fuser /dev/ttymxc0 
/dev/ttymxc0: 716

command: ps -fp 716 UID PID PPID C STIME TTY TIME CMD 
root 716 1 2 00:19 ? 00:00:02 /opt/eight/bin/frankenfirmware

command: kill 716

Commentary:

• I need to read though the instructions again, wasn't expecting to need to kill off a running process, maybe missed something.
• My next step is testing with the provided home assistant.

going to restart as i see some errors,

After Restart
it's back, traced it down to frank.service that is starting it.
Running command:
sudo systemctl disable frank.service
restarting

service seems to start up now, seeing only one error when running in debug:
ERROR opensleep::common::codec] Frozen/TargetUpdate wrong size: expected 6, got 2. Buffer: b"\xc0\x02"

[securitycopper]

Having issue setting temperature, in mqtt, shows left_temp 0 and right_temp 0,
sensor: piezo_ok false

giving up on it for the night, wasn't able to get the bed to start cooling. reverting back to stock.

[securitycopper]

Looking back at the instructions here compared to other guides.

Opensleep has:
Stop services: systemctl disable --now dac frank capybara swupdate-progress swupdate defibrillator

What I ran, likely based off a referenced guide:
systemctl disable --now swupdate-progress swupdate defibrillator

I'll try again tomorrow using the correct disable steps and see if that resolves my issue.

I'll follow up with the result, if it works, then I'll work on a PR for a troubleshooting.md to capture that the error means the service wasn't disabled.

Notes for toubleshooting.md:

• manager.rs: Device not responding -> This can happen if the frank service wasn't disabled.
• SleepEight App Crashes after disabling the services -> Clear cache and data doesn't work, fully removing the app and installing it back seems to resolve the app crashing. Recommend removing the pod from account prior to factory reset, then exist out of setup as soon as it's paired, leaving no pod on your account.
• Public key errors -> You have a short window to ssh in and disable the services before the update service updates the pod, to where your keys will be dropped.
• Do I need to factory reset, can't I just update the live partition? -> (speculation) Seems the pod's security does some checking to where the live partition authorized keys won't work if they don't match a signature from the factory reset. This impacts going back to base image.
• How do I go back to base image? -> Assuming you've written back the original sdcard image or are using the original sd card, do a factory reset after placing in the old card, using the card without a factory reset runs into the security preventing ssh from working.

[LiamSnow]

Hey! I was busy this weekend so I missed this.

Good job on the debugging. As I mentioned in #4 I accidentally deleted those setup instructions to disable frank and capybara. Completely my fault.

I think a troubleshooting.md would be a really good idea.

Currently opensleep does nothing with the Piezo, so if its not working thats fine - but slightly odd.

So at the moment is it working for you?

[securitycopper]

I've had a family event take priority, I won't be retesting till Friday when i can afford it not working.
I had so much trouble getting the files in the factory image that I have a script now to do it in an automated fashion from wsl in windows. I wasn't able to get automatic wifi connection working, so part of the script isn't needed. thinking when I do a pr, could include the file as WIP windows wsl ubuntu script as it's functional but has more in it then needed.

[securitycopper]

Progress Update:

I'm currently in process of testing a full workflow script that patches everything into the factory image with multiple options with goals:

• Flash with your files passed in as args, factory reset, reboot already fully configured to connect to wifi and start service

Preview of help menu:

[securitycopper]

Draft PR: #7

Finishing up with password setting working to get opensleep back in debug to look at logs.

@LiamSnow I haven't been able to get the cooling to turn on when setting left right temps with sleep schedule being the full day (trying to force it to cool). I'm able to set left right configs via mqtt, where it says success. I don't know if I'm doing something wrong or not, having an mqtt endpoint to test components would be helpful. This ends the update for the day, exhausted, been working on this all day. will pick up on the password issue tomorrow. (i've had password working before, so hope it won't be to much longer). Feel free to skim the PR for an idea on what i'm working on,

I currently run it with the following options, ** i removed sensitive details **:
/mnt/f/workspaces/opensleep/scripts/full_patch_workflow.sh \ -i /mnt/f/drive\ images/pod3_rootfs_orgional.img \ -k /mnt/c/Users/Matrix/.ssh/id_ed25519.pub \ -s "wifi endpoint" \ -p "wifi password" \ -b /mnt/f/drive\ images/opensleep \ -S /mnt/f/drive\ images/opensleep.service \ -c /mnt/f/drive\ images/config.ron \ -m "mac address" \ -d

What i like is that i:

• patch
• image the disk
• factory reset
• wait for green blinks to stop
• power cycle
• wait for mqtt connection (loads fully configured, eightsleep disabled, wifi connection, and corrected mac address)

[securitycopper]

pr ready to review #7