{"id":56,"date":"2007-11-17T14:02:36","date_gmt":"2007-11-17T14:02:36","guid":{"rendered":"http:\/\/blog.danplanet.com\/wordpress\/?p=56"},"modified":"2011-11-29T16:53:35","modified_gmt":"2011-11-29T16:53:35","slug":"automatic-pidgin-status-with-dbus-and-networkmanager","status":"publish","type":"post","link":"https:\/\/www.danplanet.com\/blog\/2007\/11\/17\/automatic-pidgin-status-with-dbus-and-networkmanager\/","title":{"rendered":"Automatic Pidgin status with DBUS and NetworkManager"},"content":{"rendered":"

It’s official.\u00a0 I have a new mistress and her name is DBUS.\u00a0 After seeing how easy it was<\/a> to take an action when a particular storage device was attached, I was hooked.\u00a0 Since I know NetworkManager has a robust DBUS interface<\/a> , I decided to try something a little more interesting.<\/p>\n

Something I’ve always wanted is for Pidgin to be aware of my network connectivity and adjust my status accordingly.\u00a0 I work from home most of the time, so I set my status to indicate this fact and expose my home office phone number for colleagues.\u00a0 I go into the office so occasionally that I never remember to change my Pidgin status accordingly, thus confusing people who were expecting me to be in that day.<\/p>\n

I set out to write something to effectively bridge NetworkManager’s DBUS interface with that of Pidgin.\u00a0 There would need to be some logic in the middle to determine the proper status message given the current state of the network.\u00a0 First, I wrote<\/a> a python module to query NetworkManager for details about activated devices.\u00a0 Next, I wrote a (probably overly complicated) location module<\/a> that reads a config file and provides an interface to return properties of the current location, based on the information about the current active device, as determined by the previous module.\u00a0 The config file looks something like this:<\/p>\n

\n

[Home]
\ndevices = eth0
\nsubnet = 192.168.1
\ncaption = At Home
\nfoobar = baz<\/p>\n

[Home-Wireless]
\ndevices = ath0
\nsubnet = 192.168.1
\ncaption = At Home (wireless)<\/p>\n

[Work]
\ndevices = eth0
\nsubnet = 10.0.12
\ncaption = At the office<\/p><\/blockquote>\n

This lets me match settings based on not only a bit of the IP address, but also on the device name.\u00a0 With those two data points, I can have separate status messages for Home and Home-Wireless.<\/p>\n

Next, all I needed was something to watch for NetworkManager’s DBUS signal that the active device has changed, determine the new location, and tell Pidgin about it.\u00a0 After seeing some examples<\/a> , I found that it is surprisingly simple<\/a> :<\/p>\n

\n

import dbus
\nimport gobject
\nimport dbus.mainloop.glib<\/p>\n

import locations
\nimport sys<\/p>\n

def change_status(id, caption):
\nglobal pidgin<\/p>\n

status = pidgin.PurpleSavedstatusNew(“”, 2)
\npidgin.PurpleSavedstatusSetMessage(status, caption)
\npidgin.PurpleSavedstatusActivate(status)<\/p>\n

def dev_changed(*args, **kwargs):
\nif not kwargs[“member”] == “DeviceNowActive”:
\nreturn<\/p>\n

loc = locations.LocationService(sys.argv[1]).current_location()
\nchange_status(loc.name, loc.caption)<\/p>\n

def monitor_nm():
\ndbus.mainloop.glib.DBusGMainLoop(set_as_default=True)<\/p>\n

bus = dbus.SystemBus()
\nbus.add_signal_receiver(dev_changed,
\ninterface_keyword=”dbus_interface”,
\nmember_keyword=”member”\"Smilie:<\/p>\n

loop = gobject.MainLoop()
\nloop.run()<\/p>\n

def connect_to_pidgin():
\nglobal pidgin<\/p>\n

bus = dbus.SessionBus()
\nobj = bus.get_object(“im.pidgin.purple.PurpleService”,
\n“\/im\/pidgin\/purple\/PurpleObject”\"Smilie:
\npidgin = dbus.Interface(obj, “im.pidgin.purple.PurpleInterface”\"Smilie:<\/p>\n

if len(sys.argv) < 2:
\nprint “Usage: %s <location_config>” % sys.argv[0]
\nsys.exit(1)<\/p>\n

connect_to_pidgin()
\nmonitor_nm()<\/p><\/blockquote>\n

The dev_changed() function gets called for each signal (I think there must be a better way to select specific signals you’re interested, but this is quick and it works).\u00a0 If the signal matches the correct name, then we determine the current location and call change_status() to tell Pidgin about it.\u00a0 How awesome is that?<\/p>\n

I’ve thought about generalizing this into a “Location Awareness Service” that would emit signals on DBUS to notify other applications.\u00a0 It would be really awesome to write something that would tell Asterisk to forward my extension to another line, depending on where I am:<\/p>\n