Fibaro Motion Sensor vs Aeon Labs Multisensor

[Guest Paweł Świerczyński]

Little challange :

Fibaro Motion Sensor vs Aeon Labs Multisensor

Aeon Labs Multisensor

*Motion sensor.

*Humidity sensor.

*Thermometer.

*Light sensor.

*Indoor sensor.

*Outdoor sensor

Fibaro Motion Sensor

*Motion sensor.

*Thermometer.

*Light sensor.

*Indoor sensor.

*accelerometer

What do you think, anyone comparing these two devices?

[MalvinYNJ 4]

Go for both and give a verdict!

[Dalle1985 16]

I have opted mainly for the Aeon. I have two Fibaro motion sensors and 6 Aeon labs. I like the Fibaro sensor very much because of it's design and footprint. But there are other issues which sways me towards the Aeon. Anyway, heres my thoughts:

- The Aeon runs off 4 AA batteries and drains them in 4 months, the Fibaro runs off a single battery and runs for 12 months, point Fibaro

- The Aeon has USB power supply which makes it a routing device and gives more frequent data update, point Aeon

- The Humidity sensor is far more useful to me than the accelerometer will ever be as the biggest earthquake ever in my area was a 2.8! Point Aeon

- The communication issues is a bigger problem with the fibaro, more often turning into temperature sensors. Point Aeon

- Size - point Fibaro

- Mounting, the Aeon is more solidly fixed, I've had the Fibaros go ballistic because it was mounted too close to a door and gave a tiny jolt whenever the door closed - Point Aeon

- Weather resistant - Point Aeon

It is a matter of taste, but the Aeon is the best for me. I think the "cats eye" is a silly function and I don't want my motion sensors to light up the room, but besides that, I think the Fibaro unit looks a lot better - it just isn't enough to make up for the deficiencies. The fact that I can't power it via USB is a deal breaker for me. I want updates for the light every 30 seconds or so because it is used in my scenes, but if I change the update interval of the Fibaro unit to 30 seconds, it will drain the batteries in less than a month. Therefore, I only use the fibaro sensor where I don't need the Lux reading. Also, the fact that there is no humidity sensor, means that I can't use it to control ventilation and windows - also a deal breaker. Humidity is more important for me than vibration (you'll notice that an earthquake is going on even without the accelerometer, believe me!).

[JanJoh 1]

- The Aeon has USB power supply which makes it a routing device and gives more frequent data update, point Aeon

Are you sure?

When i asked my retailer, he said that the Aeon does NOT become a routing device even with constant power.

[kallec 10]

I have asked Aeon Labs if it can act as a router and if you had to change any parameters. Got the following answer:

Yes, it can act as a router if you power it with USB. But you needn't to change the parameters. What you need to do is to re-include it to the network.

As I understand it you should include it with USB power attached.

[JanJoh 1]

I have asked Aeon Labs if it can act as a router and if you had to change any parameters. Got the following answer:

Yes, it can act as a router if you power it with USB. But you needn't to change the parameters. What you need to do is to re-include it to the network.

As I understand it you should include it with USB power attached.

Oh?

Interesting. Thanks!

Then mine should be routing, given that I re-include them quite often due to the #(/)&%#/&%/& buggy Fibaro software.

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[Dalle1985 16]

I have asked Aeon Labs if it can act as a router and if you had to change any parameters. Got the following answer:

Yes, it can act as a router if you power it with USB. But you needn't to change the parameters. What you need to do is to re-include it to the network.

As I understand it you should include it with USB power attached.

Oh?

Interesting. Thanks!

Then mine should be routing, given that I re-include them quite often due to the #(/)&%#/&%/& buggy Fibaro software.

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

I have a zniffer and it shows that they are actively participating in the Mesh, but yes, only when included while being powered by USB. I wasn't aware it was the case, I just reincluded all of them when they were connected over USB as the Fibaro box wouldn't accept the fact that they were no longer battery operated and was very persistent that all of them were running out of juice constantly... Some more flexibility in the device configuration would be lovely. Then I could also fix the damned becomming a temperature sensor issue that especially the Fibaro motion sensors are prone to. I've tried posting a new json package to the device to return it to motion sensor, but it refuses to accept the package. So as Fibaro can't get their z-wave engine to work (don't really understand why that affects this) they should at least give us the option to change the devices manually - an expert mode with a disclaimer if that would make them more comfortable. Anyway, I can't really be bothered as I am building my own "Z-waving" engine on a Raspberry to suit my needs!

[dawiinci 5]

...

- The communication issues is a bigger problem with the fibaro, more often turning into temperature sensors. Point Aeon

My Aeon is turned to a temperature sensor as well. Same as Fibaro.

[JanJoh 1]

...

- The communication issues is a bigger problem with the fibaro, more often turning into temperature sensors. Point Aeon

My Aeon is turned to a temperature sensor as well. Same as Fibaro.

No way to avoid dthat completely with anything other then the (/%/&¤/(/(/#&(/!/& 4.x betas...

[Dalle1985 16]

...

- The communication issues is a bigger problem with the fibaro, more often turning into temperature sensors. Point Aeon

My Aeon is turned to a temperature sensor as well. Same as Fibaro.

No way to avoid dthat completely with anything other then the (/%/&¤/(/(/#&(/!/& 4.x betas...

My Aeons have the same bug, but out of the Aeons I have (and I have a few) it has only happened twice, however, the Fibaros have done it several times. I have stopped deleting and reincluding them - they still perform their function, they just look sh*t doing it. The Aeons I have never reincluded, and only two are showing up as thermometers.

[alex88 71]

I would be nice if someone could make an all-in-one with the best parts of the Aeon and the Fibaro, but until then (after weighing up the pros and cons) and having 9 Fibaro versus 4 Aeon’s I regret not buying more Aeon’s in place of the Fibaro’s.

[Guest gembrain]

2015 will hopefully see some major advances....

Multi Sensor from Bosch apparently with Zigbee AND Z Wave built in.

Please login or register to see this link.

This little thing caught my eye as well....Single unit to go in a back box with inputs for 4 switches.

Please login or register to see this link.

Only problem is all the different communication standards! If Fibaro are going to have a chance long term they will need to address this.

[Dalle1985 16]

The Osram Lightify is basically zigBee connecting to a wifi bridge - so very similar to Philips Hue. The big thing here is having wifi connectivity and a good API. As long as manufacturers can't agree on one common protocol, the ability to integrate through different protocols is key. That way, it doesn't really matter what frequency the actual switching is done on, as long as you can collect the data with a reliable API.

I actually think this is one of the HC's strongest points. The API is simple to use and you get a lot of information from it - also, the response is (usually) very fast (I have a round trip time of about 70 ms for the HC). This is something the likes of Philips and Netatmo could learn from. The Hue bridge has a response time of approx. 250 ms, but you have to poll lights or groups individually to get their status. I have 6 groups, so the absolute minimum is a response time of 1500 ms to get status returned for all six groups. Furthermore, the response time slows by about 50 ms for each extra light you add. I have 29 now and need an additional 10 - which will bring me up to a round trip time of 2,5 seconds. That means that when I switch a light, it takes 2,5 seconds before it changes status on my interface.

So responsiveness of a http API is more important to me, than having a common communications standard - because that battle will take years to conclude.

[Guest gembrain]

Thanks Dalle - useful info on those trip times. I wasn't aware the Hue would be so slow.

[Dalle1985 16]

I've just found a solution, it isn't really perfect, but it works. I've just updated my Bridge and part of the update was a change to the lights api which means I can retrieve the status of all lights at once. I now just call this resource and then use an id of a single light in each group to return the status of the lights. This is far from perfect, but it works and the responsetime has gone down from 1600 ms to 70 ms!

[Guest gembrain]

Thanks Dalle - think we got somewhat off topic but that is good news. Goes from being not acceptable to very practical!

[rantta 2]

Why does these both have temperature limit on -20°C?

Is there any decent Z-wave temperature sensors that would actually work on winter, or do I have to build one with dallas sensor?

[carmar74 4]

I tried them out yet, because their design is not attractive, but the sensors Philio seems that they are 100% reliable and have no manufacturing defects such as the Motion Sensor Fibaro and Multisensor Aeonlabs

[rantta 2]

I tried them out yet, because their design is not attractive, but the sensors Philio seems that they are 100% reliable and have no manufacturing defects such as the Motion Sensor Fibaro and Multisensor Aeonlabs

Temperature: -10 to +70°C

[carmar74 4]

I the temptation to test it ...

Please login or register to see this image.

/emoticons/default_icon_mrgreen.gif" alt=":mrgreen:" />

Please login or register to see this attachment.