Skip to content

Add rak12035 VB Soil Monitor Tested & Working #6741

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 45 commits into
base: master
Choose a base branch
from

Conversation

Justin-Mann
Copy link

@Justin-Mann Justin-Mann commented May 5, 2025

Introduce the RAK12035 sensor as an environmental telemetry sensor, including necessary calibration checks and default values. Update relevant files to integrate the sensor into the existing telemetry system.

star of the show... https://docs.rakwireless.com/product-categories/wisblock/rak12035/quickstart/

This hardware is not just one module, but a couple.. RAK12023 and RAK12035 is the component stack, the RAK12023 does not seem to matter much and allows for multiple RAK12035 devices to be used.

Co-Authored-By: @fifieldt

This has been uploaded and tested on a RAK WIS Block hardware stack.
RAK19007 WIS Block Base Board
w/
RAK4631 WIS Block Module
RAK12500 GPS WIS Block Module
RAK12035 VB SOIL Monitor WIS Block Module
w/
solar panel
battery

Improvements could be made around the calibration of the RAK12035 devices.. I currently have it checking to see if the device has been pre-calibrated (this is highly recommended) and if not I am simply using some 'reasonable' values. the pre-calibration can be done by following the instructions and using the sketch supplied here [https://github.com/RAKWireless/RAK12035_SoilMoisture?tab=readme-ov-file#usage].

My build is currently in a waterproof case WISBLOCK Unify Enclosure and is use as part of an irrigation monitoring network we use to know when it is time to make certain adjustments to our physical irrigation resources. Pretty simple. Wanted to use WISBLOCK stuff, wanted to use Meshtastic, built using resilient enclosures and kept the code pretty simple.. Wanted the GPS for recovery purposes.. Got lots of help from @fifieldt. Things work well now. I have not finalized yet so no URL, but you can check on Instructables.com to find more detailed info about this build running in the wild (will post soon).

  • NOTES:
  • Currently this allows for a single RAK12035 to be installed and used with the RAK12023 WISBLOCK component.
  • There is nothing in any of the device clients showing the data yet.. I will work on the android stuff first probably, cause I need that for my real life project..
  • Future plan is, I will try to do some work to allow support for up to 3 RAK12035 soil monitors. I might work on allowing for some configuration values to be adjusted via the client apps as well once I start working on the android app a little. Other clients will (hopefully) get support as the community and myself have time to build it out. I would like to continue to add additional RAK WISBLOCK component support for different WISBLOCK components in general.

🤝 Attestations

  • [ Y ] I have tested that my proposed changes behave as described.
  • [ - ] I have tested that my proposed changes do not cause any obvious regressions on the following devices:
    • [ Y ] Heltec (Lora32) V3
    • [ N ] LilyGo T-Deck
    • [ N ] LilyGo T-Beam
    • [ Y ] RAK WisBlock 4631
    • [ N ] Seeed Studio T-1000E tracker card
    • [ N ] Other (please specify below)

fifieldt and others added 29 commits March 7, 2025 21:19
Introduce the RAK12035 sensor as an environmental telemetry sensor,
including necessary calibration checks and default values. Update
relevant files to integrate the sensor into the existing telemetry system.

This hardware is not just one module, but a couple.. RAK12023 and
RAK12035 is the component stack, the RAK12023 does not seem to matter
much and allows for multiple RAK12035 devices to be used.

Co-Authored-By: @Justin-Mann
Introduce the RAK12035 sensor as an environmental telemetry sensor,
including necessary calibration checks and default values. Update
relevant files to integrate the sensor into the existing telemetry system.

This hardware is not just one module, but a couple.. RAK12023 and
RAK12035 is the component stack, the RAK12023 does not seem to matter
much and allows for multiple RAK12035 devices to be used.

Co-Authored-By: @Justin-Mann
Introduce the RAK12035 sensor as an environmental telemetry sensor,
including necessary calibration checks and default values. Update
relevant files to integrate the sensor into the existing telemetry system.

This hardware is not just one module, but a couple.. RAK12023 and
RAK12035 is the component stack, the RAK12023 does not seem to matter
much and allows for multiple RAK12035 devices to be used.

Co-Authored-By: @Justin-Mann
Introduce the RAK12035 sensor as an environmental telemetry sensor,
including necessary calibration checks and default values. Update
relevant files to integrate the sensor into the existing telemetry system.

This hardware is not just one module, but a couple.. RAK12023 and
RAK12035 is the component stack, the RAK12023 does not seem to matter
much and allows for multiple RAK12035 devices to be used.

Co-Authored-By: @Justin-Mann
…K: RAK19007/RAK4631/RAK12035VB/RAK12500

looks like soil monitor is working correctly, new environmental metrics are comming thru [new protos soil_moisture, soil_temperature] and GPS is working again with the RAK 12500.

improvements could be made around the configuration of the monitor.

next steps include updating the client(s) to react to, log and display the new proto metrics for soil temp and humidity.
@Justin-Mann
Copy link
Author

@fifieldt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants