Monoprice Motion Sensor constantly triggered

So I updated my Vera Edge to the latest firmware last Thursaday and I also received two Monoprice motion sensors the following day. Before the update I had one Monoprice motion sensor and it ran my scenes to turn on and off lights perfectly. Now when the motion sensor detects motion the lights turn on but now will not turn off. When i looked at my device list i noticed that all my Monoprice sensors have the wave bars red. I am assuming that red means sensors tripped and grey means not tripped. Anyone else own Monoprice motion sensors and notice this behavior since updating their Vera device. I have tried excluding and including all the Monoprice sensors eventually will stay red in my device list.

This is a known issue with the new firmware and there are already several threads on it. Vera is aware of it and has it listed as a bug.

See below thread for a LUUP snippet you can run in a scene every eg 15 minutes that will untrip your sensors for now.

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

Ugh, I guess I searched the wrong forum. However, that temporary fix probably will do the job until the next firmware release.

Glad I found this thread. I was going crazy trying to figure out what was going on with my scenes with my motion sensor!

Vera is aware of the issue. I was notified today that they were able to reproduce this behavior themselves. It’s been escalated to the development team. For now I’ll just use the untrip scene kludge. I could probably make scenes for each to untrip them eg 90 seconds after they trip. But as I’m pretty sure this will be fixed by the next release, that’s too much work. :wink:

PSA: My Vera3 locked up on me yesterday with a ‘Luup engine is taking longer to reload.’ on the UI and an error 245 on the log-init-LuaUPnP. Vera was able to remote in, find the issue and resolve it. It appears that the ‘Untrip Motion’ kludge scene I created caused the behavior. They removed it. Based on my experience, I suggest you may wish to do the same as to avoid the above issue.

Anybody tested 7.0.7 to see if it is fixed?

I am testing it right now on my UI7 Vera3. Standby…

Update: censored This issue has not been resolved. I can see the sensor untrip after the 1 minute I set but it immediately trips again and stay tripped. I’ve been watching it closely for the last 6 minutes.

Seeing the Untrip script messed up my Vera pretty bad, I’m now using a manual solution. Thanks to rstrouse’s virtual panels. I already had one setup with all sensors as persistent toggle button triggered by the ‘Tripped’ variable of each sensor. I now set each button’s off state to set that Tripped variable to 0.

Email sent to Vera based on the last time I reported this issue. Lets see what comes out this time. All I can say is that if you have the same problem, go to Settings → Tech Support and click the Contact Support button to let them know.

still an issue here as well :frowning:

I submitted a support ticket, posted on their Facebook again. This may not be a big issue for most users, but this is the ONE thing I had in mind when starting this HA venture, have my lights turn on automatically when walking into a room. Which has been working fine for the past few months until they broke it. I’m just frustrated with the level of service Vera has been providing lately.

Maybe you could downgrade until its reported fixed. We know they only post updates once a month at most and this was just posted. So if they broke it after an update and you really need it, just downgrade until the fix is made then move on back up.

It wasn’t 7.07 (the latest update) that broke them but the previous 7.06 one. I’m seriously considering downgrading back to 7.05 so I can regain the use of my sensors again until Vera completes addressing this issue. Hopefully in the next release.

I just wish they would focus on getting UI7 running as it should first, then start adding new features. And we have to hope that they fix it in the next release in another month? I figured it would definitely be fixed in this release, so who’s to say it’ll be done by next month! And from what I’ve read it’s not only affecting motion sensors but also door/window sensors.

Where can we download older firmware?

Sent from my iPhone using Tapatalk

Now I remember why I never upgrade the firmware on my edge!

Even my monoprice door/window sensors don’t untrip >:(