Expiration timer sometimes fails

[BiloxiGeek (Steve Berg)]

OH3.1.0M3 running on centos 8.

I’ve set up an expiration timer on a bathroom fan switch. When it’s set to say 5 seconds it works just fine. I reconfigure it for two hours which is what I want eventually and the fan never turns off. The toggle switch isn’t getting activated by hand, the OH software isn’t being restarted and the system isn’t getting rebooted.

Added: I’m not seeing any state changes in the log beyond the actual physical toggle switching that is being done.

I tried changing the code to 7200 seconds and the fan is still on after five and a half hours.

I’ve tried setting:

2h0m0s
1h59m59s
7200 seconds

None worked

I’ve successfully tried:

5 seconds
10 seconds
1 minute
1 minute, 10 seconds
5 minutes

What’s the trick to getting a two hour timer working to send an off command?

[OMR (Ole Morten Rønning)]

A wild guess. Do you use persistence?
Could it be that ‘something’ is updating your timer items?
Have a look in the /var/log/openhab/events.log

[rossko57]

Depending on the device technology, periodic routine updates may be sent. Updates to same state are not shown in logs.

[OMR (Ole Morten Rønning)]

@BiloxiGeek are you using the Expire binding?

[BiloxiGeek (Steve Berg)]

Yes, I’m defining the timer in the expiration metadata.

[BiloxiGeek (Steve Berg)]

The switch is z-wave, GE 14292 in-wall toggle switch.

[rossko57]

Permanently powered zwave device make periodic status reports. You won’t be able to use a long ‘expire’ directly, because the periodic update restarts the timing.

Expire binding does not expire when using longer intervals

Using openHAB 2.4.0 Release Build and Expire binding 1.13.0 which is just great! But, I have a z-wave wall socket that reports fine and has associations set and all …that has issues with the binding. When I set it to expire “2s, command=OFF” or 20m it just works. But 59m or 1h or more (longer intervals) it does not send command OFF it just keeps on going. I have looked in the logs and could not find anything suggesting it is updated during this period of time. Any tips ?

[OMR (Ole Morten Rønning)]

More from the guru

Expire Binding - Not Expiring

events.log does not include Item Updates. But based on the description, it sounds like the Item is being updated once per half hour. It is not unusual for bindings to update Items on a set polling period or periodically if the device reports it’s current state or the like. In fact, many users use this fact to find out when a device has stopped reporting using the Expire binding. You can create a Rule that triggers when the Item receives an update to confirm (in OH 3 look at the events feed in t…

[BiloxiGeek (Steve Berg)]

Okay, resurrected my old 2.5 timer into a rules file. Seems to be working as expected.

Thanks.

[Bruce_Osborne]

@OMR
There is no expire binding in OH3. It is part of the core functionality.