Devolo zwave motion sensor mt02647 binary sensor always triggered

[gerald (Gerald Public)]

Hi,

i have one of these Devolo mt02647 Motion Sensors i would like to include in my setup - the connection is working well, i get values for temperature andso on, but the motion detection itself is not working correctly.

i understand the binary sensor is the motion on/oiff switch - this switch is always on and never changes - i have tried a couple of setting combinations (with operation mode etc…) but i couldnt get it to work - does anyone know the correct settings? plz help? thx…

System Openhab2 stable on an rpi3

thx, greets
Gerald

[rlkoshak (Rich Koshak)]

Not all motion sensors go to OFF. They just publish ON commands when motion is detected. You will have to write a Rule to set the Item linked to the motion sensor channel to OFF after a time.

Design Pattern: Motion Sensor Timer

Edit: Updates for OH 4 Please see Design Pattern: What is a Design Pattern and How Do I Use Them for details on how to use DPs. Problem Statement Many motion detectors only report ON when they detect motion but do not send a corresponding OFF after no motion has been detected after a period of time. In addition, often one wants to control a device like a light for a certain period after the last motion is seen, not after the motion sensor goes to OFF. Therefore one needs to keep a Contact OPEN…

[gerald (Gerald Public)]

hmm, thanks for the reply, the issue is, that it stays on the whole time, means the binary sensor is always active

[rlkoshak (Rich Koshak)]

The state in OH reflects the last reported state from the device. If the device never reports OFF then the channel and linked Item will also never show as OFF. So you have to turn the Item OFF yourself using a Rule or Expire Binding. If you watch the zwave logs (you may need to turn on debug) I’m certain you will see that the device is reporting ON when motion is detected and each ON gets sent to the Item as an ON command.

Everything in OH works on events. An Item staying ON does not mean that the sensor is always active. It just means the sensor is not sending OFF events.

[5iver (Scott Rushworth)]

@gerald

i understand the binary sensor is the motion on/oiff switch - this switch is always on and never changes - i have tried a couple of setting combinations (with operation mode etc…) but i couldnt get it to work - does anyone know the correct settings? plz help? thx…

This device does send ON/OFF. Parameters 8 and 9 look to be the ones that would affect the timeout. Try adjusting these, and if the device is still not reporting there may be an issue to work through. It looks like this is a battery powered device, so you will likely need to wake it up to get the configuration changes to take affect.

[gerald (Gerald Public)]

yes, you are right, the device sends on and off - i solved it in the meantime, the problem was the default sensitivity setting, it was 80 - to get it working correctly im using now 10 to 12 --> now it sends off as expected…
Thanks for the help, your infos pointed me in the right direction…

greets
Gerald

[Holger_Rausch]

hi gerald,
setting the PIR sensitivity seems strange for me, because this is the sensitivity of the PIR sensor as the name stated I think what you want to have is setting the parameter 7 to a decimal value of 22, which results in the on/off behaviour, see below.

2018-08-15 08:32:07.670 Info, Node003, Received encapsulated multi-command from node 3
2018-08-15 08:32:07.670 Info, Node003, Received Battery report from node 3: level=100
2018-08-15 08:32:07.670 Detail, Node003, Refreshed Value: old value=100, new value=100, type=byte
2018-08-15 08:32:07.671 Detail, Node003, Changes to this value are not verified
2018-08-15 08:32:07.671 Info, Node003, Received SensorBinary report: Sensor:12 State=On
2018-08-15 08:32:07.671 Detail, Node003, Refreshed Value: old value=false, new value=true, type=bool
2018-08-15 08:32:07.671 Detail, Node003, Changes to this value are not verified
2018-08-15 08:32:07.671 Info, Node003, Received SensorMultiLevel report from node 3, instance 1, Luminance: value=93%
2018-08-15 08:32:07.671 Detail, Node003, Refreshed Value: old value=94, new value=93, type=decimal
2018-08-15 08:32:07.671 Detail, Node003, Changes to this value are not verified
2018-08-15 08:32:07.672 Info, Node003, Received SensorMultiLevel report from node 3, instance 1, Temperature: value=77F
2018-08-15 08:32:07.672 Detail, Node003, Refreshed Value: old value=76, new value=77, type=decimal
2018-08-15 08:32:07.672 Detail, Node003, Changes to this value are not verified
2018-08-15 08:32:07.672 Info, Node003, End of encapsulated multi-command from node 3
2018-08-15 08:32:07.672 Detail, Node003, Notification: ValueChanged
2018-08-15 08:32:07.681 Detail, Node003, Notification: ValueChanged
2018-08-15 08:32:07.690 Detail, Node003, Notification: ValueChanged
2018-08-15 08:32:07.701 Detail, Node003, Notification: ValueChanged
2018-08-15 08:32:31.169 Detail, Node003, Received: 0x01, 0x0e, 0x00, 0x04, 0x00, 0x03, 0x08, 0x8f, 0x01, 0x01, 0x04, 0x30, 0x03, 0x00, 0x0c, 0x4a
2018-08-15 08:32:31.169 Detail,
2018-08-15 08:32:31.169 Info, Node003, Received encapsulated multi-command from node 3
2018-08-15 08:32:31.169 Info, Node003, Received SensorBinary report: Sensor:12 State=Off
2018-08-15 08:32:31.170 Detail, Node003, Refreshed Value: old value=true, new value=false, type=bool
2018-08-15 08:32:31.170 Detail, Node003, Changes to this value are not verified
2018-08-15 08:32:31.170 Info, Node003, End of encapsulated multi-command from node 3
2018-08-15 08:32:31.170 Detail, Node003, Notification: ValueChanged

[klausO (Klaus Ostwaldt)]

Hello Holger,
could you please explain, how you get from the descripted binary values to the decimal value of 22 (sugested in the config-parameters ist 21).
I´m not a developer and the description seems a bit spooky for me…
thanks in advance
Klaus
btw: 22 is not working in my case
but 21 isn´t working either…

this is the description of Parameter 7 (Customer funktion):
Parameter 7 Customer Function.

Available_Bits_for_Z110_Model Default Recommended Bit0: unused for Z110 Model 0 0 Bit1: unused for Z110 Model 0 0 Bit2: unused for Z110 Model 1 1 Bit3: Disable send out BASIC OFF after door closed. (1:Disable, 0:Enable) 0 0 Bit4: Notification Type, 0: Using Notification Report. 1: Using Sensor Binary Report. 0 1 Bit5: Disable Multi CC in auto report. (1:Disable, 0:Enable). 0 0 Bit6: Disable to report battery state when the device triggered. (1:Disable, 10 0:Enable). 0 0 Bit7: unused for Z110 Model 0 0

Comments / Tips for this device from the community:

• Setting this Parameter to 20 is from user side wanted as this enables Binary Sensor to report OPEN / CLOSE status by changing Bit 4

The calculation from the recommended column is: Bit7 to Bit0 = 000100100 Binary which is euqal to 20 decimal

[klausO (Klaus Ostwaldt)]

…to make it a bit easier for all who have the same problem…
could anyone post the correct configuration settings?
Mine are (not working):
2: basic set level: -1
3: PIR sensitivity: 80
4: Light threshold: 99
5: Operation Mode: 4
6: Multi-sensor function switch: 21
7: Customer Function: 20
8: PIR re-detect interval time: 3
9: Turn of the light time: 4
10: 11: 12: 13: Auto-reports are all 12
20: Auto-report Tick Interval: 30
21: Temparatur Differential report: 1
22: Illumination Differential report: 0
Thanks in advance
Klaus

[gerald (Gerald Public)]

This are my settings, its working with that since March…

Only differences:

• 3: 5 - 80 is too high a lot, this was my initial problem
• 4: empty
• 5: 12
• 7: 22

Good luck, greets Gerald

[klausO (Klaus Ostwaldt)]

Hello Gerald,

now I tried your settings and it works perfect but as I checked the log I saw, that the ON/OFF-sequences were shown since this afternoon with my settings too...

So it seems, that it takes a long time until the z-wave-controler has trained the sensor.

I´m using an Aeon Z-wave-stick in a cubietruck.

thanx a lot for your fast reply

Klaus