OpenNethome - an open home automation project

I have been reading up a bit on Wemo, and I think I will buy one and start experimenting a bit with it. In the mean time, you can actually control wemo stuff with nethome via the http://ouimeaux.readthedocs.org/en/latest/index.html software that was mentioned earlier in the thread. Ouimeaux lets you...

The WEMO stuff looks really interesting. But I think the socket switch is a bit expensive? When it comes to the light bulbs they are cheaper than the Philips Hue at least, but there is one thing I don't quite understand - do you need that little bridge device or do the light bulbs connect to the WLA...

Oops... Well, you are totally right goranem, OpenNetHome really lacks a good beginners guide. I have been thinking about recording a few short introduction films on how to make basic configurations of Tellstick and switches, but I have not had the time yet... If you have some good tips on what kind ...

Ok, fixed it. It is in the nightly build.

I am running my NetHome on an Ubuntu server. I currently don't use Tellstick on it, but I use other serial port devices using RxTx, which it seems causes your problems. One difference is that I use Oracle's Java (Hot spot) instead of OpenJDK, so it might be worth trying that instead.

It is specified via the -l flag at startup. See the /opt/nethome/rpi_daemon_start.sh file.

Oops - that is a bug... It should really save and restore the disabled state. I will fix that.

Wow - 200 Items, that is a large system! I have fixed the issue you talked about and it is in the nightly build. It looks a bit weird that the state is off but the level is 20, but apart from that it seems to work. You can try it out and see how you like it. I think generally using the Nexa dimmers ...

Well it is a bit messy, since the dim state is sort of stored both in the lamp and NetHome. The current behavior works as I intended it, there is a separate method in the NexaLCDimmer called "store" which is meant to be used for exactly this case. When you call that, is takes the current d...

First check under View->Decoders and see that the protocol is enabled. It could also be the audio settings - Nexa Learning Code protocol has very short pulses, so sometimes the settings has to be very accurate to get it right. Switch on RAW decoding so you can look at the audio signal and hot that i...