But on my phone, the notifications appear to be on?
Can you try refresh in the mobile app (More >> App Settings) and test again from the Device Details page in the hub's interface, before you do anything else.
Click refresh on the driver and it will hopefully refresh. Other option is to switch the driver to "Device" and use the command button to Delete Current States, then switch back to the previous driver you had it on for the Airthings.
OK, I'm now getting notifications, silent for some reason, even though my notification volume is set to max. I'll work on that. So is the next step to swap apps?
Yes swap app from the old device to the new one, that will transfer any of your existing notifications you setup in apps to the new virtual device.
So did fixing that html attribute issue fix the notifications?
Jeff, my notifications are working now. I had to change my default notification sound in my phone to get the sound to work. I think a recent phone update might have messed that up. Thanks so much to you and Bobby for your help with this.
A refresh of the AirThings device didn't resolve the html, and the type is grayed out, can't change it. Perhaps I'll ask the developer of that driver.
1 Like
I was participating in this thread at one point but had to drop out. Since then I've Replaced my iphone with an Android. The good news is when I reloaded hubitat It saw my new phone, so I added it in. The bad news is that Hubitat notifications still don't work Even on the new phone., however, as before, pushover notifications work beautifully. I'd rather have Hubitat Notifications, but frankly, I cannot spend any more time on this. IMHO, It should not be this difficult, but then I don't know anything about Hubitats software, so I'll leave it to the experts. Thanks I'll keep an eye on this thread.
I don't believe it. I went into my device list and checked off the old phone and started to get hubitat notifications On my new phone. So it's fixed I think
2 Likes
Hi team, I have a similar issue that isn't being solved by the solution in the post. The phone in question (not mine - belongs to a Guest user, i.e., not an Admin). Renaming the DNI and creating a new device sets up a new device with the same original DNI (is that typical?) and no notifications are sent to the phone connected to the new device.
I recall a problem way back where the mobile app devices accidentally got duplicated by a rule import so I am wondering if that is a possible culprit.
I removed the app and reinstalled before trying to create the new device but it still used the same DNI. Is there a way to change the DNI that the app uses when it creates the device?
I have searched for duplicate DNIs in the devices and can't find any.
App version 2.0.5 (273).
I even went as far as removing the guest account and reading, uninstalling and reinstalling the app and then creating a new device. Still the same result (and the same DNI)...
I think the new Android app uses the device UUID for the DNI so yes it will always be the same for the new app.
How are you testing the notifications? Did you try to send a test right from the device page of the mobile device created on the hub?
Yes, from the device page. For the record, this is also affecting the presence updates - they aren't happening either
@jtp10181 Is the UUID associated to the device or the account?
For android the device UUID is used for the DNI, I think.
Thanks. No point in creating a new account then, I presume?
It won’t change the DNI that the app uses, no. The DNI is just how it links the phone to the virtual device.
I am experiencing a similar issue (no notifications, etc.) and have been unable to resolve it using the suggestions above. App notifications are turned on. I tried the steps outlined by @jtp10181 to replace the mobile device with a new one. Test messages sent from the device page on my laptop are received on the new mobile device after it was created by the App. However, the notifications page and the notifications panel on the home page of the App show nothing. On the notifications page all I get is a spinner.
I see nothing in the logs related to the test messages. The only thing I see in the logs are periodic messages with the following:
Received cloud request for App 104 that does not exist, path: /mobile//mobile-app-events from cloud
Received local request for App 104 that does not exist, path: /mobile//hsm from local
They come from the hub (sys:1). I had no idea what App 104 was. But, if I go to the page http:///installedapp/configure/104, it says it's the "Mobile App Manager". There's nothing on that page that enables me to do anything, though, so I'm stuck.
This has been going on for some time and I was hopeful that an App update would fix it w/o me having to intervene, but that does not seem to be the case. I also don't have a fix. Can someone assist?
1 Like
