chaos-adept / iot-dipstick Goto Github PK

it is required to assembly autonomy flow watering based
the key abilities:

• measuring soil humidity
• measuring temperature and humidity in the air
• watering
• control of water volume in the tank
• control of water leaks on the floor
• sending monitoring data in the cloud
• working offline
• device sleeping?

Background
N Pots with soil with sensors

• Scenario: Monitor soil humidity

• Scenario: Watering dry soil on schedule

• NFR: 0-2 Pots should be supported

• NFR: Each Pot should have different watering consumption

• NFR: watering should be performed only within a specific time because of noise (if has wifi connection)

• NFR: working fully offline

actual steps

• define pot specific amount of water
• check day time (if it has a network connection)
• split single pod watering in partitions with delays for example instead of 600ml, 200ml x 3 times with 300 ms delay
• deep sleep to turn off voltage on soil sensors (to reduce oxidation)

it is useful to have

• a pre-configured environment for manual testing based terraform apply
• ready to use cpp header file with device ids and passwords and with registry id

refer to readme to find where the current firmare header file is located

#18 - related

the model
WINSENSOR ZH03B
https://www.chipdip.ru/product0/8001825831

it is required to recover sending to a dedicated device as it was initially by DEVICE_ID env variable

recommendation:

1. pass the first device id from the terraform resources as DEVICE_ID
2. verify that it works from cloud function sandbox How-to-test-Alice-Function
3. verify that it works from Alice skill How-to-test-Alice-Skill

Note, a device might be replaced by just using MQTT listener by using yc ref send a message one device

this may help

• How-to-test-Alice-Function
• How-to-test-Alice-Skill
• https://cloud.yandex.ru/docs/iot-core/operations/subscribe
• https://cloud.yandex.ru/docs/iot-core/operations/subscribe#sub-commands
• https://cloud.yandex.ru/docs/iot-core/operations/subscribe#for-all

• provide actual readme with list of community known resources to get started with arduino and esp8266 development
• provide project specific information to get started
• review and close

• TVOC/eCO2 https://amperkot.ru/msk/catalog/datchik_kachestva_vozduha_v_pomeschenii_sgp30_tvoc_eco2-32614748.html
• Temperature, Pressure and etc - https://amperkot.ru/msk/catalog/datchik_temperaturyi_i_vlazhnosti_bosch_cjmcu680_bme680-39166193.html
• Dust hello world firmware - https://amperkot.ru/msk/catalog/datchik_pyili_sharp_gp2y1010au0f-23869558.html
• Dust Sensor approach with voltage division to adopt 5v out to 1v which is supported by esp8266
• Make a 5v 1a power supply with parallel connection to the esp and dust sensor
• Test dust sensor with 1v out and esp8266
• Integrate dust sensor in the primary firmware

open questions

• can be i2c bus be placed in non D1, D2 pins
• pins can be re-ordered without gaps
• is it enough free pins in the existed firmware? i2c - 2 pins, 0-4 for pump transistors (as an option 74HC595 or other shift registers to safe pin count)
• supply 12v and stabilize to 5v over L4940V5 https://www.chipdip.ru/product/l4940v5 (the first attempt can be with 5v instead of 12v)

esp-idf - it is a framework for parallel task execution on the esp32.

this issue derives from #5 "esp-idf exploration is going to be a separate task."

it is required to adopt the following functionality under idf based:

• secured mqtt connection to the yandex cloud
• reading data from i2c sensors

https://www.chipdip.ru/product0/8001578234

it derives from #6
there is a bicycle for reading values from dust sensor it should be replaced with third party lib for reducing code base for supporting

at the moment there are a number of unit test only requirements, which are installed on the cloud only, they should be separated.
sample might be found here:
https://medium.com/ai2-blog/python-caching-in-github-actions-e9452698e98d

the main purpose of this page the short visit card/promo of the project
the resources might be taken from the presentation (will be provided on demand to the actual author of github pages)

Pages are located in the /docs folder

• https://docs.github.com/en/github/working-with-github-pages/about-github-pages
• https://developer.mozilla.org/ru/docs/Learn/Common_questions/Using_Github_pages

refer to theterraform/function.tf

there are two similar function creation with a lot of copy paste like hash calculation and zipping

https://cucumber.io
https://automationpanda.com/2018/10/22/python-testing-101-pytest-bdd/

models that could be used as the starting points:

• https://www.thingiverse.com/thing:3676533
• https://www.thingiverse.com/thing:2627220
• https://www.thingiverse.com/thing:2775946
  

Implement firmware for a sensor-only device that sends data with long intervals like 2h.
EPS has the ability to go to deep sleep, it should be used.

note the issue with sending commands to the device which sleep is out of the MVP scope

• reduce code complexity by extraction utility logic into separated modules
• extract actual ya cloud device passwords

it is not possible to get information from the Alice func, it says that there is no data for the last 3 hours, but it is not correct.

it is a regression bug.

there is no fresh log record it may has 1970 year or something like that, more details will be posted once the issue reproduced

that should be done for sure, the cloud metric function should fail when monitoring service returns non 200 HTTP response

note it might be overlapped with #10

otherwise, it is not possible to work with the same cloud folder from the different workstations

it is connected to the #11
it looks like it might be done by permanent topics
https://cloud.yandex.com/docs/iot-core/concepts/topic#permanent

• try to send mqtt tls messages to yandex cloud
• try to read values from dht12
• make a conditional compilation to include old wifi secure module for esp32

#6 there is an attempt to make the sensor composition.

there are no actual results for CO2 sensor, the SGP30 was used but it was broken before tests were finished, and it is quite expensive.

I've seen several fails with passwords which contain special chars that were passed into export-env script. I am not sure it's cmd or bash bug related with python, but seems like escaping passwords with quotes fix this issue.

The password with same special chars passed into the script separately (without terraform) doesn't make script fails.