Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Hardware
  3. BME280 Sensor Presentation

BME280 Sensor Presentation

Scheduled Pinned Locked Moved Hardware
2 Posts 2 Posters 1.4k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • naviathanN Offline
    naviathanN Offline
    naviathan
    wrote on last edited by
    #1

    I'm planning to use the BME280 in my sensor projects. Going through the information I see that I have to present the node to the controller as a specific device. I see options for each individual sensor category that this unit falls into, but I'm unsure of how to present it as all three (barometer, hygrometer and temperature). Should I just use the generic S_CUSTOM in the present or should I give it one of the sensors like S_TEMP and just message the extra data anyway? Is it possible to present a node as more than one thing? Maybe I'm over thinking it. Thoughts?

    tbowmoT 1 Reply Last reply
    0
    • naviathanN naviathan

      I'm planning to use the BME280 in my sensor projects. Going through the information I see that I have to present the node to the controller as a specific device. I see options for each individual sensor category that this unit falls into, but I'm unsure of how to present it as all three (barometer, hygrometer and temperature). Should I just use the generic S_CUSTOM in the present or should I give it one of the sensors like S_TEMP and just message the extra data anyway? Is it possible to present a node as more than one thing? Maybe I'm over thinking it. Thoughts?

      tbowmoT Offline
      tbowmoT Offline
      tbowmo
      Admin
      wrote on last edited by
      #2

      @naviathan

      You should present each child sensor as it own type, that is:
      child sensor id -> type
      1 -> S_TEMP
      2 -> S_HUMIDITY
      3 -> S_BAROMETER

      and then use the correct V_ types for transmitting the different sensor types.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      25

      Online

      11.7k

      Users

      11.2k

      Topics

      113.1k

      Posts


      Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • MySensors
      • OpenHardware.io
      • Categories
      • Recent
      • Tags
      • Popular