Announcement

Collapse
No announcement yet.

HS3 - X10 Devices Types

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

  • HS3 - X10 Devices Types

    I have mainly migrated from HS2 to HS3 and currently migrating a few remaining X10 devices to HS3.

    I have set up my X10 INTERFACE (CM12U) ON COM1 add a few device appliances and all work ok.

    I have 2 questions on this.

    1. In the X10 tab what are the differences between the Device Types, Applicance, standard, preset and extended.
    2. What type would you use for the old MS13 X10 motion sensor (old but reliable in HS2 and BLRADAR)


    Regards

    Liam K

  • #2
    433MHz X10 is supported in HS3 by the RFXCOM plugin with the old RFXCOM receiver, USB W800 and new RFXtrx433 transceivers

    Comment


    • #3
      Originally posted by slayer View Post
      I have mainly migrated from HS2 to HS3 and currently migrating a few remaining X10 devices to HS3.

      I have set up my X10 INTERFACE (CM12U) ON COM1 add a few device appliances and all work ok.

      I have 2 questions on this.

      1. In the X10 tab what are the differences between the Device Types, Applicance, standard, preset and extended.
      2. What type would you use for the old MS13 X10 motion sensor (old but reliable in HS2 and BLRADAR)


      Regards

      Liam K
      1. Appliance is on/off only. Standard, preset, and extended are dim modes ( for dimmers, of course, not appliance modules). It’s been a while , so this may not be 100% accurate, but I believe standard is a dimmer that goes full bright then dims to set level, and preset will go directly to dim level without going full bright first. Unfortunately, I don’t recall exactly how extended works.

      2. Use appliance since it’s on/off only.

      Mike

      Comment


      • #4
        Originally posted by slayer View Post
        2. What type would you use for the old MS13 X10 motion sensor (old but reliable in HS2 and BLRADAR)
        Did you get this question answered? (Post #2)
        Although X10 appears in the name of the MS13, it is not a power line device and is not handled by the HS X10 plug-in. Setup is with the RFXCOM plug-in.
        Mike____________________________________________________________ __________________
        HS3 Pro Edition 3.0.0.548

        HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

        Comment


        • #5
          Originally posted by Uncle Michael View Post
          Did you get this question answered? (Post #2)
          Although X10 appears in the name of the MS13, it is not a power line device and is not handled by the HS X10 plug-in. Setup is with the RFXCOM plug-in.
          Unless he's using a Wireless Transceiver Module in which case it would convert the MS13 RF signal to a powerline signal.
          HS 3.0.0.548: 1976 Devices 1156 Events
          Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

          Comment


          • #6
            Apologies for the very late reply, still having some trouble here with HS3 and X10.
            I have LD11 din rail dimmer set up to control a room light, but no matter what device type I set up with Preset, Extend, Standard or appliance the device management page only shows it with On or OFF button, there is no slider to dim the light.
            Any idea whats wrong

            I am using CM11A interface for the powerline

            Regards

            Liam

            Comment


            • #7
              When you first set it up, did you go directly to the X10 tab and select a dimmable device type (Standard, Preset, Extended)? If I recall correctly, you must do this first so that the device is saved as a dimmable device. Check your Configuration tab and see if "Is Dimmable" is checked. If not, you may need to recreate the device.

              Mike



              Click image for larger version  Name:	dimmable.JPG Views:	0 Size:	90.6 KB ID:	1307077
              Last edited by Mike Johnson; May 24th, 2019, 05:11 PM. Reason: Configuration tab, not General tab

              Comment


              • #8
                That worked. Thank you.

                Comment


                • #9
                  You’re welcome. Glad you got it working.

                  Mike

                  Comment


                  • #10
                    This may be a harbinger of what seems to have manifested in my system. I started first by defining the devices in my OmniPro and let the X10 plugin suck them in. But they came over as Omni Devices. I still wanted original letter name devices for compatibility as I swap out devices over a slower period of time.

                    After 3 hours of swapping out 3 (Three) TI-103's and a CM-11a, I get nothing when I try to control an X-10 device. I read forward and downloaded the .46 version of the plugin and restarted. The plugin starts normally, I turned on verbose logging, and when I go to turn on a device, it gives the following entries in the log. I can't believe that three (3) rather expensive TI-103's and brand new CM11a I just bought on eBay to test with all behave the same way. I have a couple of TW-523's right next to them, so when HS1 sends an X-10 command, they of course blink. When I issue the command from HS3, nothing at all.

                    The telling part is that I DO NOT get the X10 tab created in the new devices screen. I tried to delete a device after upgrading the plugin and recreating it but I only get the first three tabs and no X-10 tab.

                    Has anyone seen this. I've moved the interface (to other USB ports, and com ports, I used the Prolific USB/RS-232 converter which works on all other DB9 types of serial). I've checked that the com port speed is the same as the minimum 9600 baud the plugin requires.

                    The plugin initialized and finds the TI-103 but then it goes radio silent. After turning on verbose logging (see below) I can see the entries where the message in the log is:
                    Jun-22 8:38:36 PM Device Control Device: Basement Downstairs Basement Lights to Off (0) by/from: CAPI Control Handler
                    But nothing is sent or received... I'm stumped as I tried the 3 TW-523's (even took apart my existing one on HS1 to check the DIP switches were set exactly the same).
                    Even after reinstalling the '46 beta, (really familiar, as I wrote the Ignore the housecodes part of it years ago , I go as far as shutting down HS, rebooting the entire PC but to no avail.

                    Am I missing a DLL or something registered that keeps the command from going out or being received. As you can see, the plugin does log that tried to send the command not no errors in the log but no blinking on the TW-523's.

                    Any advice at this point would be greatly appreciated. I've completed the breadboard of the system and ready to start migrating over the events but I'd still like to keep the old conventions, like P3 is the Kitchen Table Light, so when I move from X-10 to Z-Wave, Radio-RA or whatever, I'd still like to just change the interface but keep the P3 base control code for script compatibility.

                    Any thoughts would be appreciated. 4 hours in the basement yesterday yielded nothing but a real need for more coffee.

                    Thanks in advance, and I hope I just missed something simple. I gave up around 8:38 last night.

                    George

                    Jun-22 8:38:42 PM Device Control Device: Basement Downstairs Basement Lights to On (100) by/from: CAPI Control Handler
                    Jun-22 8:38:36 PM Device Control Device: Basement Downstairs Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:36:00 PM Device Control Device: Basement Basement Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:35:56 PM Device Control Device: Basement Basement Basement Lights to On (100) by/from: CAPI Control Handler
                    Jun-22 8:35:52 PM Device Control Device: Basement Basement Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:35:43 PM Device Control Device: Basement Basement Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:35:04 PM Info Plugin X10 with instance: has disconnected
                    Jun-22 8:35:04 PM X10 ERROR Error in Ti103.CommThreadProc:Thread was being aborted.
                    Jun-22 8:35:04 PM Plug-In Shutting down Plug-In: X10
                    Jun-22 8:34:34 PM Device Control Device: Basement Basement Basement Lights to On (100) by/from: CAPI Control Handler
                    Jun-22 8:33:45 PM X10 INFO Ti103 communications established.
                    Jun-22 8:33:40 PM Plug-In Finished initializing plug-in X10
                    Jun-22 8:33:40 PM Starting Plug-In X10 loaded in 699 milliseconds
                    Jun-22 8:33:40 PM Starting Plug-In Plugin X10 started successfully in 404 milliseconds
                    Jun-22 8:33:40 PM X10 INFO Ti103 Warning, plugin is set to ignore the following housecodes: A, B, C, D, E, F, G, H
                    Jun-22 8:33:40 PM X10 INFO Starting Ti103 v3.0.0.46, using serial port: COM5
                    Jun-22 8:33:40 PM Starting Plug-In Initializing plugin X10 ...
                    Jun-22 8:33:40 PM Info Plugin X10 has connected. IP:127.0.0.1:54893
                    Jun-22 8:33:32 PM Error Displaying remotely connected interfaces: Object reference not set to an instance of an object.
                    Jun-22 8:33:32 PM Info Plugin X10 with instance: has disconnected
                    Jun-22 8:33:32 PM X10 ERROR Error in Ti103.CommThreadProc:Thread was being aborted.
                    Jun-22 8:33:32 PM Plug-In Shutting down Plug-In: X10
                    Jun-22 8:33:19 PM Device Control Device: Basement Basement Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:32:39 PM Device Control Device: Basement Basement Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:32:33 PM X10 INFO Ti103 communications established.
                    Jun-22 8:32:28 PM Plug-In Finished initializing plug-in X10
                    Jun-22 8:32:28 PM Starting Plug-In X10 loaded in 699 milliseconds
                    Jun-22 8:32:28 PM Starting Plug-In Plugin X10 started successfully in 399 milliseconds
                    Jun-22 8:32:28 PM X10 INFO Ti103 Warning, plugin is set to ignore the following housecodes: A, B, C, D, E, F, G, H
                    Jun-22 8:32:28 PM X10 INFO Starting Ti103 v3.0.0.46, using serial port: COM5
                    Jun-22 8:32:28 PM Starting Plug-In Initializing plugin X10 ...
                    Jun-22 8:32:28 PM Info Plugin X10 has connected. IP:127.0.0.1:54506
                    Jun-22 8:32:20 PM Info Plugin X10 with instance: has disconnected
                    Jun-22 8:32:20 PM X10 ERROR Error in Ti103.CommThreadProc:Thread was being aborted.
                    Jun-22 8:32:20 PM Plug-In Shutting down Plug-In: X10
                    Jun-22 8:31:36 PM Device Control Device: Basement Basement Basement Lights to On (100) by/from: CAPI Control Handler
                    Jun-22 8:31:31 PM Device Control Device: Basement Basement Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:31:18 PM X10 INFO Ti103 communications established.
                    Jun-22 8:31:14 PM Plug-In Finished initializing plug-in X10
                    Jun-22 8:31:14 PM Starting Plug-In X10 loaded in 899 milliseconds
                    Jun-22 8:31:14 PM Starting Plug-In Plugin X10 started successfully in 425 milliseconds
                    Jun-22 8:31:13 PM X10 INFO Ti103 Warning, plugin is set to ignore the following housecodes: A, B, C, D, E, F, G, H
                    Jun-22 8:31:13 PM X10 INFO Starting Ti103 v3.0.0.46, using serial port: COM5
                    Jun-22 8:31:13 PM Starting Plug-In Initializing plugin X10 ...
                    Jun-22 8:31:13 PM Info Plugin X10 has connected. IP:127.0.0.1:54214
                    Jun-22 8:31:05 PM Info Plugin X10 with instance: has disconnected
                    Jun-22 8:31:05 PM Plug-In Shutting down Plug-In: X10
                    Jun-22 8:30:00 PM X10 ERROR error in PollTimer_Tick :The port is closed.
                    Jun-22 8:29:59 PM OMNI ---------------------------
                    Jun-22 8:29:57 PM OMNI Plugin startup is complete.
                    Jun-22 8:29:55 PM OMNI ---------------------------
                    Jun-22 8:29:53 PM OMNI Synchronization complete.
                    Jun-22 8:29:47 PM Device Control Device: Basement Basement Basement Lights to On (100) by/from: CAPI Control Handler
                    Jun-22 8:29:45 PM Device Control Device: Basement Basement Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:29:39 PM Device Control Device: Basement Basement Basement Lights to On (100) by/from: CAPI Control Handler
                    Jun-22 8:29:34 PM Device Control Device: Basement Basement Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:29:28 PM X10 INFO Ti103 communications established.
                    Jun-22 8:29:24 PM Plug-In Finished initializing plug-in X10
                    Jun-22 8:29:24 PM Starting Plug-In X10 loaded in 893 milliseconds
                    Jun-22 8:29:24 PM Starting Plug-In Plugin X10 started successfully in 532 milliseconds
                    Jun-22 8:29:23 PM X10 INFO Ti103 Warning, plugin is set to ignore the following housecodes: A, B, C, D, E, F, G, H
                    Jun-22 8:29:23 PM X10 INFO Starting Ti103 v3.0.0.46, using serial port: COM10
                    Jun-22 8:29:23 PM Starting Plug-In Initializing plugin X10 ...
                    Jun-22 8:29:23 PM Info Plugin X10 has connected. IP:127.0.0.1:53765
                    Jun-22 8:29:09 PM OMNI Synchronizing OMNI devices with HomeSeer...
                    Jun-22 8:29:07 PM OMNI Requesting initial system troubles
                    Jun-22 8:29:00 PM OMNI Requesting Output status...
                    Jun-22 8:28:55 PM Error Displaying remotely connected interfaces: Object reference not set to an instance of an object.
                    Jun-22 8:28:55 PM Info Plugin X10 with instance: has disconnected
                    Jun-22 8:28:55 PM Plug-In Shutting down Plug-In: X10
                    Jun-22 8:28:39 PM X10 ERROR error in PollTimer_Tick :The port is closed.
                    Jun-22 8:28:26 PM Device Control Device: Basement Basement Basement Lights to On (100) by/from: CAPI Control Handler
                    Jun-22 8:28:21 PM Device Control Device: Basement Basement Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:28:07 PM X10 INFO Ti103 communications established.
                    Jun-22 8:28:03 PM Plug-In Finished initializing plug-in X10
                    Jun-22 8:28:03 PM Starting Plug-In X10 loaded in 799 milliseconds
                    Jun-22 8:28:02 PM Starting Plug-In Plugin X10 started successfully in 397 milliseconds
                    Jun-22 8:28:02 PM X10 INFO Ti103 Warning, plugin is set to ignore the following housecodes: A, B, C, D, E, F, G, H
                    Jun-22 8:28:02 PM X10 INFO Starting Ti103 v3.0.0.46, using serial port: COM5
                    Jun-22 8:28:02 PM Starting Plug-In Initializing plugin X10 ...
                    Jun-22 8:28:02 PM Info Plugin X10 has connected. IP:127.0.0.1:53385
                    Jun-22 8:27:53 PM Info Plugin X10 with instance: has disconnected
                    Jun-22 8:27:53 PM Plug-In Shutting down Plug-In: X10
                    Jun-22 8:27:41 PM X10 INFO Ti103 communications established.
                    Jun-22 8:27:38 PM OMNI Requesting Area status...
                    Jun-22 8:27:36 PM OMNI All configuration and properties retrieved.
                    Jun-22 8:27:32 PM OMNI -->Reading properties...
                    Jun-22 8:26:56 PM X10 INFO Ti103 Warning, plugin is set to ignore the following housecodes: A, B, C, D, E, F, G, H
                    Jun-22 8:26:56 PM X10 INFO Starting Ti103 v3.0.0.46, using serial port: COM5
                    Jun-22 8:26:46 PM Device Control Device: Basement Basement Basement Lights to On (100) by/from: CAPI Control Handler
                    Jun-22 8:26:40 PM Device Control Device: Basement Basement Basement Lights to Off (0) by/from: CAPI Control Handler
                    Jun-22 8:26:37 PM Z-Wave Starting Z-Wave Polling for Network E5CB4660...
                    Jun-22 8:26:27 PM Plug-In Finished initializing plug-in X10
                    Jun-22 8:26:27 PM Starting Plug-In X10 loaded in 1599 milliseconds
                    Jun-22 8:26:27 PM Starting Plug-In Plugin X10 started successfully in 1182 milliseconds
                    Jun-22 8:26:26 PM Info Initializing CM11A/12U on COM port COM5
                    Jun-22 8:26:26 PM Starting Plug-In Initializing plugin X10 ...
                    Jun-22 8:26:26 PM Info Plugin X10 has connected. IP:127.0.0.1:52980
                    Jun-22 8:26:22 PM TTS Speak ():Welcome to Home-Seer
                    Jun-22 8:26:21 PM Speaker Speaker host added, Name: Dino Instance: Default IP address: 127.0.0.1
                    Jun-22 8:26:11 PM Z-Wave ************************************************************ *******************
                    Jun-22 8:26:11 PM Z-Wave STARTUP COMPLETE: All configured interfaces were successfully initialized.
                    Jun-22 8:26:11 PM Z-Wave ************************************************************ *******************

                    Comment


                    • #11
                      Note that here running HS3 (2 boxes) on Ubuntu 18.04. Thinking what you will see is the same in Windows.

                      When I clip and paste the logs to the forum I clip and paste them to notepad (linux) and then copy them over to the forum.



                      Yes you will need to manually install the X10 devices with the Homeseer 3 X10 plugin.

                      Read this:

                      How to create a new X10 device in HS3 **VERY IMPORTANT**

                      to see this:

                      Click image for larger version  Name:	x10tab.jpg Views:	0 Size:	25.6 KB ID:	1312068
                      - Pete

                      Auto mator
                      Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                      Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                      X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                      Comment


                      • #12
                        Here is what the logs will show with the X10 plugin.

                        Enabling the plugin:

                        6/23/2019
                        Jun-23 7:04:45 AM Plug-In Shutting down Plug-In: X10
                        Jun-23 7:04:46 AM Info Plugin X10 with instance: has disconnected
                        Jun-23 7:05:29 AM Info Plugin X10 has connected. IP:127.0.0.1:49190
                        Jun-23 7:05:29 AM Starting Plug-In Initializing plugin X10 ...
                        Jun-23 7:05:29 AM Info Initializing CM11A/12U on COM port /dev/ttyUSB0
                        Jun-23 7:05:30 AM Starting Plug-In Plugin X10 started successfully in 685 milliseconds
                        Jun-23 7:05:30 AM Starting Plug-In X10 loaded in 1804 milliseconds
                        Jun-23 7:05:30 AM Plug-In Finished initializing plug-in X10

                        Sending an X10 on to Device A3.

                        Jun-23 7:07:41 AM X10 DEBUG CM11A Sending: 4 62 Size: 2
                        Jun-23 7:07:41 AM X10 DEBUG CM11A Got checksum: 66
                        Jun-23 7:07:41 AM X10 DEBUG CM11A Checksum OK, sending 0
                        Jun-23 7:07:41 AM X10 DEBUG CM11A Got ack of: 55
                        Jun-23 7:07:41 AM X10 DEBUG CM11A Sending: 6 62 Size: 2
                        Jun-23 7:07:41 AM X10 DEBUG CM11A Got checksum: 68
                        Jun-23 7:07:41 AM X10 DEBUG CM11A Checksum OK, sending 0
                        Jun-23 7:07:42 AM X10 DEBUG CM11A Got ack of: 55

                        Sending an X10 off to device A3

                        Jun-23 7:08:59 AM X10 DEBUG CM11A Sending: 4 62 Size: 2
                        Jun-23 7:08:59 AM X10 DEBUG CM11A Got checksum: 66
                        Jun-23 7:08:59 AM X10 DEBUG CM11A Checksum OK, sending 0
                        Jun-23 7:08:59 AM X10 DEBUG CM11A Got ack of: 55
                        Jun-23 7:08:59 AM X10 DEBUG CM11A Sending: 6 63 Size: 2
                        Jun-23 7:08:59 AM X10 DEBUG CM11A Got checksum: 69
                        Jun-23 7:08:59 AM X10 DEBUG CM11A Checksum OK, sending 0
                        Jun-23 7:09:00 AM X10 DEBUG CM11A Got ack of: 55

                        Sending an X10 on to device A5 from the OmniPro 2 panel. (note that there is no A5 defined in HS3 at this time).

                        Jun-23 7:11:12 AM X10 DEBUG CM11A Upload byte count: 3
                        Jun-23 7:11:13 AM X10 DEBUG CM11A Upload Data: 2 Time: 25873.008

                        Sending an X10 off to device A5 from the OmniPro 2 panel. (note that there is no A5 defined in HS3 at this time).

                        Jun-23 7:13:06 AM X10 DEBUG CM11A Upload byte count: 3
                        Jun-23 7:13:06 AM X10 DEBUG CM11A Upload Data: 2 Time: 25986.972
                        - Pete

                        Auto mator
                        Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                        Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                        X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                        Comment


                        • #13
                          Originally posted by George View Post
                          The telling part is that I DO NOT get the X10 tab created in the new devices screen. I tried to delete a device after upgrading the plugin and recreating it but I only get the first three tabs and no X-10 tab.
                          Has anyone seen this.
                          When you say you do not see the X10 tab, what did you do to create the new device?
                          Did you use the green button with the white '+' sign in the upper right corner of the Device Management page?
                          After you select that button do you see a screen like this (but without the X10 tab):
                          Note the 'Cancel Add' button in the lower left.

                          Click image for larger version  Name:	newD.PNG Views:	0 Size:	367.8 KB ID:	1312082
                          Mike____________________________________________________________ __________________
                          HS3 Pro Edition 3.0.0.548

                          HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

                          Comment


                          • #14
                            If you haven't, please also see this post:
                            https://forums.homeseer.com/forum/li...very-important

                            The device will not be recognized by the X10 plug-in if it is not created according to this post.

                            If you do not see the X10 tab, then the behavior you see is exactly what I would expect.
                            Mike____________________________________________________________ __________________
                            HS3 Pro Edition 3.0.0.548

                            HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

                            Comment


                            • #15
                              If, after clicking on the green add button you have to look through your list of devices for a New Device with Unknown / Unknown room and floor, you will not find the X10 tab. This is a long-standing bug in the HS device creation process. There is only one way to deal with it that I know of. Hit the the 'Add' button again. You may have to do that several times, but in my experience at least, eventually you will get the add device screen.

                              Once you have that screen, create a 'model' X10 device following Mark's instructions and save it.
                              You can then use that X10 device to create additional devices by copying it and changing the House code/Unit code.
                              (You may also want to go back to your device list and discard the extraneous New Devices that you created in the process.)
                              Mike____________________________________________________________ __________________
                              HS3 Pro Edition 3.0.0.548

                              HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

                              Comment

                              Working...
                              X