Marc this is a very positive action to show two companies working together as opposed to pointing fingers! Well done!
Just FYI, I have been able to get these sensors working (except for UV sensor) on a Vera 3 running UI7 Version 1.7.619.
The only issue is the icon only indicates tripped (turns red) in AltUI, NOT in UI7 with Chrome or IE.
I mostly followed ZW-Tom’s instructions in reply 105 on this thread. First updated the firmware using the Z-stick following Tom’s steps 1 - 6
On adding the device to the Vera3, I changed Tom’s steps as shown
Do the following: 1.) Add the sensor to the Edge using the Aeon 4 in 1 sensor. It will add as a "D_GenericIO1" device. 2.) After the device has been added, the LED will blink on the sensor, don't touch the sensor. 3.) Select the new device, then click the Advanced line. 4.) Under the Params tab, change the following. Be sure to click outside each box to add the change. 5.) device_type: urn:schemas-micasaverde-com:device:MotionSensor:1 6.) device_file: D_MotionSensor1.xml 7.) device_json: D_MotionSensor1.json 8.) Now you must wait for the blinking light on the sensor to stop blinking. Don't touch the sensor until it does. 9.) When the LED on the sensor stops blinking, reboot Vera.
1.) Add the sensor using “Generic Z-Wave device” (I could not get it to add as the Aeon 4 in 1)
2.) Once the Zwave light on the Vera3 is slow flashing and showing “Add new device now”, press the “Action Button” on the back of the sensor to add
2a.) As soon as the screen shows “Device Added” click next twice to get the Vera out of inclusion mode - then do Tom’s steps 3-7
3.) Select the new device, then click the Advanced line.
4.) Under the Params tab, change the following. Be sure to click outside each box to add the change.
5.) device_type: urn:schemas-micasaverde-com:device:MotionSensor:1
6.) device_file: D_MotionSensor1.xml
7.) device_json: D_MotionSensor1.json
8.) Click the New Service tab, and click Reload Engine
9.) When the Vera3 Zwave light comes back on, go back to the device, Advanced, Commands tab
10.) Press and hold the sensor’s Action button for 4 seconds, release and click the “Configure Node Right Now” in your browser
At this point, wait 5 - 10 minutes, do a screen refresh, and you should have the main sensor and the 4 child devices
I don’t know exactly what I did to make it work. My first several attempts failed, and it SEEMS to me that if I didn’t change the device Params quickly enough, the sensor would configure as a GenericDevice, and then not work correctly even after I changed those values. YMMV.
I have 3 of these sensors working on 2 different Vera3’s, and they work well. I can change the 4 minute delay time on Parameter 3 to any value in seconds, but changing parameter 6 for sensitivity gets a “Failed at setting user configuration” message. The default was not what the manual says, so I wonder if simthing has changed since the manal was written.
Just a reminder. The red lines above the sensor never show on UI7 but you can see it’s tripped by looking in the variables. AltUI shows it correctly (thank you amg0)
Good luck!
For the people that don’t see the device icon change to red when tripped, make sure the device has the right category and subcategory!
It should have:
[ul][li]category_num: 4[/li]
[li]subcategory_num: 3[/li][/ul]
(you can change this in the Advanced configuration of the device)
See also: http://wiki.micasaverde.com/index.php/Luup_UPNP_Files#Device_Categories
@trafex, your a clever person… ;D no one including Vera, Inc made any mention of simply changing device category/subcategory to make the icon change, it was always wait until we get it to work in an updated version… Many thanxs makes it easier to look at the icon rather than bouncing around inspection each device log activities. Mike
[quote=“trafex, post:143, topic:187238”]For the people that don’t see the device icon change to red when tripped, make sure the device has the right category and subcategory!
It should have:
[ul][li]category_num: 4[/li]
[li]subcategory_num: 3[/li][/ul]
(you can change this in the Advanced configuration of the device)
See also: http://wiki.micasaverde.com/index.php/Luup_UPNP_Files#Device_Categories[/quote]
[quote=“trafex, post:143, topic:187238”]For the people that don’t see the device icon change to red when tripped, make sure the device has the right category and subcategory!
It should have:
[ul][li]category_num: 4[/li]
[li]subcategory_num: 3[/li][/ul]
(you can change this in the Advanced configuration of the device)
See also: http://wiki.micasaverde.com/index.php/Luup_UPNP_Files#Device_Categories[/quote]
Yes you are clever!
Thanks for this little gem. Makes things a lot easier!
Has anyone figured how to turn off the Motion sensor LED when motion is detected, would like a stealth mode if possible? My significant other doesn’t like seeing the light blink whilst on the porcelain throne… claims doesn’t like something watching her… :
also I notice that of my six sensors this one seems to flash blue vs the green can one choose what color the LED flashes?.. Mike
Can someone help me with basic motion sensor monitoring on this? I am struggling.
It looks like it says it can run a command, then it will wait until it has detected no motion for 240 seconds, then turn something back off.
How can I get this set up? I have made a scene that says, whenever the motion sensor detects motion, turn on my living room lamp, and another for no motion/turn off, but this is really laggy and unresponsive.
I feel like I need to set this up to be an “associated” device? can anyone point me in the right direction there?
Thankyou for any help,
Why can’t the firmware be updated via the USB cable, like the old one?
Progress ???, I guess once Vera implements the OTA capability it will remove the need for special loading utilities. I bit the bullet and bought a z-wave stick and am happily running 8 sensors that are working great with Vera 1.7.1419, Mike
@charlesmerceriii, I’m assuming that your motion sensor are at the latest firmware? Also I find reducing the default motion trigger reset from 240 seconds (4 minutes) to 30 Seconds allows the sensor to re-sense motion every 30 seconds and create a scene to keep the Light on for X minutes based on motion, what will happen is that if motion is re-sensed the light stay on for an extended time, if no motion is sense the light will turn off after X minutes timer expires. Mike
I just thought that I’d check back in on this thread…
There was a recent Vera Edge firmware update that I applied (turns out it did something bad to my RFXtrx dongle, but that’s another story and something I’m trying to fix with Support) but I was curious - has anyone yet managed to confirm that we can get this sensor working properly with our Vera now, or are we still waiting?
Apologies for being lazy but I didn’t fancy trying it again (like, the 11th time) before I heard something positive…
I’ve got it included with U15 1.5.672 and a Vera 3 after changing the .xml and category, as per the thread, but it seems permanently tripped. Anyone else find a way around this?
I have the same problem. I mitigated it by running this code every five minute when i?m in “Home” mode. Also i rund the code once when changing mode.
Big time work-around for something that should just work doh.
-- (motion sensors)
for k, v in pairs(luup.devices) do
if v.category_num == 4 and v.subcategory_num == 3 then
luup.variable_set("urn:micasaverde-com:serviceId:SecuritySensor1", "Tripped", "0", k)
end
end[quote=“jonte, post:153, topic:187238”]I have the same problem. I mitigated it by running this code every five minute when i?m in “Home” mode. Also i rund the code once when changing mode.
Big time work-around for something that should just work doh.
-- (motion sensors)
for k, v in pairs(luup.devices) do
if v.category_num == 4 and v.subcategory_num == 3 then
luup.variable_set("urn:micasaverde-com:serviceId:SecuritySensor1", "Tripped", "0", k)
end
end
[/quote]
That’s very clever and it does indeed reset the ‘tripped’ problem, but I can’t get it to trigger again after that.
Hmm, mine gets tripped as expected after i run the script. One different that might be importent or not is that my sensors are Aeotec 4-1 Multisensor, but i think it should work the same in this matter.
Mine is the MultiSensor 6, ZW100-B, the Australian version of the sensor.
There’s a list of the differences on the Aeon site:
MultiSensor 6 ZW100-A,V1.04,US
MultiSensor 6 ZW100-B,V1.04,AU
MultiSensor 6 ZW100-C,V1.04,EU
Unrelated to issues with the device itself, has anyone purchased the optional recessed bracket ? Haven’t found one for sale and no idea on cost.
I have one running well on latest ui7 after having made device changes as per this thread. One thing to note I think if on battery the motion sensor stays tripped for 4 minutes and if triggered again in that time will reset the timer so if you can constantly looking at it out would stay tripped. Guess related to it being on battery and limiting the amount of messages it needs to send over zwave?
[quote=“helraiser, post:128, topic:187238”]I’m on a vera3 with ui5 672. Works great, except the UV reading which doesn’t report. I’m probably going to order a second for another side of my house.
A lot less false positives too.[/quote]
Did you update your firmware in the sensor? I don’t have a Z-Wave stick to do mine, but otherwise it’s the same setup. Did you make any changes to the device options, like the bit in the picture?
Thanks
How are these working for you guys?
I’m still on UI5, any issues?
What is the motion reset time? Adjustable? (I like the ‘test’ mode on the Schlague units - 4 second reset - great to entry alerts)
How good is the Motion sensitivity adjustment?
thx