Announcement

Collapse
No announcement yet.

Occasional ‘bad’ data from rfxsensor?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Occasional ‘bad’ data from rfxsensor?

    I’m getting occasional bad data using rfxsensors and rfxrec....any clues in this log data?

    ay-15 5:22:46 PM RFXCOM 38 (RecRxChar) Unknown packet: 20D02EA05F
    May-15 5:22:46 PM RFXCOM Warning: 38 (processdm10) Unknown command=A0 SensorM10[53294]GF
    May-15 5:22:46 PM RFXCOM 38 (RecRxChar) receiver #1 packet: 20D02F40BF
    May-15 5:22:46 PM RFXCOM 38 (RecRxChar) Unknown packet: 20D028502F
    May-15 5:22:46 PM RFXCOM 38 (RecRxChar) receiver #1 packet: 20D02F40BF
    May-15 5:22:37 PM RFXCOM 38 (RecRxChar) receiver #1 packet: 2021D100C2
    May-15 5:22:37 PM RFXCOM 38 (Display_Z) RFXSensor A/D: type=Hum Device:RFXSensor[8657]Z Value:-23
    May-15 5:22:37 PM RFXCOM 38 (Display_H) Humidity Device:J10 Value:0
    May-15 5:22:37 PM RFXCOM 38 (Display_Z) RFXSensor A/D: RFXSensor[8657]Z Temp Value:5.7
    May-15 5:22:37 PM RFXCOM 38 (Display_Z) RFXSensor A/D: RFXSensor[8657]Z Volt: Supply Voltage used:497
    May-15 5:22:37 PM RFXCOM 38 (RecRxChar) receiver #1 packet: 2021D12309
    May-15 5:22:37 PM RFXCOM 38 (Display_Z) RFXSensor A/D: type=Hum Device:RFXSensor[8657]Z Value:62
    May-15 5:22:37 PM RFXCOM 38 (Display_H) Humidity Device:J10 Value:62
    May-15 5:22:37 PM RFXCOM 38 (Display_Z) RFXSensor A/D: RFXSensor[8657]Z Temp Value:5.7
    May-15 5:22:37 PM RFXCOM 38 (Display_Z) RFXSensor A/D: RFXSensor[8657]Z Volt: Supply Voltage used:497
    HS3 Pro Edition 3.0.0.435 (Windows 10 vmware)
    BLOccupied:,UltraNetCam3:,weatherXML:,RFXCOM:,Current Cost 3P:,UltraGCIR3:
    DMMQTT:,Kodi:,Z-Wave:,BLRadar:,EasyTrigger:,MySensors:,BLBackup:

    #2
    If only one RFXSensor transmits the unknown packets it could be an almost empty battery or bad sensor.
    If multiple sensors are received with wrong packets I guess there is high RF traffic that disturbs packets.

    Comment


      #3
      it’s multiple devices, all rfxsensors ....they used work but now they’re occasionally wrong enough to where you can’t trust,or make decisions based on value.


      Given the j10 device in question set value twice within a second, any way to set a percentage value from previous where a new value would be ignored?

      I’ve tried ignoring 0 values, then high values, but now seeing values that could be ok, just wrong because the swing is so large over such a short time...
      HS3 Pro Edition 3.0.0.435 (Windows 10 vmware)
      BLOccupied:,UltraNetCam3:,weatherXML:,RFXCOM:,Current Cost 3P:,UltraGCIR3:
      DMMQTT:,Kodi:,Z-Wave:,BLRadar:,EasyTrigger:,MySensors:,BLBackup:

      Comment


        #4
        The RFXsensors are 433MHz?
        If so, do have other 433 sensors that operate correct?

        Comment


          #5
          Click image for larger version

Name:	Screen Shot 2019-05-16 at 1.54.56 PM.png
Views:	124
Size:	318.5 KB
ID:	1305264
          I have 4 RFXSensors all occasionally give issues....but some more than others.

          I have one THGR810 on same interface and I have never observed an issue with it.
          HS3 Pro Edition 3.0.0.435 (Windows 10 vmware)
          BLOccupied:,UltraNetCam3:,weatherXML:,RFXCOM:,Current Cost 3P:,UltraGCIR3:
          DMMQTT:,Kodi:,Z-Wave:,BLRadar:,EasyTrigger:,MySensors:,BLBackup:

          Comment


            #6
            I still don't get why the devices 'sometimes' updates from rfxsensor within a second have wildly different values???? See J21 below the 63 value is just wrong....

            May-23 2:24:50 PM RFXCOM 38 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 211
            May-23 2:24:49 PM RFXCOM Transceiver #1 alive check, seq# D3
            May-23 2:24:39 PM RFXCOM 38 (RecRxChar) receiver #1 packet: 2080701582
            May-23 2:24:39 PM RFXCOM 38 (Display_T) Temperature: J13 Value:70.7
            May-23 2:24:23 PM RFXCOM 38 (RecRxChar) receiver #1 packet: 20CC3C1142
            May-23 2:24:23 PM RFXCOM 38 (Display_T) Temperature: J21 Value:63
            May-23 2:24:23 PM RFXCOM 38 (RecRxChar) receiver #1 packet: 20CC3C1A85
            May-23 2:24:23 PM RFXCOM 38 (Display_T) Temperature: J21 Value:79.7
            May-23 2:23:57 PM RFXCOM 38 (RecTRXChar) transceiver #1 packet: 0A5202BE250100BD410059
            May-23 2:23:57 PM RFXCOM 38 (Display_L) Battery dvref: 231 value:75
            May-23 2:23:57 PM RFXCOM 38 (Display_H) Humidity Device:J5 Value:65
            May-23 2:23:57 PM RFXCOM 38 (Display_T) Temperature: J7 Value:66
            May-23 2:23:57 PM RFXCOM 38 (RecTRXChar) transceiver #1 packet: 140100D20252190000210001011C00000000000000
            May-23 2:23:57 PM RFXCOM 38 (decode_InterfaceMessage)Info: transceiver #1 Get Status received, Sequence nbr = 210
            HS3 Pro Edition 3.0.0.435 (Windows 10 vmware)
            BLOccupied:,UltraNetCam3:,weatherXML:,RFXCOM:,Current Cost 3P:,UltraGCIR3:
            DMMQTT:,Kodi:,Z-Wave:,BLRadar:,EasyTrigger:,MySensors:,BLBackup:

            Comment


              #7
              If you enable X10 in the RFXtrx433 is the RFXSensor also received with wrong data?
              You can contact support rfxcom.com if the RFXSensor is also received with wrong data by the RFXtrx

              Comment

              Working...
              X