Does anyone know how to turn off/reset the alarm_tamper on this zwave device?
I have excluded the device from the controller, removed the thing from openHAB and factory reset the device. I can re-include the device without issue but as soon as I move it to place it in the desired location the alarm_tamper get’s triggered and never resets.
I use zwave-js-ui to communicate with the MS7 . There is no parameter or signal, that reacts to the opening of the backside of the sensor ( tamper alarm). I also couldn‘t find any hint in the docu about tamper alarm.
Don‘t know which parameters the oh zwave binding supports.
Try changing parameter 6 to 0, to disable. Usually tamper and vibration alarms are the same.
That’s quit interesting, there is no parameter which shows the tamper alarm,
but zwave-js sends a topic without any payload.
Might be worth a question on the zwave-js github. 
I don’t have the MS7, so can’t test, but from the manual
Hi
I’ve tried to set parameter 6 to 0… I get the following in the debug logs when I do
2024-12-08 15:02:27.529 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update set config_6_0 to 0 (BigDecimal)
2024-12-08 15:02:27.530 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Size error (0) from config_6_0
2024-12-08 15:02:27.530 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored node_id to 4 (BigDecimal)
I found an error in the ZW DB setup and fixed it. It should work after the next DB update. If you can’t wait you could use this file
zwa024_0_0.xml (42.9 KB)
and this method to overwrite the current entry in the zwave jar (folder is aeotec in this case)