Hi,
I've just been trying out the XBMC service but there doesn't seem to be a method of passing a username or password.

My XBMC instances expect authentication so is there any way to include this in the xbmc service?

Thanks

Is it possible to add this line to mqttwarn.py?

os.chdir(os.path.dirname(os.path.realpath(file)))

I start mqttwarn as a deamon from another folder and would love this to be a 'standard' feature. Unless this will hurt those that start from the same folder obviously.

Thanks,

Marcel

The code currently uses one Queue to handle all incoming requests, irrespective of how many services are configured.

Enhance to add a per/service Queue so that "slow" targets don't hinder "fast" targets.

Already do this in openHAB but it would be good to move to mqttwarn.

Using the Google translation web service, but that only accepts a max of 100 chars, so would need to break up long sentences.

Similar to title functions. Just needs to return an int instead.

Nice-to-have - not critical in any sense...

Can we get a condition that drops a message once a condition is true (use case: don't push me notifications for normal messages but just those with a JSON event attribute in them) ?

this one is more out of interest than need and fyi...

when you setup the target to log feature with a title and format, i will use my weather example config again;

[weatherforecast-alerts]
topic = /software/bom_forecast2mqtt/forecast/Victoria/Melbourne/json
targets = log:info,pushover:weather
title = Weather Forecast for {fcast_town}
format = {fcast_today_precis} with a top of {fcast_today_temperature}\n\n(Issued {fcast_date}  @{fcast_time})

all that gets logged to the log file is the message, the title gets ignored.

2014-03-18 11:27:14,009 DEBUG [log] *** MODULE=services/log.pyc: service=log, target=info
2014-03-18 11:27:14,009 INFO  [log] Shower or two developing with a top of 25\n\n(Issued Tuesday 18 March 2014  @5:15 am)

if this is meant to be the way it works, maybe something needs to be added to the readme file

Add config for file and mqtt to enable optionally

re-use open connection

A page for each service etc.

A bit like the IRC target, not sure if useful (I don't need it).

Should be easy using: https://github.com/twilio/twilio-python

Call Notifications requires a slight complex setup using TWIML https://www.twilio.com/docs/api/twiml

Messages only support should be good at the moment

When mqtt2pushover receives a pub, it crashes with NoneType' object is not iterable.

I traced it back to `onMessagewhere users is initialized tonone``after which it is iterated in``for user in users``. Shouldn't it be filled with users somewhere before?

If I use the priority map of 2 the service doesn't seem to send the notification....

2014-02-27 23:06:30,290 pushover *** MODULE=services/pushover.pyc: service=pushover, target=cfaalerts 2014-02-27 23:06:30,290 pushover Sending pushover notification to cfaalerts [{'priority': 2, 'retry': 60, 'expire': 3600}]... 2014-02-27 23:06:31,399 pushover Error sending pushover notification to cfaalerts [{'priority': 2, 'retry': 60, 'expire': 3600}]: HTTP Error 400: Bad Request 2014-02-27 23:06:31,400 mqttwarn Notification of pushover for /notifications/cfaalerts' FAILED`

But if I change it back to a 1 it works fine......

2014-02-27 23:06:55,930 pushover *** MODULE=services/pushover.pyc: service=pushover, target=cfaalerts 2014-02-27 23:06:55,930 pushover Sending pushover notification to cfaalerts [{'priority': 1, 'retry': 60, 'expire': 3600}]... 2014-02-27 23:06:57,062 pushover Successfully sent pushover notification

I tired sending the same message with another python script I wrote with a priority of 2 and the same retry and expire times and it works fine.

Matt.

Suggested by @sumnerboy12

Hi,

I want to log every item change and event change from openHAB through mqttwarn but need a different format for the log than for the message I send to, for example, my mqtt server.

Is that possible or should I use the event trigger available in openHAB for this?

Thanks,

Marcel

To interface with URL-based APIs (my use case is delivering a json payload to a domoticz url) it would be nice to have the notification type "open url" where the URL is constructed by combinations of filters and/or transforms.
This may even be generalized to execute commands with arguments taken from filters/transforms.

If the message payload has json objects in it, and you want some of them to pass thru to the title/subject in 'titlemap'

For example I want to past the {fcast_town} json object thru to the title, this object exists in the payload message.

titlemap = {
    'monitoring/icinga/#'   : 'Info',
    'notification/warn'     : 'Warning',
    'notification/error'    : 'Error',
    '/software/bom_forecast2mqtt/forecast/#' : 'Weather Forecast for {fcast_town}',
}

I'm having some issues with the following config.

# Logging
import logging
loglevel = logging.DEBUG
logformat = '%(asctime)-15s %(module)s %(message)s'

# MQTT Broker
broker = 'localhost'
port = 1884
username = 'redacted'
password = 'redacted'
lwt = None        # Where the MQTT LWT will be publied to. Ignore if None

# List of services we will be using. Omit services you won't be using
# This loads the respective service plugins from the services/ directory
services = ['mqtt', 'pushover']

# Outgoing MQTT publishes
mqtt_config = {
    'host'       : 'localhost',
    'username'   : 'redacted',
    'password'   : 'redacted',
    'port'       : 1884,
    'qos'        : 0,
    'retain'     : False
}
mqtt_targets = {
    'owntracks'    : [ 'events/notifications/owntracks' ]
}

pushover_config  = None    # This service requires no configuration
pushover_targets = {
    'owntracks'     : ['redacted', 'redacted'],
}

# Republishes
mqtt_targets = {
  'owntracks' : ['events/notifications/owntracks'],
}

# Subs
topicmap = {
    'owntracks/bucks/#'         : ['mqtt:owntracks'],
    'owntracks/sina/#'         : ['mqtt:owntracks'],
    'events/notifications/owntracks'        : ['pushover:owntracks']
}

def owntracksTopicDataMap(topic):
    if type(topic) == str:
        try:
            # owntracks/username/device
            parts = topic.split('/')
            username = parts[1]
            deviceid = parts[2]
        except:
            deviceid = 'unknown'
            username = 'unknown'
            return dict(username=username, device=deviceid)
    return None

topicdatamap = {
    'owntracks/+/+' : owntracksTopicDataMap
}

# Used by: pushover
prioritymap = {
    'events/notifications/owntracks'    : -1,
    'events/notifications/warn'    : 0,
    'events/notifications/alert'  : 1
}
formatmap = {
    ##'owntracks/bucks/+'    :  '{topic} at {lat}/{lon}\n'
}

titlemap = {
    'events/notifications/owntracks'   : 'OwnTracks',
    #'notification/warn'     : 'Warning',
    #'notification/error'    : 'Error'
}

I'm getting the following log when a message is published to owntracks/bucks/nexus4:

2014-02-16 11:26:15,074 mqttwarn Topic [owntracks/bucks/nexus4] going to ['mqtt:owntracks']
2014-02-16 11:26:15,075 mqttwarn New `mqtt:owntracks' job: owntracks/bucks/nexus4

It should (tm) format the message and then publish it to events/notifications/owntracks where it should be picked up by the pushover connector. However, no message is ever published. Instead the task just hangs and cannot be exited without a kill -9. Ideas?

Also the format map wasnt working and complaining about topic being an unknown key before.

Hi,

Are there any plan to add PushBullet support ?

https://www.pushbullet.com/api

Thanks !

-RB

I had to put in the samplefuncs.py file.

import json

to get it to work.

Otherwise I got the error.

2014-03-18 10:46:58,206 WARNING [mqttwarn] Cannot invoke filter function OwnTracksBattFilter defined in owntracks-battery: global name 'json' is not defined

I have tried to use pushbullet this morning but keep getting the following :-
2014-02-20 11:54:35,723 mqttwarn processor is handling: `pushbullet' for warnme
2014-02-20 11:54:35,723 pushbullet *** MODULE=services/pushbullet.pyc: service=pushbullet, target=warnme
2014-02-20 11:54:35,723 pushbullet Sending pushbullet notification to warnme...
2014-02-20 11:54:35,732 connectionpool Starting new HTTPS connection (1): api.pushbullet.com
2014-02-20 11:54:37,165 connectionpool "GET /api/devices HTTP/1.1" 200 None
2014-02-20 11:54:37,170 pushbullet Cannot notify pushbullet: PushBullet instance has no attribute 'pushNote'

is it something I'm doing wrong?

Pushbullet

pushbullet_config = None
pushbullet_targets = {
'warnme' : [ 'abcdefghi', '1234567890'],
}
topicmap = {
'/openhab/notification/info/#' : ['smtp:special', 'pushbullet:warnme'],
'/openhab/notification/alert' : ['smtp:special', 'pushbullet:warnme'],
'/openhab/notification/warn' : ['smtp:special', 'pushbullet:warnme'],
'/openhab/notification/alarm' : ['smtp:special', 'pushbullet:warnme'],
}

The readme for the out going mqtt publishing is different to the sample config file.
https://github.com/jpmens/mqttwarn#mqttpub

also have you removed the config for an different mqtt server to publish to?

Reported/suggested by @sumnerboy12 and I had stumbled over this problem earlier too :)

I have just noticed an issue with my mqttwarn config however. I
already had a notification set up for enter/leave events using
OwnTracks. This was based on your example and involves adding a custom
filter to check for 'event' messages, and formatting to 'ben: enter =>
home' etc.

This works like a charm, however now I want to add a second
notification based on the 'batt' parameter.

Because the filters are applied at the start of the processing loop,
the first filter (in my case it seems to be the battery filter) is
applied to all OwnTracks publishes and so the event stuff never gets
hit.

Not sure of the easiest way to deal with this, but I am starting to
think it might be better to have a separate set of config for each
topic. This would allow multiple definitions of a given topic (or
allow overlapping topics) to all be processed one-by-one with their
own config, without fear of overlapping filters etc impacting on one
another.

Not sure how it should be defined, but the general idea would be
something like;

# topic name is the section header, followed by the config for that topic
[/owntracks/ben]
target = ['pushover', 'twitter']
format = 'Ben\'s phone battery getting low ({batt}%)!'
priority = 1
title = 'OwnTracks'
filter = owntracks_battfilter

Inspired by #51

I don't yet know exactly how/what/why, but I think we need this. ;-)

Used initially only in the XBMC service to specify an image URL to use in the notification popup.

Not sure if any other services could use this?

So the script will clean up properly when being run as a service

@sumnerboy12 as discussed.

item['data'] never gets set if the json parse fails in format.

in the readme, is it missing an apostrophe after pushover?

Now simply add your choice of target(s) to the topicmap and a nice format string and you are done;

topicmap = {
'/owntracks/#' : ['pushover, 'xbmc']
}

Not sure if it is been mentioned before. RSS target.

Could be called via pipe or file i guess.

I don't need it.

Enhancement.

couldn't see this anywhere, but are we able to add the silent option, maybe for a low priority message for pushover?

"None (silent)"
https://pushover.net/api#sounds

http://developer.boxcar.io/api/publisher/

Not sure if it is been mentioned before. Boxcar.

Looks like you could just use the https target for this one.

I don't need it.

Maybe add a feature that if x amount of the same messages is published within y amount of time, then just send one message saying that. Instead of publishing all the messages, then goto sleep on that message for z time.

As you could easily blow api limits on some services, or it just becomes annoying on your mobile device!

topic processing and format functions are done in the job queue, i.e. they're invoked N times if a message has N targets.

Pull those up and invoke before the job is added to the queue.

Simultaneously, attempt to parse JSON from payload BEFORE the filter() function is invoked, and pass data{} to it as well. (Doesn't cost more, and adds functionality.) In order to not break existing filter(), add data=None to end of call.

The main difficulty, I think, is how to describe the desired schema.

Must test whether broker restarts make mqttwarn 'hang'. It appears to reconnect but doesn't seem to get subscriptions.

Needs tests

previously I could do a newline with \n in the formatmap, can't seem to do it with the new format.

example.

[weatherforecast-alerts]
topic = /software/bom_forecast2mqtt/forecast/Victoria/Melbourne/json
targets = log:info,pushover:weather
title = Weather Forecast for {fcast_town}
format = {fcast_today_precis} with a top of {fcast_today_temperature}\n\n(Issued {fcast_date}  @{fcast_time})

will display the characters in the pushover message as \n\n not as two newlines.

Shower or two developing with a top of 25\n\n(Issued Tuesday 18 March 2014  @5:15 am)

If a plug script fails (e.g. /services/xbmc.py) then the mqttwarn processor hangs. Attempting to shutdown the main mqttwarn loop gets to the;

2014-02-16 10:53:06,957 pushover Successfully sent pushover notification
2014-02-16 10:53:06,957 mqttwarn processor is handling: `xbmc' for living
2014-02-16 10:55:01,730 mqttwarn Disconnecting from MQTT broker...
2014-02-16 10:55:01,730 mqttwarn Clean disconnection
2014-02-16 10:55:01,730 mqttwarn Waiting for queue to drain

The queue never drains so the process never shuts down. Have to kill -9 to stop it.

if plain text in payload, can a func handle that? (ie transform MUST be possible even if not JSON)

I was wondering how to handle dealing with several messages at the same time, or remember state when I was thinking about logging the time it took for my daily commute to work and back.

I would use owntracker to detect the timestamp when I leave location home, and then later with a new message the timestamp when I enter location work.

I would need something like:

If leave home, remember timestamp as LEFTHOME (perhaps publish as a message /commute/towork/leavingtimestamp)
if arrive at work, subtract LEFTHOME from ARRIVEWORK and publish as /commute/towork/duration

It seems mqttwarn only deals with a single message at a time, and perhaps that is its purpose, so I wonder if there is a way to do the above scenario?

Thank you very much for the work you put into mqttwarn.

(I was able to solve my earlier issue with a filter by the way, I ended up with the following filter:

def OwntracksFilter(topic, message):
data = dict(json.loads(message).items())
if 'desc' in data and 'event' in data:
if data['desc'] == "Werk" and data['event'] == "leave":
return False
return True

plugin to PUB to a redis key?

Pushover was unreacheable for 20m for me, and something @sumnerboy12 said made me think: Do we need failover in case a particular notification cannot be emitted?

Assuming mqttwarn should notify target xxxx:urgent, but that service cannot be reached, should we instead have some way of configuring a "failover" service for that particular target? In other words: "get the message to the user by whichever means possible"?

If so, we have to think up some clever way to configure that.

Instead of hard coding to 'mqttwarn' - can still default to this.

Not sure if useful, just an idea.