HS3 - X10 Devices Types

[mfisher]

Happy to hear you got it working!

[George]

Oh, and while I was re-downloading drivers, I went to the support side and loaded the speaker client to my 1.7 Win XP HS machine. So now, my live system is Kate and HS3 is Mike. So at least I know which machine is talking to me.

[George]

Thanks for all the responses guys.

After about 3 hours - 3 TI-103's, a CM-11A and a partridge in a pear tree, I threw in the towel. Uninstalled the plugin, reinstalled the beta plugin, still no X-10 tab from the Green +. Out of giving up an all things, I checked the devices manager to make sure that the speed of the Prolific com port was 9600 which it was. But, for shits and giggles, I went online and re-downloaded the Prolific USB-Serial drivers. I reinstalled the Prolific drivers, rebooted about 2 times and "As if by Magic", POOF, the X-10 TAB started to show up.

Then it took me about 2 hours to take about (this is what I miss about the HS 1.7 console client ) and really, really really hate the Web Interface, 50 X-10 devices, delete them (as they still did not show the tab) which also as a good side effect removed the Link to the same device on the OP, which is what I wanted. When I Green +'d to add a device, I followed the directions.

• Named it
• Put it on a Floor
• Put it in a Room
• Set it as a light of not
• Went to the X-10 tab and added the house code (can anyone remember the word BSR and why the housecode for X-10 are the way they are? LOL) and set if it was an appliance, light and the type of extended support.
• Then saved it,
• Then opened it and when in to change the On/Off icons to the appropriate ones if they were not normal lights like Fans, etc.

I attribute it somehow to the reinstall of the Prolific drivers, but it may have cleaned up some other remnants as well. For now, whenever I add a device, the X-10 tab does pop up consistently. Sunspots!

Thanks again, I'm back to my 4 month project!

BTW, did I say that I really Hate the web interface, but I guess that's what we will live with until HTML5 and the new container features which I hope Rich is working on.

George

[mfisher]

Hey George, glad to see you back on the board!

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.

The X10 plugins cannot take ownership of any existing devices, and unfortunately all X10 plugin owned devices must be created from scratch as described in this post:

https://forums.homeseer.com/forum/li...very-important

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.

I'm pretty sure your hardware interfaces are just fine as there are no connection errors in the log entries you posted. If you want to prove this to yourself create an event that will 'send X10 command' rather than trying to control a device using HS. Also, if the 'special' logging entries are enabled for the Ti103 and 'Enable Developer Mode' is enabled on the plugins page, you will be able to see the received X10 data. For the CM11a (using plugin version v.46) just enabling 'Developer Mode' will allow you to see sent and received X10 data detail.

The issue you are seeing is that while the X10 plugin is working, you're trying to control devices you think are X10, but since the plugin doesn't own them HS3 doesn't pass the CAPI command to the plugin.

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.

When you create a new device (by clicking '+'), HS querries the status of each device related plugin for it's status and if it returns 'OK' it will display an additional tab for each plugin on the new device page. Unfortunately (as Uncle Michael mentioned) there is a longstanding issue where HS just creates the device without displaying the 'new device' page, or it displays the 'new device' page without the "X10" tab. Personally this has never happened to me on either Windows or Linux but many have reported it. Michael's workaround seems to be the only way to circumvent this.

[Uncle Michael]

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.)

[Uncle Michael]

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.

[Uncle Michael]

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.

[Pete]

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]

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:

[George]

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 ************************************************************ *******************

[Mike Johnson]

You’re welcome. Glad you got it working.

Mike

[slayer]

That worked. Thank you.

[Mike Johnson]

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

[slayer]

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

[sparkman]

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.