Blog

FlashAirDownloader – development: Now it’s your turn

Hi,. folks,

I just programmed a small windows service to automatically FlashAir-pictures when I found out that I lost my FlashAir – card

So I am not able to test that program anymore. I decided for myself that I need something better than the unstable FlashAir-Cards and bought a camera with WiFi inside. (Just in case you are curious: It is a Sony HX400)

I do not publish this as a working download, because I am not able to test it. So there is a big chance that this even breaks the original program. But FAD2 is open source, so I checked the code in into the development-branch on GitHub.

So if there is any C# – developer out there who is willing to invest one or two hours to finish that, feel free to do that.

 

P.S: No, please don’t buy me a new FlashAir 🙂

Advertisements
apps
Posted by in Tagged with Tags: , , , , , , ,

Two Apps at the same time: Deploy SharePoint Add-In to Cloud AND On-Premise

What the fuzz is this about?

I am not absolutely sure if I am the first one who did this, but it seems at least noone else wrote it down until now. 🙂
We hat a customer who liked our Office365 Provider-Hosted App “Mydea”, but wanted us to install that on his SharePoint 2013 – Installation. In Germany a lot of companies do not trust the cloud. So we had three options:

  1. Tell the customer this does not work
  2. Copy&paste the whole solution and change it so it works on OnPrem
  3. Do something else

The first option – of course – wasn’t valid for me. The second would have worked. But I did not want to end up in maintanance hell. Our product is about innovation management. And the most innovative about that is the product itself. We develop agile, adding new features (and sometimes bugs) continuously. We do not want to do that twice.

So I ended up on the third option: Changing my solution so it will run in an Office365 – SharePoint and on an On-Premise installation of SharePoint 2013 (or above).

Continue reading

way-back1
Posted by in

Wayback Machine and 301 redirects

As you might know: the wayback machine from archive.org saves snapshots of websites. It does this automatically or can be forced to do so. However. If you ever had a 301 redirect on your site you are very much doomed.

Like browsers also the wayback-machine caches the redirect and does not continue to take snapshots from your sites. Even if you enter your url into the wayback-machine, you still will be redirected.

You can however force it to ignore the cache by manually store your site again:

https://web.archive.org/save/[YOURSITE]

for example:

https://web.archive.org/save/http://blathering.de

Et voílà: Everything works nice from now on.

 

[Image is CC-BY-NC-ND © David Baldingerhttp://www.dbaldinger.com/opinion_cartoons/second_page/wayback.html]

fiddler-935375_6401
Posted by in Tagged with Tags: ,

Getting rid of Proxy limitations using Fiddler

If you work in a company that uses Proxy authentication (aka forces you to enter a password to access websites) and are a developer you know my pain: Some Most applications just don’t really like proxies. Visual Studio itself for example does not like proxy authentication at all and responses with a wide variety of error codes (407 for example).

You can get rid of all these errors through different workarounds, but these are a real PITA.

In addition the application you code itself needs Internet access, for example if you develop Office365 AddIns, you are very much screwed.

After a long research I finally found a solution using Fiddler.

Most developers already use Fiddler for debugging reasons so there isn’t even any software that needs to be installed.

Continue reading

gauge
Posted by in Tagged with Tags: , ,

Displaying Data from HomeMatic Actors on a WebInterface

This tutorial assumes that you already installed and configured FHEM and know how to use AngularJS.

 

As you might know I use my Raspberry PI to automate tasks at home. I already detect my SmartPhone, and my FitBit and also control my Webcam and Harmony remote using a raspberry and a web interface.

Now I also wanted to include actors from HomeMatic thermostats into my configuration and display it in a nice way.

Hardware used:

  • HomeMatic Wireless Configuration Adapter LAN (HM-CFG-LAN)
  • HomeMatic Thermostate HM-CC-RT-DN
  • Raspberry Pi V2.

Software used:

  • HTML/CSS
  • JavaScript
  • AngularJS
  • FHEM
  • PHP (optional)

Before we begin make sure you have already installed FHEM and the hardware for it. I will not discuss that here as there are a lot of good tutorials for that. A good (german) tutorial can be found in the FHEM Wiki. (If you got any english documentation, feel free to post it in the comments.) Continue reading

Support this blog

Feel free to send some money to my Panama-Account if my posts were helpful.