There may not be a way to do this, but I have to ask.
Background:
I have an old Leviton 6308 X10 Dusk to Dawn Sensor. The great functionality of this device is the ability to send On or Off commands to up to 4 devices when triggered. It has been my failsafe over the years to turn on/off all of my exterior home lights (4 unit codes) in the event that HomeSeer was down or not functioning properly. It has also been a great way to trigger other scripts through HomeSeer when dusk/dawn is detected. This thing is hard-wired and outdoor rated just like a typical 120v dusk to dawn sensor that many homes have to automatically turn on/off garage lights.
Problem:
When I was running HS2, the commands generated by this device were picked up fine. Now with HS3, they are not. I am using a TI103 and version 3.0.0.40 of the X10 plugin. The sensor is set to Housecode C and is set trigger units 1,2,3,&4. At dusk, the command generated (as seen is the log) is:
Callback: Dev= C1+C2+C3+C4, HC= C, Cmd= 2, 0/0
I have been able to replicate this transmission on the powerline using an old Maxi-controller, set to housecode C, press[1]press[2]press[3]press[4]press[on]
I have X10 devices C2, C3, C4 defined (properly through the X10 tab) that will indeed respond to discreet individual On/Off/Dim commands , but HomeSeer does not seem to understand the above command sequence. None of the Housecode C 1-4 devices change status in HomeSeer, and I have been unsuccessful in defining an event that will capture this sequence.
Any X10 experts out there know of a way to accommodate this through an event or definition of the X10 device, or is this a limitation of the plugin?
I have yet to find a suitable, robust replacement for this device and I would love to continue to keep it a part of my setup.
Thanks for any help or suggestions!
Background:
I have an old Leviton 6308 X10 Dusk to Dawn Sensor. The great functionality of this device is the ability to send On or Off commands to up to 4 devices when triggered. It has been my failsafe over the years to turn on/off all of my exterior home lights (4 unit codes) in the event that HomeSeer was down or not functioning properly. It has also been a great way to trigger other scripts through HomeSeer when dusk/dawn is detected. This thing is hard-wired and outdoor rated just like a typical 120v dusk to dawn sensor that many homes have to automatically turn on/off garage lights.
Problem:
When I was running HS2, the commands generated by this device were picked up fine. Now with HS3, they are not. I am using a TI103 and version 3.0.0.40 of the X10 plugin. The sensor is set to Housecode C and is set trigger units 1,2,3,&4. At dusk, the command generated (as seen is the log) is:
Callback: Dev= C1+C2+C3+C4, HC= C, Cmd= 2, 0/0
I have been able to replicate this transmission on the powerline using an old Maxi-controller, set to housecode C, press[1]press[2]press[3]press[4]press[on]
I have X10 devices C2, C3, C4 defined (properly through the X10 tab) that will indeed respond to discreet individual On/Off/Dim commands , but HomeSeer does not seem to understand the above command sequence. None of the Housecode C 1-4 devices change status in HomeSeer, and I have been unsuccessful in defining an event that will capture this sequence.
Any X10 experts out there know of a way to accommodate this through an event or definition of the X10 device, or is this a limitation of the plugin?
I have yet to find a suitable, robust replacement for this device and I would love to continue to keep it a part of my setup.
Thanks for any help or suggestions!
Comment