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. Development
  3. Can one child-sensor-id have multiple values

Can one child-sensor-id have multiple values

Scheduled Pinned Locked Moved Development
sensorid
8 Posts 3 Posters 3.2k 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.
  • daulagariD Offline
    daulagariD Offline
    daulagari
    Hero Member
    wrote on last edited by
    #1

    Looking more in detail in MySensors Serial Protocol (1.4) I see that there are two possible ways to have a node sending multiple values but I am wondering what is the way things are done. There seems to be some overlap in the protocol.

    Suppose I have a node (node-id = 7) that can measure the temperature (V_TEMP) and the light level (V_LIGHT_LEVEL), will the temperature and the light level then be reported with the same child-sensor-id or will both measurements be reported with different child-sensor-id values?

    1 Reply Last reply
    0
    • hekH Offline
      hekH Offline
      hek
      Admin
      wrote on last edited by
      #2

      I would probably present them as different childs.

      1 Reply Last reply
      0
      • daulagariD Offline
        daulagariD Offline
        daulagari
        Hero Member
        wrote on last edited by
        #3

        I would probably present them as different childs.

        Mwwh, this kind of freedom is not really good in protocols I think as it makes the job of implementing the controller more difficult ;-)

        1 Reply Last reply
        0
        • hekH Offline
          hekH Offline
          hek
          Admin
          wrote on last edited by
          #4

          Yes. The 1.4 protocol gives much freedom. If you follow the normal behavior between the sensor examples and controller you shouldn't run into any ambiguity.

          You might wanna look at the proposal for next version of the unit/protocol and give your feedback over there.
          http://forum.mysensors.org/topic/304/unit-standardization-2-0

          1 Reply Last reply
          0
          • daulagariD Offline
            daulagariD Offline
            daulagari
            Hero Member
            wrote on last edited by
            #5

            Good to understand that this is a known problem and that the sensor examples follow the rule different child-sensor-id per sensor.

            Yes, let's further discuss this in the other thread(s).

            YveauxY 1 Reply Last reply
            0
            • daulagariD daulagari

              Good to understand that this is a known problem and that the sensor examples follow the rule different child-sensor-id per sensor.

              Yes, let's further discuss this in the other thread(s).

              YveauxY Offline
              YveauxY Offline
              Yveaux
              Mod
              wrote on last edited by
              #6

              @daulagari I think that currently a child-id is meant to represent a single physical sensor. If you have a combined humidity/temperature sensor for example, it can use a single child-id. No one will stop you to implement it as two separate child-id's, though.

              http://yveaux.blogspot.nl

              1 Reply Last reply
              0
              • daulagariD Offline
                daulagariD Offline
                daulagari
                Hero Member
                wrote on last edited by
                #7

                I think that currently a child-id is meant to represent a single physical sensor. If you have a combined humidity/temperature sensor for example, it can use a single child-id.

                Yes, that makes sense although not from an user perspective.

                An user will not be interested in the fact that the "box" he has measures with one combined humidity/temperature sensor or with two separate sensors.

                YveauxY 1 Reply Last reply
                0
                • daulagariD daulagari

                  I think that currently a child-id is meant to represent a single physical sensor. If you have a combined humidity/temperature sensor for example, it can use a single child-id.

                  Yes, that makes sense although not from an user perspective.

                  An user will not be interested in the fact that the "box" he has measures with one combined humidity/temperature sensor or with two separate sensors.

                  YveauxY Offline
                  YveauxY Offline
                  Yveaux
                  Mod
                  wrote on last edited by
                  #8

                  @daulagari said:

                  that makes sense although not from an user perspective

                  Of coarse not. I just wanted to sketch the idea behind it.

                  http://yveaux.blogspot.nl

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


                  12

                  Online

                  11.7k

                  Users

                  11.2k

                  Topics

                  113.0k

                  Posts


                  Copyright 2019 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