I got so frustrated with door sensors getting stuck in the wrong triggered status that I set up a test Vera Plus. Factory reset, latest firmware, ect. I added a motion sensor and 3 door/window sensors from 3 different manufacturers. I tested all the devices and they work perfectly and respond quickly.
Now the problem, I trip all the devices and while they are tripped I restart my Vera. While the vera is rebooting I untrip all the devices. After reboot all the devices still show tripped. The unit has been in this state for 2 days waiting on Vera support to figure it out. Phone support was unable to help and asked me to email.
My Question, Battery devices are supposed to update thier status when they wake up and are polled, Correct??
Devices are being polled because the battery % and last wake time are updated.
[quote=“Bill Scruggs, post:1, topic:195786”]I got so frustrated with door sensors getting stuck in the wrong triggered status that I set up a test Vera Plus. Factory reset, latest firmware, ect. I added a motion sensor and 3 door/window sensors from 3 different manufacturers. I tested all the devices and they work perfectly and respond quickly.
Now the problem, I trip all the devices and while they are tripped I restart my Vera. While the vera is rebooting I untrip all the devices. After reboot all the devices still show tripped. The unit has been in this state for 2 days waiting on Vera support to figure it out. Phone support was unable to help and asked me to email.
My Question, Battery devices are supposed to update thier status when they wake up and are polled, Correct??
Devices are being polled because the battery % and last wake time are updated.
Any help would be greatly appreciated!![/quote]
When polled, if you are in the window that it is awake, yes it should update the status. I have found this doesn’t really work.
The wakeupinterval variable is only supposed to “listen” to see if Vera has anything to tell it.
I have found that I had to change manually the trip variables, open/close my door to get things to reset correctly. I will say they are finnicky.
Check your poll settings and wakeupinterval. It is possible your poll settings are longer than 2 days. Probably not but recheck them.
Thanks tomtcom, I’ve tried a lot of combinations of polling and wakeup settings and nothing works. All are back to Default.
To Quote Z-Waver from another thread “Polling is used to see if the device is still present on the network and to determine it’s present state(tripped/untripped).”
This is definitly not working for me. I hope Vera support gets back to me soon. I’ve put a lot of hours in tring to figure this out, and it is really frustrating!
I know you said three different manufacturers, so it seems unlikely to be the device itself. But, you didn’t name any one of them. When troubleshooting, it’s usually best to focus on one device.
Vera should poll the sensor during the wakeup interval.
The wakeup interval is supposed to cause the sensor to wake up and announce to the Z-Wave controller that it is awake. The controller then issues any queued commands that may be outstanding, like a heal’s configure command or a poll. If the polling interval is set and has passed, Vera should poll the device.
Some devices are set to never poll “Poll this node at most once every” 0 = Never If your sensors are set to 0 then they will not reset via polling. Though they should “get back in sync” after being tripped and untripped while Vera is powered on. If your device is set to never poll and you decide you want/need it to poll, you should set the polling interval to something very high, so as not to kill the battery. A common default polling interval for battery operated sensors is “Poll this node at most once every” 10800 seconds(3 hours).
I sometimes see battery devices that don’t seem to ever wakeup and behave as expected. Usually when this happens, Vera has not configured the device after inclusion. The device must be awake and Vera have a chance to configure the device. I think, though I don’t know, that it may be that Vera needs to set the node for the device to report to upon wake up. If that’s the case, it will be even more important in cases where the Z-Wave network was imported or transferred to Vera from another controller, as Vera will not be node 1 in those cases.
Having said all that, I do remember seeing posts about certain sensors never untripping. This was regardless of Vera being powered on or not. It was due to a firmware bug that I believe has been fixed in the most recent firmware updates. You may want to also search for that and verify that your sensors and your Vera firmware version are not subject to that bug.
Thanks Z-waver
The 2 main devices I am testing are the Fibaro FGMS-001 motion sensor and a Linear WADWAZ-1 Door/Window sensor.
My logs show that the devices are waking up and successfully being polled. Wakeupratings, LastWakeup time,LastPollSuccess,ect are all being updated.
Vera support emailed and are escalating my issue to level 2.
Update: Vera support says my problem is I have only battery operated devices and need to add a repeater. Thats funny because all devices are within 3 feet of the Plus. They did state that all of my devices are compatible with my Vera unit and should update the next time they wake up.
Update from Vera support: They found the problem and were able to replicate it in thier office, and reported it to the developement team for further investigation. They also suggest downgrading to firmware 7.19.
This tells me that it is not just my setup, but a firmware issue. That is a big deal if it effects all Vera Pluses running the latest firmware.
Chrisfraser05 , You are kidding right? I’ve spend months trying to figure this out and a lot of time on the phone and emailing support. I can not believe that they would waste thier supports staffs time troubleshooting something that they already knew about. And why didn’t someone else on the forum let me know when I posted about this weeks ago?