HomeGenie Forum
Development => Feature request => Topic started by: gustavo on September 16, 2015, 01:23:49 AM
-
I was able to get my minimote associated with HG eventually, but I believe that the way it's being recognized is problematic. As a basic sensor, when I press a button the status is "1.0" or "2.0" or "3.0" etc depending on the button press.
This makes sense for senors, the device is updating its state. But for remotes, I believe the logic is wrong. After the state switches to "1.0" it should automatically switch back to "0.0". The way, a button press can be followed by the same button press to trigger logic.
Otherwise, if I have code that says "If the state changes to 1.0 do X" - works the first time I press the button, but not the second time. E.g. say I have button 1 setup to turn on all of the lights in the house. Eventually the lights get turned off through various means and I want to turn them all on again. If I press the 1 button again, it does nothing, because the state of the sensor did not change. If the state change is to "1.0" followed by "0.0" immediately after, then I can have logic based on button repeats, and overall use the remote in a much cleaner way.
-
Try the attacched program. It will add a new feature "Level Autoreset" to sensor type modules in Z-Wave domain. Once the program is activated you can configure the autoreset delay in milliseconds from the module options dialog.
g.
EDIT: updated hgx file with few optimizations
-
I just got my own minimote and got it working, and added this program. I get the autoreset option, but it's not resetting. Is there something I might have configured wrong?
Try the attacched program. It will add a new feature "Level Autoreset" to sensor type modules in Z-Wave domain. Once the program is activated you can configure the autoreset delay in milliseconds from the module options dialog.
g.
EDIT: updated hgx file with few optimizations