liam96
@liam-price · Şubat 2025 tarihinde katıldı
Engineering student · university · new to IoT
- Konular
- 8
- Yanıtlar
- 13
- Puan
- 0
Oluşturulan forum yanıtları
The raw -= 65536 fix works, Hermetry shows -12.5 now and the chart doesn’t jump to 6000 anymore. Yesterday’s 6541 points are still sitting in the history, but everything new is right lol. Thanks Aoife.
That explains it, thanks Ciaran. We swapped the NPN proxes for PNP ones (the lab had some), the door and float switch go from +24 V to the inputs, all four show 0/1 in Hermetry now.
We only need on/off states, no counting. Good to know though.
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.
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.
Yapay zekâ tarafından English dilinden çevrildi ·
çalıştı!!! Otobüsten test ettim. Beni takılan bir şey: Komutu önce Privileged olarak oluşturdum, çünkü şebeke gerilimini anahtarlıyor ve karttaki anahtar komutun karttan gönderilemediğini söyledi. Basic olarak değiştirdim ve geçti. Ayrıca artık on_connect içinde abone oluyorum, sizin yazdığınız gibi; önceden Pi’nin Wi-Fi’si kısa süreliğine kesildikten sonra çalışmayı bırakıyordu.
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.
Yapay zekâ tarafından English dilinden çevrildi ·
Yani bulut ona geri komut gönderebiliyor mu? Peki telefon bunda nasıl devreye giriyor?
oh so the cloud can talk back to it? How does the phone come into it though?
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.
Yes. One Serial.println per sample.
Could it be a library conflict with the MQTT lib?
oh nice, didn’t know about dtostrf at all
is it a printf setting in the IDE? I think there’s a flag for floats somewhere
Yapay zekâ tarafından English dilinden çevrildi ·
Bu çok yardımcı oldu. Kafamda “şifre” ve “protokol” kavramlarını karıştırmışım. Uygulamalı bölüm için yeni planım: SPECK64/128’i ChaCha20 ile ATmega328P üzerinde karşılaştırmalı olarak ölçmek (bayt başına çevrim sayısı, flash, RAM) ve ESP32’leri broker’a normal TLS ile bağlı tutmak. Anahtar değişimi kısmını anlattığımda danışmanım “TLS yerine” kısmına güldü, bu yüzden sanırım zaten şaka yapıyordu.
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.