Zwave motion sensor not reporting

Hey guys,

i’m new to Home assistant, i started 2 weeks ago and already added a few devices (plex, netatmo thermostat, chromecast, ikea smart lights etc…).

I bought 2 aeotec multisensor gen5 and i’m having a hard time getting the motion sensor to work.
A few informations :

  • I’m testing on a plugged sensor, so no need to check battery levels, it’s always on “ready”.
  • Motion sensor is “Enabled”
  • Command options is set to “Binary sensor report”
  • I changed the group 1 report interval to 60 sec, and it’s updating without problems.

However, even if i dance around the sensor, the “burglar” circle stays at 0.
I feel like i’m missing something really simple, but i can’t find what…

Does someone have an idea ?

Thanks !

Other than the sensitivity dial I’m not sure. It may be defective. I have 2 and to the best of my recollection, other than setting them to binary I did nothing but add in to my network and they worked.

Perhaps do a full reset on them and try again if you have not already. It would be odd that 2 would be like that. I did receive 1 dud from Amazon a while back.

honestly I ignore the burglary circle and look at the alarm state information directly. Aeotec stuff needs some configurations sent to them to make them report specific alarm types I spent hours trying to get my aeotec door switches to have anything other than a 2 in the burglar circle and realized that it’s not with it just to make a number in a circle on the web page what I want, I want the action to happen… I just use the sensor state in my scripting as that seems to be extremely reliable.

From what I can tell that is just an information indicator, and not used for anything else. Mine changes to a 3 when I trigger the tamper switch.

A bit more info, if have the burglar now at 7, it triggered yesterday evening and stayed at 7 all day long…
Could it be a parameter i’m missing somewhere ?

did you edit your options.xml to use encryption and did you join the sensors securely (add_node_secure) ? when doing so the sensor works as designed when changing it to binary - at least in my tests …