As i mentioned before, there were still some interesting things that could be added to the Plug-in and i thought it was time to revive the Plugin by adding some functionality that was asked for, make it future proof by supporting the newer firmware versions. Some of the things that have been added in the last 2 weeks are:

- Retrieving the Phone Book from the Fritz!Box and using it for Caller ID(entification);

- Searching websites on the Internet for Caller ID;

- Supporting the challenge/response security mechanism built into new firmware;

- Switching the WLAN from Homeseer;

- some useful stuff for use in scripts;

- upgrade of configuration pages to ASP.NET.

You can read all about it in more detail on domoticaforum.eu

This should do for some time; maybe some small additions or fixes, but that’s it for now; time to move on to development of another brand new and exciting Plugin!

The last couple of days i was looking at how i could spend the huge amounts of free time i have lately and decided to spend it on extending the Plugin with some extra features; the Fritz!Box has a lot to offer, so there are still a lot of things to explore.

But first i had to tackle the new way of logging in to the Web-interface that has changed in the recent firmware versions (xx.04.74 and higher). This new method of logging in involves calculating MD5 value based on a challenge provided by the Fritz!Box, and having read once that a lot of faulty MD5 routines exist, i decided to look into that issue first. I mean, creating additional functionality without supporting the latest firmware sounds rather stupid to me.
OK, the sequence of actions to do a successful login were clear to me, that wouldn’t be the problem; only thing i hoped for was that the calculation of the MD5 hash would succeed with the .NET provided classes/routines. So i created a simple function that could return the MD5 of a given string:

The resulting md5bytes should contain the correct hash value when each byte was written as hex string value and all 16 of them were concatenated. But something strange was going on…

The AVM documentation stated the resulting MD5 should be: 9e224a41eeefa284df7bb0f26c2913e2 And what did i get? 58224a41eeefa284df7bb0f26c2913e2.

What’s this… well OK, it’s almost the same, maybe it will work, lol.
On the contrary, this ain’t funny at all of course… what’s going on here ??? I just didn’t know what was wrong; was it the encoding? The AVM guideline speaks of UTF-16LE (LE = Little Endian), BOM, trailing 0-bytes, Codepoints; not really the stuff i deal with on a daily basis, so …??

Searching MSDN i found this:

With just a tiny adjustment (there where the cursor is) and it worked…

I still don’t understand why; these things can really bug me and now i’m struggling to either just go on and let it be, or go to the bottom of this?

Let’s hope i don’t encounter to much of these mysteries.. 

Fritz!Box Plugin Devices in Homeseer

Work on the Fritz!Box Plugin for Homeseer is progressing. Currently it’s being tested while i’m working on the code to log all phone calls to an Access database.

The Plugin has been tested with the Fritz!Box FON WLAN 7170 and the 7270. Other models will be added to this list as more users will start using the Plugin.

This is what the Plugin Config page looks like:

Fritz!Box Plugin Configuration Page

The nicest feature (IMO) is that the information displayed in the Devicestring is user configurable.

That means that the user has control of what pieces of information (incoming or outgoing, phone numbers, call duration) are shown and their sequence.

I must say, after getting a bit familiar with Homeseer (i’ve never used it before, but had to install it to test my own plugin), i’m beginning to like writing Plugins for it But using Homeseer as a regular user? No, not my cup of tea…

Fritz!Box FON 7170

Not for myself ofcourse (i’m not using Homeseer), but just to see if i could do a thing like that. And to help a Domotica buddy ofcourse

Not knowing anything about Homeseer, i managed to create a plugin that could serve as a trigger for Homeseer events. The plugin is going to be tested in the next couple of days. I hope everything will work out as expected and the plugin is stable enough to continue building on  a Homeseer plugin that could be usefull to all those who own both Homeseer and this Fritz.