New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

Liam Price

liam96

@liam-price · Joined February 2025

Newcomer

Engineering student · university · new to IoT

Topics
8
Replies
13
Points
0
Newcomer10 points to Member

Forum Replies Created

Viewing 13 posts – 1 through 13 (of 13 total)

Fixed, but it was two things! Log tab showed keepalive_timeout AND “Taken over by a new session”. My first breadboard prototype was still plugged into a USB charger at home with the same token. Unplugged it, switched to the millis() version, and the device has been online for 6 hours.

♥ 0

Got it working on the lab furnace with clark.c’s script and a 10-minute expiry on the Pi side. My first deploy didn’t fire because I’d put the blocks before Save telemetry on the wrong branch, moved them after it. Leaving the request open in case a no-code version ever appears, but the flow does the job for my thesis.

♥ 0

it works!!! tested from the bus. One thing that tripped me: I first made the command Privileged because it switches mains and the switch on the board just said it can’t be sent from a board. Changed it to Basic and it went through. Also I subscribe in on_connect now like you wrote, before it stopped working after the Pi’s Wi-Fi blipped.

♥ 1

Switched to API mode with 10 samples per frame and the radio side is clean now, no lost frames in 20 minutes. The Pi sends x/y/z RMS and peak once a second. My supervisor actually prefers the RMS chart. I didn’t know about the per-device limits at all, that explains the warnings.

♥ 0

This helps a lot. I think I had “cipher” and “protocol” mixed up in my head. New plan for the practical chapter: benchmark SPECK64/128 against ChaCha20 on the ATmega328P (cycles per byte, flash, RAM), and keep the ESP32s on normal TLS to the broker. My supervisor laughed at the “instead of TLS” part when I explained the key exchange bit, so I think he was joking anyway.

♥ 0
Viewing 13 posts – 1 through 13 (of 13 total)