Lastest UI7 1.7.569 on Vera 3 - issues detected

Community Playground General Discussions
1

I just upgraded my UI7 Vera 3 to the latest 1.7.569 firmware.

Issues noted so far:
My Monoprice PIR sensors(I believe them to be Vision models) no longer untrip after being tripped. Which really screws up my ‘security system’. I have to manually set the ‘tripped’ variable to 0 in Advanced settings ->variables to get the sensors untripped.
The same goes for the Monoprice Shock window sensor. Once tripped, it no longer times out to untrip.

Listed improvements confirmed:
My Monoprice glass break/shock sensor icon no longer is a PIR one but now looks similar to the garage door one.

I’ll update this post if/when I find more problems.

2

Reported the same problem here:
http://forum.micasaverde.com/index.php/topic,31769.15.html

At least we are consistent.

3

[quote=“BOFH, post:1, topic:186924”]I just upgraded my UI7 Vera 3 to the latest 1.7.569 firmware.

Issues noted so far:
My Monoprice PIR sensors(I believe them to be Vision models) no longer untrip after being tripped. Which really screws up my ‘security system’. I have to manually set the ‘tripped’ variable to 0 in Advanced settings ->variables to get the sensors untripped.

Listed improvements confirmed:
My Monoprice glass break/shock sensor icon no longer is a PIR one but now looks similar to the garage door one.

I’ll update this post if/when I find more problems.[/quote]

Me too…

4

Until this gets fixed, I ended up setting up a scene to run every 15 minutes that untrips all PIR sensors. I found it on the forums when researching how to do the LUUP for it. I also created a ‘untrip’ button on my security VP to run the scene manually.

LUUP snippet

function resetSensor (device)
    local SECURITY_SENSOR_SERVICE ="urn:micasaverde-com:serviceId:SecuritySensor1"
    luup.variable_set (SECURITY_SENSOR_SERVICE, "Tripped", 0, device)
end

resetSensor(xx)

in the resetSensor(xx) call replace xx with the device # found on the device’s advanced tab at the top. Add a resetSensor(xx) call for each sensor you want to untrip with that sensor’s device ID replacing the xx value.

5

I love the avatar… lol

I was going to do the same thing but since this sensor is not critical to my system I think I will just delete it for now.

6

I actually have 3 of those as room mates. :slight_smile: I unfortunately depend on mine (together with some other sensors) to alert me of incidents in the part of the house they are not normally able to access while I am at work. Although the youngest one is figuring out how to operate a lever lock. So yeah, for now, I need that ‘untrip’ scene. I just hope this does not take a month to get fixed…

7

My upgrade exceeded 15 min so at 20 min I unplugged and plugged back. When it came up it said it had the latest f/w. I tried a few things and they worked. I then went to settings and it asked me to login. I did that and got a spinning wheel which now I get and can’t access the system even when I restart. All lights seem normal. Help?

8

Update - I was using Firefox so I tried Safari on my mac… It seems to work now although not always seeing the screen…

9

I use the same snippet of LUA but instead of running the scene every 15 minutes I trigger the scene with the device I want to reset, but delay the action 30 seconds, it seems to Work.

10

Great idea but 30s seems a bit short given the refresh for the trip state of the device should be 60s at least if you configured it that way. The default is 3min.

Since I only have only one sensor, this is the code I used to reset mine after 65 seconds. XX being my sensor’s device number

[code]function resetSensor ()
local SECURITY_SENSOR_SERVICE =“urn:micasaverde-com:serviceId:SecuritySensor1”
luup.variable_set (SECURITY_SENSOR_SERVICE, “Tripped”, 0, XX)
end

luup.call_delay(‘resetSensor’, 65)[/code]

11

Thanks so much for this post. I’m in the initial setup process of my Monoprice sensors, and thought I was doing something wrong. Since it’s such a recent bug, Google wasn’t much help.

With Vera does the “squeaky wheel get the grease?” – would it help for everyone who has this problem to call in so they can prioritize it? Or best just to let them take care of it?

Justin

12

Dang! I like that reset after x seconds when tripped idea. Going to implement that myself!
The issue is being checked by GetVera and I’ve enabled the support account for them to get at the info they need.

13

Update: George from Vera is poking around in my Vera3 to check into this issue more. Unfortunately I had forgotton to disable the ‘untrip sensor’ scene that ran every 15 minutes prior to his first foray. Oops! That has now been resolved so I am awaiting the Ok to disable support access indicating Vera has what they need.

This issue has already been listed as a bug on the Vera side.

I just noticed in another thread it’s also affection Vision door sensors…

14

My upgrades NEVER seem to work; I have to call support, and they perform the upgrade effortlessly. The support agent shared that he deleted a few files before performing the upgrade. Of course, if WE try removing any temporary files (log files or otherwise), we risk Vera support no longer helping us :-).

15

Ditto. I think you should reboot right before you try to upgrade.

16

Update: I heard from Vera. They were able to reproduce the not untripping issue in their lab so I’m sure it will be addressed in the next upgrade. In the mean time I will just use my lil untrip scene to keep things running.

17

I got the same issue for my door sensors (Linear door sensor I remember) but my PIR sensors (Ecolink) are all good… But I can’t use the manual untrip scene as I need to know when the door sensor is untripped so that door lock can lock itself when door is actually closed. Now I have to lock the door based on delay (30s) which is not ideal if I keep the door open longer than that. The lock will lock and I have to unlock it to close the door. Waiting for the fix update too.

18

Public Service Announcement: 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 this experience, I suggest you may wish to do the same as to avoid the above issue.

19

Did this ever get sorted out? I have several wireless Monoprice Motion sensors that get stuck in the tripped state on UI7.
I also have some Ecolink Door tilt sensors that get stuck as well.
I’m on firmware 1.7.730 which I believe to be the latest.