| Author |
|
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: January 29 2014 at 22:36 | IP Logged
|
|
|
Things did not progress well today. Because the motion
sensor is I2CS there are additional messages flowing from
the device when motion is sensed. This delays the sending
of subsequent messages to the point where the motion
sensor has gone back to sleep. Looking into how HL
handles this to see if I can pattern the macro the same
way.
__________________
Lee G
|
| Back to Top |
|
| |
smarty
Super User
Joined: May 21 2006
Location: United States
Online Status: Offline
Posts: 728
|
| Posted: January 30 2014 at 09:08 | IP Logged
|
|
|
Wishing you the best of luck.
Hoping that these MS's will also serve as light/dark indicators as well (useful information for other decision points).
__________________
Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
| Back to Top |
|
| |
smarty
Super User
Joined: May 21 2006
Location: United States
Online Status: Offline
Posts: 728
|
| Posted: February 19 2014 at 13:29 | IP Logged
|
|
|
Dave,
Will the next release of PH be able to handle the twist with these Insteon motion Sensors?
Lee,
Any new news? Is their anyway I could possibly assist?
__________________
Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: February 19 2014 at 16:27 | IP Logged
|
|
|
The change is simple in concept, the current macro uses a
Standard message cmd1=32 cmd2=24 to stop the device from
going to sleep. It uses a Standard message cmd1=32
cmd2=25 to allow the device to sleep after the update is
done. An I2CS motion sensor requires an Extended
message issuing the same commands. The easiest change is
to make a new macro for I2CS motion sensors that uses
Extended messages. The problem is an I2CS device sends
additional messages when motion is sensed which delays
the arrival of the 32/24 command long enough to prevent
the device from sleeping. Have not found the right
combination of wait or whatever to allow the command to
reach the device before it sleeps.
The final solution would be to query the device and
determine if it is an I2CS device and either use the
Standard message or Extended message.
I have not had much time to play with this lately and it
will be weeks or more before I can spend more time on
this, if there is a way of doing it at 2.1.4.
After 52 years of good coverage my past employer
cancelled all forms of medical coverage for some 100,000
retires (thanks Obamacare). Coverage for meds, vision,
dental, supplemental all gone. Has taken months to
establish new coverage with more work needed. Wish I
had more time to work on this but it is not possible at
present.
Edited by grif091 - February 19 2014 at 16:29
__________________
Lee G
|
| Back to Top |
|
| |
smarty
Super User
Joined: May 21 2006
Location: United States
Online Status: Offline
Posts: 728
|
| Posted: February 21 2014 at 15:11 | IP Logged
|
|
|
Thanks Lee.
If it matters, I surely didn't vote for B.O.
Hang in there....
__________________
Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome Hardware
Topic: Motion Sensor - SetUp Issues
