X10 issues

[Steve Q]

I am having all kinds of issues with my X10 motion sensors. I'm not sure if the problems are your plugin or HS3. First let me say that I have about 15 DS10 door/window sensors that are working great with your plugin. No issues so far. On the other hand, my X10 motion sensors are not working all the time. I have 10 x10 motion sensors setup in HS3. When I set them up they seem to work for a few hours then they stop. I spent some time this morning working on this and I discovered that CAPI on HS3 was apparently not running. I did not see any CAPI statements in the HS3 log. So I restarted HS3 and the BLRF plugin and now HS3 is seeing the X10 motion sensors.

I have no working knowledge of CAPI; what it does and how it works. But I know it is involved with device control. So I am guessing that your plugin uses CAPI. There were no error messages in the HS3 log. And I think only the x10 motion sensors were affected. My other x10 devices were still working.

Is there a way to determine if CAPI is running on HS3?

Steve Q




Sent from my iPad using Tapatalk

[TeleFragger]

{subscribed as I own 30 motions}


side note that I believe you already know but in case anyone else is reading...you have the motions in HS3?

so you create device, give it a name, floor, room
goto x10 tab and house code and appliance

done...

if you check off virtual will toast the device....

so as you know I had a C5 on happening all kinds of times with some offs...
turns out ms13a under kitchen desk with low battery was burping away. Now I found that but have a D13 doing the same. I am now putting all my x10 devices in excel to track this stuff for future use.

I know my motions were acting up as I created the devices different ways like using the house code on the main tab... big no no...

also I do know I had to disable the x10 plugin, remove it and re-install it...

just food for thought...

[Steve Q]

X10 issues

After a lot of trial and error, I learned not to mess with the settings while setting up the X10 wireless devices. I'm now using a TI103 but I have also tried the CM15a. I gave up on the CM15a, I could not get it to work.

Like you, I have also recreated several devices before I could get them to work. It's a PITA.

But I think we will get it figured out. There are a lot of smart people on this board.

Steve Q


Sent from my iPad using Tapatalk

[Steve Q]

X10 issues

This is Blades thread?



Sent from my iPad using Tapatalk

[TeleFragger]

This is Blades thread?



Sent from my iPad using Tapatalk

correct but the actual issue you are seeing is in the X10 protocol plugin correct?
Blades plugin is pulling in and seeing it... these arent things you are changing in BLRF???

so far my ds10a's, housecodes, etc all things in BLRF have been good so I feel your issues will lie in X10 plugin

[Steve Q]

The only way I can get an X10 motion sensor to do anything is through the BLRF plugin. The triggers are coming from BLRF. The setup is controlled by the X10 plugin. Both are involved.

Steve Q


Sent from my iPad using Tapatalk

[TeleFragger]

Both are involved.

Steve Q


Sent from my iPad using Tapatalk

Right... i know both are involved... are you seeing issues on blades side?
what triggers are you using?

I am looking at setting up one of mine back up tonight as I have batteries back in my garage motion and replaced my light switch as it seems my other died...

so i can try and post similar and test similar as you are doing...

side note i also use the RFXCOMM plugin for my temps... i thought of switching over to it for my motions too to see if things go differently but I havent had an issue with BLRF and my motions (unless I mess with them in the x10 plugin)

[Steve Q]

X10 issues

I have only created a few events that are triggered by an x10 motion sensor. I.e. Turn on upstairs light when motion is detected in the hallway. When you create an event you will find a BLRF: x10 trigger. My events will sometimes work; sometimes not. When they do work, they quit working after X hours.

Steve Q


Sent from my iPad using Tapatalk

[TeleFragger]

I have only created a few events that are triggered by an x10 motion sensor. I.e. Turn on upstairs light when motion is detected in the hallway. When you create an event you will find a BLRF: x10 trigger. My events will sometimes work; sometimes not. When they do work, they quit working after X hours.

Steve Q


Sent from my iPad using Tapatalk

ahhhh see I didnt know that...

so a question... when the event doesnt work.. did the device update its last time tripped?

I usually only use the plugin for incoming into HS... for motions to control light I use...

when device changes and becomes (think that is it off top of head)....

what if you disable yours and try that? see if better results.
I was having an issue with an email on alarm disarm and got some emails when we were sleeping so rogue....

[Steve Q]

X10 issues

No, the time is not updated. When I was using the CM15a, I tried unsuccessfully to use the trigger "when the device value changes...." At some point, I tried the BLRF: x10 trigger and that worked. Like all things HS3, I have learned that when you get something working, don't mess with it. So I never went back to try again. I suspect it will work as long as the device value for the wireless X10 HS3 device is actually changing when the motion sensor is firing. In my experience, I don't always see the the device value changing from off to on when the motion sensor fires. This is where CAPI comes in. CAPI is the controller of the HS3 device value. So, if CAPI is misbehaving then the device value will not reflect the actual status of the device.

Note, in the list of device triggers, there is also an "x10 device change" trigger. This does not work for me.

Steve Q


Sent from my iPad using Tapatalk

[Thickman]

Not that it helps with your problem but using BLRF and BLRadar, no problems with motion events.

[TeleFragger]

Ok so I had a fun night...

I removed my 23890w light switch which wouldn't reprogram and replaced it with the utility one. It allowed me to program and give it a house code...
I then set my MS13A up

setup and event where if EITHER garage door to house/left garage door/right garage door opens....

1. trip motion (previously didn't do this but lights wont turn off if no one trips motion)
2. turn light on

now this works. I just tested it with

garage door (concord 4 alarm) and device changes and becomes FAULTED
right garage door (DS10A with merc switch) and BLRF: Garage Right Garage Door is ALERT

I didn't test motion yet. going to in a minute as I didn't create that event yet.....

Also do you have retransmit set at house code tab?

I'm not doing it for D as I have a rogue device I'm still tracking down...
I unchecked that and turned BLRF logging to HS off... hah...


hope these help... but you can see my ms13a has motion on and time... dark sensor is off and time... blah blah blah...

[TeleFragger]

While reviewing to make sure I typed it all right and good pics... I see my motion off tripped..

still looks good...
Dark sensor On
Motion Off
Light Off

[TeleFragger]

any of my screens show you anything usefull?

[Steve Q]

I'm not sure I understand how you are using motion detection. Your event sets the motion sensor device to ON. If it is working properly it should change to ON independently. Do you have multiple "garage motion" devices?

My x10 motion sensor devices change from off to on automatically. Your log should have lines something like: BLFR........CAPI control.........

Steve Q


Sent from my iPad using Tapatalk