I think it meant regular infusion vs the security inclusion. I’m using UI7, most recent firmware on my VeraEdge.
Aeon tech support said to follow instructions here, HOW TO INCLUDE THE MULTISENSOR 6 ZW100-A TO YOUR VERA - The Smartest House , but even though I exclude and then factory reset the sensor, I get the same end result. The motion sensor device gets in a purging associations loop, and never polls any of the sensors for data.
Quite frustrating.
-Andrew
Using Veralite UI7 - and getting that Purging associations loop ->anyone figured out a fix yet?
Installed fairly seamlessly on Vera 3, UI5, 1.5.672. All but UV reports.
Now to place it outdoors and see how well it performs.
[quote=“user1121, post:61, topic:187238”]I think it meant regular infusion vs the security inclusion. I’m using UI7, most recent firmware on my VeraEdge.
Aeon tech support said to follow instructions here, HOW TO INCLUDE THE MULTISENSOR 6 ZW100-A TO YOUR VERA - The Smartest House , but even though I exclude and then factory reset the sensor, I get the same end result. The motion sensor device gets in a purging associations loop, and never polls any of the sensors for data.
Quite frustrating.
-Andrew[/quote]
@user1121, I too am having the same problem. I just purchased a Vera Edge, update the UI 7 to the latest version and followed the same procedure suggested by Aeon Tech Support. Am able to exclude and re-include get the motion sensor device, and 4 other children devices, but then I left with the “purging associations” loop, I even thought letting alone over night might help/heal with no joy. I just got a note back from Aeon stating that others have been able to get the sensor working… obviously we must be doing something wrong or there is something we’re missing within the procedure, e.g. there is no explained of the color changes such as when the device doesn’t have an association with any controller the motion sensor colors cycle through different colors. Once pairing occurs the LED is a solid green also if the controller is trying to configure/purge the motion sensor it turns on solid green for short duration which can be verified looking at the Vera page (top status).
I’m slightly confused with “click on the MultiSensor’s action button” vs “press and hold the inclusion button” within the procedure am I to assume that it is the the little button located on the bottom of the Motion device and that they are one in the same? I notice that when I look at the “parms” tab that it identifies the device as an AEON mfgr along with various features (not sure if they are all there and/or correct as there is not real explanation". I have 5 of these devices and am seriously thinking about sending them back and move on to another solution. Mike
Mike,
I’m confident they’ll figure it out soon. I want to buy more once they’re working.
I wonder if it’s related to us having more than one?
Or the secure vs normal inclusion?
Andy
I wonder if it's related to us having more than one?I've only been working with one and actually move to another to exclude the possibility that something might be faulty with 1st sensor.
Or the secure vs normal inclusion?How is this accomplished?
I'm slightly confused with "click on the MultiSensor's action button" vs "press and hold the inclusion button" within the procedure am I to assume that it is the the little button located on the bottom of the Motion device and that they are one in the same?Is my assumption correct?
Your assumption reads correct to me.
Normal inclusion is one click.
Secure inclusion is a very fast double click.
Neither seems to be working for me.
Andy
Andrew,
I’m a touch embarrassed to say i noticed the parameters in the manual (which I had conveniently put in a folder of other instructions I’ve never read) earlier today. And, while it was my oversight, I still want a job in the marketing and product roll out division at Aeon Labs. Who makes such neat products, and then provides the end users with little online technical information and or documentation? Hire me and I would make sure every developer and techno junkie had access to everything needed in order for our products to be utilized everywhere by anyone. Anyhow, thank you just the same for pointing to the parameters. To answer your question, no I only had to follow Tom’s guide (Thank you Tom)
Tom,
I am using a Vera 3 and running UI5.672
User1121 and NMB, you are not alone! I’m running the Vera Edge FW: 1.7.1248 and can’t get the new Aeon MS6 working with my unit either. I’ve tried both the Normal Inclusion and the Secure inclusion methods following ZW-Tom’s instructions and no luck. I’ve left it for days and it never comes out of the Purging associations loop. I had high hopes that this new sensor would work right off the bat even if the UV sensor didn’t work, the better battery life was promising, Oh Well… I guess I’ll box it back up and put it on the shelf until Aeon releases updated FW for it or Vera starts supporting it in future releases. Until then I’ll keep checking back here for updates, at least I know that I’m not alone in my disappointment. I’m also going to contact Aeon to let them know that their user guide stinks (what do the different color lights mean?) and let them know that it’s not working universally in Z-Wave land. 
I’ll tell you what, I’ve gotten 5 emails from Aeon on this issue, including the manual PDF and engineering info on parameters. I’ve gotten nothing but an automated reply from Vera. It’s sad to have such poor customer service on what it otherwise a fantastic controller.
I’ve followed Tom’s directions on the VeraEdge and have: Temp, Humidity, Light, and Tamper protection (but not motion it seems). I did have to try it 3 times, but realized that after the first reboot, I needed to constantly place the MultiSensor6 back into ‘wake’ mode to prevent the “purging association loops”. Each time the banner would show errors (by turning red), I would place the sensor back into “wake” mode and the banner would turn blue and the VeraEdge would continue whatever it was doing. It took a while.
I’m new to this. Could someone please explain to me why it is so difficult to write an “app” for this particular device so that we can have all the functions? UV would be awesome.
@signalgod, can you tell us how you placed your sensor into “wake” Mode and what LED observations that indicated a successful wake mode? also I notice that the colors on the LED change the longer (10 sec) that you hold down the motion sensor inclusion button (I seem to get to red that flashes around 8 seconds and gets faster). any help would be greatly appreciated. Mike
[glow=red,2,300]Update:[/glow] Just read a review in Amazon.com where someone made mention of errors documented within the manual in particular; “The directions for waking up the device also appear to be incorrect. I was unable to wakeup the device following the directions, and the light cycled through a couple different colors as I held the button, suggesting I was accessing some other functionality the manual didn’t describe at all. (This was also the case for the previous Gen5 multi-sensor. The manual said “hold for 3 seconds” to wakeup when in fact you needed to press three times.)”.
[glow=red,2,300]Update II:[/glow] Found two other sources that suggest the following;
[ol][li]Web Page "Procedure to Wake-Up: Pressing the Z-Wave button once will trigger sending the Wake up notification command. If press and hold the Z-Wave button for 3 seconds, the MultiSensor will wake up for 10 minutes." [/li]
[li]Complete Aeotect Multisensor 6 manual 21 pages (tried to attached but too big) has everything one would want to know about the sensor including various table describing library and command classes, All functions of each trigger, association Command Class, and Configuration Set Command Class parameters.
Waking up your MultiSensor.
If your MultiSensor is battery powered, you will need to ensure that it is active when configuring it. To do this, press the Action Button once, which will trigger to send out a wake up notification command. If you want it to wake up for 10 minutes, to do this, press and hold its Action Button for 3 seconds and then release it. Your MultiSensor?s (orange) LED will fast blink for 10 minutes to indicate that it is active. When you are done configuring or communicating with your MultiSensor, you can put it back into sleep mode to conserve battery power. To do this, press and hold its Action button for 3 seconds and then release it. Your MultiSensor?s LED should now be off to indicate that it is asleep."[/li][/ol]
Can anyone confirm or deny this information. When I pressed the inclusion button three times the LED came on with a steady “BLUE” light, when I press the inclusion button for 3 seconds it changes color to ~orange but did not flash and/or stayed on for 10 minutes. Still haven’t got pass the looping purge…
[quote=“signalgod, post:71, topic:187238”]I’ve followed Tom’s directions on the VeraEdge and have: Temp, Humidity, Light, and Tamper protection (but not motion it seems). I did have to try it 3 times, but realized that after the first reboot, I needed to constantly place the MultiSensor6 back into ‘wake’ mode to prevent the “purging association loops”. Each time the banner would show errors (by turning red), I would place the sensor back into “wake” mode and the banner would turn blue and the VeraEdge would continue whatever it was doing. It took a while.
I’m new to this. Could someone please explain to me why it is so difficult to write an “app” for this particular device so that we can have all the functions? UV would be awesome.[/quote]
@MNB
I pressed and held for 3 seconds, but I did it over and over. If that didn’t work after 3-4 times (as in, stuck), I rebooted.
@Signalgod, did you noticed whilst you press the button for three seconds that the LED changed colors and did it flash. By the way you described it I assume no it did not flash nor did flash for 10 minutes as prescribed by Aeotec engineering manual, can you confirm. Also when you rebooted again I’m assuming you rebooted your Vera unit after words did you continue to try to awake your sensor (press button for three seconds) and if so did you recall when you restarted? It’s obvious that these sensors are not working the same for all folks which makes wonder if there is something different in these sensor (firmware) unfortunately I do not see any way of determining their level and or an ability to update manually. Mike
@ MNB
The LED would begin it’s cycle through the colors. No flashing or blinking.
I noticed that when I have it paired and connected via usb power, I cannot get it to flash after holding the button for 3 seconds. but it does flash when holding the button on battery power. But still getting the purging loop after all that.
@badvlad, thanxs for providing your observations…
Interesting that it blinks (flashes) on battery power only (I will have to try it, as I just purchased batteries in the hopes of being successful). I’ve been using USB power all this time thinking that I would have a better chance at properly including the sensor. Can you confirm how long the blinking (flashing) occurs and is it after the three seconds time. I feel like a blind man trying to explain an elephant due to lack of proper documentation and limited technical guidance. Based on what you have shared I’m wondering if the senors when under USB power defaults to continuous Wakeup time and that’s why the led never blinks when depressed for 3 seconds, also I’ve noticed that with USB power that Vera is able to access the sensor (the Blue LED) that comes on and turns off when Vera is performing “Please wait getting the Manufacture Info” or “Purging Associations” but like several of you out there it goes into the continuous purge association loop.
I’ve now tried the procedure with three different Aeotec ZW100-A sensors with the same resolve - Looping on “Purge Associations” which sort of eliminates a bad sensor theory. Yesterday evening I just included another type of motion sensor HSM-200 which worked like a charm and confirmed that it works properly, which suggests that the Vera is able to successfully include other Motion sensor types. I’m now wondering if the problem is associated with the z-wave plus properties in some manner (speculating at this point). I have been in contact with Aeotec customer service last week and shared my latest motion sensor device parameter contents, according to them it appears that the device parameters are correct but will have to wait until Monday to have someone technical to review and advise.
[glow=red,2,300]Update:[/glow] Unplugged the USB power and inserted batteries, depressed the button for 3 seconds and now have two sensors blinking (flashing) Orange for 10 minutes.
@MNB Glad that worked with the batteries. let us know if you get any further then me. I am also in communication with Aeotec and will keep everyone posted if they have any ideas. My guess is that we will not progress anymore until Vera or Aeotec release a firmware update.
Hi,
I am currently searching for an answer myself about the purging association. For some users, they do not get this issue, while others do. I don’t have any logs that i can analyze the situation. I can only provide suggestions in hopes that it would help.
First plug in the device as a USB device and remove the batteries, then re-include the sensor and see if that helps out or removes the purging association loop.
Let me know if that helps at all, in the meanwhile, I will be looking for a solution.
Cheers,
Chris
Received a reply from Aeotec:
Hi,
To my current knowledge right now, i heard that Vera has been collecting logs to solve the issue with the next firmware update. I suggest that you message Vera support about it.
Besides the blog available, the Multisensor should be V1.04 which can be seen under “VersionInfo.” The last 2 digits should be 1.4.
Cheers,
Chris
@badvlad, Thanxs for the comeback, I’ve been in touch with Aeotec and Vera, Inc. I got the same response from Aeotec in fact the 1.4 came from my parm file that I shared with him to determine if there might be a different firmware other there. I got a response back from Vera Inc to unpair and re-include my sensors and enable customer support port, I’ve yet to get any feedback such as; confirmation of the problem, we’re working or have a solution to resolve… will keep you abreast once I get someone from VERA to respond to my subsequent progress emails. Mike
[quote=“badvlad, post:79, topic:187238”]Received a reply from Aeotec:
Hi,
To my current knowledge right now, i heard that Vera has been collecting logs to solve the issue with the next firmware update. I suggest that you message Vera support about it.
Besides the blog available, the Multisensor should be V1.04 which can be seen under “VersionInfo.” The last 2 digits should be 1.4.
Cheers,
Chris[/quote]
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules