Has anyone seen their sensors disarming by themselves?
I have it happening to my HRDS1 door sensor - not sure when it happens, but after awhile of being armed, I often find it in “Bypass” mode…
Im having same problem.
Yes now that you mention it.
I think I saw that happen when the device reset after it Tripped.
I would think this is a bad Idea.
I’ll do a test. Stand by.
I ran it overnight and it is working fine.
I think I saw the problem before. I bet it was because the device was not configured. Make sure you get it a green cog , look at the log and see if all the polls and configs are successful.
Of course, all my devices are configured and green… Are you saying you saw it once when your sensor was not configured?
I saw it 2 times, but it’s intermittent and hard to reproduce. Now that you mentioned it, I believe in at least one of those instances I found it disarmed right after it was tripped…
I found it diarmed after I upgraded to the new firmware
I can’t get any of my ZIR000 sensors to configure after the latest firmware upgrade. Two of the sensors keep toggling back and for between Zensys and ACT as the Manufacturer. The 3rd has always stayed as ACT. I think ACT is correct since it will list the version and model. For the 2 being detected as Zensys, there is info.
I have also noticed that the 2 detected as Zensys when armed will disarm about every 5 minutes. I think that corresponds to the 300 seconds default wakeup interval. The one that shows ACT as the model will stay armed until disarmed.
I have also experimented with the “automatically configure” option and if I set to No, then the sensor doesn’t seem to disarm itself.
pjgolian, here’s a recommendation… Go to advanced, logs, and turn on ‘verbose logging’ and also ‘lock log levels’ and ‘archive old logs on findvera’. If you don’t check ‘lock log levels’, verbose logging is automatically turned off after a couple hours because it really bogs the system and creates a flood of network traffic. So be sure to uncheck ‘lock log levels’ in a couple days when this problem is resolved.
Now, set everything back to auto-configure, and be sure everything is configured. Note the date/time by clicking the Location button.
When you next see that the sensor was disarmed automatically, go to advanced, tech support, and submit a trouble ticket, and include in the description the date/time you noted earlier. This way we know that the sensor disarming occurred between that date and the time of the trouble ticket, and you will have verbose logs that have been archived on our server, which we can go through and find the exact time the sensor was disarmed and why.
I still can’t configure the sensors (even after the latest upgrade). When I allow the “automatically configure” option, the device manufacturer changes from ACT to Zensys. I think that is the reason why it is failing to configure and disarming itself.
are you still trying the 300 second wake-up?
I tried that a few days ago and I had similar issues
Try waking those devices up and clicking confgure again with the Default setting
This is from my logs where is is trying to get info and/or configure the sensors. I’ve tried removing the battery and reinserting before configuring each sensor.
Log:
[size=6pt]
04/04/09 20:12:27.894 54 getnodedetails 23 09-04-04 20:12:27 09-04-04 20:12:27 09-04-04 20:12:27 0.538926000 0.524349000 Successful
04/04/09 20:12:28.469 55 version node 23 09-04-04 20:12:27 09-04-04 20:12:27 09-04-04 20:12:28 0.543088000 0.525705000 Successful Successfully got the response command 23 47 ZWaveBinarySensor
04/04/09 20:12:29.010 56 manufacturer node 23 09-04-04 20:12:28 09-04-04 20:12:28 09-04-04 20:12:29 0.523201000 0.506903000 Successful Successfully got the response command 23 47 ZWaveBinarySensor
04/04/09 20:13:05.026 57 wakeup cap get node 23 09-04-04 20:12:29 09-04-04 20:12:29 09-04-04 20:13:05 35.993312000 35.976734000 Aborted Waiting for node to reply after 2 retries 23 47 ZWaveBinarySensor
04/04/09 20:13:46.567 60 wakeup cap get node 23 09-04-04 20:13:05 09-04-04 20:13:05 09-04-04 20:13:46 41.495942000 41.479073000 Aborted Timed out waiting for the node to reply 23 47 ZWaveBinarySensor
04/04/09 20:13:46.969 63 wake int set node 23 09-04-04 20:13:46 09-04-04 20:13:46 09-04-04 20:13:46 0.379737000 0.314663000 Successful Transmit was ok 23 47 ZWaveBinarySensor
04/04/09 20:13:46.997 51 conf_jh#23 09-04-04 20:12:26 09-04-04 20:12:27 09-04-04 20:13:46 80.987602000 79.646653000 Aborted Failed at: Setting special configuration 23 47 ZWaveBinarySensor
04/04/09 20:13:47.525 64 getnodedetails 24 09-04-04 20:13:47 09-04-04 20:13:47 09-04-04 20:13:47 0.507404000 0.493611000 Successful
04/04/09 20:13:48.171 52 pollnode_wake #23node 23 1 cmds 09-04-04 20:12:26 09-04-04 20:13:47 09-04-04 20:13:48 82.151243000 0.526364000 Successful Successfully polled node 23 47 ZWaveBinarySensor
04/04/09 20:13:48.602 61 pollnode_wake #24node 24 1 cmds 09-04-04 20:13:18 09-04-04 20:13:48 09-04-04 20:13:48 29.896185000 0.413035000 Successful Successfully polled node 24 38 ZWaveBinarySensor
04/04/09 20:14:28.047 65 wakeup cap get node 24 09-04-04 20:13:47 09-04-04 20:13:48 09-04-04 20:14:28 40.434200000 39.379395000 Aborted Timed out waiting for the node to reply 24 38 ZWaveBinarySensor
04/04/09 20:14:28.497 66 wake int set node 24 09-04-04 20:14:28 09-04-04 20:14:28 09-04-04 20:14:28 0.402118000 0.367172000 Successful Transmit was ok 24 38 ZWaveBinarySensor
04/04/09 20:14:28.527 59 conf_jh#24 09-04-04 20:13:05 09-04-04 20:13:47 09-04-04 20:14:28 83.494241000 41.521826000 Aborted Failed at: Setting special configuration 24 38 ZWaveBinarySensor
04/04/09 20:14:38.811 67 getnodedetails 19 09-04-04 20:14:28 09-04-04 20:14:28 09-04-04 20:14:38 10.270297000 10.257129000 Failed
04/04/09 20:14:38.836 58 conf_jh#19 09-04-04 20:13:05 09-04-04 20:14:28 09-04-04 20:14:38 93.822140000 10.301466000 Aborted Unable to get any information on node 19 29 ZWaveBinarySensor
04/04/09 20:15:48.602 53 Wakeup done 23 09-04-04 20:12:26 09-04-04 20:14:38 09-04-04 20:15:48 202.577117000 69.758462000 Aborted Timed out waiting for the node to reply 23 47 ZWaveBinarySensor
[/size]
[quote=“zmistro, post:11, topic:164418”]are you still trying the 300 second wake-up?
I tried that a few days ago and I had similar issues[/quote]
Did you change the 300 second wake-up value? I already tried to wake-up the sensors by removing the batteries.
My sensors are disarming themselves also!
Another case of motion sensors disarming on their own.
Note: This is an install at a remote location, and no one is there. Sensors showed up as disarmed this morning, and no events tripped.
**All motion sensors are green-cogged and configured. No change in their config since April 14th.
I have locked log levels, etc. and re-armed everything. Will send if/when they disarm themselves again. Seems to be more than a few reports of this.
I am wondering if this is somehow related to the unsolved random light or two being on every few days as well?
** Doesn’t seem to be a way to trigger an event notification when an armed sensor becomes disarmed. That certainly would help troubleshooting, as this could be happening regularly - and the sensor then gets re-armed. user would never know.
.//A.
[quote=“micasaverde, post:9, topic:164418”]pjgolian, here’s a recommendation… Go to advanced, logs, and turn on ‘verbose logging’ and also ‘lock log levels’ and ‘archive old logs on findvera’. If you don’t check ‘lock log levels’, verbose logging is automatically turned off after a couple hours because it really bogs the system and creates a flood of network traffic. So be sure to uncheck ‘lock log levels’ in a couple days when this problem is resolved.
Now, set everything back to auto-configure, and be sure everything is configured. Note the date/time by clicking the Location button.
When you next see that the sensor was disarmed automatically, go to advanced, tech support, and submit a trouble ticket, and include in the description the date/time you noted earlier. This way we know that the sensor disarming occurred between that date and the time of the trouble ticket, and you will have verbose logs that have been archived on our server, which we can go through and find the exact time the sensor was disarmed and why.[/quote]
The HRMD1 Motion sensor from Hawking is also bypassing after I tell it to ARM.
Ok I have been playing with the sensor and finally have it working right.
- set a scene to activate when a sensor is tripped
- select the device you want turned on and how long.
- select the sensor bypass for the same amount of time then Arm.
Thanks for the help, I have my sensor working to turn on a light and the light will turn off for 5 min, but I notice that after 5 min the sensor will not re-arm right away. I just setup another scene with your suggestions and will try that and let you know. Thanks for the help!
Ive got my 3-in-1 sensor so that when it detects motion, it flips on a light
Its set to leave the light on for 5 min, then turn off, and rearm the sensor
No matter what, I cannot get the sensor to RE-ARM less than 1 hour
I noticed that the sensor once detects motion will trigger the light, and although the ARM button in vera is ON, the red light states that it’s not armed and ready
How can I get the Express Controls 3-in-1 sensor to rearm after 5 minutes, I don’t want to have to wait another hour for an event.
Here is my sensor SCENE I have set, Can someone help me try and get the 3-in-1 sensor to REARM after 5 min? It always takes at least 1 hour until it REARMS!
thanks