Hi,

Nice work. Would you bother to explain the demo video setup you have ?
I guess you are running commands on your android phone ?

Thanks.

• Document shell focus support
• Better intro (what to focus on more? shell integration? push notifications?)
• Update install for single file exe
• Fixup references to extras
• Re-record demo (how could I demo shell integration?)

See https://github.com/jml/undistract-me for an example

Main concern is long running interactive jobs. Ie, I don't want a notification for vim.

I want to use ntfy to notify me from my headless serve (ubuntu 14).
A script starts at inserting a disc in the drive
SUBSYSTEM=="block", KERNEL=="sr0", ACTION=="change", RUN+="/usr/local/bin/add-disc.sh"
In add-disc.sh i do some differnet things (in the backgrond -> headless) and want be notified via ntfy. All commandos in add-disc.sh works - not nfty.
Is there a parameter to let nfty work in background?

It works very nicely on normal terminal but, I get an error on guake terminal.

Hello!

I have a problem with ntfy on my Raspberry Pi 2 Model B running the last version of Raspbian. All my packages are up to date.

I installed ntfy with sudo pip install ntfy without any error.

If I type just ntfy, no problem, the help page is displayed. But when I try to add any argument I have that error :

pi@raspberrypi:~ $ ntfy send test
Warning: there was a problem loading ~/.ntfy.json (Expecting property name: line 5 column 3 (char 80))Traceback (most recent call last):
File "/usr/local/bin/ntfy", line 11, in
sys.exit(main())
File "/usr/local/lib/python2.7/dist-packages/ntfy/cli.py", line 128, in main
return send_notification(args.func(args), args, config)
File "/usr/local/lib/python2.7/dist-packages/ntfy/cli.py", line 74, in send_notification
*_backend_config)
File "/usr/local/lib/python2.7/dist-packages/ntfy/backends/default.py", line 9, in notify
module.notify(title=title, message=message, *_kwargs)
File "/usr/local/lib/python2.7/dist-packages/ntfy/backends/linux.py", line 7, in notify
bus = dbus.SessionBus()
File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 211, in new
mainloop=mainloop)
File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 100, in new
bus = BusConnection.new(subclass, bus_type, mainloop=mainloop)
File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 122, in new
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

The error is talking about ~/.ntfy.json but I'm pretty sure that the file is ok because I copied it from the Wiki ^^

Hope you can find a solution :)

Add 'ntfy/VERSION' to beginning of requests.utils.default_user_agent().

Use yapf to format all the source and add a contributing.md suggesting contributors do the same.

Options:

• PyInstaller (crossplatform)
• py2exe (windows)
• cxfreeze (linux)
• py2app (macoss)

A potential pitfall: virtualenv issue. Possible solution (tested on Linux): create virtualenv but then use system python and add that virtualenv's site-packages to PYTHONPATH. (or.. just pip install --target)

Hello,

Really happy that #19 exists but it doesn't seem to read the ignore options in my .zshrc profile:

eval "$(ntfy shell-integration)"                                                                                                                                                                                                               
AUTO_NTFY_DONE_TIMEOUT=${AUTO_NTFY_DONE_TIMEOUT:-40}                                                                                                                                                                                           
AUTO_NTFY_DONE_IGNORE=${AUTO_NTFY_DONE_IGNORE:-emacs gstat info less /usr/local/bin/lua53 mail man meld most mutt nano screen ssh tail tmux top vi vim}

Pushover notification: "/usr/local/bin/lua53" succeeded in 1:09 minutes
and for python3: "python3" succeeded in 1:27 minutes

Is there something wrong in my configuration above?
I've re-loaded the zshrc profile many times with source .zshrc and completely logged off and back but it continues to ignore settings for python and lua.

Currently there doesn't seem to be a way to set the sound used on pushover. Is there a possibility of exposing the sound attribute so that it could be used?

https://pushover.net/api#sounds

$ pip3 install ntfy[emoji] returns zsh: no matches found: ntfy[emoji]

I use the same .bashrc on desktop and server systems so I don't want shell integration complaining about lack of dbus missing or DISPLAY env var not being set if I haven't set a push based notification. Focus support should also only warn if it doesn't work.

Should I use XDG Base dirs for the config? EG: ~/.config/ntfy/ntfy.yml instead of ~/.ntfy.yml. Use ~/Library/Appplication Support/ntfy/ntfy.yml on Mac? Windows???

ref: http://stackoverflow.com/questions/3373948/equivalents-of-xdg-config-home-and-xdg-data-home-on-mac-os-x

Executing ntfy with Pushover backend this way:
$ ntfy -o priority 2 send "f*ck"

yields to this error:
ERROR: Failed to send notification using pushover
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/ntfy/init.py", line 30, in notify
module.notify(message=message, title=title, **backend_config)
File "/usr/lib/python3.5/site-packages/ntfy/backends/pushover.py", line 63, in notify
if priority <= 2 and priority >= -2:
TypeError: unorderable types: str() <= int()

https://github.com/dschep/ntfy/blob/master/ntfy/backends/pushover.py#L63

ntfy is nifty. Are you interested in adding support for Telegram? I made a package that could be used. It has a configure function to guide users in setting it up and a send function to send stuff.

conf = "~/.config/ntfy/telegram-send.conf"
telegram_send.configure(conf)
telegram_send.send(messages=["hello"], conf=conf)

That call to configure saves the credentials (api token, and which user to send messages to) in the conf file and the call to send uses it to send a message.

I'd like to help if you're interested.

At least on Windows 10 the icon looks like crap, despite being high enough resolution for the size it's displayed at.

The reason that you can't emit notifications within a virtualenv is simply that the Info.plist which would make the virtualenv a valid app-bundle is missing. This blog post shows how to fix it up so that it'll work.

Idea from @danryder.

Questions:

• stderr and stdout separately or combined?
• suppress output or still print to console?

the tag/pkg-resources version thing doesn't work with the single file bin

The python icon is ugly

when running with

export AUTO_NTFY_DONE_UNFOCUSED_ONLY=-b 

Notification are send only when the window isn't focused, but when one works with multiple tabs open,
it will be nice to have notifications sent too. The solution right now is to completely disable this option
and accept that notifications will be sent even if the current tab is focused.

did it support mac?

and also create a github releases? or maybe just artifacts?

I have an issue with the pushbullet backend:

> ntfy -b pushbullet send "hey"
Traceback (most recent call last):
  File "/usr/bin/ntfy", line 11, in <module>
    load_entry_point('ntfy==2.1.1', 'console_scripts', 'ntfy')()
  File "/usr/lib/python3.5/site-packages/ntfy/cli.py", line 304, in main
    **dict(args.option.get(None, [])))
  File "/usr/lib/python3.5/site-packages/ntfy/__init__.py", line 34, in notify
    backend_config.update(kwargs)
AttributeError: 'NoneType' object has no attribute 'update'

cat ~/.config/ntfy/ntfy.yml 
backends:
- linux
- pushbullet

pushbullet:
access_key: <my_key>

$ ntfy -b pushover -o user_key secret_token send 'Pushover test!'
ERROR: Failed to send notification using pushover
Traceback (most recent call last):
  File "/usr/local/bin/ntfy/ntfy/__init__.py", line 34, in notify
    module.notify(message=message, title=title, **backend_config)
  File "/usr/local/bin/ntfy/ntfy/backends/pushover.py", line 107, in notify
    headers={'User-Agent': USER_AGENT})
  File "/usr/local/bin/ntfy/requests/api.py", line 107, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/usr/local/bin/ntfy/requests/api.py", line 53, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/bin/ntfy/requests/sessions.py", line 468, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/bin/ntfy/requests/sessions.py", line 576, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/bin/ntfy/requests/adapters.py", line 447, in send
    raise SSLError(e, request=request)
SSLError: [Errno 20] Not a directory

Where my secret_token is replaced with my actual user token.

Thoughts?

XMPP service jit.si is down ATM so my notifications can't be sent. However, ntfy[xmpp] tries over and over to make a connection:

ERROR: Could not connect to [2001:41d0:a:1c2c::17]:5222. Socket Error #65: No route to host
ERROR: Socket Error #54: Connection reset by peer
ERROR: Could not connect to [2001:41d0:a:1c2c::17]:5222. Socket Error #65: No route to host
ERROR: Error reading from XML stream.
ERROR: Could not connect to [2001:41d0:a:1c2c::17]:5222. Socket Error #65: No route to host
ERROR: Socket Error #54: Connection reset by peer
ERROR: Could not connect to [2001:41d0:a:1c2c::17]:5222. Socket Error #65: No route to host
ERROR: Socket Error #54: Connection reset by peer
ERROR: Could not connect to [2001:41d0:a:1c2c::17]:5222. Socket Error #65: No route to host
ERROR: Error reading from XML stream.
ERROR: Could not connect to [2001:41d0:a:1c2c::17]:5222. Socket Error #65: No route to host
ERROR: Socket Error #54: Connection reset by peer
ERROR: Could not connect to [2001:41d0:a:1c2c::17]:5222. Socket Error #65: No route to host

Could it be made to quit trying to connect after 60 to 120 seconds?

By calling ntfy done sleep 2 I'm getting:

Traceback (most recent call last):
  File "/usr/local/bin/ntfy", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python2.7/dist-packages/ntfy/cli.py", line 247, in main
    message = args.func(args)
  File "/usr/local/lib/python2.7/dist-packages/ntfy/cli.py", line 26, in run_cmd
    if args.pid:
AttributeError: 'Namespace' object has no attribute 'pid'

It does not matter what I append to done. I'm getting the same Traceback.
Anyway what is the correct syntax for calling ntfy done with a pid?
I'm using ntfy 1.3.0 including ntfy[emoji] and ntfy[pid].

Hello,

I have 1.2.0.post13 how do I get the pid functionality?

Send push notification when command finishes

positional arguments:
  {send,done,shell-integration}
    send                send a notification
    done                run a command and send a notification when done
    shell-integration   automatically get notifications when long running
                        commands finish     

It would be nice if ntfy could read the config from /etc/ntfy/ntfy.yaml if no ~/config/ntfy/ntfy.yaml exists.

% ls -l
...
ntfy done: error: argument --formatter: expected 3 arguments

This is with the single binary and with zsh AUTO_NTFY_DONE setup. Will I need to continue to use pip for auto shell integration?

Unlike #72, which is about the structure of the virtualenv's metadata, ntfy doesn't work on Ubuntu because it needs to import dbus, and you can't pip install dbus easily, so you need to use the system version.

One potential fix for this is to simply hack in a sys.path.append that adds the directory where the importable dbus is found, import it, and then sys.path.pop() to remove it; this will be more restrictive than a full-on --system-site-packages virtualenv, but can still get that one library from the system.

Hi,

Version of ntfy: 2.0.3
Platform: i386 freebsd
python version: 3.4.4

shell integration in my .zshrc:

eval "$(ntfy shell-integration)"
AUTO_NTFY_DONE_TIMEOUT=60
AUTO_NTFY_DONE_IGNORE='atop emacs gstat info less lua53 jupyter mail man meld most mutt nano screen ssh sqlite3 tail tmux top vi vim' 

On the client.pushover.com site:

[email protected]:/usr~
"sleep 50" succeeded in 0:50 minutes

Does this happen with your bash integration?

After installing the dependencies, I tried ntfy.

root@3b84f399b67d:~# ntfy -b linux -v send 'test'
WARNING: Failed to send notification using linux
root@3b84f399b67d:~# ntfy send test
WARNING: Failed to send notification using linux
root@3b84f399b67d:~# ntfy done sleep 2
WARNING: Failed to send notification using linux

Without any other exceptions showing, I can not find out the root cause.

Just a random silly idea: using a context manager to help with notifying about tasks

Would intergrate well and easily with personal python scripts n' stuff, or any codebases which would benefit from being able to easily add in notifications (buildbots perhaps?)

(note: the following code isn't exactly clean or complete, if you want this to be made into a pull request or whatever, I can)

class TaskNotifier:
    def __init__(self, task_name, on_enter=True, on_exit=True, on_error=True,
                 config=None, **kwargs):
        self.task_name = task_name
        self.on_enter = on_enter
        self.on_exit = on_exit
        self.on_error = on_error
        self.config = config
        self.kwargs = kwargs

    def __enter__(self):
        # start_time = now()
        if self.on_enter:
            # questionmark notification icon?
            ntfy.notify("Task: {}".format(self.task_name),
                        "task has started!")

    def __exit__(self, exc_type, exc_value, traceback):
        # task_time = start_time - now()
        # task_time = enprettyfy(task_time)
        if exc_type and self.on_error:
            # X notification icon?
            ntfy.notify("Task: {}".format(self.task_name),
                        "task has errored out after {}!".format(task_time))
        elif self.on_exit:
            # Tick notification icon?
            ntfy.notify("Task: {}".format(self.task_name),
                        "task has finished in {}!".format(task_time))
        # if self.suppress_error: return true ?

It would also simplify the whole run-a-process command already within the library (not that it isn't already)

def for_a_process_thing(commandline):
    with TaskNotifier(commandline):
        subprocess.check_call(commandline)

However this is just a silly idea, a tad bit complicated for what it does, and might not be worth the maintenance cost! but if you like the idea, I'd be happy to implement it for you

And a flag like --longer-than 60 to ntfy done to suppress notifications for jobs that end in less than a minute. Even a value of 1 is useful, because it prevents notifications from being sent immediately because you got the command wrong.

Go back through closed tickets to see what the most frequently missing needed info was. Basic starting point:

How was ntfy installed?

• Global pip (sudo pip install ntfy)
• Single file bin (curl'd)
• Virtualenv pip (virtualenv foobar && foobar/bin/pip install ntfy)

What version is installed?

$ ntfy --version

What Operating System are you running?

• Linux
• MacOS X
• Windows
• Other? (BSD?)

What does your config file contain (eg: ~/.ntfy.yml)

---
# paste your yaml :)

Hello,

I've instaledl 'ntfy[xmpp]' but I don't know what the yml file needs to look like and how I connect it to a xmpp server. Do you have any documentation that can be shared so I can set it up?

Thanks,
sean

Should maybe just use pygtk and so forth, downside of this is that they can't be pip installed, similar to Mac OS X notifications.

Currently get messages like this, which aren't useful to users:

ERROR: Failed to send notification using pushover
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/ntfy/__init__.py", line 30, in notify
    module.notify(message=message, title=title, **backend_config)
TypeError: notify() takes at least 3 arguments (2 given)

If possible, introspect the function signature to find what the arguments accepted are.

It'd make sense to allow multiple configurations for the same backend type in your config file. I propose doing this by adding a special backend parameter to options that is used instead of the name listed in the backends option and the backend's top level key. For example, to have a configs that send to different devices in pushover:

---
backends:
    - pushover
pushover:
    user_key: t0k3n
cell:
    user_key: t0k3n
    device: nexus5x
    backend: pushover

Then ntfy send foobar would send a notification to all your pushover devices, where as ntfy -b cell send foobar would only go to the device named nexus5x using pushover.

cc @danryder

http://www.pyinstaller.org/
https://www.appveyor.com/docs/deployment/github/

I'm finding pyinstaller quite difficult to use, but I'll have a branch up shortly.

Hello,

Can the -t option also be added for the ntfy done setting?
https://github.com/dschep/ntfy/blob/master/ntfy/cli.py#L84-L88

Upon running with out a config, it'd be nice to have zsh-like options of:

1) do nothing (this messge reapears next time)
2) create an empty config file (supresses this message and use desktop notifications)
3) configure a push notifications

Where 3 would then guide you through a wizard.

It could be useful to use both desktop and cloud notifications at the same time.

Config example:

{
    "backends": ["default", "pushbullet"],
    "pushbullet": {"access_token": "<redacted>"}
}

CLI Example:

ntfy -b default,pushbullet send foobar

Suggested by @danryder as well.

If setting the access_token option for Pushover (as mentioned in the Readme and in the code's documentation), the following error is printed in the console:

ERROR: Got unknown arguments: {'access_token'}

The same happens if specifying options through the CLI:

$ ntfy -b pushover -o user_key MYUSERKEY -o access_token MYACCESSTOKEN send 'Pushover test!'
ERROR: Got unknown arguments: {'access_token'}

My ntfy.yml

   pushover:
     user_key: key
   pokemon:
     backend: pushover
     user_key: key
     api_token: key
     title: Pokemon Go

Gives error

`ntfy -b pokemon send 'Lvl up'`
ERROR: Failed to send notification using pushover
Traceback (most recent call last):
  File "c:\python34\lib\site-packages\ntfy\__init__.py", line 48, in notify
    **backend_config)
TypeError: notify() got multiple values for keyword argument 'title'

not sure why i didn't think of this initially.