Domoticz

Solution

RB87 wrote:The issue has been resolved by exchanging the sensor for a new one. This one reacts as described on the motion sensor and burglar state.

Thank you all for your assistance, because of this Aeotec concluded quickly it was a faulthy sensor.

Kind regards

Problem state

Versions used:
- Domoticz: V3.6959 (beta)
- OpenZWAVE: 1.4-2435-gc61d20d-dirty

Hardware used:
- RaspPi 2
- Aeotec ZW090 Z-Stick Gen5
- Aeotec ZW100 MultiSensor 6

Related topics found/studied
- https://www.domoticz.com/forum/viewtopi ... =24&t=5545

Issue
Motion Sensor is not found/working or responding.

Hi, I think the motion sensor is the one on Device ID 70 (it was named differently and i changed the device icon before, original it was a light switch). Looking at the timestamp you can see it wasnt triggered for a while now and haven't been triggered even once. I included it thourgh the node include of Domoticz.

In version 1.3 of OpenZWAVE i see the following line meaning the multisensor 6 of Aeon Labs should be working
Fixed issue #467 - Fixed Aeon Labs Multisensor Gen5 (Justin)

I've changed the sensor data to Binary Sensor report, nothing changed.

I've changed the sensor to enable polling, nothing changed regarding the motion sensor.

I've changed the group1 interval and the wake-up interval to 300 sec.

The sensor is powered through USB.

The rest of the sensors seems to be working out of the box.

Anyone knows how to enable the Motion Sensor? Help is appreciated! Thanks.

There has been a change to the way the sensors work. The device you need to note is shown as your device '75'. The Aeotec Multisensor 6 which also now appears as an "Alarm Type: Burglar 7 (0x07)". The motion & vibration detection is working as follows:
In a 'normal undisturbed state', it reports 'Event: 0x00 (0)'
when 'motion' has been detected, it reports 'Event: 0x08 (8)'
when 'vibration' has been detected, it reports 'Event: 0x03 (3)'

Some simple LUA code (Device) illustrating how it can be used:
I have same sensor and this is working just fine on my install. Polling is not required to be turned on - the rest of the settings match mine.

rjblake wrote:There has been a change to the way the sensors work. The device you need to note is shown as your device '75'. The Aeotec Multisensor 6 which also now appears as an "Alarm Type: Burglar 7 (0x07)". The motion & vibration detection is working as follows:
In a 'normal undisturbed state', it reports 'Event: 0x00 (0)'
when 'motion' has been detected, it reports 'Event: 0x08 (8)'
when 'vibration' has been detected, it reports 'Event: 0x03 (3)'

Some simple LUA code (Device) illustrating how it can be used:

Code: Select all

-- Script To Parse AEOTEC MultiSensor 6 
--
-- The following need updated for your environment get 'Name' off the Device tab. 
local sensorMotionMS01 = 'VibrationMotion [MS01]'
--
 
commandArray = {}

if devicechanged[sensorMotionMS01] then
    sensorValue = tonumber(otherdevices_zwavealarms[sensorMotionMS01])
    if sensorValue == 3 then
        print("Sensor: VIBRATION ALERT")
    elseif sensorValue == 8 then
        print("Sensor: MOTION ALERT")
    elseif sensorValue == 0 then
        print("Sensor: BACK TO NORMAL")
    end
end

return

I have same sensor and this is working just fine on my install. Polling is not required to be turned on - the rest of the settings match mine.

thanks for you reply! Seems like Event: 0x03 (3) isnt clearing.. it will stay on this event.

With your script i do get a vibration alert when i pick the sensor up though.

any advice? Or maybe you can take a screenshot of your settings for the sensor, i think that can help!

Below picture seems wrong, sensor is off, what ever i do i dont get it to ON. Any suggestions?

Thanks! i changed my settings to the same but still no luck. Can you post a screenshot of the /ozwcp/cp.html > MultiSensor > Current values for me? I have no clue what can be the issue/difference

And how did you add this sensor? when i add it securely after a hard reset of the controller, i saw status 0x08! Before i could change the config to Binary sensor report is changed and stayed at status 0x03. The sensor is in ON status now though, so that seems to be improved.

Also the mesh network seems bad, or isnt it?

I did not add as secure. Perhaps try adding normally and make any changes using Domoticz and not the OZWCP.

Thanks! I don't see to see your controller in the OZWCP, why is it missing? When i remove the sensor from Domoticz it doenst show the removal in the OZWCP which makes it out of sync (sensor responds for certain events but reports on old name).

I did a reset of the controller through the zensys-tools. I also get this error in the OZCP all the time:

Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)

Node002 is the MultiSensor.

This is so totally fucked now... this doesn't make any sense. A hard reset is constantly needed to remove old devices, shouldn't be that hard right?

I'am almost giving up, at least removing all ZWAVE stuff of this domoticz installation... will start to re-configure it at a different installation.

My Controller is there, just not in the images as didn't capture all devices (nor relevant). What firmware version do you have on the MultiSensor? V1.07 or v1.08?

v1.07

Don't really have much else for you - I'm using same firmware, same controller and it has worked without issue since I installed. I add/remove using Domoticz and only use the OZWCP when I need to check things. All config is done using Domoticz

I recently purchased two of these things and went through the same issue. They are not supported properly in OpenZwave yet and I never got the motion working right. I returned them. These seem to be OK for temp, LUX, but motion does not work properly at all.

It is so dissapointing. They are small, USB powered and do a lot. Will be an amazing sensor for Domoticz when it is implemented by OpenZwave correctly.

As a further issue, I tried two other name brand usb plug in motion sensors. They both used an almost identical chipset and had motion detection issues as well

I have them several months and they work flawlessly. Also the motion part.


Verzonden vanaf mijn iPad met Tapatalk

schulpr wrote:I have them several months and they work flawlessly. Also the motion part.


Verzonden vanaf mijn iPad met Tapatalk

As in the burglar alarm changes state of event?

I am not having issues with multisensor 6 either. Same setup, but I have been using RaZberry as controller.

Motion detector is working fine for months already.

I have a switch added to the MultiSensor's motion sensor device and it keeps updating ok. Turns on when there is a movement and changes its status to off after some 4 minutes if there is no other movement.

FW version of the sensor is 1.07

I haven't been using the new 0x07 burglar device in my scripts at all, though it seems to be updating correctly as well. I am only referring to the manually added switch in all my scripts and have been detecting its on/off states.

Just for the record - Domoticz version is 3.6838 but I have not noticed any issues with other versions.

i'am not sure of this issue is related: https://github.com/domoticz/domoticz/issues/1107

When i revert back to stable using: ./updaterelease, the data for the Alarm Type: Burglar 7 (0x07) says 3, now instead of 0x03

There should be no difference between controllers (so an aeotec/zwave.me/razberry, would make no difference, only maybe for reception/transmission/rf-noise)

Tested the motion sensor... working good here
Make sure you enabled accept new hardware, you should get a new alarm sensor (burglar = 7)
For a explanation of the values see this excellent post, or see the "technical" manual..

Also the switch labeled "sensor" with the ID ending on '00' get's ON for motion, and OFF when there is no motion

Also check your parameters, ( #3 is set to 240 by default, = motion of after 4 minutes of no motion), and command #5 = basic set
And make sure your controller (node 1) is in Group 1 of the multisensor

gizmocuz wrote:Tested the motion sensor... working good here
Make sure you enabled accept new hardware, you should get a new alarm sensor (burglar = 7)
For a explanation of the values see this excellent post, or see the "technical" manual..

Also the switch labeled "sensor" with the ID ending on '00' get's ON for motion, and OFF when there is no motion

Also check your parameters, ( #3 is set to 240 by default, = motion of after 4 minutes of no motion), and command #5 = basic set
And make sure your controller (node 1) is in Group 1 of the multisensor

Thanks ill try that!

accept new hardware was already enabled in the settings.

How do you put the controller in group #1 same with the sensor? Is this ok?
And some logging:

2017-03-20 20:11:25.356 EventSystem: reset all events...
2017-03-20 20:11:25.362 EventSystem: reset all device statuses...
2017-03-20 20:11:25.363 EventSystem: Started
2017-03-20 20:11:25.856 OpenZWave: Starting...
2017-03-20 20:11:25.866 OpenZWave: Version: 1.4-2228-gbce4a88-dirty
2017-03-20 20:11:25.866 OpenZWave: using config in: /home/pi/domoticz/Config/
2017-03-24 10:48:01.447 Error: OpenZWave: Driver Failed!!
2017-03-24 10:48:37.527 Incoming connection from: 192.168.0.4
2017-03-24 10:49:24.452 OpenZWave: Closed
2017-03-24 10:49:25.956 OpenZWave: Starting...
2017-03-24 10:49:25.956 OpenZWave: Version: 1.4-2228-gbce4a88-dirty
2017-03-24 10:49:25.956 OpenZWave: using config in: /home/pi/domoticz/Config/
2017-03-24 10:49:25.961 Error: OpenZWave: Driver Failed!!
2017-03-24 10:49:58.465 OpenZWave: Closed
2017-03-24 10:50:01.978 OpenZWave: Starting...
2017-03-24 10:50:01.978 OpenZWave: Version: 1.4-2228-gbce4a88-dirty
2017-03-24 10:50:01.978 OpenZWave: using config in: /home/pi/domoticz/Config/
2017-03-24 10:50:02.190 OpenZWave: Driver Ready
2017-03-24 10:50:02.213 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2017-03-24 10:50:02.213 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SENSOR MULTILEVEL, Label: Temperature, Instance: 1
2017-03-24 10:50:02.213 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SENSOR MULTILEVEL, Label: Luminance, Instance: 3
2017-03-24 10:50:02.214 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SENSOR MULTILEVEL, Label: Relative Humidity, Instance: 5
2017-03-24 10:50:02.214 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: SENSOR MULTILEVEL, Label: Ultraviolet, Instance: 27
2017-03-24 10:50:02.216 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: ALARM, Label: Alarm Type, Instance: 1
2017-03-24 10:50:02.216 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: ALARM, Label: Alarm Level, Instance: 1
2017-03-24 10:50:02.216 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: ALARM, Label: SourceNodeId, Instance: 1
2017-03-24 10:50:02.217 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: ALARM, Label: Burglar, Instance: 1
2017-03-24 10:50:02.217 OpenZWave: Value_Added: Node: 3 (0x03), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2017-03-24 10:50:05.051 Error: Webserver: File '/images/General.png': No such file or directory (2)
2017-03-24 10:50:14.771 OpenZWave: All Nodes queried (Some Dead)
2017-03-24 10:50:14.771 OpenZWave: Received Node Dead notification from HomeID: 4149631228, NodeID: 3 (0x03)

2017-03-24 10:51:00.350 OpenZWave: Received timeout notification from HomeID: 4149631228, NodeID: 3 (0x03)

2017-03-24 10:58:29.241 User: Admin initiated a switch command (11/MS-Motion/On)
2017-03-24 10:58:29.241 Error: OpenZWave: Internal Node ValueID not found! NodeID: 3 (0x03), instanceID: 0