paulcollinsiii / iot-boards Goto Github PK

• Able to get / set sensor params via protobuf commands over MQTT

Local logging is extremely helpful for direct local debugging, but remote logging is needed

• StructLog like writing
• to the MQTT logging channel
• Logging capture on the Kube side, prometheus like support?
• Initial testing would be via a PING command on the command handler to dump the PONG message out on the response as well as to the log channel

Metadata needs to be able to have a friendly location name set on the sensor so that we can track which sensor is which from it's reported data a bit more easily

• Location is stored in NVS
• Location is pushed as part of the metadata field of measurement data, so as to not show up in every single measurement but rather once per batch sent
• telegraf is configured to include that metadata for each row that's being added (is this possible?)
• grafana dashboads updated so that labeled lines show up with the location name (as opposed to the device UUID)

• S2 will be wifi only
• Will need extra configuration options
• Local console provision script for testing setup?
• How to add a reset firmware button press
• Some kind of user feedback via LED's for status and resetting firmware

• Basic publish of a message to some test server from board
• Hardcoded authentication for now is fine, no TLS
• simple docker container for running mqtt broker, set QoS 0? Quick client to show message published

• Oneshot should actually be supported
• There's a long running crash, potentially timing related interaction between senor read, wifi beacon, and alarm firing? Any extra heap corruption detection that can be done?
• If the device reboots, alarms are gone. That's not okay. NVS and wear-leveling though is also going to be really annoying, so store it in cloud and pull on reboot?

Right now it's something that really can only be loved by a developer. See how hard it would be to make that something a bit nicer looking.

https://learn.adafruit.com/adafruit-eink-display-breakouts/drawing-bitmaps Worth testing out if we can draw a bitmap on there. If so that's icons AND data logging to SD card capabilities

Yes, sortof. Usually there's an amp involved for this and stereo output. https://www.adafruit.com/category/526 so it's possible but probably annoying to setup and get going.

The goal of having this make simple noises is still pending.

This will likely be a huge effort to add as getting the device on there is moderate complexity but getting the graphics libraries setup is probably high complexity.

Lvgl did most of the graphic library, translate driver for support and the are utter examples of ppl using it for eink displays

• Alarms configured via crontab style entry
• Alarms simply flash LED (GPIO #13) for 5 seconds for now
• Can CRUD alarms via MQTT
  • Need hooks to register commands with the MQTT command channel handler
  • Python test util to send in alarm commands from CLI

Currently the stack only supports the SHTC3 sensor. I have these sensors, need to get the driver written and working for them

• Driver written and able to read data
• RingBuffer added for this sensor's data
• JSON converter to pump data out to MQTT added

Datasheet: https://optoelectronics.liteon.com/upload/download/DS86-2015-0004/LTR-390UV_Final_%20DS_V1%201.pdf
Adafruit driver: https://github.com/adafruit/Adafruit_LTR390

Pods need inter-pod dependencies before they report as ready

e.g. Almost everything depends on the infuxdb being up before other traffic should be accepted

This would allow the device to send a long string securely to a mobile device and prove that you physically possess the device. There are some example apps out there for working with LiFi on Android and there is a couple Arduino libraries for sending data but they seem simplistic at the moment. Further digging is needed but this is very much a case of over engineering

MQTT is completely unauthenticated and sent in the clear. This isn't high-security stuff, but at the same time it should at least be authenticated. Get a hardcoded example of TLS or equiv authentication working on the board. Self-signed certs are fine for now, later maybe a real signed cert would be good.

https://github.com/fhessel/esp32_https_server

This alarm feature is based on the idea that the kid alarm clock is missing features. Duplicating things like the

• light colors
• increasing brightness over time
• nap timer
• Cutsy Face animations

Need a couple buttons on the board:

• Immediate attempt to connect to WiFi button
• Immediate dump ring buffer to disk and send system to power off state (deepsleep it?)
• Each button should have some kind of feedback via the led or neopixel

Battery Data

• Battery levels sent via sensormgr
• Low battery sets a light to flashing on the board (NeoPixel on S2, GPIO13 on ESP32)

Filesystem Data

• Disk freespace reported via sensormgr (very low datarate needed for this)

CPU Temp

• Same idea, report via sensormgr

DevOps stuff needed:

• Some way to serve static files from Kubernetes
• SSL certificate setup and signing. This will probably need some extra details from cert-manager to get that signing chain and verify the certificates it's currently creating for the Pods
• Some way of uploading the static files to the Kube so that we don't have to redeploy ever time we compile

IOT stuff needed:

• Build version should not just be the datestring of the compilation. I mean it can be the timestamp, but it should only be rebuilding when there are changes. That'll be a dig into the toolchain because it currently rebuilds every time it's requested to when it doesn't need to
  - [ ] OTA build output needs to be signed somehow and uploaded to the Kube for serving
• How do we name builds for the hardware to know what it's suppose to download?

Hook up a GPIO to a conductive strip and see if that's enough to make a refresh button out of. If so then it's worth adding that as a button for refreshing the display and putting it on a timer to refresh it again after a couple minutes. Guard against pushing it too often to prevent breaking the e-ink

Can probably copy most of the SHTC3 sensor code over, but update this to support the 4x sensor

• Update the command channel to support similar settings
• Update the protobuf test script to test commands sent to this sensor

Features needed:

• Set polling interval
• Start / Stop Polling
• Set sensor metadata? (e.g. location, friendly name)

Metadata needs to be able to have a friendly location name set on the sensor so that we can track which sensor is which from it's reported data a bit more easily

• Location is stored in NVS
• Location is pushed as part of the metadata field of measurement data, so as to not show up in every single measurement but rather once per batch sent
• telegraf is configured to include that metadata for each row that's being added (is this possible?)
• grafana dashboads updated so that labeled lines show up with the location name (as opposed to the device UUID)

• Be able to read data off it at configurable rate
• Be able to echo that data over the serial line if a command is received over serial to do so
• Add a serial command library