Talk About the Latest in Home Automation/Home Electronics
Home Automation Forum

Smarthome Forum
Login or Register
 
Home | Profile | Register | Active Topics | Search | FAQ | Smarthome
 All Forums
 General Discussion
 Computer Interfaces
 HouseLinc 2 - Slow Events
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

rberd
Starting Member

USA
14 Posts

Posted - 11/18/2010 :  10:07:45 PM  Show Profile  Reply with Quote
Wondering if someone might be able to give me some insight on this…

I'm running into a problem with a series of events I have set up in HouseLinc 2. These events evaluate the status of my closet light when I open/close the door and respond accordingly by either turning the light off, on or not doing anything. The problem I'm running into is that there is a great delay between opening/closing the door and the light responding accordingly. I'm wondering if this might have something to do with the time it takes to send/receive signals and software/hardware limitations.

Here is what I am using:
• HouseLinc 2 bundled with PowerLinc USB Modem (Dual-Band) 2413UH
• TriggerLinc
• KeypadLinc Dimmer 6-Button (Older Version - 3 Years)
• Various Access Points and Other Devices

The Setup:
I have two events programmed in order to get this to work the way I want.

• Closet On
Trigger: TriggerLinc - Opened
Condition: KeypadLinc Dimmer - Turned Off
Action: KeypadLinc Dimmer - Set Level to 90%

• Closet Off
Trigger: TriggerLinc - Closed
Condition: KeypadLinc Dimmer - On Level is equal to 90%
Action: KeypadLinc Dimmer - Turn Off

The closet light is actually a track lighting fixture mounted on the outside of the closet, which also lights part of the main room. I set up these events because I was tired of the light turning off if it was already on previously… hence the 90% level condition/action.

If there is a better way to do this that yield speedier response time please let me know! Any help would be greatly appreciated!

Ryan

rberd
Starting Member

USA
14 Posts

Posted - 12/02/2010 :  9:46:24 PM  Show Profile  Reply with Quote
Anyone have any thoughts whatsoever on this?
Go to Top of Page

stusviews
Moderator

USA
11449 Posts

Posted - 12/02/2010 :  10:27:11 PM  Show Profile  Visit stusviews's Homepage  Reply with Quote
What do you mean by "a great delay." Some delay is expected. The least is with a direct connection (e.g., mechanical switch). There is, even then, a delay of approximately 186,000 mi/sec (300,000 km/sec). Of course, unless we're experiencing astronomical distances, the delay is indiscernible by a human eye

Within an Insteon context, the next shortest delay is a link on the same leg of the electric supply, followed by, in no particular order, a link to the other leg with a direct-wired or RF coupling device. These delays are sometimes barely noticeable (device set instant response).

And then there are actions that depend on circuitry such as a powerline interface with yet another device (e.g., programs, events, etc.) in which case some delay is inherent depending on the speed of all these devices.

So, is the delay more or less than, say, a second or two. I'm not saying any delay is OK, just that some can be expected and some indicate a problem.

Stu's Views is Education and Fun. What do YOU want to VIEW today?
MathLandia High school mathematics learning fun.
Both Stu's Views and MathLandia are free websites that do not sell anything.
Saving energy is not always free. Be a world saver.
Go to Top of Page

Tfitzpatri8
Administrator

USA
8595 Posts

Posted - 12/03/2010 :  08:27:07 AM  Show Profile  Reply with Quote
Are you getting an extended flickering from your TriggerLinc when it activates, something indicating it might be having trouble getting messages through? Can you clear your event log, trigger the event, then copy & paste the log here so we can look for anything out of the ordinary?

Volunteer Moderator & Home Automation Enthusiast
Go to Top of Page

rberd
Starting Member

USA
14 Posts

Posted - 12/06/2010 :  7:44:56 PM  Show Profile  Reply with Quote
Thank you both stusviews & Tfitzpatri8 for your help with this, it is much appreciated!!! I've done several timed tests of the "door open" & "door close" events and it seems to take anywhere from about 2.5 to 5 seconds for the closet light respond accordingly. I will say that the delay times seems to vary in length on a random basis. I've included the output from the logs when triggered the "door open" event when openeing the closet door. Please let me know if I can provide anything else useful.

Time Level Message
12/6/2010 7:29:36 PM DEBUG Low priority tasks, pause released. There are 0 pause requests pending.
12/6/2010 7:29:36 PM INFO >>>>>>>>>>>>>>>>>>>> Finished updating device status for TriggerLinc 13.E4.4A
12/6/2010 7:29:36 PM DEBUG Firing RF device 13.E4.4A StatusChanged event ...
12/6/2010 7:29:36 PM NOTICE TriggerLinc Status update: TriggerLinc sent "On" message at 7:29:27 PM 12/6/2010
12/6/2010 7:29:36 PM DEBUG Pinging 13.E4.4A try 1 of 1 succeeded
12/6/2010 7:29:36 PM DEBUG Rx: Std Ack, From: 13.E4.4A, To: 13.21.F5, Flag: 23 (Hops: 0/3), C1: 0F, C2: 00
12/6/2010 7:29:36 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:36 PM TRACE All the data was not available.
12/6/2010 7:29:36 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:36 PM DEBUG Rx: PLM Ack, 02 62 13 E4 4A 0F 0F 00 06
12/6/2010 7:29:36 PM DEBUG Tx: Std Msg, To: 13.E4.4A, Flag: 0F (Hops: 3/3), C1: 0F (Ping), C2: 00
12/6/2010 7:29:35 PM DEBUG Waiting for 1000 before sending next message
12/6/2010 7:29:35 PM DEBUG Pinging 13.E4.4A try 1 of 1 ...
12/6/2010 7:29:35 PM TRACE Task Synchronizing properties for TriggerLinc 13.E4.4A is at 0% with status Finished syncrhonizing properties for 13.E4.4A
12/6/2010 7:29:35 PM INFO >>>>>>>>>>>>>>>>>>>> Finished synchronizing properties for TriggerLinc 13.E4.4A
12/6/2010 7:29:35 PM INFO <<<<<<<<<<<<<<<<<<<< Start synchronizing properties for TriggerLinc 13.E4.4A
12/6/2010 7:29:35 PM TRACE Task Synchronizing properties for TriggerLinc 13.E4.4A is at 0% with status Syncrhonizing properties for 13.E4.4A ...
12/6/2010 7:29:35 PM INFO >>>>>>>>>>>>>>>>>>>> Finished synchronizing database for TriggerLinc 13.E4.4A - Succeeded.
12/6/2010 7:29:35 PM TRACE Task Synchronizing database for TriggerLinc 13.E4.4A is at 100% with status Database synchronizing succeeded.
12/6/2010 7:29:35 PM TRACE Skipping refresh of database for 13.E4.4A, because it hasn't changed
12/6/2010 7:29:35 PM DEBUG Device DB Delta = 25, HL DB Delta = 25.
12/6/2010 7:29:35 PM INFO ,Triple matching for database delta succeeded: delta = 25
12/6/2010 7:29:35 PM DEBUG Rx: Std Ack, From: 13.E4.4A, To: 13.21.F5, Flag: 23 (Hops: 0/3), C1: 19, C2: 00
12/6/2010 7:29:35 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:34 PM DEBUG Rx: PLM Ack, 02 62 13 E4 4A 0F 19 00 06
12/6/2010 7:29:34 PM DEBUG Tx: Std Msg, To: 13.E4.4A, Flag: 0F (Hops: 3/3), C1: 19 (Light Status Request), C2: 00
12/6/2010 7:29:33 PM DEBUG Waiting for 1000 before sending next message
12/6/2010 7:29:33 PM DEBUG Rx: Std Ack, From: 13.E4.4A, To: 13.21.F5, Flag: 23 (Hops: 0/3), C1: 19, C2: 00
12/6/2010 7:29:33 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:33 PM DEBUG Rx: PLM Ack, 02 62 13 E4 4A 0F 19 00 06
12/6/2010 7:29:33 PM DEBUG Tx: Std Msg, To: 13.E4.4A, Flag: 0F (Hops: 3/3), C1: 19 (Light Status Request), C2: 00
12/6/2010 7:29:32 PM DEBUG Rx: Ext Msg, From: 0A.AF.3C, To: 13.21.F5, Flag: 10 (Hops: 0/0), C1: 8F (Unknown Ext Command), C2: A9, Data: FE 80 00 00 00 00 00 00 00 00 00 00 00 00
12/6/2010 7:29:32 PM TRACE Found event: InsteonExtendedMessage
12/6/2010 7:29:32 PM TRACE All the data was not available.
12/6/2010 7:29:32 PM TRACE Found event: InsteonExtendedMessage
12/6/2010 7:29:32 PM DEBUG Waiting for 1000 before sending next message
12/6/2010 7:29:32 PM INFO Closet On: KeypadLinc Dimmer
ON / OFF - Set level to: 90% Success
12/6/2010 7:29:32 PM INFO Successfully sent Set level to: 90% command to ON / OFF.
12/6/2010 7:29:32 PM DEBUG Rx: Std Ack, From: 0A.AF.3C, To: 13.21.F5, Flag: 23 (Hops: 0/3), C1: 11, C2: E5
12/6/2010 7:29:32 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:32 PM DEBUG Rx: PLM Ack, 02 62 0A AF 3C 0F 11 E5 06
12/6/2010 7:29:32 PM DEBUG Tx: Std Msg, To: 0A.AF.3C, Flag: 0F (Hops: 3/3), C1: 11 (Light ON), C2: E5
12/6/2010 7:29:31 PM DEBUG Waiting for 985 before sending next message
12/6/2010 7:29:31 PM DEBUG Rx: Std Ack, From: 13.E4.4A, To: 13.21.F5, Flag: 23 (Hops: 0/3), C1: 19, C2: 00
12/6/2010 7:29:31 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:31 PM TRACE All the data was not available.
12/6/2010 7:29:31 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:30 PM DEBUG Rx: PLM Ack, 02 62 13 E4 4A 0F 19 00 06
12/6/2010 7:29:30 PM DEBUG Tx: Std Msg, To: 13.E4.4A, Flag: 0F (Hops: 3/3), C1: 19 (Light Status Request), C2: 00
12/6/2010 7:29:29 PM DEBUG Rx: Std Ack, From: 0A.AF.3C, To: 13.21.F5, Flag: 23 (Hops: 0/3), C1: 23, C2: 00
12/6/2010 7:29:29 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:29 PM DEBUG KeypadLinc 0A.AF.3C 90%
12/6/2010 7:29:29 PM INFO Closet On: KeypadLinc Dimmer
ON / OFF - Set level to: 90%
12/6/2010 7:29:29 PM DEBUG Waiting for 1000 before sending next message
12/6/2010 7:29:29 PM INFO Closet On: All conditions were evaluated and are true.
12/6/2010 7:29:29 PM DEBUG Closet On: Condition On Level is equal to Off was evaluated to true.
12/6/2010 7:29:29 PM DEBUG Rx: Std Ack, From: 0A.AF.3C, To: 13.21.F5, Flag: 23 (Hops: 0/3), C1: 23, C2: 00
12/6/2010 7:29:29 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:29 PM DEBUG Rx: PLM Ack, 02 62 0A AF 3C 0F 19 00 06
12/6/2010 7:29:29 PM DEBUG Tx: Std Msg, To: 0A.AF.3C, Flag: 0F (Hops: 3/3), C1: 19 (Light Status Request), C2: 00
12/6/2010 7:29:28 PM DEBUG Waiting for 1000 before sending next message
12/6/2010 7:29:28 PM TRACE Task Synchronizing database for TriggerLinc 13.E4.4A is at 0% with status Database synchronizing in progress...
12/6/2010 7:29:28 PM DEBUG Pinging 13.E4.4A try 1 of 2 succeeded
12/6/2010 7:29:28 PM DEBUG Rx: Std Ack, From: 13.E4.4A, To: 13.21.F5, Flag: 23 (Hops: 0/3), C1: 0F, C2: 00
12/6/2010 7:29:28 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:27 PM DEBUG Rx: PLM Ack, 02 62 13 E4 4A 0F 0F 00 06
12/6/2010 7:29:27 PM DEBUG Tx: Std Msg, To: 13.E4.4A, Flag: 0F (Hops: 3/3), C1: 0F (Ping), C2: 00
12/6/2010 7:29:27 PM DEBUG Rx: Std Msg, From: 13.E4.4A, To: 13.21.F5, Flag: 41 (Hops: 0/1), C1: 11 (Light ON), C2: 01
12/6/2010 7:29:27 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:27 PM TRACE All the data was not available.
12/6/2010 7:29:27 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:27 PM DEBUG Re-sending message.2, try 1 of 1, wait 300ms
12/6/2010 7:29:27 PM DEBUG Rx: Std Msg, From: 13.E4.4A, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 01
12/6/2010 7:29:27 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:27 PM DEBUG Rx: PLM Nak, 15
12/6/2010 7:29:27 PM DEBUG Tx: Std Msg, To: 13.E4.4A, Flag: 0F (Hops: 3/3), C1: 0F (Ping), C2: 00
12/6/2010 7:29:27 PM DEBUG Pinging 13.E4.4A try 1 of 2 ...
12/6/2010 7:29:27 PM INFO <<<<<<<<<<<<<<<<<<<< Start synchronizing database for TriggerLinc 13.E4.4A
12/6/2010 7:29:27 PM DEBUG Low priority tasks, pause requested
12/6/2010 7:29:27 PM DEBUG Firing device 13.E4.4A StatusChanged event ...
12/6/2010 7:29:27 PM DEBUG Queue In Updating status for TriggerLinc 13.E4.4A
12/6/2010 7:29:27 PM INFO <<<<<<<<<<<<<<<<<<<< Start updating device status for TriggerLinc 13.E4.4A
12/6/2010 7:29:27 PM DEBUG Queue In Synchronizing properties for TriggerLinc 13.E4.4A
12/6/2010 7:29:27 PM DEBUG Queue In Synchronizing database for TriggerLinc 13.E4.4A
12/6/2010 7:29:27 PM INFO Closet On: Trigger TriggerLinc Opened fired
12/6/2010 7:29:27 PM DEBUG Firing TriggerLinc 13.E4.4A Open event ...
12/6/2010 7:29:27 PM DEBUG Rx: Std Msg, From: 13.E4.4A, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 01
12/6/2010 7:29:27 PM TRACE Found event: InsteonStandardMessage
12/6/2010 7:29:27 PM TRACE All the data was not available.
12/6/2010 7:29:27 PM TRACE Found event: InsteonStandardMessage
Go to Top of Page

LeeG
Advanced Member

USA
2253 Posts

Posted - 12/07/2010 :  3:46:04 PM  Show Profile  Reply with Quote
For some reason HouseLinc2 thinks it needs to sync the TriggerLinc link database and properties. That activity should not happen on a routine basis. If you see the following messages every time the TriggerLinc fires there is a problem somewhere. Did you request a device sync or do something with the TriggerLinc options.

12/6/2010 7:29:27 PM INFO <<<<<<<<<<<<<<<<<<<< Start synchronizing database for TriggerLinc 13.E4.4A
12/6/2010 7:29:35 PM TRACE Skipping refresh of database for 13.E4.4A, because it hasn't changed
12/6/2010 7:29:35 PM DEBUG Device DB Delta = 25, HL DB Delta = 25.
12/6/2010 7:29:35 PM TRACE Task Synchronizing database for TriggerLinc 13.E4.4A is at 100% with status Database synchronizing succeeded.
12/6/2010 7:29:35 PM TRACE Task Synchronizing properties for TriggerLinc 13.E4.4A is at 0% with status Finished syncrhonizing properties for 13.E4.4A
12/6/2010 7:29:35 PM INFO >>>>>>>>>>>>>>>>>>>> Finished synchronizing properties for TriggerLinc 13.E4.4A
12/6/2010 7:29:35 PM INFO <<<<<<<<<<<<<<<<<<<< Start synchronizing properties for TriggerLinc 13.E4.4A

Lee G
Go to Top of Page

Tfitzpatri8
Administrator

USA
8595 Posts

Posted - 12/07/2010 :  4:01:25 PM  Show Profile  Reply with Quote
I'm also curious about that 00.00.01 destination address. Did you switch PLMs at some point, or did you originally install HL2 on this computer with that unit?

Volunteer Moderator & Home Automation Enthusiast
Go to Top of Page

LeeG
Advanced Member

USA
2253 Posts

Posted - 12/07/2010 :  4:08:06 PM  Show Profile  Reply with Quote
Tom,

The To: 00.00.01 Flag: CB is Group 1 in a Group Broadcast message from the TriggerLinc.

Lee

Lee G
Go to Top of Page

rberd
Starting Member

USA
14 Posts

Posted - 12/07/2010 :  5:06:15 PM  Show Profile  Reply with Quote
Hello all,

Thanks again for the replies. I went ahead and triggered the event this time... didn't see the messages about synchronizing the database for the TriggerLinc again this time so it may have been a fluke thing. I've included the information from the logs again below.

Time Level Message
12/7/2010 4:56:06 PM INFO Closet On: KeypadLinc Dimmer
ON / OFF - Set level to: 90% Success
12/7/2010 4:56:06 PM INFO Successfully sent Set level to: 90% command to ON / OFF.
12/7/2010 4:56:06 PM DEBUG Rx: Std Ack, From: 0A.AF.3C, To: 13.21.F5, Flag: 27 (Hops: 1/3), C1: 11, C2: E5
12/7/2010 4:56:06 PM TRACE Found event: InsteonStandardMessage
12/7/2010 4:56:06 PM DEBUG Rx: PLM Ack, 02 62 0A AF 3C 0F 11 E5 06
12/7/2010 4:56:06 PM DEBUG Tx: Std Msg, To: 0A.AF.3C, Flag: 0F (Hops: 3/3), C1: 11 (Light ON), C2: E5
12/7/2010 4:56:05 PM DEBUG Waiting for 1000 before sending next message
12/7/2010 4:56:05 PM DEBUG KeypadLinc 0A.AF.3C 90%
12/7/2010 4:56:05 PM INFO Closet On: KeypadLinc Dimmer
ON / OFF - Set level to: 90%
12/7/2010 4:56:05 PM INFO Closet On: All conditions were evaluated and are true.
12/7/2010 4:56:05 PM DEBUG Closet On: Condition On Level is equal to Off was evaluated to true.
12/7/2010 4:56:05 PM DEBUG Rx: Std Ack, From: 0A.AF.3C, To: 13.21.F5, Flag: 27 (Hops: 1/3), C1: 23, C2: 00
12/7/2010 4:56:05 PM TRACE Found event: InsteonStandardMessage
12/7/2010 4:56:05 PM DEBUG Rx: PLM Ack, 02 62 0A AF 3C 0F 19 00 06
12/7/2010 4:56:05 PM DEBUG Tx: Std Msg, To: 0A.AF.3C, Flag: 0F (Hops: 3/3), C1: 19 (Light Status Request), C2: 00
12/7/2010 4:56:05 PM WARN Message expired From:0A.AF.3C, To:0A.AF.3C, Flag:0F, C1:19, C2:00
12/7/2010 4:56:03 PM DEBUG Rx: Std Msg, From: 13.E4.4A, To: 13.21.F5, Flag: 42 (Hops: 0/2), C1: 11 (Light ON), C2: 01
12/7/2010 4:56:03 PM TRACE Found event: InsteonStandardMessage
12/7/2010 4:56:03 PM TRACE All the data was not available.
12/7/2010 4:56:03 PM TRACE Found event: InsteonStandardMessage
12/7/2010 4:56:03 PM DEBUG Rx: PLM Ack, 02 62 0A AF 3C 0F 19 00 06
12/7/2010 4:56:03 PM DEBUG Tx: Std Msg, To: 0A.AF.3C, Flag: 0F (Hops: 3/3), C1: 19 (Light Status Request), C2: 00
12/7/2010 4:56:03 PM DEBUG Rx: Std Msg, From: 13.E4.4A, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 01
12/7/2010 4:56:03 PM TRACE Found event: InsteonStandardMessage
12/7/2010 4:56:03 PM TRACE All the data was not available.
12/7/2010 4:56:03 PM TRACE Found event: InsteonStandardMessage
12/7/2010 4:56:02 PM DEBUG Re-sending message.2, try 1 of 1, wait 300ms
12/7/2010 4:56:02 PM DEBUG Rx: PLM Nak, 15
12/7/2010 4:56:02 PM DEBUG Tx: Std Msg, To: 0A.AF.3C, Flag: 0F (Hops: 3/3), C1: 19 (Light Status Request), C2: 00
12/7/2010 4:56:02 PM INFO Closet On: Trigger TriggerLinc Opened fired
12/7/2010 4:56:02 PM DEBUG Firing TriggerLinc 13.E4.4A Open event ...
12/7/2010 4:56:02 PM DEBUG Rx: Std Msg, From: 13.E4.4A, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 01
12/7/2010 4:56:02 PM TRACE Found event: InsteonStandardMessage
12/7/2010 4:56:02 PM TRACE All the data was not available.
12/7/2010 4:56:02 PM TRACE Found event: InsteonStandardMessage

Tfitzpatri8, I wanted to mention that I was using the PLM & HL2 for a while on an initial computer... but it crashed so I moved everything over to a new computer. I was not able to transfer any of the HL2 data that I set up, I had to basically start from scratch. Not sure if this matters or not.
Go to Top of Page

LeeG
Advanced Member

USA
2253 Posts

Posted - 12/07/2010 :  6:46:51 PM  Show Profile  Reply with Quote
The Condition to verify the KeypadLinc is Off causes HouseLinc2 to actually Query the KeypadLinc for its current status. The initial Query is getting lost due to the traffic that continues to flow from the TriggerLinc (normal). Only after the Query request has timed out, which takes a few seconds, does HouseLinc2 issue the Query again which works. Once it has been determined in real time that the KeypadLinc is really Off are the Conditions known to be True and HouseLinc2 issues the ON to 90%.

Some Home Automation packages keep track of device status by tracking commands from the device in real time. This would permit an in memory check of the KeypadLinc level rather than having to Query the device at the time of the TriggerLinc On. With HouseLinc2 issuing a Query command immediately while TriggerLinc traffic is still in progress the real time Query will fail on occasion. Even if the Query would work the first time there will always be some latency associated with issuing that command before the On to 90% is issued.

There is a timing option in HouseLinc2 that allows you to effectively slow down command processing. This may delay issuing the Query long enough to always work. However, there will always be some latency associated with the Query command itself.

If the TriggerLinc will always turn on the KeypadLinc before the KeypadLinc button can be pressed you could drop the Condition part of the On Event. The Off Event would continue to be longer so the KeypadLinc level can be Queried but the timing of the Off Event is not so important. Only if the KeypadLinc is at 90% when the TriggerLinc sends an Off would the KeypadLinc be turned Off by the Off Event. If the KeypadLinc had been overridden by a manual On to 100% the KeypadLinc would remain On. This only works if the TriggerLinc On Event is guaranteed to happen before someone could reach the KeypadLinc button to turn it On manually.

Lee G
Go to Top of Page

rberd
Starting Member

USA
14 Posts

Posted - 12/09/2010 :  7:04:07 PM  Show Profile  Reply with Quote
Hello LeeG,

Thanks for your input! I went ahead and dropped the condition on the on event like you had suggested... which seems to help eliminate most of the delay. With that being said though, this defeats the point of what I was trying to do originally. The reason I came up the the conditional events is that occasionally I will already have the closet light on, and after opening then closing the door I want the light to remain on if it was already on initially (via the KeypadLinc). So to get what I want it looks like there may be no way around the delay, unless you suggest I try to adjust the timing option? I have no idea where this is or how to adjust it in HouseLinc2. Can you give me any tips on this?

Also, several years ago I used ActiveHome Pro with X10 products. From what I can remember ActiveHome Pro kept device status in memory which made working with conditional macros easier/faster (as you were talking about). Is there any other software that does this that is compatible with Insteon devices/PLM? Would the Universal Devices ISY be better at this?

As always thanks for your help!
Go to Top of Page

stusviews
Moderator

USA
11449 Posts

Posted - 12/09/2010 :  8:13:23 PM  Show Profile  Visit stusviews's Homepage  Reply with Quote
A direct link is fastest, but that eliminates conditions. The ISY is, IMO, the next fastest.

Stu's Views is Education and Fun. What do YOU want to VIEW today?
MathLandia High school mathematics learning fun.
Both Stu's Views and MathLandia are free websites that do not sell anything.
Saving energy is not always free. Be a world saver.
Go to Top of Page

LeeG
Advanced Member

USA
2253 Posts

Posted - 12/09/2010 :  10:56:34 PM  Show Profile  Reply with Quote
Under Tools | Options | System there is a Delay after ACK field. You can try increasing this value but it will slow everything down (maybe not perceptively). Not sure you can find a value that will help.

I use a similar setup with a motion sensor setting the bathroom light on to 80% and then if I want to override press the KPL ON button to turn On to Full Bright. The logic on the Motion Sensor Off side checks the current Bright level for 80% and turns Off the bathroom light. If not at 80% the Motion Sensor Off is ignored. This is being done with a SimpleHomeNet EZSrve device which is a stand alone controller. The EZSrve keeps track of the current device Bright level so a Query is not necessary. There is a slight delay in turning on the bathroom light by the Motion Sensor because it is going through an EZSrve Action triggered by the Motion Sensor On. As Stu said the fastest way is a direct link but I needed the EZSrve to be aware of the Motion Sensor activity. About a .5 second delay compared to a direct link. I plan to move this logic to an ISY device which is also a stand alone controller and also keeps track of device Bright levels in memory.

Lee G
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
Smarthome Forum © 2000-2014 SmartLabs, Inc Go To Top Of Page
Powered By: Snitz Forums 2000 Version 3.4.07