Announcement

Collapse
No announcement yet.

Raspberry Pi B+ & Homeseer Pi X-10 (CM11a) not working

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

  • travisdh
    replied
    I am having the same issues with the TI103 on the linux X10 plugin, my logs say this and I can't even get it to connect:

    Mar-05 1:44:16 PM ACT TI103 Cannot open com port: Invalid argument
    Mar-05 1:44:16 PM Info TI103 Plug-in, Version 3.0.35
    Mar-05 1:44:16 PM ACT TI103 Calling initIO in TI103 with port:/dev/ttyS4
    Mar-05 1:44:16 PM Info Plugin X10 has connected. IP:127.0.0.1:55068

    Baud rates and so on are fine from what I can see.

    Leave a comment:


  • Rupp
    replied
    Originally posted by JWD View Post
    Al, selecting the TI103 X10 interface in HS3 gives 2 parameter choices - 9600 (default) or 19200 baud. 9600 is what I have always used with HS2.
    The Other parameter is a polling interval which defaults to 4000 (4 seconds) with a warning that setting too low can cause unexpected results. I have tried lowering this but I noticed no change to response times - I might try a more methodical test. One assumes that the 4000 default in the software was chosen for a reason originally.
    9600 is the proper rate.

    Leave a comment:


  • JWD
    replied
    Al, selecting the TI103 X10 interface in HS3 gives 2 parameter choices - 9600 (default) or 19200 baud. 9600 is what I have always used with HS2.
    The Other parameter is a polling interval which defaults to 4000 (4 seconds) with a warning that setting too low can cause unexpected results. I have tried lowering this but I noticed no change to response times - I might try a more methodical test. One assumes that the 4000 default in the software was chosen for a reason originally.

    Leave a comment:


  • sparkman
    replied
    I don't have any personal experience with the TI103, but I understand the baud rate is configurable on it. I believe the CM11a's baud rate is 4800bps. If there's a baud rate mis-match, it could perhaps explain the delays.

    Cheers
    Al

    Leave a comment:


  • JWD
    replied
    Now I have done some more controlled timed tests comparing CM11A and TI103 Zee response times.
    Test setup is HR10 X10 RF remote control, receivers are TM13s (2x) and then either TI103 or CM11A into a USB Serial adapter into the Zee.
    The X10 received signal just triggers a simple Speak action from the Zee.

    With the TI103 I'm averaging 7-8 seconds from HR10 button press to hearing the Speak. With the CM11A the average is about 2 seconds and much more acceptable.
    However, (and this is part of the reason I moved to the TI103 on HS2) the CM11A doesn't appear to be as good at detecting the inbound X10 signal as the TI103 so although I get the faster response it is a bit more hit and miss with the CM11A. I have found before that the TI103 is more reliable at sending / or sends stronger signals out to devices.
    With Barry's evidence this seems quite conclusive about the Zee/HS3 TI103 handling having a performance problem. It would be good to have an HST comment / fix for this.

    Leave a comment:


  • lhfarm
    replied
    I'll do a few more tests later. I only have a few devices on the Zee. I it is my garage and was going to be my way of expanding my Z-wave out there. So not a robust system at all.

    I also notice that there was a slight delay when I used the Zee to turn off the lights, vs the HS3/TI103. So that may be a function of the RPI too.

    Barry

    Leave a comment:


  • JWD
    replied
    Thanks very much Barry. Was that consistently better on the CM11A over several tests?
    I have a CM11A and will try mine but from previous experience I know the power output of the TI103 X10 signal reaches my devices much more reliably than the CM11A. I also remember the CM11A randomly getting itself in a muddled state.
    So it would appear that something about the Zee/HS3 TI103 driver isn't right.
    I will add this to the Bugzilla ticket and hope someone at HST looks at it soon!

    Leave a comment:


  • lhfarm
    replied
    A slight delay with the CM11a, but nothing like the TI103.

    Barry

    Leave a comment:


  • lhfarm
    replied
    Just hooked up the TI103 and I am seeing the delay in incoming X10. I set up an event to track my overhead lights going to off. I used my HS3 box to turn the light off and noted the change time. Then watched the Zee log. Up to 20 seconds before the event fired.

    I'm going to try the CM11a and repeat the test. I'll get back to you.

    Barry

    Leave a comment:


  • JWD
    replied
    Thanks Barry.
    It would be very helpful to know if you get the inbound delay coming through the Ti103 which is what my theory is about why my system is currently unusable.

    Leave a comment:


  • lhfarm
    replied
    Originally posted by JWD View Post
    I wondered if anyone who had been involved in this thread might have any suggestions on the problem I am having with X10 on my Zee with a TI103?
    Please see here http://board.homeseer.com/showthread.php?t=173170
    I have also opened a Bugzilla (#2630) but nothing seems to be happening on that - I assume it is visible to the people at HS?
    Thanks for any ideas!
    I'm really disappointed in HST right now. Once I got the Zee going, I haven't touched it. However, I have a spare TI103 left over from my HS2 box. If I get a chance, Ill try it with the Zee.

    Wish I had something better to offer.

    Barry

    Leave a comment:


  • JWD
    replied
    I wondered if anyone who had been involved in this thread might have any suggestions on the problem I am having with X10 on my Zee with a TI103?
    Please see here http://board.homeseer.com/showthread.php?t=173170
    I have also opened a Bugzilla (#2630) but nothing seems to be happening on that - I assume it is visible to the people at HS?
    Thanks for any ideas!

    Leave a comment:


  • lhfarm
    replied
    Originally posted by Android View Post
    Hi, I was just curious if anyone else is having the same problem I am across reboots with running a CM11a and a Z-Stick on a Raspberry PI B+ with HomeSeer 3.0.0.152 (also 147 - just upgraded). (I also have an Edimax USB WiFi adapter).

    It looks like to me that the developers erred by statically reference USB ports like ttyUSB0, ttyUSB1, etc, as they can vary across reboots. They should be looking for device ID's on the USB ports to reference devices properly.

    So basically what I'm experiencing is, first it's painful to get both X10 and the Z-stick going - I have to do the opposite of the quick start guide. I have to make sure both the CM11a and Z-Stick are connected, and that both plugins are disabled. Then I have to enabled the Z-Stick first, the figure out what port it's on by trying to initialize it on both ttyUSB0 and ttyUSB1. Then, I have to go and set the USB port on the CM11a, then enable that plug-in. When I reboot, I have to go through this all over again if the ports have changed.
    Once I followed Pete's instructions, everything is working even through many reboots. Maybe Pete will see this and can help. I'd give serious thought to wiping the system and starting over. That might be painful, but better than fighting it.

    Barry

    Leave a comment:


  • Android
    replied
    Hi, I was just curious if anyone else is having the same problem I am across reboots with running a CM11a and a Z-Stick on a Raspberry PI B+ with HomeSeer 3.0.0.152 (also 147 - just upgraded). (I also have an Edimax USB WiFi adapter).

    It looks like to me that the developers erred by statically reference USB ports like ttyUSB0, ttyUSB1, etc, as they can vary across reboots. They should be looking for device ID's on the USB ports to reference devices properly.

    So basically what I'm experiencing is, first it's painful to get both X10 and the Z-stick going - I have to do the opposite of the quick start guide. I have to make sure both the CM11a and Z-Stick are connected, and that both plugins are disabled. Then I have to enabled the Z-Stick first, the figure out what port it's on by trying to initialize it on both ttyUSB0 and ttyUSB1. Then, I have to go and set the USB port on the CM11a, then enable that plug-in. When I reboot, I have to go through this all over again if the ports have changed.

    Leave a comment:


  • lhfarm
    replied
    Raspberry Pi B+ & Homeseer Pi X-10 (CM11a) not working-FIXED

    I fear HST is spread very thin. I'm hoping either they get some help or take a break from development in the new year.

    Barry
    Last edited by lhfarm; January 2, 2015, 07:25 AM.

    Leave a comment:

Working...
X