EZMotion PIR detector - any success?
Posted: 10 Dec 2014 23:52
Hello there,
Quite a while ago I bough this PIR motion detector:
http://expresscontrols.com/pdf/EZMotion+OwnerManual.pdf
In an old version of the RaZberry/ZWay-Server, I had no problems using this detector.
I fact, in my eyes this is one of the best PIR detectors on the market, the sensitivity is configurable and really great, it has quite a few neat options, as well.
However, after some update to server version 1.7, things broke. I wasn't able to get this device stable, anymore.
First, the motion triggers stopped working. As the device didn't update its own commandClass value properties, anymore. Instead, the server property devices.1.instances.0.commandClasses.32.data.level is changed, therefore I created a fix by binding to this property and checking if devices.1.instances.0.commandClasses.32.data.srcNodeId is pointing to the EZMotion.
This worked, but soon I noticed that the device still fails after a while and drains its batteries tremendously... so I tried to remove and re-include the device...
The z-way server has MASSIVE problems (re-)including the device, it mostly fails to perform the full interview. I have to press the wakeup button like crazy to get the interview complete. This is completely reproducible!
To sum it up: This device was useless and I replaced it by an Everspring PIR detector.
Two days ago I upgraded to server version 2.0.0 and I tried it once again: Same behavior, same problems.
So here is my question: Is anyone out there who has a recent z-way server setup (2.0.0) and a flawlessly running EZMotion PIR detector?
If the detector wouldn't have failed directly after a z-way server update somewhen in the past, I would suspect that the device is broken... but I am quite sure that this is some interoperability problem...
Any hints are highly appreciated!
Many thanks in advance!
Quite a while ago I bough this PIR motion detector:
http://expresscontrols.com/pdf/EZMotion+OwnerManual.pdf
In an old version of the RaZberry/ZWay-Server, I had no problems using this detector.
I fact, in my eyes this is one of the best PIR detectors on the market, the sensitivity is configurable and really great, it has quite a few neat options, as well.
However, after some update to server version 1.7, things broke. I wasn't able to get this device stable, anymore.
First, the motion triggers stopped working. As the device didn't update its own commandClass value properties, anymore. Instead, the server property devices.1.instances.0.commandClasses.32.data.level is changed, therefore I created a fix by binding to this property and checking if devices.1.instances.0.commandClasses.32.data.srcNodeId is pointing to the EZMotion.
This worked, but soon I noticed that the device still fails after a while and drains its batteries tremendously... so I tried to remove and re-include the device...
The z-way server has MASSIVE problems (re-)including the device, it mostly fails to perform the full interview. I have to press the wakeup button like crazy to get the interview complete. This is completely reproducible!
To sum it up: This device was useless and I replaced it by an Everspring PIR detector.
Two days ago I upgraded to server version 2.0.0 and I tried it once again: Same behavior, same problems.
So here is my question: Is anyone out there who has a recent z-way server setup (2.0.0) and a flawlessly running EZMotion PIR detector?
If the detector wouldn't have failed directly after a z-way server update somewhen in the past, I would suspect that the device is broken... but I am quite sure that this is some interoperability problem...
Any hints are highly appreciated!
Many thanks in advance!