Announcement

Collapse
No announcement yet.

Problems with HE remotes

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

    Problems with HE remotes

    I've recently recieved my RFXCOM transmitter/reciever (LAN version) and got everything set up. I can control all my lights etc from Homeseer with no issues.

    I've started to set up my HE remotes to trigger events in Homeseer, so for example, a wall switch in my lounge controls all the lights.

    The switch is set up as an input device and the event is triggered on 'value set to' e.g. 250 for on, 0 for off. (A seperate event for each).

    The problem is that this doesn't work 100% of the time - the signal is recieved and logged, but the event does not always fire - the log below shows this in action. In this case a key fob state is used to trigger an event, but the same behaviour occurs with wall switches and HE remotes of any type.

    <TABLE cellSpacing=2 cellPadding=0 width="100%" border=0><TBODY><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType1 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry1 align=left colSpan=8>(display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:256</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Event Trigger "Key Fob 1 Off"</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Event Trigger "Kitchen Lights Off"</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Device: Ground Floor Kitchen Display Cabinet Lights (A11) OFF</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Device: Ground Floor Kitchen Bar + Cupboard Lights (A10) OFF</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Device: Ground Floor Kitchen Pelmet LEDs (A9) OFF</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType1 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry1 align=left colSpan=8>(SetIOEx):A11, Xmit=1, Cmd=3, Brt=0, D1/D2=0/0, Vcmd=, Host=</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType0 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry0 align=left colSpan=8>(SetIOEx):A10, Xmit=1, Cmd=3, Brt=0, D1/D2=0/0, Vcmd=, Host=</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType1 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry1 align=left colSpan=8>(SetIOEx):A9, Xmit=1, Cmd=3, Brt=0, D1/D2=0/0, Vcmd=, Host=</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType0 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry0 align=left colSpan=8>(RecRxChar) packet received: 2201A26EA0D0</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:53:58 </TD><TD class=LOGType1 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry1 align=left colSpan=8>(RecRxChar) duplicate packet ignored: 2201A26EA0D0</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:54:10 </TD><TD class=LOGType0 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry0 align=left colSpan=8>(RecRxChar) packet received: 2201A26EB0D0</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:54:10 </TD><TD class=LOGType1 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry1 align=left colSpan=8>(display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:496</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:54:10 </TD><TD class=LOGType0 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry0 align=left colSpan=8>(RecRxChar) packet received: 2201A26EB0D0</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:54:10 </TD><TD class=LOGType1 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry1 align=left colSpan=8>(RecRxChar) duplicate packet ignored: 2201A26EB0D0</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:54:12 </TD><TD class=LOGType0 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry0 align=left colSpan=8>(RecRxChar) packet received: 78EA00F70048000022C4FF5F1DE01E00</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:54:12 </TD><TD class=LOGType1 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry1 align=left colSpan=8>(display_E_r) Current: ELEC1[63232]r Device:[2 Value:0</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:54:12 </TD><TD class=LOGType0 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry0 align=left colSpan=8>(display_E_s) Counter: ELEC1[63232]r Device:[5 Value:18</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:54:12 </TD><TD class=LOGType1 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry1 align=left colSpan=8>(display_E_t) Counter: ELEC1[63232]r Device:[6 Value:0</TD></TR></TBODY></TABLE>

    A second press fires the event:

    <TABLE cellSpacing=2 cellPadding=0 width="100%" border=0><TBODY><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:57:28 </TD><TD class=LOGType1 align=left colSpan=3>RFXCOM </TD><TD class=LOGEntry1 align=left colSpan=8>(display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:496</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:57:28 </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Event Trigger "Key Fob 1 On"</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:57:28 </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Event Trigger "Kitchen Lights On"</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>21/12/2008 09:57:28 </TD><TD class=LOGType0 align=left colSpan=3>Info </TD><TD class=LOGEntry0 align=left colSpan=8>Device: Ground Floor Kitchen Display Cabinet Lights (A11) ON</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>21/12/2008 09:57:28 </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Device: Ground Floor Kitchen Bar + Cupboard Lights (A10) ON</TD></TR></TBODY></TABLE>

    #2
    Can you post the 3 screens of the events used (small but readable pictures please)

    This has nothing to do with the evenet not triggered:
    If you want to control 3 HE modules from an event you can create a virtual HE device and program this in all 3 HE modules. The transmitter wil now send only 1 On/Off command and switch all 3 HE modules on the same time. You can have a max of 6 remotes=6 Homeseer HE devices programmed in each HE module. To be sure the HE module has no remotes programmed you can clear the HE by pressing the program button for about 10 seconds until the LED flashes, release the program button and press again. The memory is now cleared in the HE module and up to 6 remotes can now be programmed in this module.

    Comment


      #3
      I have quite a lot of HE devices in my setup and I have seen this kind of behaviour in the past when there are multiple transmissions required to HE devices folowing receipt of an HE command.

      I use 2 different approaches to get around this.

      First is the solution that Bert mentions, where you program the modules to accept 2 commands. I do this with my outside lights, each of 4 modules are programmed to respond to L1, L2, L3 and L4 commands and also the L10 command. Switching L10 results in all outside lights On / Off but each light can also be switched individually if required.

      The problem with this approach is that you then don't have the correct status in Homeseer for devices L1, L2, L3 and L4 but you have L10 status as On.

      I use a script to update the status of devices L1, L2, L3 and L4 whenever L10 is changed.

      The other approach I use for some things is to have a module programmed to respond to say Homeseer device A5 via the RFXCom plug-in and transmitter and also to respond directly to a HE switch or remote. I then use scripting to update the device status in Homeseer if a HE transmission is received by the RFXCom receiver.

      Example: Kitchen lights are on a HE304 which is programmed to accept L15 from Homeseer and also switch 1 of a HE 2 gang switch. Switching the lights is possible from Homeseer via device L15 which updates the status. If switch 1 is pressed, then the HE304 switches the lights. The RFXCOM receiver also picks up the transmission from the switch and the script updates the status of L15 in Homeseer.

      This method relies on the switch or remote being picked up OK by the RFXCom receiver but this is my preferred method because it also allows manual switching if Homeseer is down for some reason.

      Of course in your example, you can program more than 1 receiver to respond to your 2 button remote and have the script update multiple device statuses.

      Paul..

      Comment


        #4
        I've attached the screenshots as requested.

        This event switches on various lights.

        I can hit the switch sometimes and nothing is triggered at all, the signal is recieved and logged, but there is no record of the event firing - even if I have only one device this still happens.

        If I use the switch a second time this generally works, but an off signal may need two transmissions as well.

        I've tried with and without the Handshake checkbox ticked, this does not affect the behaviour.

        I quite like the idea of a virtual device, but this won't solve this problem as it occurs regardless of the number of HE signals sent.

        Many thanks,

        Paul
        Attached Files

        Comment


          #5
          For reference here's another event that has the same issue but is less complex, only switching on one HE device.
          Attached Files

          Comment


            #6
            Paul,

            I'm sure that the activity you describe with HE remotes has been discussed before on this board.

            Not sure what your scripting skills are like but I achieved much more reliable results with HE by running a vb script from the event rather than adding the actions to the event.

            If you put a 5 second wait before the 1st action does this make any difference?

            Paul..

            Comment


              #7
              I've just tried with a 5 second delay, and it seems to be more reliable, I still had one failure to respond to an off signal in about 10 on/off cycles.

              There was a discussion on the boards for a earlier version of the receiver - but symptoms are very similar.

              I've played with VB scripting in the past, so this seems like the next thing to try if it gives better results than using events.

              Comment


                #8
                Paul,

                I don't know what goes on behind the scenes when the RFXCOM receiver is processing an HE transmission, but the transmitter does not seem to like being asked to make an immediate HE transmission. I found that inserting a delay before transmission made things much better but this is not an ideal solution.

                This does not really explain why the event does not get triggered but I suspect it is something to do with Homeseer and / or the RFXCOM plug-in being busy processing the received HE transmission and somehow not processing the event.

                I'm sure Bert will be able to comment on the more technical side of things.

                Paul..

                Comment


                  #9
                  To help diagnose where the issue is, I set up an event to respond to an HE remote and speak as the action (therefore removing the HE transmission part of the action).

                  It appears that even in this case, the event does not always fire, particularly if several transmissions are sent in short succession.

                  So, 10 key pressess may only result in 8 events being triggered.

                  I need to do some more testing, but I think the intepretation of the received signals is the issue here.

                  Comment


                    #10
                    pauln,

                    Looking to the log you posted, the value is changed for the device but the event does not trigger. You can check this by checking the status page (after refresh).
                    Can try with the "priority event" deselected in the events?

                    Some technical information how the receiver and transmitter operate together:
                    The receiver and transmitter communicate together using the handshake signals. This must be enabled by the HS flag at the transmitter configuration by you.
                    The role of this handshake is:
                    1 - the transmitter is only allowed to transmit if the receiver does not receive valid data. This avoids RF collisions as much as possible.
                    2 - the receiver stops receiving during the time the transmitter is active. So data transmitted is not received back and endless loops are eliminated.

                    Point 1 explains why the transmitter will wait when you press for a long time a remote button and only starts transmitting when you release the remote button. If the transmitter would send the RF data immediately an RF collision would occur and none of the RF data is received anymore as valid data.

                    Concerning point 2: In the transmitter configuration you must select only the RF protocols to be used.
                    Why? The plug-in controls all protocols using one command. The transmitter translates this command to the appropriate format and transmits the RF data. Thus if for example X10, ARC and Harrison protocols are enabled in the transmitter, the transmitter will send 5 X10 RF packets, 5 ARC RF packets and 15 Harrison RF packets. The transmission of all these signals will take about 2 to 3 seconds and during this time the receiver will not receive anything
                    This is valid for all protocols except HomeEasy. The transmitter has default HomeEasy enabled and this cannot be disabled as there is no reason for. The HE protocol is different from the other protocols. When the plug-in sends HE data the transmitter will only transmit a HE signal.

                    Configure HomeEasy devices as a AC MODULE or AC DIMMER. If you configure a HomeEasy device as a LIGHT MODULE or APPLIANCE MODULE it will be controlled using the ARC protocol. The ARC protocol is much slower when using other protocols in the transmitter and it is less secure because it is using a simple addressing mode that allows anybody to control your modules.

                    Bert

                    Comment


                      #11
                      Bert - thanks for the info.

                      I'll check all my settings - I think I have the Tx set up for HE only, and the reciever set up for HE and OS? The HS box is ticked.

                      I may try disabling OS in case this is somehow blocking the HE signals - as in my previous post I can replicate the error even when no transmission is sent (so it's not a transmitter/receiver comms problem).

                      Comment


                        #12
                        pauln,

                        the important item in my previous message is:

                        Can try with the "priority event" deselected in the events?

                        Bert

                        Comment


                          #13
                          Bert,

                          Priority event is switched off, and I've tested with no transmission as an action - simply a speak 'On' or 'Off.

                          The reciever picks up everything perfectly, but the event triggers sporadically - the trace below shows how bad the issue can be.

                          I'm not sure how the event is detected, but it just isn't working reliably - the following shows several on presses before the event is fired:

                          22/12/2008 18:21:04 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:04 RFXCOM (display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:496
                          22/12/2008 18:21:04 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:04 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:04 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:04 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:04 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:04 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:05 RFXCOM (display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:256
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:05 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:06 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:06 RFXCOM (display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:496
                          22/12/2008 18:21:06 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:06 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:06 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:06 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:06 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:06 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:06 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:06 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:07 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:07 RFXCOM (display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:256
                          22/12/2008 18:21:07 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:07 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:07 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:07 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:07 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:07 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:07 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:07 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:27 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:27 RFXCOM (display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:496
                          22/12/2008 18:21:27 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:27 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:27 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:27 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:27 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:27 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:27 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:27 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:35 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:35 RFXCOM (display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:496
                          22/12/2008 18:21:35 Info Event Trigger "Key Fob 1 On"
                          22/12/2008 18:21:35 Info Speak ():On
                          22/12/2008 18:21:35 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:35 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:35 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:35 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:35 RFXCOM (RecRxChar) packet received: 2201A26EB0D0
                          22/12/2008 18:21:35 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EB0D0
                          22/12/2008 18:21:45 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:45 RFXCOM (display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:256
                          22/12/2008 18:21:45 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:45 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:45 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:45 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:45 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:45 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:50 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:50 RFXCOM (display_E_a) Sensor: AC[1A26E2]a Device:[19 Value:256
                          22/12/2008 18:21:50 Info Event Trigger "Key Fob 1 Off"
                          22/12/2008 18:21:50 Info Speak ():Off
                          22/12/2008 18:21:50 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:50 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:50 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:50 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0
                          22/12/2008 18:21:50 RFXCOM (RecRxChar) packet received: 2201A26EA0D0
                          22/12/2008 18:21:50 RFXCOM (RecRxChar) duplicate packet ignored: 2201A26EA0D0

                          Comment


                            #14
                            I will do some test to see how it performs on my system. I have installed HS 2.3.0.16
                            If you don't have this version installed can you install that version too so that we have the same software level.

                            Comment


                              #15
                              I've got that version installed and the latest RFXCOM software.

                              I carried out a complete uninstall and reinstall of everything just in case - haven't had time to retest yet - but will keep you posted.

                              I lost all my input devices despite copying the RFXCOM database over though - is this correct?

                              Comment

                              Working...
                              X