Can Wyze take accountability for extremely delayed notifications?

Cameras
82

I downloaded the 2.8.24 version of the app. will install it tonight and see what happens.

I purchased my Pixel directly from Google, unlocked with no bloat from the providers. so it is as clean as can be.

I will let everyone know as I test it out.

2 Likes
83

ok – gave up and decided to test sooner than later and here are the results:

  • Version 2.8.24 - Did not work. Once the phone entered Deep Doze, notifications stopped
  • Version 2.7.19 - Did not work. Once the phone entered Deep Doze, notifications stopped

Unfortunately, neither of these worked on my phone running the latest update to Android 10.

I am only successful when the phone is unlocked, on charger, or the ADB Command has been run.

My settings are as follows for each version:

  • Display over other apps - Allowed
  • Modify System Settings - Allowed
  • Background Date - On
  • Unrestricted data growth - On
  • Permissions - Storage
  • Notification Sound - Default
  • Vibrate - On
  • Lock Screen - Show all Notification Content
  • Show Notification Dot - On
  • Override Do Not Disturb - On
  • Wifi Control - Allowed
  • Battery Optimization - None

Wondering if you did a different setting? I see a lot of articles indicating that Pixel / Google removed the Wifi Keep Alive option. Curious if you have that in your network area.

As I was typing this message, I got the alert - 7 minutes after it occurred.

2 Likes
84

I wondered about the fact that @sodcam didn’t just use an older version of the Wyze app, but also used an older version of the camera firmware. If that’s correct, then is it the firmware that broke things? What about the combination of old firmware but new app?

85

That could be the issue. However, my issue and tests is with a motion sensor as well. I tested with that to keep things consistent on my side. I really think it is related to some change in the Android OS - one of the latest updates. I used to get the notifications quickly and then sometime this year is when I noticed a change. I will see if I can downgrade the motion sensor firmware and see. But, I don’t believe it will make a difference.

You never know though.

86

I’m also more interested in motion and contact sensor notifications. When I heard about camera firmware as the potential problem, I thought it wasn’t relevant to the motion and contact sensors. But then I remembered that those sensors connect to a bridge that’s plugged into a camera. So maybe the camera firmware is involved after all?

87

Forgot about that as well, good catch. so I will do 2 tests.

  1. Put the old Firmware on the Motion Sensor and test - then Upgrade it back if it does not work
  2. Put the old Firmware on the Camera and test again.

I will try to do that this weekend

88

Experiment not going well today.

Added an old iPhone 5S to the table of “racing phones” and it beats the Androids every time for fastest alert response time.

The ‘old’ Android still beats the ‘new’ one much of the time, but not like yesterday.

Today the ‘new’ Android is now staying within 10-15 minutes, but last night it hit a new high of 45minutes tardy! Late in the night there was a sudden song of 7 alerts - in this group, the worst was 45 minutes late, the best was 30 minutes late. WTF.

It looks like Samsung pushed a “Samsung Experience” update one one or both of them, so new variable. Thought I’d disabled that…

I hate it when things seem to reliably repeat one day, but not the next… :rage:

But we consumers should not have to be doing any of this this - the Wyze guys get the big bucks - even for a $25 camera

1 Like
89

I echo your sentiments. My iPhone just works - I have an XS. With ADB command, the Pixel 4 works as expected. some of the times, it seems to beat the iPhone in notifications.

I am planning on testing the firmware as the app did not work. But I am betting it will not work as the notifications come from the app and not the firmware. However, this is the only thing I did not do.

2 Likes
90

Yeah, annoyingly the delays are not consistent on my non ADB’d standard set-up Samsung with all doze/ batt saving options available off. Typically they’re in the 10-15 minute range, sometimes a little less, around 6 or 7 minutes. But the other day I also had a bunch that took almost an hour before they started a blooming buzz-fest on my wyze band.

I’ve wondered if it takes till another apps notification(s) gives the doze a poke causing the WYZE notifications to then get through?
Like, what is the factor that would cause the delays to vary, and what is the trigger that eventually allows the WYZE app to push through doze to release the fishies after x amount of time?

Still haven’t attempted another go at the ADB console commands, but plan to.

1 Like
91

Still double checking those - they look about right - not sure about data growth and wifi control

What about this area - on Samsung Android 9 (not sure how 10 places or describes them):

Settings → Device Care → Memory → exclude Wyze
Settings → Device Care → Battery → Settings → Adaptive Battery - off
Settings → Device Care → Battery → Settings → Put Unused apps to sleep - off
Settings → Device Care → Battery → Settings → Auto disable unused apps - off
Settings → Device Care → Battery → Settings → Optimize settings - off

I think you’re right. The ‘old’ app is doing somewhat better this evening, but not enough that I’d recommend it at this point.

And all alerts have to go from the cam to Wyze to be distributed to each device ‘signed up’ for them, right? So maybe there’s something wonky with what the Wyze servers send out - like it’s not a high priority ‘wake up now’ code, but a lower level one? I really don’t know enough about the nuts and bolts of this stuff…

92

Been wondering similarly!

My thoughts were more about the carrier pre-installed apps and settings, but your idea is more likely.

Yes, I have a slightly different mix of apps on the test phones, also one is a Verizon and one is Sprint/Boost mobile - but am using both wifi only. I have not rooted them, but did clean them up as much as possible when I started using them. ( Die Bixby, Die! ) I have another Verizon of the same model, and the correct thing to do would be factory reset the two Verizons and only install the different Wyze apps for comparison.

93

The Pixel does not have some of the settings you referenced with the exception of Adaptive Battery. I turned Adaptive Battery off and it was noticeable difference in the battery drain, but not enough to worry about. Turning it back on, keeps the phone similar to the iPhone, somewhat better. In both cases, the issue still existed, so I decided not to turn that off.

I agree with your opinion here. In my job, we write apps for iOS. The process to get timely notifications to the phone is a bit involved. If not done correctly, they are delayed or you don’t get them at all. I am sure Android is the same way.

1 Like
94

I don’t think that is the case. My experience has been as follows: While using the phone or recently set down, the Alerts come in. I then put the phone down and set my iPhone next to it. after a period of time, the Alerts stop coming in on the Pixel but the iOS they still display. During this period, my Arlo Camera has notified me which triggered both phones to Alert. Even though the Pixel Alerted on the Arlo motion, none of the Wyze Alerts came through. I then opened the phone and was flooded with a number of Wyze Alerts.

So, as everyone has been saying, if Arlo and Eufy Cam can get the Alerts to come through, Wyze should be able to as well. There are a lot of setting which need to be set to indicate the urgency of the Alert. It is possible that something is not being set correctly or one of the updates to Android changed how this worked.

Hopefully this will be fixed soon.

1 Like
95

Yes, makes perfect sense. And if this bugs you as a programmer, there’s gotta be something wrong!

Good point! I missed this because I intentionally tried to narrow the variables by having only the Wyze app allowed to send notifications while testing. ( I was usually listening for alerts rather than being there watching them ) But, yes, we have a couple of Blinks and I never recall any alert weirdness with them.

Yeah, I mean, the alerts worked properly on Android at one time, didn’t they? I don’t recall an issue, but maybe it was an older Android version that wasn’t as dozy…

Amen!

1 Like
96

I’m just popping by to say that I don’t have an update but I am still watching the developments in this thread.

3 Likes
97

Thanks for popping in… :slight_smile:

Since this discussion is all over the Wyze forums, can you let me know if there is a consolidated location pertaining to these notification delays on Android devices? Also, as I offered before, if Wyze Developers would like to test a potential fix, before the app goes to Beta, please feel free to reach out. I would be glad to perform some basic testing to see if the issue has been resolved.

As you can ascertain from the thread, it is easy to reproduce and therefore, would be easy to test as well.

thanks

1 Like
98

(Pssst. How much would you be willing to pay to have this taken care of. I know a guy who knows a guy. Just sayin’…)

99

LOL, I can’t not reproduce it.

I tried the ADB route again last night, and sadly I just cannot get the commands in my Terminal to work. I followed the exact steps multiple times, carefully typed in the exact commands suggested in an above thread by jaffkey, and my Terminal doesn’t seem to recognize the ADB folder sitting right there on my desktop. Then tried putting the unzipped platform-tools folder into downloads and typed in cd~/Downloads/platform-tools, which is the exact title of the folder, and the response is still “no such file or directory”.

Next, I dragged and dropped the platform -tools folder directly into the terminal window, which then looks promising, as it looks like its right there no problems. Then plugged in the phone to the mac, USB is set to file transfer mode, USB debugging is turned on, type in ./adb shell dumpsys deviceidle disable , and the response I get is -bash: /Users/Macbook/Downloads/platform-tools: is a directory.
That’s it. Tried it many times and no joy… BTW, for some reason this imac was titled Macbook by the original owner, not sure why.
Maybe this imac’s OS is so ancient (it really is) the version of Terminal is somehow different and doesn’t want to play? Shame really, because otherwise it seems like it should pretty straightforward.

So, as long as I’m not able to get the ADB doze disable thing working, my only prayer is that WYZE can come up with a fix… Help me @UserCustomerGwen…you’re my only hope :wink:

Edited * just had a large batch of notifications arrive… 57 minutes after the fact :roll_eyes:

Edit from Sunday Morning* A new worst. Notifications bloom at 11:32 am telling me I should check out the event(s)…which occurred at 10:08 am. C’mon, that’s horrible. And these only came in after unlocking the phone, so who knows how long they’d have taken to come in, if at all.

100

With all of the testing in this one, I’m actually using this as my default thread at this point. I’d recommend continuing to use this one.

I know that this report is being shared and investigated but I can’t promise resolution timelines.

5 Likes
101

It’s greatly appreciated! I’ll for sure be checking in and more than happy to help test anything out as we go.

2 Likes