Odd door/window sensor behavior since firmware update

Other Devices & Integrations Door Locks & Sensors
1

Hi all,

I recently updated my Vera Lite to 1.7.569. All seems well, but now my door/window sensors are behaving… oddly.

Sometimes they work fine, but mostly, they seem to show constantly open/tripped. When I open the door, nothing changes in Vera, and no scenes are fired… but when I close the door, Vera quickly shows it as closed, and then immediately shows it returning to open, including firing the scenes. I’ve tried manually setting the sensor to not be tripped under Advanced > Variables > Tripped, but it seems to go right back as soon as the door is opened and closed again (I even waited for the wakeup interval, and for Vera to clear the related message).

I’ve confirmed that the light on the sensor is only flashing once (which it does during both opening and closing events).

Any advice would be appreciated.

2

I would suggest 3 things.

  1. Run a heal and only for the affected devices.
  2. Exclude the devices and re-Include them.
  3. Create a support ticket, they can read the logs and determine what is going on.
3

I actually just heard back from support. Apparently it’s a known issue with the Monoprice sensors that they “hope to fix in a future version”. Irritating, since it worked just fine before, but… w/e.

4

I’m having the same issues with my motion sensors. You would think Vera would be on top of this and release a patch to fix what their most recent update has broken. I’m still pretty new to Vera but this screw up really messes everything up for me. I use motion sensors to trigger a few lights in my house to turn on and then back off when no motion is detected, and this error on their part has left my lights turning on and off at random times.

This isn’t only affecting Monoprice sensors, several other brands have been mentioned by other users.

Here’s a thread that has a piece of LUUP code where it change the Triggered variable back to 0. It’s a good work around for now, but no where near perfect.

http://forum.micasaverde.com/index.php/topic,31793.msg230737.html

5

Ah good to know I’m not the only one. Thanks!

6

Maybe it’s just me but it seems like a recent firmware upgrade for various Vera models caused lots of quirky behavior and some fine points to stop working…and all with the vague reply of “it should be resolved in the next firmware update” :-\

7

Yep. Definitely not something you’d want to hear about an issue they caused. I posted the same thing on their Facebook page and Marc asked me to email him with more information about the issue. He replied on a Sunday and said he would check with customer care on Monday but I haven’t heard anything back yet. It’s very disappointing, I’m still very new to Vera and HA but I have already spent too many hours trying to get this VeraEdge to perform like I expected when I purchased it…

8

New firmware came out today. Didn’t really fix my notifications issue but maybe it’ll fix something on your list. Try it out.

9

Doesn’t seem to fix the Monoprice PIR issue. On that note, be careful using that untrip scene I posted a while back. It borked my Vera3 over the weekend and it took Vera Support to resuscitate her…