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. Bug Reports
  3. [Solved] Help: gateway is sometimes receiving wrong values

[Solved] Help: gateway is sometimes receiving wrong values

Scheduled Pinned Locked Moved Bug Reports
13 Posts 4 Posters 3.0k Views 4 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.
  • HeinzH Heinz

    Nobody who can explain the jammed data on 16:21:30?
    What happens if two sensors send data at the same time?

    Nca78N Offline
    Nca78N Offline
    Nca78
    Hardware Contributor
    wrote on last edited by mfalkvidd
    #3

    @Heinz said in Help: gateway is sometimes receiving wrong values:

    What happens if two sensors send data at the same time?

    Data from both sensors is corrupted and they have to resend. You cannot have "mixed" data as there is a checksum in the message and even if it picked up cleanly one of the two checksum there's no way it could match a "mixed" message.

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

      No, I don't get it either..

      The (Serial COM 13) log you show is from the node right? It looks corrupted from the start. You aren't trying to read out a signed value into uint32 right?

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

        Yes the left one is printed directly from the sensor node.
        Why does it look corrupted from the start???

        The value to be transmitted is an uint32_t which represents a resistance in Ohm.
        On the left side the values are ok, but the value received from the gateway is sometimes a very large one.
        This occurs sporadically 1-3 times per hour. The value should be transfered every 10 seconds.

        All other nodes here in my home work very well. Only this one makes problems.
        Adruino Uno, NRF, BME680 breakoutboard from watterott (http://www.watterott.com/de/BME680-Breakout) via I2C.

        The strange thing is that not only the value is damaged, but also the type.
        Sketch can be found here:
        https://github.com/windkh/mysensors/tree/master/BME680Sensor

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

          Sorry, misread. Yes, the value is being sent correctly.
          I have no clue why it behaves like this. Any corrupted message should be caught by the NRF24-hardware and be thrown away.

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

            Then I will exchange the radio...

            1 Reply Last reply
            0
            • rejoe2R Offline
              rejoe2R Offline
              rejoe2
              wrote on last edited by
              #8

              What type of GW do you use?
              There had been reports on (constantly) corrupted messages in some versions of the Wifi-GW (ESP8266). You may update to version 2.2-beta and use recent versions of the ESP stuff.

              Controller: FHEM; MySensors: 2.3.1, RS485,nRF24,RFM69, serial Gateways

              1 Reply Last reply
              0
              • HeinzH Offline
                HeinzH Offline
                Heinz
                Hero Member
                wrote on last edited by Heinz
                #9

                Arduino uno with Ethernet
                https://forum.mysensors.org/uploads/upload-2ceff83a-1538-4fd4-816d-d3cfef6e0c06.JPG

                mysensors 2.0

                1 Reply Last reply
                0
                • rejoe2R Offline
                  rejoe2R Offline
                  rejoe2
                  wrote on last edited by
                  #10

                  Nice case :grinning: .
                  Does mysensors 2.0 mean 2.0.0 or 2.2.0-beta?

                  I still recommend to try most recent beta code (in between transport problems @nrf24 seem to be solved) at least for the gw.

                  Controller: FHEM; MySensors: 2.3.1, RS485,nRF24,RFM69, serial Gateways

                  1 Reply Last reply
                  0
                  • HeinzH Offline
                    HeinzH Offline
                    Heinz
                    Hero Member
                    wrote on last edited by
                    #11

                    I am not using the beta but the standard 2.0.0 release

                    1 Reply Last reply
                    0
                    • HeinzH Offline
                      HeinzH Offline
                      Heinz
                      Hero Member
                      wrote on last edited by
                      #12

                      Ok, it seems that I found the cause of the problem: after changing the radio everything works as expected:

                      Here the green line with sporadic wrong values:
                      0_1509743234795_BME680.png

                      And here the result with a new radio:
                      0_1509743267882_BME680-2.png

                      --> SOLVED

                      1 Reply Last reply
                      3
                      • HeinzH Offline
                        HeinzH Offline
                        Heinz
                        Hero Member
                        wrote on last edited by
                        #13

                        Studying the log files of the night I found one damaged value

                        2017-11-04_23:02:43 MYSENSOR_BME680_R 33597 Ohm
                        2017-11-04_23:02:53 MYSENSOR_BME680_R 33760 Ohm
                        2017-11-04_23:03:04 MYSENSOR_BME680_R 33814 Ohm
                        2017-11-04_23:03:25 MYSENSOR_BME680_R 33705 Ohm
                        2017-11-04_23:03:25 MYSENSOR_BME680_R 2164818857 Ohm
                        2017-11-04_23:03:36 MYSENSOR_BME680_R 33814 Ohm
                        2017-11-04_23:03:46 MYSENSOR_BME680_R 33869 Ohm
                        2017-11-04_23:04:07 MYSENSOR_BME680_R 33624 Ohm
                        2017-11-04_23:04:49 MYSENSOR_BME680_R 33924 Ohm

                        Well, exchanging the radio improved the situation significantly, but unfortunately the problem might be still there....

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


                        11

                        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