Tired of having the power go out without warning? Now you can get warnings about predictable load-shedding sent to the Jabber account of your choice – including Google Talk accounts. Unfortunately, at the moment the warnings are for the City of Cape Town supply area only.
To set it up, ask your Jabber client to subscribe to loadshed@frith.co.za – in Pidgin that’s the “Add Buddy” command, in GMail it’s “Invite to chat”. The loadshed bot will accept your subscription, and reciprocate with a subscription request to you. When you accept it, the bot will send you instructions about how to proceed.
You can search the list of suburbs by sending the message “search [text]“, which will give you a list of suburbs in the City Council’s list with a name matching “[text]“. Then you can subscribe to warnings for a suburb with “subscribe [number]“, where [number] is the number that was listed next to the suburb in the search results. There’s also a “list” command which shows what susburbs you’re subscribed to; and “unsubscribe [number]” which works in the same way as “subscribe”.
The bot will send you warnings 15, 10, 5, and 2 minutes before the load shedding period is scheduled to start. A planned future development is to make the warning times configurable.
Tags: bot, Jabber, load shedding, loadshed
Wow…this is awesome.
Dude, this is pretty cool. How many subs have you got? What is it coded on top of? etc?
j.
You, sir, are awesome.
Where do you get your data from?
[...] [via: Adrian’s Thoughts] [...]
[...] Photos « Get load shedding warnings via Jabber [...]
Answers to your questions (and more!) are in a new post at http://blog.frith.co.za/2008/04/17/load-shedding-bot-faqs/
Cape Town Load-shedding alerts via MXit if……
…only MXit allowed more jabber services entry to their platform. We’d even be able to twitter from MXit
Tired of having the power go out without warning? Now you can get warnings about predictable load-shedding sent to the Jabber account o…
It doesn’t respond to me… is it still going?
No, it’s been switched off since scheduled load-shedding is no longer in effect. If load-shedding returns, so will the bot.