Author |
|
mike0999 Groupie
Joined: June 14 2009 Location: United States
Online Status: Offline Posts: 56
|
Posted: February 08 2014 at 23:30 | IP Logged
|
|
|
I've been running powerhome for some time using one of the original PLM's - the usb version. I recently updated to the dual band PLM - still the usb version.
I had some triggers defined to run a macro that turned a hot water recirculating pump on when there was a "fast-on" at the light switch in each of two bathrooms and also when a particular button was pressed on a keypadlinc in the hallway. The macro ran the pump for 30 seconds. I also had some timed events so my wife would have hot water waiting for her when she woke up in the morning. The keypadlinc light was controlled by the macro to indicate when the pump was on and when it was done running. etc. Everything worked great. The pump is plugged into one of the older icon appliance modules.
I hooked up the new PLM today and believe I deleted all of the links for the old PLM and recreated new links for the new PLM. For the life of me I have not been able to get any of the triggers to work. I even installed the I2CS patch in case that had something to do with it. No luck.
I actually hooked up the old PLM; recreated appropriate links to the old PLM; and the triggers all work again. Really scratching my head. Is there a difference between the old PLM and the new PLM that might cause this behavior.
One thing that I didn't do when I installed the new PLM was recreate the group that I am using to control the icon module. Is that my problem? I guess I'll try to change that tomorrow. But, is there anything inherently different about the new PLM that might impact triggers?
I understand that you may need quite a bit more info from me to help me. E.g., exactly what links do I have. Thanks in advance for any help.
Edited by mike0999 - February 08 2014 at 23:32
|
Back to Top |
|
|
mike0999 Groupie
Joined: June 14 2009 Location: United States
Online Status: Offline Posts: 56
|
Posted: February 09 2014 at 13:02 | IP Logged
|
|
|
Rather than rely upon the triggers, I have simply run the macro manually, and it seems that it is not executing the "insteon" commands in the macro. I actually even recreated the macro, which now is simply
command: insteon ID: RECIRC value: faston
command: wait value: 30
command: insteon ID: RECIRC value: fastoff
If I run manually using the run box, the only thing that my event log shows is the macro being run. It does not show that it is even attempting to execute the faston or fast off commands. RECIRC is the ID I have given to the icon appliance module.
I've tried restarting powerhome, but that didn't help. I am going to reboot the computer at this point to see if that helps.
Edited by mike0999 - February 09 2014 at 13:04
|
Back to Top |
|
|
mike0999 Groupie
Joined: June 14 2009 Location: United States
Online Status: Offline Posts: 56
|
Posted: February 09 2014 at 13:20 | IP Logged
|
|
|
Ok. I deleted the device "recirc," and re-added it. I allowed Powerhome to autodetect the device type. It now seems that the Macro works when I execute it. Not sure if this relates to I2CS or something else. Perhaps there is an explanation for this on the forum I didn't see?
|
Back to Top |
|
|
mike0999 Groupie
Joined: June 14 2009 Location: United States
Online Status: Offline Posts: 56
|
Posted: February 09 2014 at 14:03 | IP Logged
|
|
|
Dave, don't worry about responding to this. Go ahead and focus on 2.1.5. I've got it working at this point. I also was experiencing the issue described here:
http://www.power-home.com/forum/forum_posts.asp?TID=3219&KW= i2cs
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: February 09 2014 at 14:34 | IP Logged
|
|
|
Mike,
Based upon the behavior you're describing, Im thinking that you may
have created the new controller with a different ID than the old one. If
so, you would want to set the controller of each insteon device
(devices tab) to the ID of the new controller in order for commands to
be sent.
Let me know if this isn't the problem as there shouldn't be any
differences between the old and new controller that would cause the
problem you're having.
Dave.
|
Back to Top |
|
|
mike0999 Groupie
Joined: June 14 2009 Location: United States
Online Status: Offline Posts: 56
|
Posted: February 09 2014 at 16:59 | IP Logged
|
|
|
I originally had the same name for the controller and couldn't get it to work. I then changed the controller to a new name, which I think did in fact cause some of the behavior I described. I do think that the manner in which I had the trigger defined for the old controller may not have worked with the new controller. But, let me look at that a bit more closely, and see if I can give you more info, before I cause any sort of wild goose chase.
Edited by mike0999 - February 09 2014 at 17:00
|
Back to Top |
|
|
mike0999 Groupie
Joined: June 14 2009 Location: United States
Online Status: Offline Posts: 56
|
Posted: February 09 2014 at 17:42 | IP Logged
|
|
|
I am sure I am probably doing something wrong. But, I am having trouble finding it. I have my recirc macro triggered by a fast on in each of my two bathrooms. I now have that working fine with the new PLM.
The thing that seemed to work with the old PLM that I am having trouble getting to work with the new PLM is the following trigger. I have a trigger defined to run the recirc macro when I press the "A" button on a 6 button keypadlinc. I am using "Insteon Group In" as the trigger type; the Trigger ID is the ID for my keypadlinc; the trigger ID number is 3 (my understanding is that the A button on the keypad linc is group 3); and I have the trigger value as On(0x11).
When I press the keypadlinc button A, I get the following message in my event log. But, the trigger is not triggered.
"Incoming Insteon received on INSTEON PLM controller NEW PLM. From Address:[0A.E0.BC] To Address:[2A.00.CB] Flags:[65] Cmd1:[17] Cmd2:[3]. Decode: Group Cleanup. From: MSTRBDRM OUTER To: PLMCTLR1 Group: 3, On"
0A.E0.BC is in fact the keypadlinc; and 2A.00.CB is the new PLM.
If, instead of using the Insteon Group In trigger type, I use an Insteon Device Chg trigger type, the trigger will in fact fire. But, then I get some sort of infinite loop going (haven't figured that out completely yet).
Edited by mike0999 - February 09 2014 at 17:56
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: February 09 2014 at 20:34 | IP Logged
|
|
|
Mike,
It looks as if you're missing the group broadcast command from the KPL. It could be that communications just are not as good with the new PLM compared to the old. You are getting the group cleanup command though (Keypresses sent from an Insteon device are sent as group broadcast commands...they don't target a specific device and are not acknowledged. This is then followed up with a group cleanup which does get sent to a specific device and is much more reliable).
I would create an additional trigger for the group cleanup command (or figure out why your PLM cant hear the group broadcast...you might need to do an "Add Full"). This is an Insteon Direct In, KeypadLinc ID, Grp Cleanup - To Any.
Dave.
|
Back to Top |
|
|
mike0999 Groupie
Joined: June 14 2009 Location: United States
Online Status: Offline Posts: 56
|
Posted: February 09 2014 at 21:50 | IP Logged
|
|
|
Appreciate the help Dave. With the group cleanup approach that you described, is there anything tying the trigger to the group 3 button on the keypad?
|
Back to Top |
|
|
mike0999 Groupie
Joined: June 14 2009 Location: United States
Online Status: Offline Posts: 56
|
Posted: February 09 2014 at 22:04 | IP Logged
|
|
|
Hi Dave,
Looks like "add full" did the trick. Thanks. Any chance you can help me understand why that addressed the issue so that I better understand. You never know when I will run across something similar in the future.
Edited by mike0999 - February 09 2014 at 22:07
|
Back to Top |
|
|