Vision ZS5101EU-5 support template

[moky 0]

Hi,

 

I have acquired those devices. When i do the inclusion they are recognized as motion detector.

Which is fine as long as it is working. The only challenge is that the status is never updated. So if I breach the device it never update on the fibaro HC2

 

I find crazy that the only ZWAVE device shock dectore is getting so many issue with HC2.

The previous version used to work but now I have replace 15 of them with the new one.

 

How long will it take for Fibaro to bring this new device ?

 

Thanks for the answer.

[tinman 1,011]

set the Vision ZS5101EU-5 to "windows sensor" and use this simple scene to see the alarm frames, no need to arm/disarm it.

 

Please login or register to see this code.

this works with Vision fw version 15.4, if you have different version please let me know how it works for you.

[moky 0]

Hi Tinman,

 

First of all thank you so much for your reply. So I am running version 16.6 of the sensor. 

When I use your script the detection is working if I shake the device. But we I am testing the scene every time I click on the play button he gave me a tamper alaram trigger status ??

Is it normal ? I would believe not.

 

Thanks

 

[tinman 1,011]

normally when running manually the scene, the last state should be displayed, but it can be everything. The idea of this scene is to be triggered by value change, not by run it manually. Btw, if the enclosure is opened, the LED should lit and the tamper alarm state is "triggered".

 

But it might be as well that Vision changed something then i will need some information from you to update the scene. 

 

What if you open the enclosure?, it should trigger then that scene and display alarm result properly.

Edited June 4, 2017 by tinman

[moky 0]

Hi Tinman,

Sorry for the late reply. But I wanted to make sure that the test I made was correct. 

So when I do any type of test remove the enclosure or shake the device to simulate a glass break. The update status is only display if I manually press the start button of the scene. 

Otherwise it just stay to the last known debug information even if the status change ?

 

Any idea ?

 

Thanks

 

[tinman 1,011]

stupid question, but did you changed IDs in the trigger section of the scene as well? Did you set the scene to run automatically?

[moky 0]

Yes the right ID and the scene is set to automatic. I have other scene where I can see the debug correctly. But not for this one ?

 

I need to press the button manually to trigger the new status 

[tinman 1,011]

2 hours ago, moky said:

 I have other scene where I can see the debug correctly. But not for this one ?

copy/paste/special character problem?

[moky 0]

No I have create the scene manually by typing the code so no copy past and still the same issue ? 

I am wondering if it is not a bug of the 4.130 ?

 

[tinman 1,011]

On ‎08‎.‎06‎.‎2017 at 1:33 AM, moky said:

No I have create the scene manually by typing the code so no copy past and still the same issue ? 

I am wondering if it is not a bug of the 4.130 ?

 

 

i did tested it for you with 4.130 and no issues, it was still working

[moky 0]

3 hours ago, tinman said:

 

i did tested it for you with 4.130 and no issues, it was still working

So do you see in the scene the update of the status trigger automatically ? Because for me it doesn't work

[moky 0]

Could that be the version of the firmware from the device itself ? I have create the scene like 10 times and still the same problem.

the status is not updated in the debug log... If I trigger the scene by client the start button then I got the status. 

I really don t understand where the problem is coming from.

 

Any hint would be appreciated

 

thanks

[tinman 1,011]

as you can see below, when i run it manually (the new version of ) the scene stops, when i move the sensor (to trigger glass breakage) and open the enclosure (to trigger tamper alarm) it does works

 

Please login or register to see this code.

 

Please login or register to see this attachment.

Please login or register to see this attachment.

 

so what remains is the firmware version difference.

 

Open hc2-ip/api/devices/yourdeviceid and copy the json, then trigger the sensor, refresh page and copy the json content again. Post both here, there need to be difference between sensor in idle and in triggered mode.

 

 

[moky 0]

 

Here is the output of the json 

 

Please login or register to see this code.

 

This is the output when the device is open : tamper trigger

 

Please login or register to see this code.

 

 

Yes indeed something is wrong with that new script when I click start button I only get the debug line about manually started and never the updat

 

Edited June 18, 2017 by moky

[moky 0]

On 6/12/2017 at 0:05 AM, tinman said:

as you can see below, when i run it manually (the new version of ) the scene stops, when i move the sensor (to trigger glass breakage) and open the enclosure (to trigger tamper alarm) it does works

 

Please login or register to see this code.

 

Please login or register to see this attachment.

Please login or register to see this attachment.

 

so what remains is the firmware version difference.

 

Open hc2-ip/api/devices/yourdeviceid and copy the json, then trigger the sensor, refresh page and copy the json content again. Post both here, there need to be difference between sensor in idle and in triggered mode.

 

 

 

[tinman 1,011]

hmm, alarmType and alarmLevel are changing, that's good, so the scene must trigger (as long proper device id and scene type has been entered)

 

try following and let me know the results

 

Please login or register to see this code.

 

[moky 0]

1 hour ago, tinman said:

hmm, alarmType and alarmLevel are changing, that's good, so the scene must trigger (as long proper device id and scene type has been entered)

 

try following and let me know the results

 

Please login or register to see this code.

 

 

If i just look at the scene log , nothing happening I need to click manually to the start button.

But When I click on the button, This is the output : 

 

[DEBUG] 13:34:09: manually started, end of scene here

 

 

[tinman 1,011]

try to set 203 instead of 204 for alarmType / alarmLevel in trigger section and of course for sensorID as well.

 

If that still didn't work, then the last thing you can do is to do hard reconfiguration and test again (with updated / new IDs of course).

 

[moky 0]

4 hours ago, tinman said:

try to set 203 instead of 204 for alarmType / alarmLevel in trigger section and of course for sensorID as well.

 

If that still didn't work, then the last thing you can do is to do hard reconfiguration and test again (with updated / new IDs of course).

 

 

I don't really understand what do you want me to set ? you are talking about 204 for alarmType/alarmLevel but I dont see that settings ?

 

I did a hard reconfiguration but still doesn't help I still get no automatice update on the status I need to trigger it by manually clicking the start button of the scene. 

 

Edited June 19, 2017 by moky

[tinman 1,011]

moky,

 

the 204 is deviceid coming from your post

 

 

that means you have to use that 204 in my lua scripts, e.g:

 

Please login or register to see this code.

and if that is still not working to try 203, which is the parentid of that sensor, e.g : (for your information, to use parentid is not working on my sensor, but i wish that you test it because you have different firmware version on that sensor)

Please login or register to see this code.

 

[moky 0]

On 6/19/2017 at 8:12 PM, tinman said:

moky,

 

the 204 is deviceid coming from your post

 

 

that means you have to use that 204 in my lua scripts, e.g:

 

Please login or register to see this code.

and if that is still not working to try 203, which is the parentid of that sensor, e.g : (for your information, to use parentid is not working on my sensor, but i wish that you test it because you have different firmware version on that sensor)

Please login or register to see this code.

 

Thanks Tinman

 

Actually changing the alarmlevel and alarmtrigger with the ID of the device did the trick now I can see the update.

Work like charm now I need to build some scene to trigger an alarm etc

 

You are the Man !!