Wonky things happening on 2.3.0.119 that never has happened before

Since upgrading to 2.3.0.119 there has been a few things that worked great and never acted up until this upgrade, and now its just strange like the hub has some type of mind of its own.

This one is the one that bothers me, I left at 4am this morning, wife left at 430am to go to work. Presence worked fine, it noted that Lisa had left, we both are gone locked both the doors and set the hub to Away. However right after the message we were away was sent, the laundry room door became unlocked! What is stranger about this is I got no notification that the door was unlocked even though I have a rule that says if everyone is away. I tested when I got home and if we are all away, door is unlocked we get notified so..

Thoughts? start from bottom and work back towards top

If I'm reading this I don't see where the laundry door got locked and if that is the case, why would it set my home in Away when I have it HSM set for any unlocked door or open door to notify me. I know this works because the other night I got notified when I left a door open (testing things)

device 72 laundry door

dev:14 12021-12-17 04:35:32.384 am infoWSensor Attic temperature is 54.38°F
dev:72 2021-12-17 04:31:40.581 am infoLaundry door lock battery is 100%

dev:72 2021-12-17 04:31:40.403 am infoLaundry door lock is unlocked

dev:98 2021-12-17 04:31:40.304 am infoFront door Lock battery is 100%
dev:98 2021-12-17 04:31:40.197 am infoFront door Lock is locked
app:34 2021-12-17 04:31:32.613 am infoArmed Away
dev:73 2021-12-17 04:31:32.520 am infoSending Message: NOTICE: Everyone is away! Doors are closed and locked and Mode set for Away Priority: 0 to Device: (all devices)
dev:73 2021-12-17 04:31:32.519 am infoSending Message: NOTICE: Everyone is away! Doors are closed and locked and Mode set for Away Priority: 0 to Device: (all devices)
app:537 2021-12-17 04:31:32.491 am infoAction: Notify Pushover: 'NOTICE: Everyone is away! Doors are closed and locked and Mode set for Away'
app:537 2021-12-17 04:31:32.485 am infoAction: Notify Pushover: 'NOTICE: Everyone is away! Doors are closed and locked and Mode set for Away'
app:537 2021-12-17 04:31:32.482 am infoAction: Mode: I'm Away
app:537 2021-12-17 04:31:32.468 am infoAction: Mode: I'm Away
app:537 2021-12-17 04:31:32.465 am infoDelay Over: Delay 0:00:05
app:537 2021-12-17 04:31:32.445 am infoDelay Over: Delay 0:00:05
app:537 2021-12-17 04:31:27.405 am infoAction: Delay 0:00:05
app:537 2021-12-17 04:31:27.381 am infoAction: Delay 0:00:05
app:537 2021-12-17 04:31:27.263 am infoAction: Lock: Laundry door lock, Front door Lock
app:537 2021-12-17 04:31:27.257 am infoAction: Wait for Expression: David - Life360, Lisa - Life360 all not present(T) [TRUE] (rule true, not waiting)
app:537 2021-12-17 04:31:27.144 am infoAction: Lock: Laundry door lock, Front door Lock
app:537 2021-12-17 04:31:27.101 am infoWait for Expression over: Lisa - Life360 presence is not present
app:537 2021-12-17 04:31:27.090 am infoSet - I'm Away Triggered
app:537 2021-12-17 04:31:27.051 am infoSet - I'm Away event: Lisa - Life360 presence not present
app:537 2021-12-17 04:31:27.050 am infoSet - I'm Away event: Lisa - Life360 presence not present
dev:141 2021-12-17 04:30:33.552 am infoWSensor Attic temperature is 55.69°F
dev:246 2021-12-17 04:30:02.865 am infoWSensor Refrigerator temperature is 73.78°F
dev:162 2021-12-17 04:29:22.376 am infoLisa - Mobile has departed

Lisa mobile device - presence not present Lisa - Mobile has departed DEVICE 2021-12-17 04:29:22.377 AM MST
Lisa life 360 device - presence not present Lisa - Life360 has departed DEVICE 2021-12-17 04:31:26.998 AM MST

This is where I notice the door is unlocked and lock it - dev:722021-12-17 05:39:59.254 am infoLaundry door lock is locked

My away rule

Wait for Expression: David - Life360, Lisa - Life360 all not present(F) [FALSE]
Lock: Laundry door lock, Front door Lock
Delay 0:00:05
Mode: I'm Away
Notify Pushover: 'NOTICE: Everyone is away! Doors are closed and locked and Mode set for Away'

There is an update to 119, I would do the 120 update.

Also, 119 had some unspecified fix for database corruption, have you tried a soft reset and restore a backup?

Lastly, I would go into that rule and try "Done" to see if that makes ay difference to how it acts.

1 Like

Should upgrade to .120 as .119 has a potential to corrupt the DB.

1 Like

I will upgrade, however the DB Corruption fix was in 2.3.0.119 not .120

NOTICE : We found an unfortunate break in a core hub module that can lead to database corruption. We strongly recommend all users to upgrade to 2.3.0.119.

That rule worked just like that without fail for years..

The platform version is not related to the reported issue -- upgrading the platform is often named for any problem that appears after the update. The presumption made of a causal relationship is false.

Look elsewhere...