Page 1 of 1

EZMOTION

Posted: Wednesday 02 April 2014 16:08
by stephgre
Hello,

i have the HOMESEER EZMOTION (3 in 1) installed, i receive the temperature and the lux, but i don't find the motion detection.

Does someone use it, and can tell me the procedure ?

Thanks

Re: EZMOTION

Posted: Thursday 03 April 2014 15:53
by bob
If your device is similar to mine from a different manufacturer, the motion detection will be seen a switch command (when motion is detected) not a sensor.

Re: EZMOTION

Posted: Friday 04 April 2014 14:27
by stephgre
hello,

i delete and réintégrate the EZMOTION and i see the switch, i didn't understand it was the motion detection.

Thanks a lot

Re: EZMOTION

Posted: Saturday 05 April 2014 7:02
by Dnpwwo
Hi,

I'm surprised to see that anyone has these working because I have 3 of them and the PIR does not work with the current Domoticz (v1.1665) as far as I can tell. In the log during start up I see the following for a single device:

Code: Select all

Sat Apr 5 15:19:50 2014 OpenZWave: Value_Added: Node: 20, CommandClass: SENSOR MULTILEVEL, Label: General, Instance: 2
Sat Apr 5 15:19:50 2014 OpenZWave: Value_Added: Node: 20, CommandClass: SENSOR MULTILEVEL, Label: Luminance, Instance: 3
Sat Apr 5 15:19:50 2014 OpenZWave: Value_Added: Node: 20, CommandClass: SENSOR MULTILEVEL, Label: Temperature, Instance: 1
Sat Apr 5 15:19:50 2014 OpenZWave: Value_Added: Node: 20, CommandClass: BATTERY, Label: Battery Level, Instance: 1
but only the Luminance and Temperature devices show up in the Devices list, the 'General' (which is the PIR) one drops through the AddValue code and does not get added at all. My devices are the original 'v1' version, can someone who has these working please confirm that their PIR reports itself as 'General' and if not, what does it report itself as?

Are you running these on batteries or or are they powered? Mine are powered and set to stay awake.

The only way I got this working was by changing OpenZWave.cpp so that it treated a 'General' multilevel sensor as a switch, I then turn it off using the 'Off Delay' functionality in Domoticz itself.

Any feedback would be great.

Re: EZMOTION

Posted: Monday 07 April 2014 12:42
by stephgre
Hi,

you are right, i can see the swith with my version 1.13xx, but the switch never go to 'ON'. So it doesn't work for me too.

bye

Re: EZMOTION

Posted: Thursday 10 April 2014 9:43
by Dnpwwo
okay, now I know I'm not the only one with this issue I'll post a request to get the device added.

The code I posted will will also make it switch ON although if you have them wired they never switch OFF (by design) so you need to do that in domoticz itself

Re: EZMOTION

Posted: Saturday 19 April 2014 16:34
by gizmocuz
Dnpwwo
Thanks for the patch, it will be included in the next beta version.

One part i did not include, that was the part of line staring 1506,
this because the 'SendSwitch' function should change the internal device state.
Does the SendSwitch function changes this correctly for the 'General' Type ?

With kind regards,
Rob

Re: EZMOTION

Posted: Sunday 20 April 2014 13:50
by Dnpwwo
Hi Rob,

Thanks for looking at this.

I updated svn and rebuilt to see if it worked but unfortunately you pasted the 'General' code into the wrong part of AddValue. It needs to go under COMMAND_CLASS_SENSOR_MULTILEVEL but you've pasted it under COMMAND_CLASS_METER, understandable given that it is one long chain of 'if' statements :)

As for the '1506' code, when the Ezmotion is powered externally (the only practical way to use it) it only sends motion events which means we just see a series of 'On' Node Events but never any 'Off' events so only a single notification is ever sent to Domoticz using the exiting logic. When I've used these devices with other automation products I've just reset the PIR to 'Off' periodically (say every 30 or 60 seconds) allowing the next 'On' to be handled as a normal sensor value change.

With Domoiticz I thought I could do the same thing with the 'Off Delay' but it didn't work. The sensor correctly showed 'Off' on screen but because the ZWaveBase layer didn't know Domoticz had changed the value this code:

Code: Select all

	if (pDevice->intvalue==nintvalue)
	{
		return; //dont send/update same value
	}
continues to ignore subsequent 'On' Node Events and the Motion Sensor never triggers.

I can understand why you only want to send all changes to the Domoticz core but the only other way to do it is to make Domoticz propagate all externally initiated changes back to ZWave so that the existing code can make the correct decisions. This logic seems to exist and in fact the WriteToHardware function calls SwitchLight at the right time to do this but GetValueByCommandClass seems to fail which makes me think my logic to create the device is flawed.

Any thoughts?

Re: EZMOTION

Posted: Monday 21 April 2014 6:39
by Dnpwwo
Ok, nailed it.

Just needed to add handling for the PIR device in three places:
  • AddValue to accept the "general" sensor type 'as is' (but not change the command class).
  • UpdateNodeEvent looks for MultiLevel Sensors as it's last attempt
  • SwitchLight changed to treat Binary and Multi Sensors the same way and propagate changes back to ZWave
These are all additions so should be backwards compatible.

For motion detection to work for wired instances an 'Off Delay' is required to clear the motion events, devices using batteries should just work out of the box.

Re: EZMOTION

Posted: Friday 25 April 2014 15:49
by stephgre
Hi,

now i see the motion sensor, does someone has made a scene to send a message or something like an alarm when the motion sensor detect something ? i don't see how to do that.

Thanks

Re: EZMOTION

Posted: Saturday 26 April 2014 1:03
by Dnpwwo
I think what you are looking for is under "Setup" \ "More Options" \ "Events", the 'blocky' editor will allow you to do a number of things.

If you are specifically after a an alarm notification, you could just set it up using the 'Notifications' button on the device itself in the Switches tab.

Re: EZMOTION

Posted: Monday 28 April 2014 10:35
by stephgre
Hi,

it's ok, this is working with 'Notifications', i'm going to look the blocky editor.

Thanks

Re: EZMOTION

Posted: Sunday 04 May 2014 22:27
by stephgre
Hi,

i've test also the blocky editor, it's working nice.

Just a little bug, is on the battery level, for the lux indicator, i have 79% of battery and for the temperature indicator i have 60% of battery.

Thanks

Re: EZMOTION

Posted: Friday 20 November 2015 11:42
by floris74
Dnpwwo wrote:Ok, nailed it.

Just needed to add handling for the PIR device in three places:
  • AddValue to accept the "general" sensor type 'as is' (but not change the command class).
  • UpdateNodeEvent looks for MultiLevel Sensors as it's last attempt
  • SwitchLight changed to treat Binary and Multi Sensors the same way and propagate changes back to ZWave
These are all additions so should be backwards compatible.

For motion detection to work for wired instances an 'Off Delay' is required to clear the motion events, devices using batteries should just work out of the box.
Hi,

I received this 3-1 sensor. I have the sensor in my network but it doesn't update any value, like temp, lux, or motion. can somebody help me with this?

Re: EZMOTION

Posted: Friday 20 November 2015 14:31
by dijkdj
Motion works for me lux is a fixed value

Re: EZMOTION

Posted: Friday 20 November 2015 21:53
by floris74
Hi DIjkdj,

How did you fix that? can you help me with it?

Floris

Re: EZMOTION

Posted: Saturday 20 February 2016 23:22
by mark.sellwood
Hi,

Has anyone got this working?
When I include it I get 3 devices, Temp, Lux & Lighting 2.
The LUX value hasn't updated since I included it, the Temp gets updated if i press the blue button on the side but it never reports motion.

I'm on 3530.

Any info would be good.

Mark