New Aeon Labs Multisensor Gen5 not supported in OpenZwave ?

[MultiZW074]

Hello guys,

I have the same problem. First thought the hardware of the sensor was defect but when reading this forum i assume the device is just not supported by the software. I have tried OpenWave software and Z-way software. They both cannot handle the motion sensor (instant). All functions (humd/temp/lux) do work fine and i am able to poll the sensor and read values that trigger actions. This polling doenst work stable regarding the motion sensor. I havent found the logic behind this instability, but sometimes when polling the general purpose sensor (motion) an event is triggerd and sometimes not. The motion sensor needs to be instant (fire signal when triggered) and set a light switch to ON inmediately.

[Het-Licht]

In short, don't buy the Aeon Labs Multisensor, it's crap....

[IDavid]

@het-licht
Parameter 3 defines the timeout for motion, in my case 240 seconds.
Make sure you stay out of range in between motions because it will directly sense motion. I guess that is a non brainer

When configuring a new multi sensor, put it on USB power and make sure polling is enabled.

That way, the device remains active and all settings you change and send to device will surely be changed.

[MultiZW074]

@IDavid
Do you mean polling should be enabled for configuring the sensor? That contradicts with info from Aeon Labs:
USB power gives you the greatest control over the Multisensor; the sensor will never go to sleep and you can configure the sensor from your Z-Wave network whenever you want.

Also as far as i know now, the motion sensor should work instantly and not by polling the sensor. Do you think the same?
What do you mean by stay out of range? When motion is sensored a new signal will be send and the 240 sec start again.

[Het-Licht]

@het-licht
Parameter 3 defines the timeout for motion, in my case 240 seconds.
Make sure you stay out of range in between motions because it will directly sense motion. I guess that is a non brainer

When configuring a new multi sensor, put it on USB power and make sure polling is enabled.

That way, the device remains active and all settings you change and send to device will surely be changed.

I did all that so it should work...

[IDavid]

@MultiZW074

I agree that it should not be a requirement for configuring the device that polling is enabled. USB power should prevent it from going into sleep mode. It was just an extra measure in case the sensor would for some reason, to awake it in that case.

Motion indeed is triggering a message instantly to the controller, so indeed no polling for that.
Polling is only necessary for getting info from the temp/lux/humidity sensor, although I would expectthat after the reporting interval (720 group 1) the device would proactively send that date. I need to verify this in practice.

Yes, out of range, to give the device an opportunity to set the sensor 'off'' after the interval of 240 seconds you set by parameter.
Staying out of range makes sense, but it could have been the case the device was next to you on a table when testing motion and then of course you will never see it goin off.

@ Het-licht, the sensor is not necessary crap, it is just not fully supported in 'OpenWave' which is also the foundation of 'Domoticz' (the Z-wave part of it). It's up to us to improve the OpenWave support, so that's why i submitted a request with Openwave this morning.

[Het-Licht]

Thank you for the request. How did you manage that ? I would like to do the same for the siren that doesn't work...

[IDavid]

@Het-Licht. As posted by other member:

If enhancing the manufacturer details works you should submit a patch request to OpenZWave so they can add it to the default config. Its a great way to give back to the open source community and everyone benefits from your investigation.

Something like this should do the trick: https://code.google.com/p/open-zwave/is ... 20Modified

There is a button to submit a new issue (left upper corner).

[Het-Licht]

Well, I tought I fixed it, but unfortunatly not... When on USB power the sensor seems to work fine, but when on battery power it's fails.
It's reconized in the Nodes list and when I press the black button in the sensor status changes to awake but it doesn't report anything to domoticz anymore....

[xces]

I just included the device with my z-stick 2 (not capable of talking z-wave plus) the device shows as "006 (0x06)" unknown. It also shows "Not all Nodes have been Queried yet, OpenZWave not fully initialized yet!". I made the changes to the manufacturer_specific.xml prior to inclusion and rebooted the system. Still no success.. Any tips?

[Het-Licht]

Can you make a screenshot of the manufacturer_specific.xml?

[gizmocuz]

not all sensors send an 'off' signal... but i would expect in this case
if it does not, edit the sensor, and specify an off delay

[IDavid]

Parameter 3 specifies the timeout in seconds before sensor will send status off, according to description, so it will send 'off' status to controller.

Parameter 2000 specifies a wake-up time in seconds .

Both need a value. See example in config settings screenshots in this topic. That should make it work, even on battery, as tested by me.

[xces]

Well i just did a rather drastic method; reinstalled "KodiBuntu" which is the operating system running my Domoticz install. The reason for that being that i did some open-zwave fixes for Domoticz and i might installed to many packages and/or compiled too many open-zwave SVN versions (some with "make install" which should not be done).. And since I have a backup of all my scripts anyway, i thought to totally reset my (ahum) major z-wave network consisting of 2 devices :p (i have 8 new devices laying on my desk here; 3x Fibaro relay switch, 2x Fibaro dimmer, 1x Fibaro roller shutter, 2x Aeon Multisensor 5Gen). This time i am going to document the steps i did and hope to finish soon.

Currently updating 150 packages with "apt-get upgrade" after that it will be:
• Download open-zwave > patch "xml" > rebuild
• Download domoticz > patch "xml" > rebuild
• Add USB dongle

p.s. i also e-mailed Aeotec support, since both my Gen5 multisensors could not be 'firmware updated' via the method mentioned on the site of Aeotec. Since that document dates from somewhere half of 2014 i think they haven't updated their site yet with the new model and the firmware update process for the Gen5 is different.

edit: en klaar met compilen van de hele boel (systeem updaten, open zwave + domoticz downloaden en compilen) in 15 minuten, toch mooi zo'n Intel NUC, dat gaat als de brandweer.

[xces]

Ok, helaas geen succes...

Hier de log van Domoticz;

2015-03-01 20:05:09.287 Domoticz V2.2296 (c)2012-2015 GizMoCuz
2015-03-01 20:05:09.287 Startup Path: /home/vdhoven/domoticz/
2015-03-01 20:05:09.317 Secure Webserver started on port: 443
2015-03-01 20:05:09.317 Webserver started on port: 1981
2015-03-01 20:05:30.319 Hardware Monitor: Fetching data (System sensors)
2015-03-01 20:06:00.325 Hardware Monitor: Fetching data (System sensors)
2015-03-01 20:06:30.332 Hardware Monitor: Fetching data (System sensors)
2015-03-01 20:06:41.819 Incoming connection from: 192.168.1.110
2015-03-01 20:07:00.338 Hardware Monitor: Fetching data (System sensors)
2015-03-01 20:07:19.840 OpenZWave: Starting...
2015-03-01 20:07:19.840 OpenZWave: using config in: /home/vdhoven/domoticz/Config/
2015-03-01 20:07:19.956 OpenZWave: Driver Ready
2015-03-01 20:07:19.956 OpenZWave: New Node added. HomeID: 21827302, NodeID: 1 (0x01)
2015-03-01 20:07:19.956 OpenZWave: New Node added. HomeID: 21827302, NodeID: 2 (0x02)
2015-03-01 20:07:19.956 OpenZWave: New Node added. HomeID: 21827302, NodeID: 3 (0x03)
2015-03-01 20:07:19.956 OpenZWave: New Node added. HomeID: 21827302, NodeID: 4 (0x04)
2015-03-01 20:07:19.968 OpenZWave: Value_Added: Node: 2 (0x02), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2015-03-01 20:07:19.968 (Aeon labs Z-Stick) Lighting 2 (Unknown)
2015-03-01 20:07:20.302 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SWITCH MULTILEVEL, Label: Level, Instance: 1
2015-03-01 20:07:20.302 (Aeon labs Z-Stick) Lighting 2 (Unknown)
2015-03-01 20:07:20.303 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SWITCH MULTILEVEL, Label: Bright, Instance: 1
2015-03-01 20:07:20.303 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SWITCH MULTILEVEL, Label: Dim, Instance: 1
2015-03-01 20:07:30.344 Hardware Monitor: Fetching data (System sensors)
2015-03-01 20:07:42.254 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: INDICATOR, Label: Indicator, Instance: 1
2015-03-01 20:07:42.254 OpenZWave: Unhandled class: 0x87 (INDICATOR), NodeID: 3 (0x03), Index: 0, Instance: 1
2015-03-01 20:07:42.381 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Alarm Type, Instance: 1
2015-03-01 20:07:42.381 (Aeon labs Z-Stick) Lighting 2 (Unknown)
2015-03-01 20:07:42.382 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Alarm Level, Instance: 1
2015-03-01 20:07:42.382 (Aeon labs Z-Stick) Lighting 2 (Unknown)
2015-03-01 20:07:42.383 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2015-03-01 20:07:42.383 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2015-03-01 20:07:42.383 (Aeon labs Z-Stick) Lighting 2 (Unknown)
2015-03-01 20:08:00.350 Hardware Monitor: Fetching data (System sensors)
2015-03-01 20:08:08.355 Hardware Monitor: Stopped...
2015-03-01 20:08:22.385 (Aeon labs Z-Stick) Lighting 2 (Sensor)
2015-03-01 20:08:22.387 (Aeon labs Z-Stick) Lighting 2 (Alarm Level)
2015-03-01 20:08:22.388 (Aeon labs Z-Stick) Lighting 2 (Alarm Type)
2015-03-01 20:08:22.389 OpenZWave: Received timeout notification from HomeID: 21827302, NodeID: 4 (0x04)
2015-03-01 20:09:02.386 (Aeon labs Z-Stick) Lighting 2 (Sensor)
2015-03-01 20:09:02.387 (Aeon labs Z-Stick) Lighting 2 (Alarm Level)
2015-03-01 20:09:02.388 (Aeon labs Z-Stick) Lighting 2 (Alarm Type)
2015-03-01 20:09:02.389 OpenZWave: Received timeout notification from HomeID: 21827302, NodeID: 4 (0x04)
2015-03-01 20:09:42.386 (Aeon labs Z-Stick) Lighting 2 (Sensor)
2015-03-01 20:09:42.387 (Aeon labs Z-Stick) Lighting 2 (Alarm Level)
2015-03-01 20:09:42.388 (Aeon labs Z-Stick) Lighting 2 (Alarm Type)
2015-03-01 20:09:42.389 OpenZWave: Received timeout notification from HomeID: 21827302, NodeID: 4 (0x04)
2015-03-01 20:09:42.779 OpenZWave: Value_Added: Node: 2 (0x02), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2015-03-01 20:09:43.664 OpenZWave: Value_Added: Node: 2 (0x02), CommandClass: SENSOR MULTILEVEL, Label: Temperature, Instance: 1
2015-03-01 20:09:43.664 OpenZWave: Value_Added: Node: 2 (0x02), CommandClass: SENSOR MULTILEVEL, Label: Luminance, Instance: 3
2015-03-01 20:09:43.664 OpenZWave: Value_Added: Node: 2 (0x02), CommandClass: SENSOR MULTILEVEL, Label: Relative Humidity, Instance: 5
2015-03-01 20:09:44.795 (Aeon labs Z-Stick) Lighting 2 (Level)
2015-03-01 20:09:49.714 (Aeon labs Z-Stick) Lux (Unknown)

Hier de afbeelding met al mijn nodes;
001 = Controller
002 = Aeon Labs Multi Sensor (oud device)
003 = Woonkamer verlichgint
004 = Aeon Labs Multi Sensor Gen5


En daarbij horen deze devices:


De oude sensor heb ik na het maken van de screenshots pas geconfigureerd volgens de multi sensor guide.

USB Powered Multisensor:
Parameter 3: 240 (Timeout period of no-motion after motion sensor trigger)
Parameter 4: 1 (Enable PIR Motion Sensor)
Parameter 101: 224 (Sets sensors [Light, Humidity, and Temperature] to be reported in group 1)
Parameter 111: 240 (Sets the interval of reports for group 1)

Hier de manufacturer XML:


Wat ik nog niet geprobeerd heb is om de sensor 'awake' te maken dmv 3x te klikken op de knop voordat ik hem verder configureer. Hebben jullie nog andere tips?

[xces]

edit: na het typen van deze post verschenen er nieuwe devices;

Code: Select all

2015-03-01 20:19:43.860 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SENSOR MULTILEVEL, Label: Luminance, Instance: 3
2015-03-01 20:19:43.860 (Aeon labs Z-Stick) Lux (Unknown)
2015-03-01 20:19:45.120 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SENSOR MULTILEVEL, Label: Temperature, Instance: 1
2015-03-01 20:19:45.120 (Aeon labs Z-Stick) Temp (Unknown)
2015-03-01 20:19:45.360 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SENSOR MULTILEVEL, Label: Relative Humidity, Instance: 5
2015-03-01 20:19:45.360 (Aeon labs Z-Stick) Temp + Humidity (Unknown)

[xces]

wat nu op zich wel jammer is, is dat het devices tabblad niet groepeerd per hardware device. je ziet wel dat het bij de zstick hoort, maar niet onder welk device.

[Het-Licht]

Yeah, thats's a pain, don't understand why it has to be so many devices...

I emailed with Aeon Labs and they said the following :

You should only select one type of battery power, and must be included on USB power or battery power (sets different settings).

I believe you may have initially included the Multisensor on USB power, then switched to batteries without re-including the sensor which is most likely the root of your issue.

If you included it on battery power, then switched to USB, you would face the same issue on USB power.

I suggest that you re-include the sensor with the new power source.

[Het-Licht]

I think it's best to leave it all for a day before you go any futher with configuring the nodes...

[xces]

All sensors are detected, however the device is not het recognized in the zwave setup so i cannot set config parameters except 2000. Can someone post their manufacturer XML and alms.XML file?