| Author |
|
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: April 03 2006 at 19:33 | IP Logged
|
|
|
1. As of the other night, my ramp rates changed to 10 seconds or so (when controlled by the PLC). I did nothing (AFAIK) but send some group on/off commands trying to figure out what groups could be used for. The ramp rates displayed in PH are 31.
2. I have two Insteon triggers that do not respond when I put a macro as the command, but if I handle it as a formula and add something before the macro is called, it works (i.e. ph_playsound(xx) + ph_macro(yy) ).
Any suggestions?
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 04 2006 at 18:49 | IP Logged
|
|
|
Tony,
Concerning the Insteon triggers, are they "Queued" or "Immediate". It's very important to use "Queued" with Insteon triggers. Can you let me know what kind of Insteon trigger it is? I'll set up some tests here and see what I can find out.
Concerning the ramprates, that is strange. Which ramprates are you talking about...local or group? If it's the local ramprate, then only way these can currently be set is by pressing the "set" button on the switch twice and the ramprate will change to reflect whatever the current dim level is. Do you have the "Background local level scan" turned on? If so, it should rescan the level every so often. If youve got 4 Insteon devices and your background scanning is every 15 seconds, then this value should be updated once a minute.
Let me know and we'll get it fixed.
Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: April 04 2006 at 19:37 | IP Logged
|
|
|
Dave,
The triggers are Queued, Insteon Group In, Group 1, On and Off.
I guess the ramp rates would be group, because the local rate is still quick; it's only slow when controlled by PH (I'm not controlling them as a group, though). I have Background Local Level scan disabled to keep the lockups from happening.
Also, how do you delete groups that only show up under "By Responder"? 
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: April 04 2006 at 20:01 | IP Logged
|
|
|
I just made the formulas "ph_delay(500) + ph_macro(xx)" and they consistently worked. A delay of 100 works also. I'll keep checking smaller values.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 05 2006 at 23:37 | IP Logged
|
|
|
Tony,
I'll run some tests and see if I can duplicate the Insteon trigger calling the macro problem. If you set the action type as Macro and call the macro directly from the Insteon trigger, does the log show that the macro is called or not?
If you are using a direct Insteon command to control the light from PowerHome, then that would be using the local ramprate. If you use a group command, then that would use the rate defined within the group. If the light is fast when switched locally and then slow when sending a direct command from PowerHome, then that is definately wierd. Is there any way you can duplicate this? I would definately need to get SmartHome involved to figure this out.
Concerning the Insteon links...are you saying that you have links that show up in "By Responder" and don't show in "By Controller"? If so, could you email me a copy of your database so I can troubleshoot?
Thanks,
Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: April 06 2006 at 22:31 | IP Logged
|
|
|
Duplicate? Sure, it does it all the time now! ;)
Once we figure out how to fix it, I'll try to break it again.
Yup, in By Responder and not By Controller.
When I get home (ugh), I'll email you the db.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 06 2006 at 23:26 | IP Logged
|
|
|
Tony,
Ive been playing with the "Insteon Group In" trigger firing a macro and it always works for me. When you send me your database, point out for me the trigger and macro where you're having the problem and I'll try to test further.
Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: April 07 2006 at 19:21 | IP Logged
|
|
|
You've got mail! 
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 20 2006 at 00:19 | IP Logged
|
|
|
Tony,
Ok...finally got around to analyzing your DB...sorry to take so long  .
First, I see what you mean about the link in the responders and not in the Controllers. It actually is in the Controllers but is not under the proper controller (the bathroom link under the NOT FOUND controller). This is because of the grouping. Im grouping by the ID and the ID is not found for two different addresses in your situation so they're grouped together. Anyways...Ive made changes to both screens to take care of this problem so you'll see the extra controller in this case.
Now...you've got some bad links that are classic problems with the pre-1.03.4.7-3 patch version. If you've got the latest patch 1.03.4.7-4, then you shouldnt get these type of links coming back. You should be able to right-click on anything that does not have a "VERIFIED" in both controller and responder status or has a NOT FOUND as the ID and do a "Delete from PH". This should clear up the problem for you. Worst case scenario, open the "Insteon DM Control" and select "Clear PowerHome Insteon Groups" and then right-click and select "Scan All Device Database" to rediscover your links.
Next problem...concerning your triggers. Ive played with this and it seems to have something to do with X10 from the CM11A being put on the line so quickly after the Insteon traffic and it's getting lost. The CM11A is unaware of Insteon traffic and so while it listens for the line to be clear, it seems to actually send when Insteon traffic is on the line from the PLC (presumably ACK command to the received group in) and it's getting squashed. The delay is basically allowing the Insteon traffic to clear and then the X10 can be sent. If you were using the PLC to send the X10, then this would probably not happen as the PLC would "know" when it was safe to send the X10. Long story short, I think you'll need to keep the delay in this type of situation.
The ramprate problem. I see in the groups screen that several of your ramprates are set to 20 and not 31. Depending upon how you're turning the lights on from within PowerHome, I can see the 10 second problem. Also...after a bit of research I might have found the problem and it would appear to be a SmartHome firmware bug. What several other people have reported is that after sending a "slow" group command to a switch, until the switch is actually physically switched on/off using the paddle, "direct" Insteon commands will now use the "last" group ramprate. So if PowerHome turns one of your lamps on/off with the slow group ramprate (20), then even if you use the Device Status screen to turn a light on/off or ph_insteon command, then the switch will use that last ramprate instead of the "local" ramprate. If you physically switch the lights paddle (presumably with a fast ramprate), then future direct commands will use this ramprate. Maybe this is by design but isnt what everyone is expecting (or what we were told). The direct commands do not have a way to specify ramprate and we were told that it would use the local ramprate unless the command was a "faston/fastoff" command. It would appear though that the direct "on/off" commands will use whatever was the last ramprate that last controlled the light.
Hope this helps,
Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: April 20 2006 at 07:29 | IP Logged
|
|
|
Cool. Thanks Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: August 26 2006 at 12:04 | IP Logged
|
|
|
The trigger issue has cropped up again. I can see the traffic...
Code:
| Incoming Insteon received on Insteon DM controller INSTEON-1. From Address:[01.7A.9F] To Address:[00.D4.2C] Flags:[67] Cmd1:[19] Cmd2:[1]. Decode: Group Cleanup. From: BATHROOM LIGHT To: POWERLINC1 Group: 1, Off |
|
|
But the trigger (SQL below) does not fire.
Code:
| insert into triggers values ('BATHRM LIGHT OFF','BATH LIGHT OFF','ph_delay(500)+ph_macro("BATH AMP OFF")',16,'BATHROOM LIGHT',0,19,'1',1,0,2); |
|
|
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: August 29 2006 at 22:31 | IP Logged
|
|
|
Tony,
The Insteon traffic you posted above is for a Group Cleanup command which does not fire triggers. Is there not a previous Group Broadcast command from the BATHROOM LIGHT? If not, then the SDM and consequently PowerHome somehow missed the command which would have fired the trigger.
I can see this happening once in a blue moon but if it is consistently missing the Group Broadcast command then most likely the POWERLINC1 does not have the BATHROOM LIGHT address in it's database (which would be the case if the BATHROOM LIGHT was added manually rather than auto-discovered). You'll need to open the Insteon DM Control window and "Clear PLC Database" followed by "Add ID's to PLC".
Let me know,
Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: August 30 2006 at 00:26 | IP Logged
|
|
|
Thanks Dave. I've cleared and added...
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome Bug Reports
Topic: Two Insteon Issues
