Skip to content
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

Add RAK12035VB Soil Moisture Sensor support #5481

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

Conversation

Justin-Mann
Copy link

Introduce the RAK12035VB 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.

I did as good a job as I could up to this point, but some correction may be necessary..

I kinda had an idea of how I wanted things to go, and I think the basic detection and registration methods being used for the sensors are probably enough so I did not implement any guards specific to the RAK soil monitoring.

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. *I did not code support for multiple RAK12035, but this could be handled in code if desired... *I wrote very simple support to default the configuration values for the soil moisture levels.. this could be imporved, but is a complex interaction so I would suggest doing what I did until the mobile apps are enhanced to support the new environmental data points.. (perhaps something could be built into the mobile admin gui to perform a water monitor config routine with feedback).

The main issue I have atm..


in ScanI2CTwoWire.cpp ln. 347...


I defined a case for devices with address 0x20.. I don't know where I got the values I did (probably left over from the pervious night's coding session from a copy and paste), but they do not work.. that check does not work.. I tried to run down registry uuid locations for both devices, but came up short.. and.. I'm apparently bad at this, so if anyone has more refined detection methods I could use or knowledge around this any help would be appreciated.


@CLAassistant
Copy link

CLAassistant commented Nov 29, 2024

CLA assistant check
All committers have signed the CLA.

@fifieldt
Copy link
Contributor

fifieldt commented Dec 7, 2024

Thanks for the updates and welcome to Meshtastic :)

As you've probably seen, the protobufs don't like to be checked in -- they're automatically generated, so its best to remove them from this commit. If you need help working with the git submodules let us know, they're a bit tricky :)

…ch form my project since there has not been that much guidance in terms of next steps for this branch.
…ties are already being used or 'set'. if not use them for the soil monitor.
@caveman99
Copy link
Member

@Justin-Mann i'd really like to include this, but due to heavy lifting in the sensor code and a few unfortunate checkins this PR is now conflicted beyond repair. Do you object if i sent in a new cleaned up PR and credited you as the author?

@Justin-Mann
Copy link
Author

Justin-Mann commented Jan 5, 2025 via email

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.

5 participants