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

Question
davyboyk 0
Hello
I've configured a super easy scene (with blocks, converted in LUA as you can see below) that turn light on on motion sensor.
--[[
%% autostart
%% properties
204 value
%% weather
%% events
%% globals
--]]
local startSource = fibaro:getSourceTrigger();
if (
( tonumber(fibaro:getValue(204, "value")) > 0 ))
--[[or
startSource["type"] == "other"
)
--]]
then
fibaro:call(22, "turnOn");
end
It has a delay of 30/40 seconds (sometimes 10, 15, 20, random), I attach a screenshot of the events panel.
I've already read about this problem but I haven't read if somebody have found a solution.
- All my sensors were joined in NO sicure mode (so the problem is not that)
- This problem happened since the last update, now I'm on 4.510
- distance between HC2 and sensors and relay is approximately 3/4 meters in a wood frame house
- all components are fibaro (motion sensor and relay switch 2x)
- sometimes delay doesn,'t appear, so it works correctly, but without rules (day or night, it happens)
- already done the mesh reconfiguration
I'm completely mad for the no solution on this f*****g stupid problem.
Please login or register to see this attachment.
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.