Grover01 wrote: ↑Thursday 15 March 2018 10:53
Do you already have a solution for this?
Message was quite old... Do not own this module, but double events can be triggered by a module malfunction/bug, but also a bad/incomplete inclusion (leading to module misconfiguration). As well as zwave communication problems (messages that are not acknowledged are retried).
So, if a net search does not show known problems that can be solved by some configuration update, my advice is:
1) Unmount the device and try close to your z-wave controller. If this work, you probably have a range issue that can be solved with a better placement of the controller (can be easily solved if this is a USB based one, even if domoticz host can't be moved easily, using a cable).
2) If this does not work, get the module close to the controller, exclude it (then reset the module if this can be done, but only after correct exclusion is done, wait 1 or 2mn, or you may have to struggle with a "ghost" node problem) and re-include taking care to be at a few tens of cm from the controller and staying there a few time, even after domoticz says inclusion is done: I suspect some parameters are still exchanged after node is allocated and if the module experience range issues while moving inclusion will be bad.
z-wave is in my experience a solid technology after setup is done correctly, but if inclusion is bad, this can turn to a nightmare with an almost unbound range of issues... So be very careful at this step.