Announcement

Collapse
No announcement yet.

xapmcsRF - W800 / RFXCOM xAP Node

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #91
    Michael,

    I am just starting to use your xAP stuff because of the gaps that ACRF don't fill. I got it all set up and am receiving data. I have what is probably a simple question though. Is there any way to change it so that the status setting doesn't have the symbol and the "watts" (this is a power meter). I am trying to transfer the values into a database as well as use them in Mainlobby and the html that is in the string is screwing me up.

    Thanks,
    PiperPilot

    Comment


    • #92
      The numeric component should be in the DeviceValue. Will this work for you?

      Comment


      • #93
        Thanks for the response...I had actually tried that, but had a typo and now I see why I had a blank value...works fine!

        Comment


        • #94
          Invalid Message

          Running RFXCOM and xapmcsRF I am getting these messages in my HUB viewer. How do I fix this?


          Error Message: Invalid name/value pairing. The length of the UID value is incorrect
          Message Line#: 5 -
          uid=FW.005:3A0D30353744
          Received From: 192.168.7.7:32768
          xap-header
          {
          v
          =13
          hop=1
          uid=FW.005:3A0D30353744
          class=xapbsc.event
          source=mcs.W800.LEXINGTON:weatherstation.RFXCOM3A0D_057_D.WindDire ction
          }
          input.state
          {
          State=ON
          DisplayText=<table><td><img alt=' N (520 degrees)' src='/xapmcsW800/images/sensors/WindDirection.gif'><img alt = ' ' src='/xapmcsW800/images/sensors/blank1.gif'> N &nbsp;(520&nbsp;degrees)</td></table>
          Text=520
          }
          The error that was generated is as follows:
          Problem reading xAP message.
          Source: xAPMessage
          Problem reading xAP message.
          Invalid name/value pairing
          The length of the
          UID value is incorrect.
          KCS.xAP.Framework.xAPMessageReaderException: Problem reading xAP message. ---> KCS.xAP.Framework.xAPInvalidMessageException: Invalid name/value pairing
          The length of the
          UID value is incorrect
          at KCS.xAP.Framework.Message.xAPMessageReader.ReadHeaderPair(xA PMessage message, String line)
          at KCS.xAP.Framework.Message.xAPMessageReader.ReadMessage()
          --- End of inner exception stack trace ---
          at KCS.xAP.Framework.Message.xAPMessageReader.ReadMessage()
          at KCS.xAP.Framework.Transport.xAPListener.OnReceive(IAsyncResu lt ar)
          HS2 Environment
          Zotac 1.83 GHz Quadcore
          HomeSeer Way2Call
          Netiom-Xap board
          opnode 1-wire 1.2.7
          Plug-In's
          WeatherXML 1.0.0.32
          Pwr Link USB 1.0.0.13
          mcsTemp V6.2.0.14
          mcsXap V3.0.0.0/3.0.0.20
          IM Connector 4.87.2.5
          Sip Connector 2.56.2.4
          RFXCOM 15.0.0.22
          Odroid X2
          Asterisk 11.5.1
          FreePBX 2.11.0.42
          WebMin 1.720
          Xap Switchboard by Mi4

          There is no place Like 127.0.0.1

          Comment


          • #95
            The viewer was not designed to accept the longer UIDs per the V1.3 xAp specification.

            uid=FW.005:3A0D30353744

            This is a known problem with the viewer and the author is aware.

            xapmcsHub does not have issue with it, but then it is only good as a hub and not as a viewer to aid in message debug.

            I may in the future change the UID to be based upon a sequence number rather than based upon the address of the RF device.

            Comment


            • #96
              ds10a with V1.7.9

              Hello,
              I've just installed a "RFXCOM 433MHz/310MHz" ( slave/slave) with "ds10" sensor door 310MHz.
              The rfxcom unit is installed and not working with "ds10".
              If I open or close the door, I get data flowing in the rfreceiver (RFXCOM software) such as:

              A9EFE0857AE200 Visonic or DS10/90 Alert (battery low) addr:151A 0D/22696 bits=41 from SLAVE

              => door is open

              If I open the "IO window" then I don't seem to get much going on at all (compared to the rf receiver):

              22:04:31 | A9, EF, E0, 85, 7A, E2
              22:04:31 | 00 | Discarded 48 bit mode Security because lower nibble of address bytes not complemented
              22:04:31 | A9, EF, E0
              22:04:31 | 85, 7A, E2, 00
              22:04:31 | A9 | Discarding E0 after seeing invalid ID for 96 byte packet | Discarding 85 while trying to sync on byte-count byte | Discarding 7A while trying to sync on byte-count byte | Discarding E2 while trying to sync on byte-count byte | Discarding 00 while trying to sync on byte-count byte | Discarding A9 while trying to sync on byte-count byte | Discarding EF while trying to sync on byte-count byte
              22:04:31 | EF, E0, 85, 7A, E2, 00
              22:04:31 | A9, EF, E0 | Discarding E0 after seeing invalid ID for 96 byte packet | Discarding 85 while trying to sync on byte-count byte | Discarding 7A while trying to sync on byte-count byte | Discarding E2 while trying to sync on byte-count byte | Discarding 00 while trying to sync on byte-count byte | Discarding A9 while trying to sync on byte-count byte | Discarding EF while trying to sync on byte-count byte
              22:04:31 | 85, 7A, E2, 00
              22:04:31 | A9, EF, E0, 85 | Discarding E0 after seeing invalid ID for 96 byte packet | Discarding 85 while trying to sync on byte-count byte | Discarding 7A while trying to sync on byte-count byte | Discarding E2 while trying to sync on byte-count byte | Discarding 00 while trying to sync on byte-count byte | Discarding A9 while trying to sync on byte-count byte | Discarding EF while trying to sync on byte-count byte
              22:04:31 | 7A, E2, 00

              => door is open

              xapmcsRF don't reconize all bytes of ds10 ( 41 bits)

              Can you help me?

              Comment


              • #97
                This should be corrected in V1.7.10. I also added more visibiltiy as to why security packets are rejected.

                Comment


                • #98
                  Thanks Michael,
                  but I have another problem with KR10.

                  If I press ALARM , I get data flowing in the rfreceiver (RFXCOM software) such as:

                  29E3EC06F98E00 KR10/SH624 ARM Away (min) addr:E3EC 8E/14279 bits=41

                  If I press ALARM the "IO window" then I don't seem to get much going on at all (compared to the rf receiver):

                  20:25:18 | 29, E3, EC, 06, F9, 8E, 00 | Discarded 48 bit mode Security because packet criteria not satisified goodParity=True,Parity=4,b0=True,b1=True,b2=True,b3=False | Discarding EC while trying to sync on byte-count byte | Discarding 06 while trying to sync on byte-count byte | Discarding F9 while trying to sync on byte-count byte | Discarding 8E while trying to sync on byte-count byte | Discarding 00 while trying to sync on byte-count byte


                  I have another question about STATUS. Is it possible to recuperate the value of byte 3

                  example for KR10 :
                  0x06 ARM AWAY (min)

                  0x86 DISARM

                  0x46 Light On

                  0xC6 Light Off

                  0x26 PANIC
                  instead off ON/OFF ??

                  Comment


                  • #99
                    I changed the encoding to be the same as the 32 bit mode. You will have seperate devices for arm and lights. See if it works for you. I do not have hardware to test more than 32 bits, but I expect it to be ok. V1.7.11.

                    Comment


                    • Michael,
                      the Status is not recognize.

                      If I press ARM, the "IO window" show:

                      23:10:42 | 29, E3
                      23:10:42 | EC, 46, B9, 8E, 00 | E3EC= | Security Ignored because location not defined for sensor

                      ON and OFF are missing. It's the same for DS10

                      Comment


                      • The xapmcsRF browser page has a location field that needs to be populated to indicate your intention that this sensor will be communicated via xAP messages. It is the equivalent of the "A"ccept checkboxes on my other xAP applications. The location will from part of the xAP address for the sensor.

                        Comment


                        • Yes Michael, I check it. But Status not change.

                          In fact, the IO window dosen't show status:

                          23:10:42 | 29, E3
                          23:10:42 | EC, 46, B9, 8E, 00 | E3EC= | Security Ignored because location not defined for sensor

                          instant of in version V1.7.10 :
                          23:10:42 | 29, E3
                          23:10:42 | EC, 46, B9, 8E, 00 | E3EC= ON | Security Ignored because location not defined for sensor

                          Comment


                          • post your xapmcsRF.ini (it may be xapmcsW800.ini)

                            Comment


                            • OK, I remane in txt file.

                              Matisere
                              Attached Files

                              Comment


                              • I used your ini file and simulated the input of the Light On that you last posted and saw it function as desired. I noticed that I allowed X10 checkboxes to exist for non-x10 devices and removed that option. I also reverted back to the full UID for Oregon Scientific sensor now that the xAP Viewer has been updated. If you still have a problem then provide the debug output that is in the \Data folder when the debug checkbox is used. V1.7.12 is last uploaded.

                                Comment

                                Working...
                                X