X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Help & Troubleshooting => Topic started by: Livingston on June 01, 2011, 01:22:27 AM
-
Installed a new controller and have set up some modules. I'm able to turn the modules on/off from my computer but can't get them to run from the controller.
I've entered a simple timed event (on dawn off a bit later) but the programs, downloaded to the controller, don't work. I have a phase coupler installed so, although not guaranteed, don't suspect an issue with the phases.
First time with ActiveHome sofware. Am I missing something?
The modules are 3-pin appliance modules (AM466) with lights plugged in.
Thanks
Liv
Suspect this should probably have been posted in Troubleshooting.
-
If you can control the devices manually from within the AHP software, then it sounds like you probably don't have a phase transmission issue.
Here are a few other things you can check:
1) What version of AHP are you running? 3.314 is the latest (as of 6/1/2011). What (if any) other plugins do you have installed?
2) Check to make sure that your location is set correctly within the AHP software, and that the Dusk/Dawn times look to be about right for the dates listed.
3) Make sure that your time AND time zone are set correctly in Windows.
4) Make sure the modules are set using the correct module type in AHP (don't set an Appliance module up as a Lamp module, etc)
5) Make sure to check the "Store in Interface" box when you set up the timer. Without that box checked, the timer will only work if the CM15A is connected to the PC, and the AHP software is open.
6) Check your Activity Monitor. Does it show the commands being sent at the time you expected them?
Some users have reported problems with dusk/dawn based timers. You can troubleshoot by trying to set the timer based on a specific time (ex: 6:30 AM) instead of using Dusk/Dawn, and see if that works for you.
If that works, let us know here. I don't work for X10, but I've been working closely with the developers over the past year to try and track and resolve a number of AHP issues, so I can report this to them for further troubleshooting.
-
Thank you very much for your post. Having a diagnostic checklist is exactly what I was after (right now).
I can answer some of you question now and others (replacing dusk/dawn with clock settings) will take a 24 hour cycle to observe.
1) What version of AHP are you running? 3.314 is the latest (as of 6/1/2011). What (if any) other plugins do you have installed?
I'm running AHP 3.313 (check for updates shows it current). The only other plug-in currently installed is an RF/motion sensor but I don't have that defined yet in AHP.. I do have a 3 receptacle and a couple switch modules installed. Once I get things working I may replace some or all since they are quite old (assuming they don't work reliably with AHP).
2) Check to make sure that your location is set correctly within the AHP software, and that the Dusk/Dawn times look to be about right for the dates listed.
I had made sure the location was set correctly when I first installed AHP. As I understand it the initial setting in AHP comes from my laptop setting which was right (i.e. I didn't need to change).
As mentioned, I have replaced the dusk/dawn used in the timers with clock setting to eliminate that variable.
3) Make sure that your time AND time zone are set correctly in Windows.
As noted earlier, I think AHP picked up its initial configuration setting from Windows which was correct.
4) Make sure the modules are set using the correct module type in AHP (don't set an Appliance module up as a Lamp module, etc)
I'm fairly certain the module setting are correct for the 2 plug-ins I'm testing. Although I have a new plug-in lamp module available, I'm not using it currently. I may eventually replace an appliance module with the lamp module. Just need to remember not to use a compact florescent.
5) Make sure to check the "Store in Interface" box when you set up the timer. Without that box checked, the timer will only work if the CM15A is connected to the PC, and the AHP software is open.
I have to look for the check box you mentioned. In the mean time, I make it a point to "download the module and timer setting" to the controller via the menu whenever I make changes so I assume it's producing the same effect.
6) Check your Activity Monitor. Does it show the commands being sent at the time you expected them?
I'm not currently in a location where I can check the Activity Monitor right now. I'll do a check tomorrow (now that dusk/dawn are removed) to see what the log shows. I'll post back if it shows something out of sync with the intent.
Again, thanks for the post. My first impression of this forum is that it's a good one. On the other forums I use I'm pretty diligent about making sure results are posted back.
Liv
-
I'm running AHP 3.313 (check for updates shows it current).
Unfortunately, the "Check for Updates" function has been broken for a number of years. You can check for new updates here:
http://www.x10.com/support/support_soft1.htm
The latest version (as of 6/1/2011) is 3.314.
... I may replace some or all since they are quite old (assuming they don't work reliably with AHP).
If they are Lamp modules (a category that includes hard-wired wall switches designed control lights), They may be the older "non SoftStart" versions. Around 2008, X10.com changed the design of certain modules, but kept the model numbers the same. Unfortunately, there is no way to tell by just looking at the modules. However, there is a simple test. Turn them on, one at a time, and watch what happens. If they come on immediately at 100% brightness, they are the older (non-SoftStart) models. If they slowly dim up to full brightness (takes about a second or two), then they are the newer, SoftStart model.
The difference is important. AHP (since version 3.302) has defaulted to using the newer SoftStart behavior for modules in the "Lamps" category. The older (non-SoftStart) versions of those modules won't respond properly to those commands, though. If your modules are non-SoftStart, then right-click on them in AHP, and click "Edit Module." From the "Type of Module" drop-down, choose "Older Lamps (no SoftStart)", and then pick the correct module type from the "Module" drop-down.
Save and re-download your programming to the CM15A.
I'm fairly certain the module setting are correct for the 2 plug-ins I'm testing. Although I have a new plug-in lamp module available, I'm not using it currently. I may eventually replace an appliance module with the lamp module. Just need to remember not to use a compact florescent.
See my note about the SoftStart and non-SoftStart modules (above)
I have to look for the check box you mentioned. In the mean time, I make it a point to "download the module and timer setting" to the controller via the menu whenever I make changes so I assume it's producing the same effect.
It is not the same thing. When you download the program to the CM15A, it ONLY downloads those items that are marked as "Store in Interface." There are a number of functions (specifically macros that utilize some of the newer "online" software plugins) that cannot be run from the interface, and require that the CM15A be connected to the PC, and that AHP be left open 24/7.
One other thing I didn't ask earlier:
You ARE using a CM15A, right? X10.com sells a package that has AHP with a CM19A, and a TM751. That combination requires the PC to be connected and turned on, as there is no memory in the CM19A.
-
Things have gone from bad to worse. I can't get the plug (I'm testing with) to respond to commands from the PC. I even moved it to the same circuit the controller is on.
I did find the check box in the timer window. I assume you mean the "store in interface" one and its checked.
And it is C15A. In fact, I ordered quite a few modules with the controller last week.
I can also pretty much assure you the receptacle and switch modules are old. I suspect I installed them close to 10 years ago. I'll run a test with the changes you suggested later today.
Also checked the Activity Report. It just continues to add a status check every half second or so.
I'm not willing to start thinking about a bad controller but it's still in the "possible" list. Although I'm quite comfortable understanding the software, I'm still assuming operator error.
Liv
-
Is the CM15A connected to the same outlet as the computer equipment?
Computers and accessories can make power line noise or absorb X10 signals.
Is the CM15A on a power strip that may have a surge and noise filter in it?
Noise filters in them can also absorb X10 power line signals.
-
Things have gone from bad to worse. I can't get the plug (I'm testing with) to respond to commands from the PC. I even moved it to the same circuit the controller is on.
What is the model number of the module you are testing with, how (exactly) do you have it defined in AHP?
I did find the check box in the timer window. I assume you mean the "store in interface" one and its checked.
Okay, so the CM15a SHOULD be trying to run the timer (but you may still have issues with dawn/dusk based timers - that is a possible software bug they are investigating)
And it is C15A. In fact, I ordered quite a few modules with the controller last week.
Thanks for verifying.
I can also pretty much assure you the receptacle and switch modules are old. I suspect I installed them close to 10 years ago. I'll run a test with the changes you suggested later today.
The difference is only important for "Lamp" modules (which includes wall switches that can dim). It shouldn't affect Appliance modules (as long as they are defined correctly in the software).
How were you controlling them before you got the CM15A? If you have another controller (plug-in, or wireless) that you can test with, make sure those modules are still responding.
Also checked the Activity Report. It just continues to add a status check every half second or so.
That's really strange. that sounds like two-way module behavior to me.
I'm not willing to start thinking about a bad controller but it's still in the "possible" list. Although I'm quite comfortable understanding the software, I'm still assuming operator error.
It can be tricky to get the system set up initially, which is probably the root of the trouble you are having.
One other thing to check is to go into the "Hardware Configuration" screen, and set the "Transcieved House Codes" to "Manual." Then, make sure to check any house codes you are using.
Make sure that the HouseCode/UnitCode combinations on your modules match what you have in AHP. You might also try rotating the code wheels all the way around a few times. Sometimes the contacts get dirty, and they don't make contact in the right combination for the codes you want.
-
Is the CM15A connected to the same outlet as the computer equipment?
Computers and accessories can make power line noise or absorb X10 signals.
Is the CM15A on a power strip that may have a surge and noise filter in it?
Noise filters in them can also absorb X10 power line signals.
Brian, the last time I ran tests I didn't have the computer (laptop) plugged in at all. And the controller is plugged directly into a wall outlet.
Tom
-
What is the model number of the module you are testing with, how (exactly) do you have it defined in AHP?
It's AM466 3-pin Appliance Module. It's defined as Type:Appliance, Module:Appliance Module (3-pin).
I did find the check box in the timer window.
A follow-up question just to confirm. So, when the "store in interface" is checked in the timer screen, AHP will automatically send any changes as soon as I change them (or when I close the app)(?)
The difference is only important for "Lamp" modules (which includes wall switches that can dim). It shouldn't affect Appliance modules (as long as they are defined correctly in the software).
How were you controlling them before you got the CM15A? If you have another controller (plug-in, or wireless) that you can test with, make sure those modules are still responding.
Before buying the new controller I was running one from SmartHome (a PowerLink 1132CU) that appeared to have failed completely. I decided to replace and it was the folk at SH that referred me to X-10.com and AHP. Since, with one exception (a 2-pin plug-in Insteon lamp module currently not in use and unplugged), all the modules are X-10 they were nice enough to recommend a much less expensive option. Very nice gesture on their part!
Since I think the 1132CU is questionable and I'm not sure would work with AHP, I suspect that's not an option as an alternate test device.
Also checked the Activity Report. It just continues to add a status check every half second or so.
That's really strange. that sounds like two-way module behavior to me.
I decided to unplug the controller and remove the batteries (in attempt to get it to reset). I wanted to eliminate the "receive status" activity getting in the way of the controller doing anything else. After I plugged it back in (with batteries) the Activity was still getting a receive status every half second.
It can be tricky to get the system set up initially, which is probably the root of the trouble you are having.
I'm still operating on the belief that it's set up issues.
One other thing to check is to go into the "Hardware Configuration" screen, and set the "Transcieved House Codes" to "Manual." Then, make sure to check any house codes you are using. Make sure that the HouseCode/UnitCode combinations on your modules match what you have in AHP. You might also try rotating the code wheels all the way around a few times. Sometimes the contacts get dirty, and they don't make contact in the right combination for the codes you want.
The button is actually called "specific". I've selected it (instead of "automatic") and confirmed the house code.
Thanks again for hanging in there. I really appreciate the time you're spending with me.
Liv
-
...A follow-up question just to confirm. So, when the "store in interface" is checked in the timer screen, AHP will automatically send any changes as soon as I change them (or when I close the app)(?)
No.
When the box is checked, then that timer (or macro) is included when you download the programming to the interface. When the box is NOT checked, then that timer (or macro) will ONLY work when the CM15A is connected, and AHP is open.
Before buying the new controller I was running one from SmartHome (a PowerLink 1132CU) that appeared to have failed completely. I decided to replace and it was the folk at SH that referred me to X-10.com and AHP. Since, with one exception (a 2-pin plug-in Insteon lamp module currently not in use and unplugged), all the modules are X-10 they were nice enough to recommend a much less expensive option. Very nice gesture on their part!
Any SmartHome lamp modules MUST be defined in AHP as "Old Lamp" modules. They don't respond to the newer "Extended Dim" commands.
Since I think the 1132CU is questionable and I'm not sure would work with AHP, I suspect that's not an option as an alternate test device.
The 1132CU is certainly not compatible with AHP.
You had mentioned that you were no longer able to control the modules when the CM15A was disconnected from the PC. How are you trying to control them? In order to control anything directly from within the AHP software, the CM15A needs to be connected to the PC. I'm not sure what you were using for testing.
Also checked the Activity Report. It just continues to add a status check every half second or so.
...
I decided to unplug the controller and remove the batteries (in attempt to get it to reset). I wanted to eliminate the "receive status" activity getting in the way of the controller doing anything else. After I plugged it back in (with batteries) the Activity was still getting a receive status every half second.
Sounds like something is still putting out those commands. Do you have ANY other X10 equipment (like the security sensors, or some Smarthome X10/Insteon modules)? If you can tell us exactly what yout are seeing in the log, we might be able to help narrow it down. You can export the Activity Log to an HTML file, then open that in your browser and copy/paste it here.
I'm still operating on the belief that it's set up issues.
Good! that means you're not giving up yet ;)
The button is actually called "specific". I've selected it (instead of "automatic") and confirmed the house code.
Sorry, I was going from memory on that one.
-
No.
When the box is checked, then that timer (or macro) is included when you download the programming to the interface. When the box is NOT checked, then that timer (or macro) will ONLY work when the CM15A is connected, and AHP is open.
Good clarification. It sounds like I still need to send the changes to the interface (via the menu). The "switch" just determines which modules and timers are sent when the download is executed.
You had mentioned that you were no longer able to control the modules when the CM15A was disconnected from the PC. How are you trying to control them? In order to control anything directly from within the AHP software, the CM15A needs to be connected to the PC. I'm not sure what you were using for testing.
I think I understand this one. I don't expect a manual on/off to be successful unless the PC is connected to the controller. What's interesting right now is that doesn't seem to work any more.
Sounds like something is still putting out those commands. Do you have ANY other X10 equipment (like the security sensors, or some Smarthome X10/Insteon modules)? If you can tell us exactly what yout are seeing in the log, we might be able to help narrow it down. You can export the Activity Log to an HTML file, then open that in your browser and copy/paste it here.
From memory, the "loop" is simply a time stamp and the words "receive" and "status". I'll look more closely the next time I have the laptop connected to the interface and do a screen shot to attach then.
This is the complete inventory of devices on the wiring. There are 2 brand new appliance 3-pin plug in modules (both are defined in AHP). One is the test module I moved to the same circuit as the controller. There are 4 wired in receptacles (all are defined in AHP). There are 1 or 2 wired in light switch modules, one is defined in AHP. There's also a plug-in RF associated with a motion sensor that is not defined in AHP.
And I haven't given up yet. It's funny that you can get pretty dependent on having the lights on/off automatically. We've had the luxury of living with a working system for a very long time. Even if we determine that the controller is suspect, I assume X-10.com will be very cooperative in getting the issue resolved.
I still owe you a screen print of the Activity report.
Liv
-
The 1132CU {I have a few myself} will not run AHP as you suspected.
Only the Smarthome Manager Essentials or the Plus Version.
Smarthome called the 1132CU legacy and never updated the software for the new DST or any Windows version newer than XP.
We did came up with t DST workaround and someone did rewrite the Installer script to do Windows newer than XP.
AHP may not control you LampLinc Dimmer as X10 and Smarthome chose a different method to do dim commands.
-
Brian, thanks for confirming my assumption about the LampLinc.
The LampLinc was the only module I bought that was Insteon so it's not too disappointing to hear it may not work with AHP. I don't use dimming anywhere in the house so it might be salvageable although I may have enough plug-in lamp modules.
I found out the 1132CU was no longer available when I started having problems with mine and was thinking about a replacement. Good to hear a more thorough explanation.
I repeat my praise for Smarthome for their referral to X10.com and AHP (as probably best for my installed hardware and plans).
Appreciate your posts.
Liv
-
As for modules, you can get X10 lamp and appliance modules from X10, Automated Outlet (http://www.automatedoutlet.com/) and other sources on the Web. I use Automated Outlet, their prices are fine and they have flat rate shipping regardless of order size.
-
An On or Off to the LampLinc should work fine. Dimming maybe a problem. Though calling it a Old before Soft Start Lamp Module. May have AHP send a stream of dim or bright commands.
-
An On or Off to the LampLinc should work fine. Dimming maybe a problem. Though calling it a Old before Soft Start Lamp Module. May have AHP send a stream of dim or bright commands.
It should work okay if defined as a "Wall Switch" from the "Old Lamps" section.
You can also define it as a "Florescent decorator Wall Switch" from the "old Lamps" category.
That usually gets AHP to send the older "on" and "off" commands (instead of the newer Extended Dim commands).
-
Have things set up for another "test". It turns out I misunderstood the role of the "store in interface" check box in the timed section. I thought the check meant I didn't have to download the modules and timers to the interface (i.e. AHP would take care of it automatically). This meant that the interface didn't have any info (since I unplugged and pulled the batteries looking for a reset).
Once I did the download, I could control the test modules directly from the computer.
I have things set up now in a way that will test whether removing dawn/dusk makes a difference.
This thread has been a great learning tool.
I'll post back results including the activity log.
Liv
-
Did you determine which of your modules are SoftStart, and which are not?
Did you set them appropriately within AHP?
Another suggestion is NOT to mix different classes of modules (Appliance modules with Lamp modules, and even SoftStart with non-SoftStart modules) on the same HouseCode / UnitCode combination. since each type requires a different set of commands to operate, you may not get the desired results.
-
Thanks for checking back. If I understand the explanations in earlier posts, the answer is "yes, I've identified them" and "yes, I've changed the definition in AHP". It comes down to 2 wired-in light switch (push button) modules. I've set them up as "Older Lamp (no SoftStart)" and "Wall Switch Module".
I noticed one of them (didn't check the other) came on last night. I'm going to watch them again tonight to make sure their working.
I've assumed that all the old wired-in wall recepticals (plugs) are not "no SoftStart".
Interesting idea to split things over house codes. I'll go ahead and do that.
One module we haven't talked about yet is a motion sensor and RF plug-in. I haven't gotten around to checking what the sensor part looks like in X-10.com terminology. The RF device shows I bought it from an X10 company in Las Vegas and has a model code of "PAT01".
It is on a different house code but happens to be the same one as the sample room in AHP. To get a good test, I'm going to change that to one other than the one the lights are on.
Finally, there's some good news on the "test" light controllers. The 3-pin plug-in appliance modules worked last night and this morning!!! Probably now have a good base configuration for them so I can start some tests like moving back to dusk/dawn (although a 1-hour delay/advance limit may not be enough for my preference).
Since prior to the failure of the old controller, these lights were controlled by receptical modules, I pulled the 3-pin plug ins and plugged the lights into the controlled recepticals. They respond to manual on/off and I'll see tonight whether they work with the timers.
-
Thanks for checking back. If I understand the explanations in earlier posts, the answer is "yes, I've identified them" and "yes, I've changed the definition in AHP". It comes down to 2 wired-in light switch (push button) modules. I've set them up as "Older Lamp (no SoftStart)" and "Wall Switch Module".
I noticed one of them (didn't check the other) came on last night. I'm going to watch them again tonight to make sure their working.
That's good news. That means you're on the right track now!
I've assumed that all the old wired-in wall recepticals (plugs) are not "no SoftStart".
Yes, the wall-outlet models are equivalent to "appliance" modules, and only have on/off functionality (no dimming).
There should be a definition within AHP for them, though.
Interesting idea to split things over house codes. I'll go ahead and do that.
It wasn't so much to split them across house codes, but rather to make sure that you didn't have two different types of modules sharing the same Unit code address.
One module we haven't talked about yet is a motion sensor and RF plug-in. I haven't gotten around to checking what the sensor part looks like in X-10.com terminology. The RF device shows I bought it from an X10 company in Las Vegas and has a model code of "PAT01".
It is on a different house code but happens to be the same one as the sample room in AHP. To get a good test, I'm going to change that to one other than the one the lights are on.
The PAT01 is the X10 Pro equivalent to the RR501 transceiver. It is used to to receive RF signals from hand-held remotes or motion sensors, and transmit those commands along the power lines. It also has a built-in appliance module, which can be set to either Unit Code 1 or 9, on whatever House Code you set the module. Keep this in mind when assigning Unit codes, you don't want it to cause a conflict (or have the audible "Clunk" when you turn on some other device that shares the same code).
Finally, there's some good news on the "test" light controllers. The 3-pin plug-in appliance modules worked last night and this morning!!! Probably now have a good base configuration for them so I can start some tests like moving back to dusk/dawn (although a 1-hour delay/advance limit may not be enough for my preference).
Make sure the modules are working in the locations where you plan to use them, before making other changes. As with any troubleshooting, changing only one variable at a time is usually better.
Since prior to the failure of the old controller, these lights were controlled by receptical modules, I pulled the 3-pin plug ins and plugged the lights into the controlled recepticals. They respond to manual on/off and I'll see tonight whether they work with the timers.
Let us know how it goes.
-
Norm,
This is the comment that made me think you were suggesting splitting the house code for different device types.
Another suggestion is NOT to mix different classes of modules (Appliance modules with Lamp modules, and even SoftStart with non-SoftStart modules) on the same HouseCode / UnitCode combination. since each type requires a different set of commands to operate, you may not get the desired results.
Sounds like some folk might set up multiple modules with the same house.unit code, presumably to "group" the devices and save some time (i.e. make changes for the group vs. for each module). Also useful if they have more than 15 modules.
Hadn't thought of doing that. For now, I'm keeping every device (hardwired or plug in) on a unique "address". Although I can't remember why, I put the X-10 Pro PAT01 (RR501) on a different house code ("A" instead of "C" which I use for all other modules). Unfortunately I chose the same house code as the sample room in AHP. I'll change the sample room modules to a different house code just to remove that variable.
When I get around to testing the PAT01, I'll review the instructions. I vaguely remember the unit's manual address setting was just for the lamp plug.
Liv
-
The PAT01's AC output. Is an appliance type. So any load suitable for an appliance module can be controlled by it.
Now having the CM15A and the PAT01 tranceive the same House Code could lead to problems. Though both are polite and try not to step on each other. It could be possible to have both units send a power line signal at the sametime and garbage the signal.
-
This is the comment that made me think you were suggesting splitting the house code for different device types.
"Another suggestion is NOT to mix different classes of modules (Appliance modules with Lamp modules, and even SoftStart with non-SoftStart modules) on the same HouseCode / UnitCode combination. since each type requires a different set of commands to operate, you may not get the desired results."
Sounds like some folk might set up multiple modules with the same house.unit code, presumably to "group" the devices and save some time (i.e. make changes for the group vs. for each module). Also useful if they have more than 15 modules.
Actually it is for those people that have two or three plug-in lamps in the same room, and they want all of them to come on and go off together. Setting them for the same HouseCode/UnitCode is the best way, since only one command is needed, and all three respond to it. However, if the modules are different types, that won't work too well.
...Although I can't remember why, I put the X-10 Pro PAT01 (RR501) on a different house code ("A" instead of "C" which I use for all other modules). Unfortunately I chose the same house code as the sample room in AHP. I'll change the sample room modules to a different house code just to remove that variable.
When I get around to testing the PAT01, I'll review the instructions. I vaguely remember the unit's manual address setting was just for the lamp plug.
As Brian noted, the outlet on the PAT01 is equivalent to an Appliance module, not a Lamp module (it has no dimming).
If you plan to use any RF remotes, or motion sensors to directly control your lights or appliances, then the PAT01 needs to be on the same HouseCode as the modules you plan to control.
As Brian also noted, the CM15A and PAT01 (or RR501) are both capable of receiving RF signals, and sending them out on the powerline. Depending on your setup, you might not need the PAT501 at all.
The CM15A is notorious for having very poor RF reception range, but there are a number of fixes for that, at least one of which doesn't involve opening up the unit or voiding the warranty. You can do a search for "Antenna Mod" in the forums and find the various options. I'm using the "passive reflector" type of mod on mine, and it works really well for me.
-
I have great news (and a lot of gratitude)!
With the exception of the PAT01, everything is running. And it's not that I'm having problems with the PAT01; I just haven't worked on it yet.
The PAT01 is used with a motion sensor (mounted right on the other side of the wall where the PAT01 is plugged in). You may find this humorous: the motion sensor is right next to a pet door. Don't want those dogs and cats going outside at night without a light. On a more practical level, its a minor deterrent against other animals thinking about coming in through the pet door.
It's far more convenient to have the CM15A in a different room, so I'll want to get the PAT01 working. The posts about the device have been helpful and will guide me when I work on it.
Actually it is for those people that have two or three plug-in lamps in the same room, and they want all of them to come on and go off together. Setting them for the same HouseCode/UnitCode is the best way, since only one command is needed, and all three respond to it. However, if the modules are different types, that won't work too well.
This makes a great deal of sense. Keeping in mind the guidance on not mixing module types, I'll be able to take advantage of the technique.
Before closing out the thread, note I am not using dawn/dusk in any of the timers. If I had my druthers, I'd prefer they work. Now that I have a solid "baseline" it will make testing much more productive. I'll change one or two modules and see what happens.
I also may need some additional help on the PAT01.
Because this has been such a very thorough tutorial, I'll close the thread with a post summarizing my learning as a legacy for others.
Liv
-
Actually it is for those people that have two or three plug-in lamps in the same room, and they want all of them to come on and go off together. Setting them for the same HouseCode/UnitCode is the best way, since only one command is needed, and all three respond to it. However, if the modules are different types, that won't work too well.
This makes a great deal of sense. Keeping in mind the guidance on not mixing module types, I'll be able to take advantage of the technique.
Lamp Modules and Appliance Modules on the same HC/UC will respond equally well to simple X10 "ON" and "OFF" commands.
-
Moving on the the PAT10 and (I assume I have) an EagleEye Activehome sensor (that I bought years ago).
I won't have a lamp plugged into the PAT10. Instead, I want motion to activate another module in the house, specifically a no-SoftStart light switch module (on/off only). Can I do that and, if so, do I do it with a macro or is there another approach systemic to the PAT01?
Given the house code is "C" for all the other modules (including the one I want to control) I assume I'll need to change the house code in the sensor to HC "C" vs. the default HC "A".
In addition, is the manual HC/Unit setting on the PAT01 only for the built-in appliance plug?
Liv
-
http://www.x10pro.com/pro/pdf/pat01.pdf
This information is in the PAT01 Instructions
1. Yes
2. You don't need a macro for the Eagle Eye/PAT01 Transceiver to directly control the Wall Switch module. You would need a macro if you wanted the wall switch to turn on only under special conditions (i.e. when not home and motion detected,etc) or if you want the light to do something other than turn on when motion and turn off after no motion ( i.e. on motion, turn on, dim 50%, wait 30 minutes then bright to 100%, wait 5 minutes then turn off, etc). In that event you would not have the motion detector and the wall switch on the same UC.
3. The PAT01 would be set to HC "C" if that is the HC of the wall switch you want to control.
4. Yes
-
Lamp Modules and Appliance Modules on the same HC/UC will respond equally well to simple X10 "ON" and "OFF" commands.
Yes, but if you define that HC/UC as a lamp module (with SoftStart), then AHP won't send the simple ON and OFF commands.
-
Yes, but if you define that HC/UC as a lamp module (with SoftStart), then AHP won't send the simple ON and OFF commands.
I'll be interested in where this conversation goes.
More results: The test (one module) of the dusk setting has been successful. Because of earlier posts mentioning possible issues with dusk/dawn, I'll continue to monitor closely while expanding the setting to other modules. For now, though, and at least in the case of a non-SoftStart wired light switch module, things work. My next test will expand to a wired plug receptacle.
Liv
-
Lamp Modules and Appliance Modules on the same HC/UC will respond equally well to simple X10 "ON" and "OFF" commands.
Yes, but if you define that HC/UC as a lamp module (with SoftStart), then AHP won't send the simple ON and OFF commands.
Guess I should have been more clear. If you are only sending simple ON-OFF commands and want to combine Appliance Module and Lamp Module on same HC/UC (say for an alarm function, which is my application), you would define as an Appliance Module.
As far as AHP not sending simple ON-OFF commands, isn't that deviation specific to a Lamp turned on via a timer, or turning on to a DIM level?