Flush of false push messages after restarting HC2

[mvdkallen 0]

Hi all,

 

I have defined several push messages which inform me once windows, doors or roller shutters are being opened or closed, plus once I leave my house then the system first informs me whether all windows and doors are closed before the alarm is enabled.

 

But I've noticed that every time I restart HC2 (.. because some scenes no longer work after some time) then the HC2 is flushing all these push messages to my devices although there hasn't been any real activity on these sensors at all. This is quite annoying because every time I then check the APP whether doors or windows are really opened or closed.

 

There is no real logic of when I will receive a push message after the restart, sometimes I get them all at once but sometimes also a few in the beginning and the rest over time (.. also during the night, so it wakes me up... for actually no reason).

 

• Is there anyone that have noticed the same, or is it just me?
• Fibaro support team, is there any trick or workaround to apply?

 

Thanks and best regards,

Mark

 

 

[j.nowacki 5]

Do set these notifications with scenes or in devices configuration?

[Cafun 13]

Why are scenes stopped working after some time? I do have the same.

@j.nowacki: I haven't contacted support about that, because I need those scenes running, so I reboot my HC2. Should I still contact support about this?

[mvdkallen 0]

Hi j.nowacki,

 

I've set these notifications as part of scenes because I'd like to get notified once a window or door is being opened AND being closed.

Under device configuration you can only set one parameter, instead of the two I prefer.

[j.nowacki 5]

Isn't scene run at start up of HC2? Clear the checkbox responsible for that in scene configuration.

[mvdkallen 0]

ah... ofcourse!

I didn't realize that this checkbox could be the responsible factor.

 

And for the LUA scenes I just remove the %%autostart from the code, right?

 

Thanks a lot for this suggestion.

[j.nowacki 5]

Yes, removing %%autostart will do the job.

[mvdkallen 0]

Hi j.nowacki,

 

I've tried the adjustment as suggested above, but unfortunately it doesn't work for all the scenes (.. for most it did the trick).

I'd like you to check below LUA scene to see if there's maybe something weird in the code that could cause the notification to be triggered. 

This script basically changes a global variable when a specific door is opened or closed (the Door ID is 132) and according to the global variable the system will send me a push message whether the door is closed (128) or opened (127):

 

------------------------- script --------------------------

 

 

--[[
%% properties
132 value
%% globals
--]]

 

local startSource = fibaro:getSourceTrigger();
if (
 ( tonumber(fibaro:getValue(132, "value")) > 0 )
or
startSource["type"] == "other"
)
then
  fibaro:setGlobal("Achterdeur", "Open");
  fibaro:call(67, "sendDefinedPushNotification", "127");
  else
  fibaro:setGlobal("Achterdeur", "Dicht");
  fibaro:call(67, "sendDefinedPushNotification", "128");
end

 

 

----------------------- end script ------------------------

 

I am thinking that maybe line 10 to 12 would trigger the false notification, but I honestly don't know whether that makes sense.

 

What is your view on this?

[j.nowacki 5]

Add some debugs to the code to see when exactly it gets triggered.

[mvdkallen 0]

Hi j.nowacki,

 

I've done this now and will monitor.

Thanks for your support so far.

 

Best regards,

Mark

[mvdkallen 0]

Hi j.nowacki,

 

I restarted the HC2 this morning at 07:10 AM, and at 07:21 AM I received a false notification from a door sensor, following by two other false notifications at 07:30 AM from two different window sensors.

 

I'll do a restart later this afternoon again to see if the frequency of the false notifications is the same as this morning.

 

From all scenes that have these notifications set up I've unchecked the "run scene at startup" option, and from the LUA scripts I have removed the %%autostart line.

 

Keeping you posted.

 

Best regards,

Mark

[mvdkallen 0]

Hi j.nowacki,

 

At 10:28 AM I received a false notification from another window sensor (.. however this sensor did not generate a false notification earlier this morning).

 

What I found out, is that it apparently only happens with Door or Window sensors where I set up the notification within the scene.

I also have z-wave curtains, and roller shutters where I also include the notifications within the scene, but from these I never get the false notifications.

 

I use the Fibaro Door/Window sensors on all of my windows, and have the Aeotec Door sensors (Aeotec ZW089) on my doors.

 

Best regards,

Mark

[mvdkallen 0]

at 10:47 I received a false notification that a door is closed, at 10:49 I got a false notification that a window is closed and at 10:50 I get a false notification that another (different) window is closed.

 

These Doors and Windows have not been opened, so it is the system that is flushing the notifications by itself.

 

Best regards,

Mark

[j.nowacki 5]

Create a scene that will be triggered by all of your D/W sensors, then print the one that triggered the scene. Maybe it is not a false push but false change of state of D/W itself?

[mvdkallen 0]

Hi j.nowacki,

 

This I tried already too, that's how I found out that it isn't a false change of state from the D/W sensors

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

After making the changes as listed above and monitoring it for some days now, I notice that it now only happens once per sensor after I reboot the HC2 so I can live with it (.. I understand the complexity of the issue here).

 

For me the topic can be closed, or at least get a much lower priority on your side.

 

Thanks for your support and advice given.

 

Best regards,

Mark