Aeotec Multisensor 6 (AEZW100A) - anyone used it?

Just received mine today, and installed on a Vera3 and UI7 V1.7.599

As ZW-Tom and others experienced, it created as _Generic IO. It also created 4 child devices. _Light Sensor, _Temperature Sensor, _Humidity Sensor and one named: “_GET_LANG(generic_sensor,sensor)”. ???

The light, temp and humidity all seem to be working. I followed Tom’s instructions, and changed the device type and file, but it gets stuck at “Purging associations”. I’ve tried excluding and re-including, reset to factory, but can’t get past purging associations, so it does not get configured.

I get no motion detection from either the parent or the _GET_LANG sensor, but I do get a tamper alarm when I pick up the device! The small manual that came with it says “view the expanded manual Support – Aeotec” but I can’t find a manual there yet for this new model.

Has anyone else had these problems? Any suggestions are appreciated. I’ll try Aeotec and The Smartest house on Monday, but always try here first.

Yes, “This item will be released on July 5, 2015.”

http://thehomeautomationsystems.comlu.com/2015/06/19/home-automation-devices/aeon-labs-multisensor-6-z-wave-plus-6-in-1.html

[quote=“ilikelife, post:21, topic:187238”]Just received mine today, and installed on a Vera3 and UI7 V1.7.599

As ZW-Tom and others experienced, it created as _Generic IO. It also created 4 child devices. _Light Sensor, _Temperature Sensor, _Humidity Sensor and one named: “_GET_LANG(generic_sensor,sensor)”. ???

The light, temp and humidity all seem to be working. I followed Tom’s instructions, and changed the device type and file, but it gets stuck at “Purging associations”. I’ve tried excluding and re-including, reset to factory, but can’t get past purging associations, so it does not get configured.

I get no motion detection from either the parent or the _GET_LANG sensor, but I do get a tamper alarm when I pick up the device! The small manual that came with it says “view the expanded manual Support – Aeotec” but I can’t find a manual there yet for this new model.

Has anyone else had these problems? Any suggestions are appreciated. I’ll try Aeotec and The Smartest house on Monday, but always try here first.[/quote]

The Multisensor 6 Motion does not work with UI7 (not supported), even if you change the device file to “D_MotionSensor1.xml”. The “_GET_LAN” sensor is the UV Sensor which is also not supported by Vera UI5 or UI7. I tested this on my Vera Edge (UI7). I don’t use the Edge and hope Vera will someday get UI7 to work. The good news is I still use the VeraLite with UI5 and the MultiSensor 6 works for Motion, Light, Temp and Humidity. Tamper and UV are not supported.

Tom

[quote=“aurora912, post:18, topic:187238”]If Vera decides to support this MultiSensor (Or any new device for that matter), does UI5 get the upgrade or will only newer versions of UI7 be supported?

Haven’t been around long enough to know if UI updates include zwave updates or if its a separate thing.[/quote]

We are in the process of testing and integrating the Multisensor into the platform.

Regarding UI5, we have not updated UI5 in over two years. The only way to have this sensor properly integrate into UI5 would be via a plugin but note that UI5 does not run on a controller with the Z-Wave Plus (500 series) chip.

[quote=“Marc Shenker, post:24, topic:187238”][quote=“aurora912, post:18, topic:187238”]If Vera decides to support this MultiSensor (Or any new device for that matter), does UI5 get the upgrade or will only newer versions of UI7 be supported?

Haven’t been around long enough to know if UI updates include zwave updates or if its a separate thing.[/quote]

We are in the process of testing and integrating the Multisensor into the platform.

Regarding UI5, we have not updated UI5 in over two years. The only way to have this sensor properly integrate into UI5 would be via a plugin but note that UI5 does not run on a controller with the Z-Wave Plus (500 series) chip.[/quote]

Mark,
Looks like a few people have made the device work almost 100% in UI5. It would be nice if you can make a plugin for it, minus functions that TRULY requires ‘plus’. Most of us don’t see Vera adding any value these days. The easiest way for you t do so is to support new devices that many of the users want via UI5.

Many (I suspect a ton) of us are not moving to UI7 …

a) We simply don’t see it as stable

b) Many frequent reports of UI5 functions that no longer work in UI7 and I often see posts of ‘was working, now broken’, with every new UI7 build.

c) Does not add any needed functionality over UI5… user built plugins like AltUI, PLEG, SmartSwitch, MultiSwitch, etc are 10x better than the UI7 interface and work great on UI5

As you can see if you read the forums… many of us have filling Vera’s shortcomings by using user plugins and done things like: purchased/integrated Wink hub, OpenHAB, ISY, etc.
This is a clear sign that Vera is not doing making strides to keep the user base happy and locked into the Vera platform. If you want to keep your user base, you need to add value.

Interested to see if you will integrate this. I will be buying one to test and I suspect my Wink hub will support it. I’d like to not need a workaround, and to have it in my Vera directly.

Totally off topic here. Though I agree with Aaron that the userbase surrounding UI5 is still fairly large, Vera as a company has chosen to go ahead with a new revision for their controller. Ultimately, we’ll all have to push ahead to UI7 and try and work through all the issues we see posted. It’s possible work is being done on the next version which will be Vera’s version of Windows 7 (considering UI7 to be Vista and UI5 WinXP :slight_smile: )

A patch here and there would be awesome but as much as I want, I can’t in good conscience expect them to go back and work on UI5 as their ultimate goal would be for the UI7 uptake to increase. Who knows, perhaps the more people are on UI5, the better the chances of getting those kinks worked out. Still, not everyone has issues with UI7.

With that said, I’m a user and not a developer. I am using the Vera as my main controller and can’t afford a second/test controller. And so as UI5 is the most stable and compatible with my plugins and devices, I will not be upgrading any time soon. FWIW, I bought the Vera with UI7 installed and gave it a shot. I ultimtately requested a downgrade after I hit boiling point on my frustratometer.

When I’m less busy at work and no one’s home, maybe i’ll take a day to go that route. Till then we have 3 choices. 1) upgrade to UI7 and work out the kinks as the developer does also, 2) stay at UI5 knowing very little, if any, change will be coming or 3) ditch Vera and go elsewhere.

GL

I’ve been looking at getting this sensor to help me monitor my mother who has dementia in her room. I want to know if there is movement in her room after 11:pm and if her lights are turned on. I am also very interested in the vibration sensor. Do you think it would be sensitive enough to detect a fall?

Shad

@ZW-Tom,

Thanks for the reply. It does seem weird that this new device works on 5 but not 7, but now I know.

@Marc Shenker,

Good to hear you’re working on it. There are not a lot of good choices in sensors available now (imho) and this one shows promise. I will comment that the updates are making UI7 a little better each month. There are still issues, but new features and fixes are showing progress.

Maybe you could just hire amg0 as a temporary consultant? ;D

Anyone got there hands on the recessed ceiling mount yet?? Interested to see how it looks.

[quote=“Aaron, post:25, topic:187238”][quote=“Marc Shenker, post:24, topic:187238”][quote=“aurora912, post:18, topic:187238”]If Vera decides to support this MultiSensor (Or any new device for that matter), does UI5 get the upgrade or will only newer versions of UI7 be supported?

Haven’t been around long enough to know if UI updates include zwave updates or if its a separate thing.[/quote][/quote]

Mark,
Looks like a few people have made the device work almost 100% in UI5. It would be nice if you can make a plugin for it, minus functions that TRULY requires ‘plus’. Most of us don’t see Vera adding any value these days. The easiest way for you t do so is to support new devices that many of the users want via UI5.

Many (I suspect a ton) of us are not moving to UI7 …

a) We simply don’t see it as stable

b) Many frequent reports of UI5 functions that no longer work in UI7 and I often see posts of ‘was working, now broken’, with every new UI7 build.

c) Does not add any needed functionality over UI5… user built plugins like AltUI, PLEG, SmartSwitch, MultiSwitch, etc are 10x better than the UI7 interface and work great on UI5

As you can see if you read the forums… many of us have filling Vera’s shortcomings by using user plugins and done things like: purchased/integrated Wink hub, OpenHAB, ISY, etc.
This is a clear sign that Vera is not doing making strides to keep the user base happy and locked into the Vera platform. If you want to keep your user base, you need to add value.

Interested to see if you will integrate this. I will be buying one to test and I suspect my Wink hub will support it. I’d like to not need a workaround, and to have it in my Vera directly.[/quote]

Aaron, Like I said, we have not done anything to UI5 in over two years, any new functionality has come from users developing plugins. The issue with things in UI5 not working in UI7 is not one that we can help. We have published and created tools for plugin authors/developers to update their plugins so that they are compatible and we have even offered them a free VeraEdge to test with but we cannot make them do it. We are working diligently at natively integrating more and more things into the platform but understand that Rome wasn’t built in a day. More and more gets integrated with every Firmware update. We also continue to add additional functionality and features that UI5 users can’t take advantage of like geofencing and others and we will be introducing more later on in the year.

If your Vera system is functioning the way that you want it to and it does what you want it do, I’m not going to try to convince you to switch. If it aint broken don’t fix it. If at some point you decide it’s time to make the switch we are here to help, me and our entire Customer Care Team.

Marc,
Any rough idea time wise as to when the user base might expect an update that incorporates this new sensor?

[quote=“Marc Shenker, post:30, topic:187238”]Aaron, Like I said, we have not done anything to UI5 in over two years, any new functionality has come from users developing plugins. The issue with things in UI5 not working in UI7 is not one that we can help. We have published and created tools for plugin authors/developers to update their plugins so that they are compatible and we have even offered them a free VeraEdge to test with but we cannot make them do it. We are working diligently at natively integrating more and more things into the platform but understand that Rome wasn’t built in a day. More and more gets integrated with every Firmware update. We also continue to add additional functionality and features that UI5 users can’t take advantage of like geofencing and others and we will be introducing more later on in the year.

If your Vera system is functioning the way that you want it to and it does what you want it do, I’m not going to try to convince you to switch. If it aint broken don’t fix it. If at some point you decide it’s time to make the switch we are here to help, me and our entire Customer Care Team.[/quote]

I couldn’t agree with you more. Going back to work on the old ui5 is not going to help any of us move forward. As ui5 gets older and less supported, less plugins get made for it, less and less new devices will get full support or function (not only software based but hardware also) eventually people will have to let go and move on. But it’s hard for some.

[quote=“Aaron, post:25, topic:187238”]Mark,
Looks like a few people have made the device work almost 100% in UI5. It would be nice if you can make a plugin for it, minus functions that TRULY requires ‘plus’. Most of us don’t see Vera adding any value these days. The easiest way for you t do so is to support new devices that many of the users want via UI5.

Many (I suspect a ton) of us are not moving to UI7 …

a) We simply don’t see it as stable

b) Many frequent reports of UI5 functions that no longer work in UI7 and I often see posts of ‘was working, now broken’, with every new UI7 build.

c) Does not add any needed functionality over UI5… user built plugins like AltUI, PLEG, SmartSwitch, MultiSwitch, etc are 10x better than the UI7 interface and work great on UI5

As you can see if you read the forums… many of us have filling Vera’s shortcomings by using user plugins and done things like: purchased/integrated Wink hub, OpenHAB, ISY, etc.
This is a clear sign that Vera is not doing making strides to keep the user base happy and locked into the Vera platform. If you want to keep your user base, you need to add value.

Interested to see if you will integrate this. I will be buying one to test and I suspect my Wink hub will support it. I’d like to not need a workaround, and to have it in my Vera directly.[/quote]

[quote=“Marc Shenker, post:30, topic:187238”]Aaron, Like I said, we have not done anything to UI5 in over two years, any new functionality has come from users developing plugins. The issue with things in UI5 not working in UI7 is not one that we can help. We have published and created tools for plugin authors/developers to update their plugins so that they are compatible and we have even offered them a free VeraEdge to test with but we cannot make them do it. We are working diligently at natively integrating more and more things into the platform but understand that Rome wasn’t built in a day. More and more gets integrated with every Firmware update. We also continue to add additional functionality and features that UI5 users can’t take advantage of like geofencing and others and we will be introducing more later on in the year.

If your Vera system is functioning the way that you want it to and it does what you want it do, I’m not going to try to convince you to switch. If it aint broken don’t fix it. If at some point you decide it’s time to make the switch we are here to help, me and our entire Customer Care Team.[/quote]

Mark,
I understand that UI5 has not been updated in years… My ask was not to update UI5. My ask was that you provide assistance (plugin, whatever) so UI5 users could make it work properly. I suspect that this would be easy for an expert in your system (Vera devs) given that the user community has seemed to get it 80-90% working. I sure hope it would not take updating libraries or the kernel. Seems like it does not, right?

Move to UI7? Sure… I and many, many others are waiting for it to be stable and provide usable function beyond UI5 - which it gives neither according to all the posts. You state 1 thing that is “new” - Geofencing. All feedback I’ve read says it does not work properly, and you know this as you commented on a post outline a lot of the issues. It is still only working for 1 phone? funny.

All the UI7 comments are similar to:
“Unstable, I had to go back to UI5”
“Every new build breaks something they just fixed or something else in core functionality”
“My Vera Edge came with UI7 but it was unusable, I put on UI5 and much happier”

I’m waiting for comment like:
"UI7 is much better than UI5 in so many ways, let me tell you… "
“Man I’m glad I moved to UI7”
“The Vera team has really got it right now”

Vera team seems to think that no one understands product development outside of your team. I have worked in product development (hardware & software) at Dell, Microsoft, and others. I’m currently a Product Category Manager and Chief Technologist at HP… I understand product dev fairly well.

I’m not complaining because I want Vera to fail… I’m hoping they don’t but since the launch of UI7 there has been very little visible/tangible progress. Bug fixing a launched software version that was in Alpha, to Beta in a year is pretty lackluster. Releasing a Vera Edge, which was not a step forward either… and not necessary as Vera 3 is just as good.

Strive to make progress that your COMMUNITY thinks is progress. What you think is progress is not as important as what your customers think it progress. (unless you don’t need money)

BTW… Rome, by experts estimates, took approximately 1,009,491 days (2764 years) to build. Vera launched UI7, approx 1.2 years ago in beta & almost 1 year ago (Aug 2014) to RC. Yet all the users that have posted still seem to consider it beta. So you are saying 2763 years more until UI7 is stable? :wink:

[quote=“Aaron, post:33, topic:187238”]Mark,
I understand that UI5 has not been updated in years… My ask was not to update UI5. My ask was that you provide assistance (plugin, whatever) so UI5 users could make it work properly. I suspect that this would be easy for an expert in your system (Vera devs) given that the user community has seemed to get it 80-90% working. I sure hope it would not take updating libraries or the kernel. Seems like it does not, right?

Move to UI7? Sure… I and many, many others are waiting for it to be stable and provide usable function beyond UI5 - which it gives neither according to all the posts. You state 1 thing that is “new” - Geofencing. All feedback I’ve read says it does not work properly, and you know this as you commented on a post outline a lot of the issues. It is still only working for 1 phone? funny. [/quote]

So do you want the focus to be working on ui7 (or fixing it as you say) or do you want the focus to be on going back and making patches, plugins or workarounds on ui5 to keep it working on new z-wave plus devices? Vera new hardware don’t even support ui5 and New devices are z-wave plus as this Aeotec Mulitsensor 6. Making a work around for this to work on outdated hardware should not be the focus, which it’s not even if you request it. Vera has to keep on moving forward and I think we all want that.

I’m on UI7 by the way and have no more complaints then I did with UI5. Things are different is all, people don’t like change.

[quote=“MNB, post:31, topic:187238”]Marc,
Any rough idea time wise as to when the user base might expect an update that incorporates this new sensor?

Mine arrived today. I’m on UI7… Any idea when this will be functional?

[quote=“Aaron, post:33, topic:187238”]All the UI7 comments are similar to:
“Unstable, I had to go back to UI5”
“Every new build breaks something they just fixed or something else in core functionality”
“My Vera Edge came with UI7 but it was unusable, I put on UI5 and much happier”

I’m waiting for comment like:
"UI7 is much better than UI5 in so many ways, let me tell you… "
“Man I’m glad I moved to UI7”
“The Vera team has really got it right now”[/quote]

It’s been about nine months since I’ve been on UI5 (so I can’t compare UI5 to UI7) - but I can tell you that, with the June update, UI7 had all of my devices (around 100) working without errors. That is until I installed four of the new 6in1 Multisensors from Aeon Labs. These devices do throw an error, though the temperature and humidity sensors are working. I’ve opened up a ticket with Vera and they claim to be working on support for them. I do think that UI7 has matured to the point that it will work fine for most people.

Multisensor6 has been released.
All pre-orders are now fulfilled and regular sale starts Tuesday, Jun 30.

MAP : $49.99

http://www.thesmartesthouse.com/products/aeotec-by-aeon-labs-z-wave-5-in-1-multisensor

Caution :
manufacturer does not include batteries !
TheSmartestHouse include the batteries ( 2 x CR123A ) for the first 100 orders.

[quote=“ZW-Tom, post:11, topic:187238”][quote=“Aaron, post:1, topic:187238”]Looks like this thing does all sorts of stuff… http://aeotec.com/z-wave-sensor

Anyone tried one, or know if Vera UI5 will actually support all the functions properly?[/quote]

I received my new MultiSensor 6 today, but it installaed as a GenericIO device. To get it working, I did the following with my VeraLite running UI5 Ver-1.5.672.

Under the Advanced Tab, change the following:

device_type:
DELETE: urn:schemas-micasaverde-com:device:GenericIO:1
ADD: urn:schemas-micasaverde-com:device:MotionSensor:1

device_file:
DELETE: D_GenericIO1.xml
ADD: D_MotionSensor1.xml

Hope that helps,
Tom[/quote]

Hi Tom,

Would you please mind sharing how you added this as a GenericIO device? I have tried to pair mine and for the life of me cannot get my Vera Lite running UI5 Ver-1.5.672 to recognize the MultiSensor 6 in any way, shape, or form. I Google’d how to add a GenericIO and nothing I’ve seen is working. Thanks in advance!!

Dave

I have figured out how to get the MultiSensor 6 to work on VeraEdge UI7.

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.

The MultiSensor 6 should now be working. You will have a child device called “_GET_LANG(generic_sensor,sensor)”. This is the UV sensor and is not supported by Vera.

Some final comments on the VeraLite and UI5.
I originally installed the MultiSensor on my VeraLite using the instructions I posted before. However over time, my Z-Wave functionality degraded. Other devices such as switches and automation controlled by scenes stopped working. I could get things back to normal by rebooting Vera, but overnight it would degrade again. I setup an auto-reboot scene to reboot Vera in the A.M. and P.M. but that did not solve the problem, it just slowed the degrading time. The more a device switch is used, the worse it gets. I even had one switch loose connection permanently. The switch is in high use throughout the day. It may be caused by the 500 series chip in the MultiSensor 6 causing problems with the older z-wave devices in the same network, I don’t know. On Monday I removed the MultiSensor 6 from my VeraLite and have not had any problems since.

I have now switched over to the VeraEdge, and with the recent updates to UI7 everything is working including the MultiSensor 6 using the above procedure. ;D

Tom

I can confirm… Following these directions on the VeraLite led to a complete lockup. May consider upgrading to the edge and selling the lite. What the advantages to upgrading besides the sensor working better?