Aeotec multisensor 6 continually firing burglar alarm

Configuration Z-Wave
1

I have a MS 6 which has been in place for a year or so - running on standard CR123 batteries. Yesterday I changed it to use 3.0V (NOT 3.7v) rechargeable batteries - no other change.

Now every 15 minutes (wake up interval) it will always see that burglar state as 8, triggering a notiification alert I have set up on that condition.

4 minutes later, it will get a state 0 and then again on the wake up, go round again.

Could this be something to do with the batteries affecting the sensor in some way?

I’ve not tried putting back standard batteries, but does seem odd…

Here’s the log from OZW log file.

Currently running HA core 2021.5.5 version, OS 3.13 and the deprecated Z-Wave integration.

I’m not confident to upgrade to either the Z-save JS or new OS 6.1 - any thoughts?

2021-08-02 19:42:58.069 Detail, Node009,   Received: 0x01, 0x0c, 0x00, 0x04, 0x10, 0x09, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0x9a, 0x65
2021-08-02 19:42:58.070 Info, Node009, Received SensorMultiLevel report from node 9, instance 1, Temperature: value=15.4C
2021-08-02 19:42:58.070 Detail, Node009, Refreshed Value: old value=15.6, new value=15.4, type=decimal
2021-08-02 19:42:58.070 Detail, Node009, Changes to this value are not verified
2021-08-02 19:42:58.070 Detail, Node009, Notification: ValueChanged
2021-08-02 19:42:59.546 Detail, Node009,   Received: 0x01, 0x0b, 0x00, 0x04, 0x10, 0x09, 0x05, 0x31, 0x05, 0x05, 0x01, 0x4b, 0x97
2021-08-02 19:42:59.546 Info, Node009, Received SensorMultiLevel report from node 9, instance 1, Relative Humidity: value=75%
2021-08-02 19:42:59.546 Detail, Node009, Refreshed Value: old value=73, new value=75, type=decimal
2021-08-02 19:42:59.546 Detail, Node009, Changes to this value are not verified
2021-08-02 19:42:59.546 Detail, Node009, Notification: ValueChanged
2021-08-02 19:43:02.004 Detail, Node009,   Received: 0x01, 0x09, 0x00, 0x04, 0x10, 0x09, 0x03, 0x80, 0x03, 0x64, 0x0f
2021-08-02 19:43:02.004 Info, Node009, Received Battery report from node 9: level=100
2021-08-02 19:43:02.004 Detail, Node009, Refreshed Value: old value=100, new value=100, type=byte
2021-08-02 19:43:02.004 Detail, Node009, Changes to this value are not verified
2021-08-02 19:43:02.004 Detail, Node009, Notification: ValueChanged
2021-08-02 19:43:06.271 Detail, Node009,   Received: 0x01, 0x09, 0x00, 0x04, 0x10, 0x09, 0x03, 0x30, 0x03, 0xff, 0x24
2021-08-02 19:43:06.271 Info, Node009, Received SensorBinary report: Sensor:36 State=On
2021-08-02 19:43:06.271 Detail, Node009, Refreshed Value: old value=false, new value=true, type=bool
2021-08-02 19:43:06.271 Detail, Node009, Changes to this value are not verified
2021-08-02 19:43:06.271 Detail, Node009, Notification: ValueChanged
2021-08-02 19:43:07.805 Detail, Node009,   Received: 0x01, 0x10, 0x00, 0x04, 0x10, 0x09, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x08, 0x00, 0x00, 0x7c
2021-08-02 19:43:07.805 Info, Node009, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Burglar event:8, status=255
2021-08-02 19:43:07.805 Detail, Node009, Refreshed Value: old value=0, new value=0, type=byte
2021-08-02 19:43:07.805 Detail, Node009, Changes to this value are not verified
2021-08-02 19:43:07.806 Detail, Node009, Refreshed Value: old value=0, new value=0, type=byte
2021-08-02 19:43:07.806 Detail, Node009, Changes to this value are not verified
2021-08-02 19:43:07.806 Detail, Node009, Refreshed Value: old value=0, new value=0, type=byte
2021-08-02 19:43:07.806 Detail, Node009, Changes to this value are not verified
2021-08-02 19:43:07.806 Detail, Node009, Refreshed Value: old value=0, new value=8, type=byte
2021-08-02 19:43:07.807 Detail, Node009, Changes to this value are not verified
2021-08-02 19:43:07.807 Detail, Node009, Notification: ValueChanged
2021-08-02 19:43:07.831 Detail, Node009, Notification: ValueChanged
2021-08-02 19:43:07.844 Detail, Node009, Notification: ValueChanged
2021-08-02 19:43:07.857 Detail, Node009, Notification: ValueChanged
2021-08-02 19:43:10.299 Detail, Node009,   Received: 0x01, 0x0c, 0x00, 0x04, 0x10, 0x09, 0x06, 0x31, 0x05, 0x03, 0x0a, 0x00, 0x00, 0xd5
2021-08-02 19:43:10.300 Info, Node009, Received SensorMultiLevel report from node 9, instance 1, Luminance: value=0lux
2021-08-02 19:43:10.300 Detail, Node009, Refreshed Value: old value=0, new value=0, type=decimal
2021-08-02 19:43:10.300 Detail, Node009, Changes to this value are not verified
2021-08-02 19:43:10.301 Detail, Node009, Notification: ValueChanged
2021-08-02 19:43:12.019 Detail, Node009,   Received: 0x01, 0x0b, 0x00, 0x04, 0x10, 0x09, 0x05, 0x31, 0x05, 0x1b, 0x01, 0x00, 0xc2
2021-08-02 19:43:12.020 Info, Node009, Received SensorMultiLevel report from node 9, instance 1, Ultraviolet: value=0
2021-08-02 19:43:12.020 Detail, Node009, Refreshed Value: old value=0, new value=0, type=decimal
2021-08-02 19:43:12.022 Detail, Node009, Changes to this value are not verified
2021-08-02 19:43:12.023 Detail, Node009, Notification: ValueChanged
2021-08-02 19:43:13.307 Detail, Node009,   Received: 0x01, 0x08, 0x00, 0x04, 0x10, 0x09, 0x02, 0x84, 0x07, 0x6b
2021-08-02 19:43:13.310 Info, Node009, Received Wakeup Notification from node 9
2021-08-02 19:43:13.311 Detail, Node009, Queuing (WakeUp) WakeUpCmd_NoMoreInformation (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x84, 0x08, 0x25, 0xe2, 0xa5
2021-08-02 19:47:04.284 Detail, Node009,   Received: 0x01, 0x09, 0x00, 0x04, 0x10, 0x09, 0x03, 0x30, 0x03, 0x00, 0xdb
2021-08-02 19:47:04.284 Info, Node009, Received SensorBinary report: Sensor:219 State=Off
2021-08-02 19:47:04.284 Detail, Node009, Refreshed Value: old value=true, new value=false, type=bool
2021-08-02 19:47:04.285 Detail, Node009, Changes to this value are not verified
2021-08-02 19:47:04.285 Detail, Node009, Notification: ValueChanged
2021-08-02 19:47:06.089 Detail, Node009,   Received: 0x01, 0x10, 0x00, 0x04, 0x10, 0x09, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x00, 0x00, 0x00, 0x74
2021-08-02 19:47:06.089 Info, Node009, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Burglar event:0, status=255
2021-08-02 19:47:06.090 Detail, Node009, Refreshed Value: old value=0, new value=0, type=byte
2021-08-02 19:47:06.090 Detail, Node009, Changes to this value are not verified
2021-08-02 19:47:06.090 Detail, Node009, Refreshed Value: old value=0, new value=0, type=byte
2021-08-02 19:47:06.090 Detail, Node009, Changes to this value are not verified
2021-08-02 19:47:06.090 Detail, Node009, Refreshed Value: old value=0, new value=0, type=byte
2021-08-02 19:47:06.090 Detail, Node009, Changes to this value are not verified
2021-08-02 19:47:06.090 Detail, Node009, Refreshed Value: old value=8, new value=0, type=byte
2021-08-02 19:47:06.090 Detail, Node009, Changes to this value are not verified
2021-08-02 19:47:06.090 Detail, Node009, Notification: ValueChanged
2

Have you measured the rechargeable battery while under load? It may not be capable of providing 3 volts to the sensor when under load.

The first step is troubleshooting an issue it to look at what recently changed.

3

I wouldn’t know how to do that. Yeah the only thing that has changed is the battery, but if I just put back old batteries and it all works I’ve just spent $60 on charger and batteries but don’t know how to investigate.

How can I measure the battery under load?

4

First start with the electrical specifications for the battery & device and compare them with whatever you purchase. Here is what I found online for the C123A battery.

image
image685×692 53.8 KB

from https://www.flashlightsunlimited.com/documents/Batteries/TenergyPropel-CR123A-Specifications.PDF

Ideally the new battery would meet or exceed those specifications. If not, perhaps it can still meet the needs of the device. If you cannot measure voltages yourself you need to trust published specifications.

Guessing only works sometimes. At other times it is a costly lesson.

5

Thanks for that info @Prodigyplace - I’ll go do some digging into the different battery specs.

6

This could be a mechanical issue with a tamper detection button inside the enclosure. I can’t remember if this device has one but a lot of my EcoLink ones do. When you go to replace the battery, a piece of plastic thats normally depressing a button comes off & it triggers an enclosure event with a home security/alarm z-wave-related code.

I would try removing the enclosure again and look for one of these. If the plastic broke you could maybe crazy glue it down.

1 Like
7

I notice a lock / unlock slider for the battery door. Is it in the Locked position?

8

From the manual:

Do not use rechargable CR123A batteries.

from https://help.aeotec.com/support/solutions/articles/6000057073-multisensor-6-user-guide-

It is always helpful to read the fine manual.

9

Yeah, don’t use rechargeables, as it says in the manual

WARNING: Not compatible to rechargeable CR123A batteries (3.7V)

These are 3,0V specifically to overcome the issue with the 3,7 rechargeables.

10

Thanks @scottt732 - there doesn’t appear to be any such piece of plastic inside, and @Prodigyplace the back was locked.

I’ve taken out one of the two batteries to see if that makes any difference, but I read a section in the manual about outdoor usage - the unit is installed under cover outside the front door. The manual talks about sensitivity and although there is no activity outside the door - I am wondering if there is something going on with the sensitivity setting and the angle I set it up at.

Anyway I will play with those things to see if that makes a difference - for now I’ve just brought it inside for the night to see if it exhibits the same behaviour.

11

You may want to contact Aeotec support then.

12

Motion seems to be behaving now - not sure if it was removing one of the batteries or just removing the cover and reseating things.