Coding and Dismantling Stuff

Don't thank me, it's what I do.

About the author

Russell is a .Net developer based in Lancashire in the UK.  His day job is as a C# developer for the UK's largest online white-goods retailer, DRL Limited.

His weekend job entails alternately demolishing and constructing various bits of his home, much to the distress of his fiance Kelly, 3-year-old daughter Amelie, and menagerie of pets.


  1. Fix dodgy keywords Google is scraping from my blog
  2. Complete migration of NHaml from Google Code to GitHub
  3. ReTelnet Mock Telnet Server à la Jetty
  4. Learn to use Git
  5. Complete beta release FHEMDotNet
  6. Publish FHEMDotNet on Google Code
  7. Learn NancyFX library
  8. Pull RussPAll/NHaml into NHaml/NHaml
  9. Open Source Blackberry Twitter app
  10. Other stuff

.Net FHEM Front-End - Feature Brainstorm

Hi all,

I'm at the point where I feel my FHEM installation is sound - it works, it's logging the data I need it to log, I can remote into it and it looks like it's behaving, all in all it's a solid, friendly enough piece of software.  

So I want to shift focus to my planned .Net front end, and I'm sitting on the train each day, and on my lunch break each day, brainstorming - what can it do for me?  The following are my own thoughts, I'd love to get some more suggestions from anyone else with this kind of setup.

I'm looking for features that tick the following boxes, probably in this order:


  1. Does this feature reduce my energy consumption?  (I need to offset the 600 quid this thing has cost somewhere!)
  2. Does this feature reduce the need for someone to "touch" the system?  Reduced fiddling with thermostats, reduced fiddling with the boiler, etc.
  3. Is this feature "cool" - something that's fun or interesting to play with?


Note - On the 13th November 2010, the feature list was migrated to its new home on the FHEMDotNet wiki at

Categories: FHEM
Permalink | Comments (0)

Add comment

  Country flag

  • Comment
  • Preview