Announcement

Collapse
No announcement yet.

Issue with x10/CM11 Plugin

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

  • mfisher
    replied
    1/5/2021 4:46:46 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Success! 0.441 seconds for CM11a to send.
    This line in your log is telling you that the CM11a has successfully transmitted the data onto the powerline. This means that the communication link between your HS machine and the CM11a is working properly, the plugin is working properly and it appears that your CM11a is working properly.

    The commands you sent above are:
    0x 04 60 = device A13
    0x 06 63 - function A OFF
    But I see in your log you think you're sending to device A1:
    1/5/2021 4:46:46 PM HomeSeer Device Control Device: X10 Unknown A1 [*** NEW X10 DEVICE ***] to Off (0) by/from: CAPI Control Handle
    Please check the X10 settings (on the X10 tab) for this device and be sure it is set as you expect.

    Leave a comment:


  • Chas821
    replied
    So......getting back into this.
    It appears from the log that the plugin is sending the data to the CM11A and the CM11A is returning a good checksum. See the log snip below:
    1/5/2021 4:46:47 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Success! 0.463 seconds for CM11a to send.
    1/5/2021 4:46:47 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
    1/5/2021 4:46:46 PM
    Legacy-Plugin X10 DEBUG CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).
    1/5/2021 4:46:46 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x69
    1/5/2021 4:46:46 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
    1/5/2021 4:46:46 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x 06 63
    1/5/2021 4:46:46 PM
    Legacy-Plugin X10 DEBUG CM11A.SendIt(): Success! 0.441 seconds for CM11a to send.
    1/5/2021 4:46:46 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
    1/5/2021 4:46:46 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).
    1/5/2021 4:46:46 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x64
    1/5/2021 4:46:46 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
    1/5/2021 4:46:46 PM Legacy-Plugin X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x 04 60
    1/5/2021 4:46:46 PM HomeSeer Device Control Device: X10 Unknown A1 [*** NEW X10 DEVICE ***] to Off (0) by/from: CAPI Control Handle

    The issue? The X10 device (appliance module) isn't responding. I've verified the module works. I've tested the CM11A/USB-to-serial adapter combination works using another Pi with Heyu installed. The CM11A and the Module are plugged into the same outlet.

    So...I'm looking for ideas where to start troubleshooting.


    Leave a comment:


  • Pete
    replied
    Good news Chas821 !!

    Leave a comment:


  • Chas821
    replied
    Thank you for your reply. I repeated steps I took yesterday to no avail. I repeated the steps just now and it appears that it's now working as it's supposed to. I dunno!!

    Leave a comment:


  • Pete
    replied
    What are you plugging in your CM11A interface to on your Linux computer? RS-232 9 pin or USB port?

    If using a USB port go to the console and type:

    sudo lsusb

    This is what I see:

    ICS-HS4:~# lsusb

    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
    Bus 001 Device 003: ID 0bef:0004 Way2Call Communications Hi-Phone Desktop USB
    Bus 001 Device 002: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    The second device above is a usb to serial interface.

    Now type:

    sudo su
    cd /dev
    ls ttyU*

    This is what I see:

    ICS-HS4:/dev# ls ttyU*
    ttyUSB0

    In my case I would use the ttyUSB0 port for my CM11A interface in the Homeseer X10 configuration



    Click image for larger version  Name:	HS4X10.jpg Views:	0 Size:	38.5 KB ID:	1444432
    This is what my logs show when enabling the x10 plugin:

    Jan-01 6:16:08 AM Info Plugin X10 has connected. IP:127.0.0.1:59178
    Jan-01 6:16:08 AM Starting Plug-In Initializing plugin X10 ...
    Jan-01 6:16:09 AM X10 INFO Initializing CM11A/12U on COM port /dev/ttyUSB0
    Jan-01 6:16:09 AM Starting Plug-In Plugin X10 started successfully in 211 milliseconds
    Jan-01 6:16:09 AM Starting Plug-In X10 loaded in 600 milliseconds
    Jan-01 6:16:09 AM Plug-In Finished initializing plug-in X10

    Leave a comment:


  • Chas821
    started a topic Issue with x10/CM11 Plugin

    Issue with x10/CM11 Plugin

    When I enable the X10 plugin I see this in the log:
    12/31/2020 7:56:50 PMHomeSeer
    Warning Plug-in X10 is set to load but was not found, removing from settings.
    12/31/2020 7:56:50 PM HomeSeer Plug-In Finished initializing plug-in X10
    12/31/2020 7:56:50 PM HomeSeer Starting Plug-In X10 loaded in 1806 milliseconds
    12/31/2020 7:56:50 PM HomeSeer Info Plugin X10 with ID: and Instance: has disconnected
    12/31/2020 7:56:50 PM HomeSeer Error Initializing plug-in(2): X10 Instance::Object reference not set to an instance of an object.STACK: at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, System.Runtime.Remoting.Messaging.IMessage msg, System.Exception& exc, System.Object[]& out_args) [0x00108] in :0 at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_remoting_wrapper(intptr,i ntptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI.InitIO(string) at Scheduler.PluginHolder.InitIO (System.String PortNumber) [0x0000b] in :0 at Scheduler.clsHSPI.CheckInterfaces () [0x000bf] in :0
    12/31/2020 7:56:50 PM Legacy-Plugin X10 INFO Initializing CM11A/12U on COM port /dev/ttyS0
    12/31/2020 7:56:50 PM HomeSeer Starting Plug-In Initializing plugin X10 ...
    12/31/2020 7:56:49 PM HomeSeer Info Plugin X10 has connected. IP:127.0.0.1:44524

    The plugin status in the Plugin Management screen shows :
    WARNING: Failed getting InterfaceStatus from X10

    Where to from here?

    Chas

Working...
X