I also have iOS shortcuts for sending Pushover notifications. On there I have some automation that notifies me on my other devices when my battery drops below a certain % and also when it rises to a certain level. iOS has the notification built-in for dropping to a certain level on the local device but not to send to other devices.
It's great to plug-in my phone 'cause I'm leaving the house but want to make sure I get a charge first. It'll notify me when it hits 80% and then again at 100%. I don't have to charge sit.
I keep forgetting stuff. The notifications come in as standard Mac or iOS notifications. Here's the screenshot of my charge report from iOS that I got on my Mac
In that case, I don't see much of a use for my workflows.
I was hoping that the PO Notifications would be more detailed, maybe like the old Growl notifications.
Given that, I'd really appreciate if you would, when you have time, review and comment on the update I just made to the KM Wiki Plugin article: Wiki Update: Plug In Actions
I found the original article very hard to follow, and hard to understand exactly what I needed to do to create a Plugin. Since you just went through that process, maybe you will have some suggestions for improvement. All comments, pro and con, are welcome.
This is also one of my workflows with the KM Pushover plugin @kvan. In combination with the Power Manager app, I always have an overview of the battery level of my MacBook Pro on all devices. Even when I am not at home
On the iMac I implement the battery messages like this:
For FCP X and ScreenFlow 9, I am also informed about the completion of the export on all devices:
It's also important to mention that thanks to your KM Pushover plugin, you can invoke Siri Shortcuts (URL field) on your iPhone or iPad.
So if my Mac's wake up unauthorized, or my 1Password autofill login is executed, I get a notification via Pushover and can trigger a Siri Shortcut from it, which creates a snapshot via the FaceTime Camera.
I also get the snapshot via a Pushover notification and can in turn trigger a Siri Shortcut from it that locks the keyboards and plays a shrill alert sound.
In this video, an example of how to pass a scan to the Finder via Siri (iOS):
The possibilities are manifold. With a Siri shortcut in conjunction with a KM macro, I unlock my Mac's daily.
So I don't need a new M1 iMac with Touch ID for the time being .
The alarm sound at the end is much louder. I only lowered it a bit for the video.
In addition to the alarm sound, the keyboard is locked with the app Foil, so that no more inputs can be made.
I use this KM / Hazel 5 / Foil - workflow next to the KM 1Password Autofill macro also when waking up the Mac's or when disconnecting the power on the MacBook.
Hi @apple_sasi, please complete the AppleScript as follows:
(1) please enter your Pushover User Key here.
(2) enter the API token for Keyboard Maestro here.
(3) Please don't make any changes here, so don't enter any User Key or API Token!
(5) Please do not enter an image/icon for the API token for Keyboard Maestro, otherwise no individual images/icons can be displayed in the Pushover notifications on iOS.
And I copied all files to the folder.. and then modified the script.
But it didn't show on the third party plugins.
So I had to "drag & drop the zip file" on dock KM.
Then it displayed. But the zip file was "Keyboard-Maestro-Pushover-Notifications-master".
Even if I tried to modify the script file on "Pushover-Notifications", it didn't work on KM. ( I think I didn't load this file. )
Therefore, I changed the script file first and zipped... and drag & dropped on KM dock.
Then it works.
Was I doing a wrong way to create a folder and copy & paste all files .. and then modify the script file?
Should I just drag & drop the zip file after I add the API keys?
I just followed the github doc.
And now, I need your help for the another problem.
I have now 3 purshover notification.
How can I removed 2 of them? Apologize if it's too beginner question.
@apple_sasi You don't have to apologize. I was also a beginner and asked the same questions you did
You had to create the "Keyboard Maestro Actions" folder first? It's been so long, but I don't remember doing that. There should actually be other folders there as well.
This approach was correct, but you must consider this...
If you insert a folder with a new plugin, you have to close and restart the KM Editor as well as the KM Engine (menu bar top right).
Only then will the new plugin be visible in the KM Editor.
Please delete the 2 unneeded folders in the "Keyboard Maestro Actions" folder and quit and restart KM (as just described).
Then they will no longer be visible in the KM editor.
If you have any questions about using the Pushover plugin in KM, please contact me. If you want to use the Pushover notification for iOS actions, I have a similar Siri Shortcut Template for you .
I have noticed something in my usage of the plugin in regard to my macro which takes a picture and pushes to my phone.
The pushover notification fails every second time it is triggered.
I can not see why this is happening.
Has anybody else noticed this behaviour?
Has anybody else been getting these errors lately?
2023-03-14 12:30:00 Plug In failed with script error: /Users/cdthomer/Library/Application Support/Keyboard Maestro/Keyboard Maestro Actions/Pushover Notifications/PushoverNotification.scpt:0:13: script error: A real number can’t go after this identifier. (-2740).
It started a few days ago and a reboot has not fixed it. No other changes have been made. Every macro that uses this plugin suffers the same error.
EDIT Friday, March 24, 2023 @ 14:43:41 EDT: I figured it out, the AppleScript this plugin uses somehow became corrupted. It started working again after I replaced the AppleScript file.
Probably kind of obvious, but thought I would call it out here - I've deprecated the Send Pushover Notification plug-in. I've not had time to look at the plug-in or even jump in on the Forum and look for issues in quite a while as is so I'm happy Peter added this.
I don't plan on deleting the github but I did add a big note to the top of the readme that it is deprecated and to use the Send Pushover Notification action in Keyboard Maesto 11 instead. Your current usage should continue working as long as it meets the minimum requirements of the Pushover API (no idea how long that will be, they seem to be content to add new optional parameters to the existing API which is great)