kevin.cto
@kevinharris · Joined June 2025
Startup founder · logistics · new to IoT
- Topics
- 10
- Replies
- 54
- Points
- 0
Forum Replies Created
Connected, -18.2 is on the device page. Log tab did say why the 1883 attempt failed (plain port not allowed), I just didn’t know it existed. Thank you, demo is Thursday.
A host name and 8883. So the 1883 in the blog is wrong for this?
Can’t you just do LoRa.begin(868.1E6) and done? That’s how I set mine.
Ordered TLV3691s. Breadboard version with a 2.5 V reference and about 300 mV hysteresis sits at 4.8 µA in power-down and wakes cleanly at 11.79 V on my bench supply. Daily heartbeat added, and the offline rule. Thanks Laura, and Keisha the WDT version is my fallback.
Tried that, it works, average around 20 µA. I was hoping for less, and it feels clumsy.
Aoife’s right, and we went down the same road on our first trackers. What we ended up doing: two cases.
When the reading goes out right away, send a flat object with no ts. Hermetry stamps it with the time it arrived, which for a 10-minute temperature is plenty.
For the buffered ones you need a clock you trust. A DS3231 RTC module costs a few dollars, drifts about a minute a year, and runs from a coin cell while the ESP sleeps. Set it from NTP every time the hotspot is up and read it on every wake.
Don’t make up times. If the clock isn’t set yet (fresh coin cell, never been online) mark those readings and drop them or send them without ts. Hermetry refuses a record more than 10 minutes in the future as bad_ts, and a record in the past lands at the wrong place on the chart, which nobody notices for months. ts has to be milliseconds UTC. All on Timestamps, late and duplicate readings.
Cheaper to just buy a continuous rotation servo? They’re like 5 dollars
Why not just use a Modbus library? Seems like a lot of pain.
Noted, both of you. Gaps in the chart in front of investors is pretty much my nightmare.