New Topic

Zipato support center Topic Question Uncategorized

This object is in archive!

Is Aeon Labs Multisensor Gen5 supported? Any suggestions about manual configuration?

Boyan Krastev shared this question ago

Need Answer

Hello,

I just got Aeon Labs multisensor Gen5 (ZW074-C) and wanted to set it up to monitor motion and

humidity in my bathroom.

After spending few hours trying to set it up... I am step away of smashing it with a hammer... (or maybe the Zipabox).

Will throw a coin to see which device will die first ;)

Adding/removing.. and again adding/removing... lots of timeouts with strange messages about MANUFACTURER or GET_CC_VERSIONS

Aeon+Labs+Multisensor+Gen5+inclusion+failed+1

When device is successfully added it shows up as Aeon_Labs: 2 and below it "SENSOR_NOTIFICATION"

I believe device is functional but not supported out of the box with Zipato.

I have searched over the forum and read all messages about incorrect readings or strange motion events but

all info is about the previous version of the multisensor.

Gen5+-+SENSOR_NOTIFICATION

I think it will be possible to manually configure the sensor (meters/triggers) if anybody can bring some light on what and how may be compatible. Already tried setting it as "Generic sensor sensor" or Temeprature and humidity meter.

The event log shows that motion state is sent and also values... but different values (temp, lux, humidity) are seen all as "VALUE1" which is strange.

Gen5+-+Event+log

Anybody has a clue how to set it up manually?

@Zipato team: Any idea if it will be supported out of the box or maybe other problem on my end?

The same question

Replies (12)

Boyan Krastev ●

I have opened a ticket with Zipato support.

Don't know if they did something (no reply yet) but tried removing and adding the multisensor

one more time and now it is fully recognized.

Aeon+GEN5+Multisensor+working

Reply URL

Guest ●

Hello Bojan,

we just got it in our office yesterday, and our Z-wave developer was able to support it immediately.

Best regards,

Hrvoje

URL

Boyan Krastev ●

Hello Hrvoje,

Can you clarify if it was already supported or your developer(s) updated the device database?

On Wednesday evening I tried at least 20 times excluding/including the unit and all the time i got AEON_Labs: 2 detected.

Yesterday (Thursday) 1 hour after opening support ticket I tried removing/adding one more time and magically it was recognized?!

Is it just а coincidence?

Thanks,

Boyan

URL

HeroS - www.domotica-blog.nl ●

Oke great. Tried it yesterday and it don't work yet.

Reply URL

Machiel Kuitert ●

I have it properly added and it seems to work (0.9.999.4 firmware) and i added it really close to the zipabox.

The default settings make that sensor update come every 12 minutes. That might be ok but i have trouble seeing the device send motion updates when they occur. I will mess with it some more.

Reply URL

HeroS - www.domotica-blog.nl ●

Some problem..temp/lum/hum are coming. Motion is not working.

Please contact support about this (I already did)

URL

Boyan Krastev ●

It seems that gen5 multisensor is supported out of the box but the sensor itself is tricky.

Replayed the procedure few times to be sure.

It seems that the sensor should be about 1m from controller when including so the device is synchronized properly. Best would be to put it on something and not hold in hand.

I guess it has poor antenna or just mine is defective.

Once included and recognized properly I mounted it at its final place.

Then did network heal so routes are done as they should.

URL

HeroS - www.domotica-blog.nl ●

@Boyan,

Is the motion working?/How did you get it to work?

Reply URL

Boyan Krastev ●

It seems that Zipabox and Aeon Gen5 multisensor doesn't understand each other very well :)

So it might take you more than 10 times to join the device properly.

If it is seen as AEON_Labs: 2 then inclusion was not successful!

You should see it as AEON Gen5 Multisensor!

Aeon_gen5_1 Aeon_gen5_2

Then make sure PIR is enabled in configuration settings of device. If you don't see configuration as mine... then try again excluding/including the sensor.

Aeon_gen5_3

I know... it will make you crazy and start thinking about smashing the sensor... but try one more time.

Make sure the sensor is awake when setting new config.

To wake up the sensor hold the button for 3 or 5 seconds till led stays lit. (See the multisensor manual).

If you receive false positives about motion... try to lower sensor sensitivity.

Mine is located in the bathroom and although it is set to maximum sensitivity i find it a bit slow in detecting motion compared to Fibaro FGMS-001

Let me know if that helps.

URL

HeroS - www.domotica-blog.nl ●

Thanks! But still no motion.

Are you running on batteries?

URL

Boyan Krastev ●

Yes, it is on batteries.

Brand new, unpacked and inserted... now after 1 week running shows 80% available.

That leads me to next question... am i going to change batteries every 5-6 weeks?! :)

URL

Christopher Cheng ●

If you are still not getting any motion try setting "CMD on PIR Motion" to "Sensor Binary"

URL

Christopher Cheng ●

If you are still not getting any motion try setting "CMD on PIR Motion" to "Sensor Binary"

URL

Machiel Kuitert ●

I do see the "no motion" but it never changes. When I set a rule based on motion I do get an email everything there is motion. It just doesn't show in the interface.......

Reply URL

Boyan Krastev ●

I had the same problem but with one Fibaro FGMS-001 and again after excluding/including few times it was ok. I guess that remove/add procedure for Zipabox is something like reboot was for Windows 95 :)

Fixes the problem... at least temporary.

URL

Machiel Kuitert ●

Boyan,

Do you see the device the same way as i do?

It seems i have one "No name" item.

b9daa04222f742cfaf604bbc3df39f50

URL

Boyan Krastev ●

@Machiel

Yes, I have the "No name" node too... I believe it is either tamper or humidity trigger.

I do see motion state changes

Aeon_Gen5_motion

And here are my device manager nodes for the multisensor:

Aeon_Gen5_no_name

URL

Machiel Kuitert ●

It works. No idea what changed, i didn't add it again or anything.

URL

Boyan Krastev ●

@Machiel

It looks like that your configuration has been applied meantime.

That's why I told you to wake up the sensor when changing configuration so it gets applied immediately.

Another option is you changed some rule or disabled it? Did you do that?

I have another thread https://community.zipato.com/topic/lighting-rule-makes-motion-sensor-not-responding-marked-as-problem

where a rule makes sensor problematic and stays on "motion" forever till i disable the rule.

Maybe the same happens on your side but in state "no motion"

Any help on the problem on my other topic is highly appreciated.

URL

Machiel Kuitert ●

I did the waking up before setting the config as you suggested.

I just "lost" the motion signaling. No idea why. I dont seem to remember changing anything.

I have disabled all rules related to this device, no effect.

I also excluded and included the device again, no effect.

I also hit the "re-apply device descriptors", no effect.

I am about to give up and send the device back to the shop...

URL

Boyan Krastev ●

Try to exclude/include it on USB power.

I believe the problem is in Zipabox... not the multisensor itself. Maybe you can open support ticket and see what Zipato support will say.

URL

HeroS - www.domotica-blog.nl ●

Still not working here :(

Does anybody see the events ((no-)motion) coming in?

Reply URL

Boyan Krastev ●

Here is how i did it on mine box.

1. Firmware 0.9.999.4

2. Exclude the multisensor:

- Delete it from device manager.

- Go to "Add new device" and when says Excluding press the multisensor button and wait till system says "Device excluded... starting inclusion process"

- Cancel the operation here and don't include it.

- Synchronize Zipabox

3. Include the multisensor

- Go to add new device again (You may even reload the Zipato page before that)

- Before selecting ZWave, remove sensor battery wait a while then insert again and click on zwave to start process

- Follow instructions as usual to exclude and include the multisensor

4. After successful inclusion go to device configuration

- Make sure PIR is enabled

- Ensure cmd on pir motion is BASIC_SET

- Timeout after no motion: mine is 120

- Wake up interval: 8 mins (try with 15 min)

5. Save configuration and leave the sensor for an hour to ensure configuration is applied ( i recommend it to leave it on its final place - where it should be permanently)

Let me know if that worked for you.

URL

Machiel Kuitert ●

I have tried this....and have given up.

No luck for me. I purchased a fibaro multi sensor and that works immediatly as it should.

I have emailed the shop if there is a way i can return the device.

URL

Boyan Krastev ●

Fibaro's multisensor is smaller and nicer... but doesn't support humidity (which I need).

Aeon's multisensor was the only one which had humidity measurement :(

URL

Magnus ●

Is this device supported, or is this thread about another device?

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

QUESTION: Does zipabox support 500 series chips?

It’s built around the latest Z-Wave 500 series chip and firmware, providing a 50% greater wireless range and a 250% faster communication speed over previous Z-Wave products. It has AES 128 bit security encryption built right in.

You need a Z-Wave gateway which operates with the 500 series chip products to take full advantage of the device. Please consult the manufacturer of your Z-Wave hub to make sure it supports all MultiSensor 6 features.

Reply URL

quizzical ●

Yes, only pretty OLD zipaboxes don't have the 500 series chip.

So is the aeotec multisensor working properly now? Did anyone try the new version "multisensor 6" yet?

Reply URL

Jacob Wiqvist ●

Also interested in this sensor !

And once again a official statment? List off tested hardware?

Reply URL

derHelle ww.zipabox.de ●

Hi Jacob,

i tested this Sensor by myself and i got all values.

regards Helle

Reply URL

Jacob Wiqvist ●

Great to hear! And you have tested to change all parameters, values and they work?

And what do you think of the sensor, anything to compare to.

I am most interested of the motion sensing?

URL

derHelle ww.zipabox.de ●

Hi Jacob,

no i just did q quick test.

But from the look und feel i can say i can beat the Fibaro Motion Sensor.

regards Helle

URL

derHelle ww.zipabox.de ●

Hi Jacob,

no i just did q quick test.

But from the look und feel i can say i can beat the Fibaro Motion Sensor.

regards Helle

URL

quizzical ●

Thanks for the feedback derHelle! This new generation 6 multisensor sure looks nice so I'm happy to hear that it's working on the zipabox

URL

derHelle ww.zipabox.de ●

Hi Jacob,

no i just did q quick test.

But from the look und feel i can say i can beat the Fibaro Motion Sensor.

regards Helle

Reply URL

DaGrizzly ●

I had also the problem, the inclusion failed...

after reading a post of Helle, it worked : http://zipabox.de/noch-ein-neues-z-wave-gerat-ist-da-der-aeon-multisenor/

the Aeotec manual says: push the button one time for inclusion

working: pressing the button three times at the inclusion

regards

Grizzly

Reply URL