Teken Posted November 1, 2011 Posted November 1, 2011 I am not sure if this question has been posed before by the forum members here at UDI. Will the ISY in the future have the ability to communicate with the motion sensor and update its programming as it is done with the HL2 software? Currently, the HL2 software allows the user the ability to simply walk over to the motion sensor, awaken it. Then, this allows the motion sensor to be updated with out the need to remove it from its installed place and press the set button. In the very near future I will be installing several motion sensors above the 20 feet range. I am not looking forward to climbing up a ladder in sub zero temps, in the dark, to simply hit a idiot button. I hope this feature will be incorporated into the next firmware release in the not too distant future. Teken . . .
oberkc Posted November 2, 2011 Posted November 2, 2011 my understanding is that battery-operated motion sensors do not listen for communication...they are one-way transmitters. This is to ensure longest battery life. Given this, I don't believe that there is anything a device such as the ISY can do to accomplish your goals. Pending a change in the design of the motion sensor, it will always be necessary to press the set button to perform linking and programming.
Teken Posted November 2, 2011 Author Posted November 2, 2011 my understanding is that battery-operated motion sensors do not listen for communication...they are one-way transmitters. This is to ensure longest battery life. Given this, I don't believe that there is anything a device such as the ISY can do to accomplish your goals. Pending a change in the design of the motion sensor, it will always be necessary to press the set button to perform linking and programming. Currently, the Houselinc 2 software does allow this feature to be invoked and update the said motion sensor. As an aside, this same feature was removed in another release, but then restored in the last iteration of the HL2 software. Because, it was resoundingly stated this one feature was not only wanted, it was needed. I hope in the future, what ever limitations that is stopping this feature is considered for implementation with in the ISY platform.
LeeG Posted November 2, 2011 Posted November 2, 2011 They pulled it from HL2 because the implementation was poor. They fixed the design and put the feature back. It is built around the fact that the Motion Sensor stays awake for a very short time after sending an On message. It allows an application to send a command to the Motion Sensor that prevents it from going to sleep. Pending updates are sent to the Motion Sensor and when complete another command is sent to allow the Motion Sensor to go to sleep normally. It is a fantastic feature. Motion Sensors are often mounted where access is difficult. Queuing updates and sending them after a Motion On is detected would be a great enhancement to the ISY.
Teken Posted November 2, 2011 Author Posted November 2, 2011 They pulled it from HL2 because the implementation was poor. They fixed the design and put the feature back. It is built around the fact that the Motion Sensor stays awake for a very short time after sending an On message. It allows an application to send a command to the Motion Sensor that prevents it from going to sleep. Pending updates are sent to the Motion Sensor and when complete another command is sent to allow the Motion Sensor to go to sleep normally. It is a fantastic feature. Motion Sensors are often mounted where access is difficult. Queuing updates and sending them after a Motion On is detected would be a great enhancement to the ISY. Absolutely !! This winter will be very long, cold, and dark. I would rather not be outside in the garage, yard, etc if at all possible when the *magic* time of doing a update / configuration change is required.
Recommended Posts