False Notification - Notifications App

I have the Notifications App set to notify me if my fridge stays opened for more than 5 minutes. I've installed a contact sensor on my fridge for this purpose.

The app had been working fine for about a week till I got my first false notification today that the fridge was opened. I checked the fridge contact sensor's logs and the fridge was closed when I got notified. To stop the notification from infinitely repeating, I had to open the fridge and close it back. Somehow, even though the fridge was clearly closed, the Notifications App missed that and thought the fridge was still opened. Logs are below.

Please does anyone know what happened here and how to prevent it going forward?

Thanks

contact closed Fridge was closed DEVICE 2020-03-08 12:18:55.959 PM EDT
contact open Fridge was opened DEVICE 2020-03-08 12:18:53.556 PM EDT
contact closed Fridge was closed DEVICE 2020-03-08 12:11:53.230 PM EDT
contact open Fridge was opened DEVICE 2020-03-08 12:11:33.872 PM EDT
Name Description Value Date
Notifier Fridge has been left open for over 5 minutes. Please close it. notified 2020-03-08 12:18:40.837 PM EDT
Notifier Fridge has been left open for over 5 minutes. Please close it. notified 2020-03-08 12:16:37.434 PM EDT

LOGS:
dev:6592020-03-08 12:18:46.475 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:6282020-03-08 12:18:44.425 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:6602020-03-08 12:18:40.798 pm warn Echo (v3.6.0.0) | speechCmd | Too Many Requests Made to Amazon | Msg: Too Many Requests

dev:702020-03-08 12:18:40.302 pm infoBedroom Motion Sensor is inactive

dev:6592020-03-08 12:18:40.208 pm warn Echo (v3.6.0.0) | speechCmd | Too Many Requests Made to Amazon | Msg: Too Many Requests

dev:6582020-03-08 12:18:39.373 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:6572020-03-08 12:18:38.692 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:6282020-03-08 12:18:38.298 pm warn Echo (v3.6.0.0) | speechCmd | Too Many Requests Made to Amazon | Msg: Too Many Requests

dev:6262020-03-08 12:18:37.904 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:6602020-03-08 12:16:43.602 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:6592020-03-08 12:16:43.049 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:6582020-03-08 12:16:42.690 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:6602020-03-08 12:16:37.417 pm warn Echo (v3.6.0.0) | speechCmd | Too Many Requests Made to Amazon | Msg: Too Many Requests

dev:6592020-03-08 12:16:37.039 pm warn Echo (v3.6.0.0) | speechCmd | Too Many Requests Made to Amazon | Msg: Too Many Requests

dev:6582020-03-08 12:16:36.469 pm warn Echo (v3.6.0.0) | speechCmd | Too Many Requests Made to Amazon | Msg: Too Many Requests

dev:6572020-03-08 12:16:35.838 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:6282020-03-08 12:16:35.195 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:6262020-03-08 12:16:34.666 pm info Echo (v3.6.0.0) | SpeakCommand Sent | (Fridge has been left open for over 5 minutes. Please close it.) | Runtime: (6 sec) | QueueItems: (0)

dev:1972020-03-08 12:11:53.219 pm infoFridge was closed

dev:1972020-03-08 12:11:33.861 pm infoFridge was opened

The notification happened at 12:18:40 and the door was closed at 12:18:55. So, why do you think it shouldn't have sent the notification? It appears that the problem is with Echo Speaks. You see the "Too Many Requests" error? I don't know what that means as far as echo speaks but the Notifications app looks good to me.

Ignore the too many requests. The door was re-opened at 12:18:53:556 PM and re-closed at 12:18:55:959 to clear the notification. If not, the notification would have kept repeating every 2 mins indefinitely.

The issue is that the door was opened at 12:11:33PM and closed 20 seconds later at 12:11:53PM. Yet the notifications app thought it was still opened so went off 5 mins later at 12:16:37PM and repeated 2 mins after that at 12:18:40PM. Issue has nothing to do with Echo Speaks

What about Fridge Door? You have two contact sensors in that notifier app, Fridge and Fridge Door. You only show "Fridge" in your events list.

Fridge Door wasn't touched during that period. Here's the event log for that.

contact closed Fridge Door was closed DEVICE 2020-03-08 12:24:09.322 PM EDT
contact open Fridge Door was opened DEVICE 2020-03-08 12:24:05.161 PM EDT
temperature 41.00 °F Fridge Door temperature is 41.00°F DEVICE 2020-03-08 12:05:56.910 PM EDT

Is this reproducible? This happens every time you open and close it within the timeout? Or was this a one-off? If it's reproducible, just for laughs, try removing one of the contact sensors and try it again.

One off

Oh....then I wouldn't be too worried about it. Any system as complicated as Hubitat is going to have one-off glitches like that. If it rears it's ugly head again, then I'd start to investigate. But if the problem isn't reporducible it's very difficult to try and find a root cause, especially considering there might not really be one.

This happens to me once in a while with my contact sensors when the batteries run low. Try checking those.

He has an event for everything that he suspected should be there. So I don't think ti's a device issue.

I've just had these false notifications occur again 3x in the last 2 days. i'm wondering if something in the latest firmware broke the Notifications app. In each of the cases, my fridge door was closed, Hubitat showed it as closed, yet the notifications app claimed it was open.

Name Value Unit Description Text Source Type Date
contact closed Fridge Door was closed DEVICE 2020-05-27 12:18:40.363 AM EDT
contact open Fridge Door was opened DEVICE 2020-05-27 12:18:36.323 AM EDT
temperature 44.60 °F Fridge Door temperature is 44.60°F DEVICE 2020-05-27 12:13:33.389 AM EDT
contact closed Fridge Door was closed DEVICE 2020-05-27 12:06:53.316 AM EDT
contact open Fridge Door was opened DEVICE 2020-05-27 12:06:42.222 AM EDT
Name Value Unit Description Text Source Type Date
contact closed Fridge Door was closed DEVICE 2020-05-25 07:53:28.018 PM EDT
contact open Fridge Door was opened DEVICE 2020-05-25 07:53:14.488 PM EDT
contact closed Fridge Door was closed DEVICE 2020-05-25 07:52:00.827 PM EDT
contact open Fridge Door was opened DEVICE 2020-05-25 07:51:55.960 PM EDT
contact closed Fridge Door was closed DEVICE 2020-05-25 07:49:58.579 PM EDT
contact open Fridge Door was opened DEVICE 2020-05-25 07:49:46.242 PM EDT
contact closed Fridge Door was closed DEVICE 2020-05-25 07:45:15.324 PM EDT
contact open Fridge Door was opened DEVICE 2020-05-25 07:44:34.485 PM EDT
Name Description Value Date
Notifier Fridge Door has been left open for over 5 minutes. Behave yourself and close it. notified 2020-05-27 12:21:41.533 AM EDT
Notifier Fridge Door has been left open for over 5 minutes. Behave yourself and close it. notified 2020-05-27 12:18:41.019 AM EDT
Notifier Fridge Door has been left open for over 5 minutes. Behave yourself and close it. notified 2020-05-25 07:52:02.323 PM EDT

I should also note that the false notifications happened when the fridge door was opened and closed very quickly (within 5 seconds).

For the false notification at 7:52:02pm, the fridge was opened at 7:51:55pm and closed just over 4 seconds later at 7:52:00pm.

For the false notification at 12:18:41am, the fridge was opened at 12:18:36am and closed just over 4 seconds later at 12:18:40am.

I suspect that when it's opened and closed too quickly, the Notifications app gets confused and gives a false notification. I've had cases of it being opened and closed in 2 seconds though and I didn't get false notifications so not sure.

It's also weird that it didn't even wait 5 mins to give the false notification. It complained as soon as the fridge door got closed.

Can anyone help here please?

Thanks!

If you android they mess with you os from the new upgrades from android add adaptive notifications

Screenshot_20200703-082357_Settings|265x500

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.