Getting more out of notifications

So this isn't strictly a Hubitat thing. I currently have notifications setup to go to mine and my wife's phones when the washer or dryer finishes. I have some ideas for other notifications as well.

Notifications can be useful, but I feel like there are a few things that could make them more useful. Here is a use case: The washer finishes. A notification goes to both phones. I move the laundry to the dryer and on the "washer is finished" notification, I hit a "done" button or something similar and clears the notification from my phone AND my wife's phone. That way she isn't left wondering if the laundry has been moved. Bonus points if it can send a command back to Hubitat to press a button. Also would prefer if the notification cannot be swiped away by accident.

Does anyone know of a way to do something like this?

1 Like

I have a Notification Tile driver that I use to split out notifications and display on a dashboard tile, that may work for you. I set it to be the destination of notifications of specific applications/integrations so that I can see the last 5 at a glance; i.e. you can have HSM going to a tile, and a general tile that shows everything else.


1 Like

For such tasks I use the App Tasker, which is an events/trigger driven programming environment for Android.

With Tasker you can intercept clicks on notifications, and e.g. then do a http-get to reach Hubitat by using it's Maker API.

1 Like

I found this and I think I'm going to mess around with it this weekend.

1 Like

Hi @thebearmay! I would like just to say THANK YOU! This driver conjugate with your app Lock History are the best alternative to the native app Lock Manager, that never worked to me!


Hi @thebearmay!

Your driver Notify Tile Device and the app Lock History aren't working anymore. Do you you intend to update them?

Are you getting an error? Haven’t looked at Lock History for a while, but willing to take a look at it if you can describe what isn’t working. Notify Tile I still use every day and haven’t seen any issues.

So the error probably is caused by the app, once I use its notifications on Notify Tile.

Lock Story just stopped to send notifications one week ago, and when I tried to access the History or the Maintain alternate names in the app it stucked with a message saying that An unexpected error has occurred trying to load the app. Check Logs for more information.

Is there an error in the log?

Nop, it is empty. It seems to be the same kind of problem that affected another app I use, Device Activity Check. When I hit the internal links the same error appear! I believe it is related to some hub update.

I’m on the road again, so it will be a couple of days before I can look at it, but I’ll take a look when I get back.

1 Like

@thebearmay, the other app I said was with an analog issue had a string that was causing the error. The solution was indicated by an user here.

I hope it be useful! By the way, is there some way to show just the last notification instead of the last five in your Notification Device Tile?

Thanks I’ll take a look at that. As for number of messages displayed try changing line 66 to

input("msgLimit", "number", title:"Number of messages from 1 to 20",defaultValue:5, range:1..20)

Edit: Same issue as thread you pointed out -embedded sections, Would have taken me a while to see that. New verision of Lock History is out on Github. Thanks.

1 Like

Who thanks again it is me, @thebearmay! Changing the value indicated made the magic.

Greetings directly from Brazil!

@thebearmay your notification driver is perfect! However, it doesn’t seem to work correctly with Webcore (but worked as expected with RM). In Webcore, only the latest notification can updated, and overwritten without “pushing” the previous ones pdown. I attempted to troubleshoot the issue without success. Any idea what the issue might be?

For webCoRE there are two ways to use it, but only one results in a push message going out. The first is using the device command sendMessage (required by the capability), this will add the message to the Notification Tile and push the previous messages down the stack, but not send a system push message - think of this as a way of testing the functionality of the device. The second, and correct way of using it, is to define the Location Tile as a notification device for webCoRE, and use the webCoRE Location command Send Push Message - this will again add the message to the device stack, but will also invoke HE's push message function.

I believe this is how I have set it up, but still only the last entry get updated rather pushing previous ones down. Here is the code I use to test:


And the way the tile is setup in the dashboard:

Again it works fine in RM, but misbehave in Webcore.

I’d appreciate your help!

I find it takes a couple of seconds sometimes to get the update. Try something like:

Using your approach I still get the same results…

Actually this time only notification #2 made it, rather than the last one (notification #3).

Download the Hubitat app