Author Topic: FGK-101 notification issue  (Read 521 times)

Offline Tlex

  • Sr. Newbie
  • *
  • Posts: 36
  • Karma: +0/-0
FGK-101 notification issue
« on: February 13, 2017, 08:18:10 am »
Hi,
I do have 4 FGK-101 door contact installed.
Basically I just want to get a notification once the doors open..
It used to work but since a certain time (and after adding an extra sensor on the network) I most of the time get double even triple notifications from sensors when a door open...

my scene is really simple :
for each sensor I set a variable via LUA (inside the "select trigger" section:
ie: TriggerName = "side door open"

then I use the following luup code:
luup.call_action("urn:veramate-com:serviceId:VeraMatePN", "SendAlert", {Msg=TriggerName}, 22)

I'm wondering if the issue comes from the sensors being to sensitive ?
Is there a way to adjust that or would there be a away to prevent notification from the same sensor if the occur multiple times in let says 100ms ? (just brainstorming here !!!)
I also tried to reset my zwave network without any success . . .

All you help is really appreciated.

Offline RichardTSchaefer

  • Master Member
  • *******
  • Posts: 9720
  • Karma: +737/-136
    • RTS Services Plugins
Re: FGK-101 notification issue
« Reply #1 on: February 13, 2017, 10:42:14 am »
You can do that in lua code ...

PLEG has the ability to do this with the multi-count operator.

If you had a trigger called Trig in PLEG.

Condition syntax for a condition named Notify would  be:

Notify           TRIG @ 2 > 10


This would only be true if  a trigger has not happened in the last 10 seconds. Then the action for the Notify condition could be to send your notification.

Offline Tlex

  • Sr. Newbie
  • *
  • Posts: 36
  • Karma: +0/-0
Re: FGK-101 notification issue
« Reply #2 on: February 15, 2017, 03:37:46 pm »
Thanks Richard !
I did installed it and did a basic setup (I know their might be better way to program that but I'm just a beginner !!!)
I've attached to logic report and debug (I've hide my registration #).
The setup did work but for some reason I get one notification and then nothing else for a very long period of time (I would say for more then 5 minutes or so...) And that, from any other sensors as well ...

Any idea ?
 
Thanks again !

Offline Tlex

  • Sr. Newbie
  • *
  • Posts: 36
  • Karma: +0/-0
Re: FGK-101 notification issue
« Reply #3 on: February 15, 2017, 03:58:59 pm »
To make it more easy, here is the debug log with just the issue..
Is it possible that the time is not counting correctly ?

Offline Tlex

  • Sr. Newbie
  • *
  • Posts: 36
  • Karma: +0/-0
Re: FGK-101 notification issue
« Reply #4 on: July 09, 2017, 11:19:32 am »
You can do that in lua code ...

PLEG has the ability to do this with the multi-count operator.

If you had a trigger called Trig in PLEG.

Condition syntax for a condition named Notify would  be:

Notify           TRIG @ 2 > 10

This would only be true if  a trigger has not happened in the last 10 seconds. Then the action for the Notify condition could be to send your notification.

Hi Richard,

orry to bother again with that but I just can't make it to work..

I tried with that condition and it works only from time to time.... basically, it will work once and then no more until lua gets restarted.

I have a multi trigger setup  (but I also tried without it) so that what I'm trying to achieve is that when a virtual mute switch is off and if the trigger didn't happen within the last 5 secs, then run the logic action..
I attach the logic report and here is the pleg log generated when it work and when it doesn't work...
Note that second time I dont get the last line : Sun Jul 09 11:14:1.259 - TriggerCondition:None
Many thanks for your help !


action working:
Sun Jul 09 11:13:58.711 - SaveDB:Memory:383138
Sun Jul 09 11:13:58.714 - RunNext:Action:doorKITCHENopenned Index:1
Sun Jul 09 11:13:58.907 - RunNext:Lua Continue
Sun Jul 09 11:13:58.908 - SaveActionDB:{}
Sun Jul 09 11:14:1.229 - TriggerPropertyUpdate:Tripped
Sun Jul 09 11:14:1.230 - TPU:Tripped :0=1
Sun Jul 09 11:14:1.231 - TriggerPropertyUpdate:Name:doorKITCHEN State:false Device:123
Sun Jul 09 11:14:1.232 - FireAction:Nothing found for:!doorKITCHEN
Sun Jul 09 11:14:1.233 - EvalConditions:Multi Trigger:doorKITCHEN
Sun Jul 09 11:14:1.236 - EvalConditions:Condition:CurtainOpenning Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.237 - EvalConditions:Condition:CurtainClosing Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.239 - EvalConditions:Condition:LightDimmedLivingRoomATNight Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.240 - EvalConditions:Condition:LightOffLivingRoomATDay Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.242 - EvalConditions:Condition:LightOnLivingRoomATEvening Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.245 - EvalConditions:Condition:doorFRONTopenned Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.248 - EvalConditions:Condition:doorKITCHENopenned Trigger:doorKITCHEN Result:true
Sun Jul 09 11:14:1.249 - EvalConditions:Condition:doorSTAIRSopenned Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.252 - EvalConditions:Condition:doorGARAGEopenned Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.254 - EvalConditions:Condition:Display_VeraMate_Infos Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.255 - EvalConditions:Condition:AirExchangeON_Week Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.257 - EvalConditions:Condition:AirExchangeON_Weekend Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.258 - EvalConditions:Condition:AirExchangeOff Trigger:doorKITCHEN Result:false
Sun Jul 09 11:14:1.259 - TriggerCondition:None


Action not working : (that was done more than 5 seconds after...):
Sun Jul 09 11:15:8.176 - SaveDB:Memory:394396
Sun Jul 09 11:15:11.476 - TriggerPropertyUpdate:Tripped
Sun Jul 09 11:15:11.477 - TPU:Tripped :0=1
Sun Jul 09 11:15:11.477 - TriggerPropertyUpdate:Name:doorKITCHEN State:false Device:123
Sun Jul 09 11:15:11.478 - FireAction:Nothing found for:!doorKITCHEN
Sun Jul 09 11:15:11.479 - EvalConditions:Multi Trigger:doorKITCHEN
Sun Jul 09 11:15:11.480 - EvalConditions:Condition:CurtainOpenning Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.481 - EvalConditions:Condition:CurtainClosing Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.482 - EvalConditions:Condition:LightDimmedLivingRoomATNight Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.483 - EvalConditions:Condition:LightOffLivingRoomATDay Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.484 - EvalConditions:Condition:LightOnLivingRoomATEvening Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.486 - EvalConditions:Condition:doorFRONTopenned Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.487 - EvalConditions:Condition:doorKITCHENopenned Trigger:doorKITCHEN Result:true
Sun Jul 09 11:15:11.489 - EvalConditions:Condition:doorSTAIRSopenned Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.491 - EvalConditions:Condition:doorGARAGEopenned Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.491 - EvalConditions:Condition:Display_VeraMate_Infos Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.492 - EvalConditions:Condition:AirExchangeON_Week Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.493 - EvalConditions:Condition:AirExchangeON_Weekend Trigger:doorKITCHEN Result:false
Sun Jul 09 11:15:11.494 - EvalConditions:Condition:AirExchangeOff Trigger:doorKITCHEN Result:false

Offline RichardTSchaefer

  • Master Member
  • *******
  • Posts: 9720
  • Karma: +737/-136
    • RTS Services Plugins
Re: FGK-101 notification issue
« Reply #5 on: July 09, 2017, 12:38:58 pm »
If you have not called Maine this fragment without adding anything else to the condition you will  need o set repeats to on,

You can tell this from the status report .. if the condition is already true and a trigger causes the condition to evaluate to rue again. Without REPEATS It will not run the actions.

Offline Tlex

  • Sr. Newbie
  • *
  • Posts: 36
  • Karma: +0/-0
Re: FGK-101 notification issue
« Reply #6 on: July 09, 2017, 02:17:27 pm »
Thanks,

Not sure to understand everything but I just tried to set repeat "on" and now, the logic action run when the door opens and close instead of only when the door opens as specified in the device trigger...
Its frutrating because it seams so close to work well and still not !