Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Recommended Posts

Posted

It happened to me twice now, yesterday and today.

I use the Fibaro as an alarm with 9 FGK-101 door/window sensors and 1 Fortrezz SSA2 Siren.

I've made several scenes that arm/disarm all devices, trigger siren, arm devices when they are closed while the alarm is armed, and send out push notifications.

Yesterday while we were not at home the alarm suddenly triggered, and offcourse adrenaline was pumping. I have a couple of camera's inside my home and they showed nothing alarming. The dog was sleeping like nothing was wrong so I calmed down a bit and kept looking at the camera's for some time. To see nothing wrong.

Using the Fibaro iPhone app it showed several door/windows were breached that were closed when I left the home.

After coming home I found all door/windows closed just as I left them. But according the HC2 several doors/windows were open. Checking the event panel showed one window sensor breaching triggering the alarm. Now other events about breaching sensors.

Today while we were still asleep the siren was suddenly screaming. I disabled the alarm, and checked the camera's again, nothing wrong. Several sensors showing as breached again. While the event panel only shows one sensor breaching (not the same as the day before) triggering the alarm. Also one of the breached sensor temperature sensors is showing as 2.96C while it is more like 35C in that room.

First time the alarm triggered it was version 3.550 and this morning I was on version 3.552 as I upgraded yesterday evening.

The system has been working OK for the last couple of weeks, so nothing like this happened before and nothing changed during that time to cause this event.

Anybody any idea why and how this happened? Or happened to him/her before?

Guest paogig
Posted

Hi sdeath,

I have some fgk-101 too, and no problem till now with3.552...

Just a hint... Check the magnets/contacts position...

Paolo

  • Topic Author
  • Posted

    Paolo, everything worked fine for several weeks.

    Nothing happened during that time that I couldn't explain.

    The magnets are all where they should be.

    [ Added: 2013-07-22, 12:42 ]

    I think I figured out what the problem is. The tape somehow isn't sufficient to keep the tamper switch pressed. As soon as I press the sensor down the light starts blinking.

    So I'll probably have to add the screws to attach them.

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Reply to this topic...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...