Last Breach timer

[anonymous66 9]

Hi ,

I'm having troubles with LastBreach timer of FGK101 Door Sensor and

FGMS001 Motion Sensor.

The sensors are working fine but after each HC2 reboot the last breach property of most of them looks like

in the picture below.

Many of my automation scenes make use of this feature but when this is not reliable

everything goes crazy and out of control.

Does anyone already had experience about this issue?

How can I reset the timer value without arming the System Alarm and then breach the sensors?

Regards

Edit : I'm on 3.590

Please login or register to see this attachment.

[petergebruers 1,268]

I can confirm this behavior. This sensor was breached a few days ago, but since then I've rebooted the HC2 several time. It says:

Please login or register to see this code.

Then, when I open the door:

Please login or register to see this code.

I don't see it reported in bugzilla... You want to report it?

I'm running 3.590. Sorry, no solution. Have to think about that one

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

[dw89 8]

Hi guys,

I have this too with door sensors on 3.590.

Perhaps there's a way to code so that checks for previous figure and recent reboot and then if last breached after reboot > previous figure then reset to 0 or whatever time since reboot and last breach since then.

Not sure if possible but just a thought.

Dave

[goran 9]

I reported this bug months ago and I have tried to get a confirmation from Fibaro.

Do you think they care?

[petergebruers 1,268]

I reported this bug months ago and I have tried to get a confirmation from Fibaro. ...

I don't see it reported in bugzilla... You want to report it? You want me to report it?

[goran 9]

I don't think I've reported it in bugzilla. To be honest, pretty much all bugs I've found have already been found and reported repeatedly by other people and I've reached the point where Fibaro's lack of interest in fixing bugs and their "it must be your own fault" kind of attitude have made me lost all hope and I really have no energy left to be a good user who file formal bug reports.

[MalvinYNJ 4]

Try clicking the b button in the sensor to update the configuration.

My motion sensor go haywire sometimes but my door sensor is going good.

Under 3.590 too.

[petergebruers 1,268]

I don't think I've reported it in bugzilla. To be honest, pretty much all bugs I've found have already been found and reported repeatedly by other people and I've reached the point where Fibaro's lack of interest in fixing bugs and their "it must be your own fault" kind of attitude have made me lost all hope and I really have no energy left to be a good user who file formal bug reports.

I think times have changed, I've reported several bugs and they were all processed by Fibaro. Some got acknowledged, some fixed or are on the list... I'd try reporting it again! You're helping with the development of the product. I did a search but couldn't find something related. That may be a wrong search strategy of mine. Bugzilla is very active nowadays, with the 4.X betas!

[ Added: 2014-12-02, 07:31 ]

Try clicking the b button in the sensor to update the configuration.

My motion sensor go haywire sometimes but my door sensor is going good.

Under 3.590 too.

This issue only shows right after HC2 reboot. And, only for as long as the sensor still is "unbreached".

Is this something you tested yourself? Is it a permanent fix, or only good until the next reboot?

[ Added: 2014-12-03, 13:30 ]

Bug reported as:

0002153: Door Sensor: Last Breach: value incorrect after reboot of HC2

[ Added: 2014-12-24, 10:31 ]

The problem has been solved in 4.024