Hi,
I just received this z-wave sensor. Adding it to the network worked great. However, two issues I encountered after 24h of operation:
For reference, an Aeotec MultiSensor 6 is running without issues in the same setup. The controller is a RaZberry 7.
I just opened a ticket with Z-wave JS. See here: Z-wave JS no longer scans parameters list from Aeotec 700 series devices · Issue #5185 · zwave-js/node-zwave-js · GitHub
I had to configure the default values from the manual in the device settings. Now the updates work as expected and the power status is correct
I also saw this behaviour. I solved it by moving the sensor within good direct connection range of 1m and re-interviewing.
trying to re-interview at distance/over repeaters always left the fields empty. The sensor worked otherwise as expected though. I tried several times with the same results. On 2 sensors. (z stick 7 controller)
This thread is recent enough and titled “Issues” so I won’t start a new one unless I really need to …
I have recently installed a ZWA024 in a room which is currently unoccupied. Every approx. 2 mins:10 secs I get “Studio Bathroom Multisensor fired Notification CC ‘notification’ event ‘Home Security’: ‘Tampering, product moved’” in my Logbook.
Has anyone seen something like this before?
My next steps will be to exclude / factory reset / include it while standing next to the controller, to ensure the interview isn’t interrupted.
RPi4B, Aeotec 700 series controller, <30 devices
Go into the devices configuration and make sure the settings are the way you need them. I have found that Aoetec devices rarely have good default config, and changing their config does seem to fix anomalies.
where you able to fix this problem? I’m noticing the same periodic message from this device, after a firmware update
answer to self - disable the vibration sensor
This solved your problem? I recently had the restore from backup and my multisensor intermittently stops providing updates. A re-interview updates those details but then stops updating from there. It’s messing with lots of luminance automations.
Yes. I’ve been really pleased with these sensors, after the initial setup pain they work really well.
I specially like the configurability that helps battery life hugely when you install the sensor in a high-usage area, e.g. kitchen. You can set it up to not retrigger if it senses continuous occupation over the next X minutes. I recall with the zooz this was limited to a 5 minutes maximum and as a consequence battery would be drained in less than 6 months, vs. one hour in the ZWA024. This sensor has double the battery capacity vs. the zooz plus a lot more flexibility with the timers. After 6 months the battery level is still 100%.
The only issue I introduced myself a few months ago when I had the idea to upgrade a few units to a newer firmware release. It introduced zero features, fixed zero problems (to me) but I ended having to factory-reset the units and re-include them, as they behaved erratically after the upgrade. After that, zero problems again
i can;t get it to update and idk what to do
You mean updates of sensor values in HA right? I suggest, start by removing them from the zwave network, factory reset them, and re-include them.
Also after the reset, ensure parameter 40 and 41 are set to 1. (specifically for temperature reporting)