I'm sorry for starting yet another Notifications thread, but I cannot find an existing one which appears to match my experience:
The hub is C-8 Pro running 2.4.0.151.
The phone is an Android RP1A.200720.011 running your mobile app 1.7.4 build 141
In the basic sense, the Notifications are "working". I can send them from hub trigger events, and directly from the hub's device Commands screen.
They'll appear in the Tools | Notifications card in the mobile app. All good there...
However, the phone itself is entirely silent about the event. Nothing in the phone's status bar, no audio alert... when the event actually arrives.
If I need to open the app and go to this section to know that something happened, then it's more of a log than a notification, no? .
Under the Android's notifications setting from this app, I have "All Hubitat notifications" checked. Just under that element is a report from Android that "This app has not posted any notifications." It gets them, but doesn't "post" (or push?) them.
So the disconnect seems to be between your app and my phone's OS. At one point I read that there may be a replacement version of the app, but many of the reviews suggested not to load it.
Does the newer version work knowingly address my problem?
The newer version is entirely rewritten. It worked knowingly towards addressing several problems.
Unless you have a specific reason to prefer the 1.x app, which is no longer receiving active development, I would try the 2.x app (the icon with the green background instead of the white background). If you have any specific problems with it and can't find a matching topic here, feel free to create one in an appropriate category with the right information to troubleshoot or narrow down the problem.
You can keep both versions of the app installed, though I'm not sure if there are still problems with the "mobile app device" getting irrevocably stolen by one version of the app (certainly not if you get the offer to create an entirely new mobile app device on the hub, which I'd suggest if you want to keep both around and keep things like notifications separate between the two -- otherwise keep in mind you need to make sure any app sending a notification is using the right device).
I guess I'll disregard the advice and try the new one. If it basically leaves the original intact, then all I could loose is time, right?
By "knowingly", I meant that there would be some post or release note that specifically acknowledged the problem and correction.
While I can understand the IT helpdesk goal to bounce as many issues as possible in a given day, I've never been a big fan of the kneejerk response of "Maybe version X will fix it." when compared to the better response "We found and fixed that in version X."
Nothing on you of course, I'm just ranting in general.
Will update the thread soon with the results... thanks again.
There aren't any known problems with notifications in 1.x from what I know. But aside from also being for (and from) Hubitat, the "new version" is an entirely different app, so what I meant is that it's sort of like asking if a new cantaloupe would fix a problem with your watermelon.
If you have problems with notifications in the new app, I'd lean towards a device configuration problem, though it seems like you checked everything reasonable above for the old version, and I'm not an Android user, so can't suggest what; but maybe other users can. Good luck!
FYI, I do not work for Hubitat support, nor do most users in the Community forum, so this is the only possibility that makes sense.
Just to circle back, I renamed the original mobile device with a "v1" in the old app - and then installed the latest Elevation app, which offered to add the same mobile device again. Kept the new one, removed the old one, and the notifications started working again. Solution time.
For now, I'm keeping the old one around too; as the latest seems a bit glitchy in other areas, which of course is a separate thread if needed.
.
