AlertMe API version? Still v2?

[kit]

Wow, it's been a while since I've checked out AM and I've noticed what they meant by 'forum updates' translated to 'removal of posts due to too many complaints' (how I saw it anyway).

Regardless, on topic: any one know if there is a newer version of the web API? I've been using version 2 (which is relatively ancient: https://api.alertme.com/webapi/v2) and have no idea what the AM guys are doing/care about third-party development. The reason is I've found a bug lately with one of the functions due to the colder weather: getDeviceChannel fails to report negative temperatures (whereas getAllDeviceChannelValues does cope.)

[phil4]

Hi, nothing I ever saw saying there was any later version. In fact practically nothing at all about the API whatsoever.

[roobarb!]

Regardless, on topic: any one know if there is a newer version of the web API? I've been using version 2 (which is relatively ancient: https://api.alertme.com/webapi/v2) and have no idea what the AM guys are doing/care about third-party development. The reason is I've found a bug lately with one of the functions due to the colder weather: getDeviceChannel fails to report negative temperatures (whereas getAllDeviceChannelValues does cope.)

There was a v2.02, the PDF for which I've just linked to. That's dated 7th May 2009 and I believe that's the last revision.

But you have just answered something that's been bugging me - I knew getDeviceChannel fails on negative temps, but I never knew that getAllDeviceChannelValues actually worked. I've been promising I'd update the perl script one day... when that day finally rolls around, I'll incorporate that. Because I doubt there'll be a fix.

[kit]

@phil4: I think I poked around the source/assets for the web interface and found that the API version was something like > 5

@roobarb: Thanks for the link - that date sounds like the last time they did seem to care about things (you know, before joining the eco/energy/green-is-so-hot-right-now bandwagon.)

Nothing like having fingers crossed and testing all the possible device-related functions in the hopes of finding something that *does* work..

So you are the face behind http://code.google.com/p/alertmepi/ ? Thanks for that - it helped with writing my app

[roobarb!]

So you are the face behind http://code.google.com/p/alertmepi/ ? Thanks for that - it helped with writing my app

Yup, that's me. I almost uploaded an update yesterday - but then realised I broke more than I fixed. One day!

[roobarb!]

Thread resurrection; I have just discovered that there is indeed a new API - or at least, it's newer than the one I knew about previously. I haven't tested it yet, but the documentation is here:

https://api.alertme.com/v5/docs/

A great project which uploads energy data to the PlotWatt service is alertme2plotwatt and the API works with the Energy-only system as well as the Monitoring system.

[roobarb!]

I haven't tested it yet...

I have now tested it. It works really well.

Rather than trying to repeat my efforts with the AlertMePI script, I think I'll post a bare-bones script for v5 that covers the basics of getting authenticated. The API v5 documentation is really good, so once you've got one function working, it's really just a case of tweaking the URI path to match the details the API requires and pow! Results come out!

I had started a rewrite in Python of AlertMePI (as I much prefer Python to Perl these days), but I will upload the latest version of that for people to tweak. It has all of the basics using API v2, so it may well be useful to someone.

[kit]

have now tested it. It works really well.

Bugger, looks like I can't put off an app update to next year then

Thanks for the API link - hope they update that status 'draft' to 'current' some time while we're still young..

[gadgethome]

I haven't tested it yet...

I have now tested it. It works really well.

Rather than trying to repeat my efforts with the AlertMePI script, I think I'll post a bare-bones script for v5 that covers the basics of getting authenticated. The API v5 documentation is really good, so once you've got one function working, it's really just a case of tweaking the URI path to match the details the API requires and pow! Results come out!

I had started a rewrite in Python of AlertMePI (as I much prefer Python to Perl these days), but I will upload the latest version of that for people to tweak. It has all of the basics using API v2, so it may well be useful to someone.

Hi, Just wondered when you think the python module would be available? I'm interested in testing on my Raspberry Pi.

Thanks

[roobarb!]

Hi, Just wondered when you think the python module would be available? I'm interested in testing on my Raspberry Pi.

It's up on Github if you'd like to have a play with it:

https://github.com/birdslikewires/AlertMePy

There's some documentation and I think everything works as advertised!

Please post back and let us know how you get on with it. I wrote it with little devices like the Pi in mind, but I'm now messing around in Objective-C and not been back to do anything useful with it as yet.

[APrettyBee]

For anyone interested in getting started with php and the V5 API, have a look here http://www.peterbatey.com/articles/alertme-api.html

[roobarb!]

For anyone interested in getting started with php and the V5 API, have a look here http://www.peterbatey.com/articles/alertme-api.html

That's great stuff. I was going to start looking at baking some AlertMe stuff into a site and this has really saved me some time!

[APrettyBee]

Happy to help! I've also got a java implementation if there's any interest.

[roobarb!]

Happy to help! I've also got a java implementation if there's any interest.

Fancy!

Just a quick question - with API v5, do you have any problems with the 'caller' parameter? No matter what I do, my caller property never shows up in the logs. All I get instead is 'disarmed from the api' and never the actual name.

[APrettyBee]

Hmm. I don't have any devices that log anything - so I can't see. The implementation is as per the API doc, so it should work.

[roobarb!]

Hmm. I don't have any devices that log anything - so I can't see. The implementation is as per the API doc, so it should work.

Sorry, I should have been a little clearer in that I don't blame your code - I've got a method in C that's written in precisely the same way, as per the docs, but it still just shows 'from the api'!

[APrettyBee]

Draft API.... There's probably a few of these nuances in there.

[djh]

Thread resurrection; I have just discovered that there is indeed a new API - or at least, it's newer than the one I knew about previously. I haven't tested it yet, but the documentation is here:

https://api.alertme.com/v5/docs/

Thanks for the pointer to the latest APIs, very useful indeed.

It might also go some way to explain why the 'History' section of https://mobile.alertme.com/ doesn't work (it just returns "Array").

The API docs linked above are blank when you click on Devices -> Events, so I guess they never got around to implementing them!

[roobarb!]

Draft API.... There's probably a few of these nuances in there.

Hehe, they've been 'draft' for years.