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