Author |
|
cmhardwick Senior Member
Joined: July 08 2006 Location: United States
Online Status: Offline Posts: 290
|
Posted: August 14 2007 at 16:30 | IP Logged
|
|
|
when this finds a switch on that was off previously (such as local load trigger on lamplinc possibly) will it update the status in PH AND trip the devicechange trigger? I'm assuming it's polling to actually get the current status since that's what's implied by the name or is it just a device "ping" request?
__________________ Cicero, Enjoying automation!
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: August 14 2007 at 17:08 | IP Logged
|
|
|
Cicero,
Yes, any change detected through a background status request (or even a user initiated status request) will fire the Device Change trigger.
The background status poll is used twofold. 1. Like a ping to verify the device is still there but more importantly to acquire the database change flag (to determine if any link changes have been made locally or through other software) and 2. to retrieve the current actual status.
Dave.
|
Back to Top |
|
|
cmhardwick Senior Member
Joined: July 08 2006 Location: United States
Online Status: Offline Posts: 290
|
Posted: August 14 2007 at 19:46 | IP Logged
|
|
|
Great, finally a way to reflect status change in lamplinc modules done by local load switching (which my wife does and I KNOW better than to disable it! hehehe)
__________________ Cicero, Enjoying automation!
|
Back to Top |
|
|
cmhardwick Senior Member
Joined: July 08 2006 Location: United States
Online Status: Offline Posts: 290
|
Posted: August 14 2007 at 20:08 | IP Logged
|
|
|
well so much for that theory. The stupid lamplinc still thinks it's off if it's turned on by the local load sensing (turn the lamp off then on, lamp then turns on)
__________________ Cicero, Enjoying automation!
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: August 17 2007 at 17:01 | IP Logged
|
|
|
I have about 9 devices. When I do the "load power on" it takes my screen, to recognize the change, about 2 minutes. That is with a polling scan set to 5 seconds. I also have the device linked to the PLC.
HTH
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
cmhardwick Senior Member
Joined: July 08 2006 Location: United States
Online Status: Offline Posts: 290
|
Posted: August 17 2007 at 22:34 | IP Logged
|
|
|
I'll try again when I get back from my trip. I've got all my devices linked to my PLC and polling on. I actually watched it poll the device, something tripped my status change trigger, but it didn't update. When I did a direct query of the device level (not database, real time query) it came back as still off.
What version are you on Pete? I'm still on 10. Maybe something in 11? I haven't upgraded because before I could people were seeing odd behaviours, so I just chilled, waiting on the next one
__________________ Cicero, Enjoying automation!
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: August 17 2007 at 23:09 | IP Logged
|
|
|
I'm on R11. Tomorrow I'll test the device itself and let you know.. And yes there might be problems with R11. Dave is looking into one as we speak.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: August 18 2007 at 07:32 | IP Logged
|
|
|
This morning when I tested the status change it took only 30 seconds and the status using ph_getinsteonlevelrt confirmed the level it was at. ph_insteonstat returned 2. I think the response time of the change is due to the polling order. Good luck.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|