Great suggestion, and you're not alone. There's been a few requests for this video. We're putting together some ideas for videos after our Month of Modules series and we'll keep this in mind. Stay tuned!
Maybe not the best place to ask this, but I'm curious - I would love to be able to integrate some longer-range LoRa sensors into Home Assistant. I know Meshtastic already has MQTT support, but I truthfully have no idea how I would get the data from Meshtastic/LoRa into MQTT. Can I just set up a "Meshtastic Base Station" with an ESP32-based Meshtastic device at home, and then have it send data directly via MQTT to an MQTT broker? Or does it have to go through the mobile app? Thank you!
Hi team, addicted newbie here. First, what a fantastic project and thanks so much for the work you are doing! Love previous suggestions, so here another one. How about a Soil module that supports moisture, pH and light?
It could be possible but depends on the sensor that is being used. The sensors that are supported in the firmware are all I2c and do instant reads without requiring any processing before sending over the mesh. Any other sensor can be supported by using a second MCU to do the processing (analog sensor data needs a lot of cleanup usually) and then pass the data back into the mesh using the serial module.
Hello, I have connected the PMSA003I sensor and BME680 sensor to the I2C interface on the TTGOLora32 board. Unfortunately, I only see the data from the BME but not the PMSA003I. What could be the problem?
Have you tried running them separately? The PMSA003I takes a lot of power. Is the fan running? I would try disabling the BME and go from there. Feel free to join the discord for additional help.
@@Meshtastic The fan runs perfectly, everything hardware seems to be working fine. I will try to install it individually but that would of course be counterproductive because I wanted to build a weather sensor board.
Is there a way to implement BME280 sensor modules in water resistant/sealed devices, or would it be better to keep water resistance and environmental telemetry features mutually exclusive? 🤔 Also, could you elaborate on counterfeit BME sensors, the pros/cons of such counterfeits, and where to source authentic ones affordably (in Canada)?
So the module sends the data over the mesh, but how does one remotely display that data back? Does it just pop out on the serial log of a receiving node when it's received?
Each client handles the data a little differently. The android app will only display the data on the device in the node list and each time a new telemetry packet is received that data is updated. The apple apps will actually log the data as well and provide you with charts/graphs as well as the ability to download the log. You can also receive the data via serial or MQTT if you want to log it externally.
I have the Rak12039 particle sensor and I am trying to integrate it into Meshtastic using the Wisblock. Could you go over swinging it up specifically? Does the data from this sensor get shown in the Meshtastic App?
@@Meshtastic I have the Rak12039 sending me "step 1" or "Step 0" based upon which GPIO pin to monitor. IS there a specific GPIO pin I should tell it to look for data at?
I'm using the Android Meshtastic app (which is awesome - thanks) and the RAK1901 TEMP HUMI module on a WisBlock and it transmits temperature and humidity data every 60 seconds when ChUtil and AirUtilTX data is sent, regardless of the Telemetry settings. The default is 900 seconds. I also tried 600 and 6000 but it always transmits every 60 seconds whenever the environmental sensor data is enabled. I only have the temperature and humidity modules so I can remotely monitor the nodes to see if they're too hot, too cold, or too wet inside their enclosures. What I'd like is to disable all transmissions unless someone sends a message, with the ability to manually interrogate a node to determine its temperature and humidity.
What version firmware and app are you running? You can join the discord and post in the #android channel and we can attempt to help you troubleshoot or if need be open a bug report. You can take a look at our `SENSOR` role, that role will prioritize telemetry packets. meshtastic.org/docs/configuration/radio/device/#roles
@@Meshtasticyou can You can use multiplication to convert hectopascals (hPa) to inches of mercury (inHg). Multiply the value in hPa by 0.02953 to get the equivalent value in inHg.
I have an idea for more functionalities, but I don't know if Meshtastic can help. Using a TSL2591, integrate a code that can function as a remote Sky Quality Meter (SQM) to monitor the sky conditions for astronomy and light pollution monitoring purposes.
It would depend on the sensor. We can only support instant read sensors. Any processing required would have to be done on a secondary MCU, but then could be sent over the mesh via the serial module.
Thanks for getting back to me. I have an MCU that is already performing the calculation and outputs an SQM value. Would it be possible to send this value to the Meshtastic platform and then remotely call for the data, essentially creating a dedicated sensor node for this purpose?
so it will show for any node the weather information in the app like it does the battery voltage, but is this possible to have one of the node capture and store this data to make a graphic or a wall display for example? is there an easy way to do this without programming.... total noob here. like the youngins say: "is there an app for that?"
The device interval is for how often you want device metrics sent over the mesh. The air quality interval is the interval for supported air quality sensors. See here for more info: meshtastic.org/docs/configuration/module/telemetry/
a working example would be useful to see. I tried to get a bme280 and a Heltec V2 to send Temp. It displays it locally, but not seen on the other nodes.
Telemetry data is sent over the Mesh and is viewable on other devices. On iOS devices you can view this data in the node menu, select the node and select "environment metrics log". For Android, the temp/humidity/pressure are displayed on the node on the node info page. meshtastic.org/docs/configuration/module/telemetry
Loving the videos! Thank you!
Great video! Please do one about the MQTT to connect via internet to bigger groups!
Great suggestion, and you're not alone. There's been a few requests for this video. We're putting together some ideas for videos after our Month of Modules series and we'll keep this in mind. Stay tuned!
This is sweet! Thank you for sharing!
need tipping bucket rain gauge and wind reporting is all I need support for.
Maybe not the best place to ask this, but I'm curious - I would love to be able to integrate some longer-range LoRa sensors into Home Assistant. I know Meshtastic already has MQTT support, but I truthfully have no idea how I would get the data from Meshtastic/LoRa into MQTT. Can I just set up a "Meshtastic Base Station" with an ESP32-based Meshtastic device at home, and then have it send data directly via MQTT to an MQTT broker? Or does it have to go through the mobile app? Thank you!
meshtastic.org/docs/software/mqtt/home-assistant
Hi team, addicted newbie here. First, what a fantastic project and thanks so much for the work you are doing! Love previous suggestions, so here another one. How about a Soil module that supports moisture, pH and light?
It could be possible but depends on the sensor that is being used. The sensors that are supported in the firmware are all I2c and do instant reads without requiring any processing before sending over the mesh. Any other sensor can be supported by using a second MCU to do the processing (analog sensor data needs a lot of cleanup usually) and then pass the data back into the mesh using the serial module.
Very cool.
How do I get the Battery infor to appear under Device Metrics when looking meshtastic map at my devices.
In iOS it is visible when you tap on the device. In Android, I don't think it provides any additional information other than the device's location.
Hello, I have connected the PMSA003I sensor and BME680 sensor to the I2C interface on the TTGOLora32 board. Unfortunately, I only see the data from the BME but not the PMSA003I. What could be the problem?
Have you tried running them separately? The PMSA003I takes a lot of power. Is the fan running? I would try disabling the BME and go from there. Feel free to join the discord for additional help.
@@Meshtastic The fan runs perfectly, everything hardware seems to be working fine. I will try to install it individually but that would of course be counterproductive because I wanted to build a weather sensor board.
Unfortunately I couldn't find a solution on Discord and have now disconnected the BME. But the PMSA is not recognized.@@Meshtastic
I have the PMSA0031 Particle Sensor. Should I get the info from the sensor on the screen?
No, there's currently no UI element for this sensor.
Is there a way to implement BME280 sensor modules in water resistant/sealed devices, or would it be better to keep water resistance and environmental telemetry features mutually exclusive? 🤔
Also, could you elaborate on counterfeit BME sensors, the pros/cons of such counterfeits, and where to source authentic ones affordably (in Canada)?
The data you receive would be only from within that seal device, not sure the benefits of it that's what you want then it's definitely possible.
So the module sends the data over the mesh, but how does one remotely display that data back? Does it just pop out on the serial log of a receiving node when it's received?
Each client handles the data a little differently. The android app will only display the data on the device in the node list and each time a new telemetry packet is received that data is updated. The apple apps will actually log the data as well and provide you with charts/graphs as well as the ability to download the log. You can also receive the data via serial or MQTT if you want to log it externally.
It would be interesting to have a Geiger counter module... Ok, I found the RadSens i2c module, cool.
This is something a few people have thought about as well. We'd love to see someone implement it into the firmware!
I have the Rak12039 particle sensor and I am trying to integrate it into Meshtastic using the Wisblock. Could you go over swinging it up specifically? Does the data from this sensor get shown in the Meshtastic App?
No data from this sensor is currently displayed in the apps. The raw data is just sent over the mesh.
@@Meshtastic I have the Rak12039 sending me "step 1" or "Step 0" based upon which GPIO pin to monitor. IS there a specific GPIO pin I should tell it to look for data at?
How can I forward the telemetry eniormental data to mqtt, or a channel?
I'm using the Android Meshtastic app (which is awesome - thanks) and the RAK1901 TEMP HUMI module on a WisBlock and it transmits temperature and humidity data every 60 seconds when ChUtil and AirUtilTX data is sent, regardless of the Telemetry settings. The default is 900 seconds. I also tried 600 and 6000 but it always transmits every 60 seconds whenever the environmental sensor data is enabled. I only have the temperature and humidity modules so I can remotely monitor the nodes to see if they're too hot, too cold, or too wet inside their enclosures. What I'd like is to disable all transmissions unless someone sends a message, with the ability to manually interrogate a node to determine its temperature and humidity.
What version firmware and app are you running? You can join the discord and post in the #android channel and we can attempt to help you troubleshoot or if need be open a bug report. You can take a look at our `SENSOR` role, that role will prioritize telemetry packets. meshtastic.org/docs/configuration/radio/device/#roles
How do you show barometric readings in inHG on the app using a BME680 and a RAK 4631?
The firmware outputs the barometric readings in hPA.
@@Meshtasticyou can You can use multiplication to convert hectopascals (hPa) to inches of mercury (inHg). Multiply the value in hPa by 0.02953 to get the equivalent value in inHg.
Is there anyway you can add this feature
I have an idea for more functionalities, but I don't know if Meshtastic can help. Using a TSL2591, integrate a code that can function as a remote Sky Quality Meter (SQM) to monitor the sky conditions for astronomy and light pollution monitoring purposes.
It would depend on the sensor. We can only support instant read sensors. Any processing required would have to be done on a secondary MCU, but then could be sent over the mesh via the serial module.
Thanks for getting back to me. I have an MCU that is already performing the calculation and outputs an SQM value. Would it be possible to send this value to the Meshtastic platform and then remotely call for the data, essentially creating a dedicated sensor node for this purpose?
so it will show for any node the weather information in the app like it does the battery voltage, but is this possible to have one of the node capture and store this data to make a graphic or a wall display for example? is there an easy way to do this without programming.... total noob here.
like the youngins say: "is there an app for that?"
capturing data is with MQTT
Is there a possibility to connect IR motion sensors or seismic sensors?
You'd like need to use a secondary MCU to then send that data via the serial module. Check out our serial video in this playlist.
I saw the serial module. Just wasn't sure if that was the way to connect them. Thank you!
Thanks! How long is the max. length of the i2c cables?
Anything past a couple of feet is pretty risky. Adafruit makes an extender though to accommodate longer runs
www.adafruit.com/product/4756
what's the difference between device update interval and air quality interval?
The device interval is for how often you want device metrics sent over the mesh. The air quality interval is the interval for supported air quality sensors. See here for more info: meshtastic.org/docs/configuration/module/telemetry/
I cannot find it on my Android phone. Any ideas?
a working example would be useful to see. I tried to get a bme280 and a Heltec V2 to send Temp. It displays it locally, but not seen on the other nodes.
Telemetry data is sent over the Mesh and is viewable on other devices.
On iOS devices you can view this data in the node menu, select the node and select "environment metrics log". For Android, the temp/humidity/pressure are displayed on the node on the node info page.
meshtastic.org/docs/configuration/module/telemetry
Niederschlag Sensor wäre noch toll.
If there's an i2c sensor that can be used, it might be possible but currently we do not have support for that.