Several of us were talking in the Webcore thread, and have noticed that notifications in the Hubitat mobile app aren't working consistently on Android. Some phones working, some not. Anyone else notice this?
The notifications appear in the Notifications section in the Hubitat mobile app, if you go there to look for them. However, they only appear in the app notification section, and otherwise are completely stealth, and make no sound or vibration, and we don't see any notification notice in the Android Notification shade.
The notifications appear in the Hubitat app Notification section:
We're not sure why this doesn't work...we were talking about this in the Webcore thread but it seems like an HE app issue that needs to be looked into, as it doesn't work from the driver page either.
Thanks for the questions. All battery saving and others restrictive actions are disabled for the app.
Notifications do not show or make any sound if the app is in the background. I have not tested it with the app in the foreground and the phone turned on, because that just doesn't work for me anyway. But I get that we should check that to see if it works in that case from a troubleshooting perspective. I'm in the road and probably won't r be able to test today.
Oops, I had forgotten I had uninstalled and reinstalled the app recently. When I reinstalled it I evidently forgot to go back in and turn off all battery optimizations. So on my most recent testing battery optimization was on. @BorrisTheCat, did you test with battery optimizations disabled?
Just tested this again and also tried with the notification page open and that DIDN'T change dynamically, is that correct? Then went to the dashboard page and back and the 2 notifications I send where then there.
So you're saying no one in the office w/Samsung phones can replicate the notification failure on their phones? That's interesting...would help if you can confirm if they include S9 and S10 devices, which I believe are what @BorrisTheCat and I have, respectively.
Regarding your suggestion for testing - I'm not sure exactly what you mean when you say "...creating a new device with the same actual device changes something..."
Can you provide more detail on what you're suggesting?
Yeah, when you select a hub, then it show a list of mobile devices, on that screen you can either select existing one or create a new one. Then with that one send a push notification from the Hub WebUI devices interface.
This may have possibility caused my issue? You said I had to have a device per hub inorder to get to the tools menu so I'm wondering if that's when it started
@moncho1138 I fixed it but had to go nuclear (or clever version of it). I changed my network I'd and changed the driver. Then clicked the hub and now my old device was gone ( tried creating a new one with it there before and it didn't work maybe a bug?) . Then created a new one and got a event sent. In the new device page in HE, I copied the network ID and added a X to the beginning of it. I then pasted this ID (without the X) In my old device ( with all the rules and apps attached) and saved it. Tested it and it worked. Then deleted the "new" device place holder and then reselected my hub and device in the app and tested again. All good. So so thing went out if wack with that network ID on HE side.
Funny, I was going to ask you if you had ever worked it out, and there was your post.
Ye gods...that is pretty nuclear. I'm glad you worked it out. Now that I have the built-in notifications working I'm pretty pleased w/it. I may try Pushover, but I went to Hubitat in part to avoid cloud connections, and don't like adding another 3rd party to all of my notifications...
This is the 1st time anything like this has happened and on my phone. My wife's had a geo issue for a while but was fixed on a few updates ago. It's a new app and has come on leaps and bounds since release, the best thing about it is your location doesn't leave your phone . That is unheard of with location apps and makes it extremely reliable for me.