I have a Z-wave network with 133 devices on it including four Schlage door locks. In an effort to keep network traffic as low as possible, I have created dedicated events for locking and unlock doors instead of just setting the lock devices directly from within an event.
In looking at my logs, it appears that even though I *think* I'm testing for whether a lock is already locked, unlocked, or Unknown before sending a lock or unlock command, the logs show that it is sending the command even though it *should* fail the logic tests and not send the command.
I've tried executing the lock/unlock events directly from the run button as well as having it called from another event and the result is the same; the command is still being sent.
I've attached a screen shot of one of the events so you can see how I have it set up.
Thanks for any input,
Paul
In looking at my logs, it appears that even though I *think* I'm testing for whether a lock is already locked, unlocked, or Unknown before sending a lock or unlock command, the logs show that it is sending the command even though it *should* fail the logic tests and not send the command.
I've tried executing the lock/unlock events directly from the run button as well as having it called from another event and the result is the same; the command is still being sent.
I've attached a screen shot of one of the events so you can see how I have it set up.
Thanks for any input,
Paul
Comment