OpenNetHomeServer

[krambriw]

Hi, here is the schematic and a url to the data sheet in English

I have changed the design a bit to make it simpler using a standard NPN instead of an op amp (actually it improved the signal quality)

The other components (resistors & cap) are uncritical, I already had them in the drawer

In the next post I will put some pictures that show how to connect the wires to the USB sound card

http://www.selectronic.fr/includes_sele ... WSZ_UM.PDF

[krambriw]

The white arrow shows where you solder the blue wire to pick up the audio output

The white arrows show where to solder red & black wires for power supply (red +5V, black 0V)

[mickelin]

Great, thanks for that. I'm using a dual OP amp. Will consider rebuilding to your design. Would you please also post the NetHome settings you use with this circuit?

Cheers,
Michael

[krambriw]

I also started with the op amp approach but it never worked with the LF356 that was recommended. I changed to a CA3130 just to desperately test and then it worked. Tried at least 10 different LF356, LF355 and LF351 but no luck, all of them can't be broken. Back to CA and no problems at all

Looking at the signal pattern with the analyser made me however try a different approach and with the simple transistor circuit the waveform became much better

The settings below are just the default, you just have to pick the sound device, click update and it should work either from NetHome's web interface (I created a new Nexa lamp just to try it) or from EG using pronto codes

Best regards, Walter

[Jostein]

But since i know my signals will have to pass thick walls and some distance, I think I will build the USB-receiver based on the AUREL receiver that was the result of Jostein and Krambriw's common ideas.

Thanks but it was thanks to Krambriw only i havent done anything.

Have finally goten all the parts for the reciever. Will post it the build is a success or not.


krambriw must say that the transmitter looks great. As i understand it this will controll the nexa devices, replacing the tellstick. How is it compared to it regarding range and so on?


Best regards Jostein

[krambriw]

Hello, here some updated info regarding transmitters

I have actually built 3 variants (they look all the same from outside )

1. The first one is just as described above, powered with 5V from the USB
Distance to receiver module in my house: 50-75 meters (from outside of my house)

2. The second is as the first one but powered with 12V using a step-up regulator (5V->12V)
Distance to receiver module in my house: 100 meters (from outside of my house)

3. The third is the "monster". It uses another type of transmitter module (TX-SAWBOOST) from here http://www.soselectronic.com/?str=371&artnum=5732
It is also powered with the same step-up regulator (5V->12V). It can take up to 15V so if I change one resistor value in the step-up regulator circuit I could gain even more power

Distance to receiver module in my house: 200-250 meters (from outside of my house sitting inside my car!!!).
Maybe it's not legal anywhere but I did it just for testing purposes

The antennas are also from AUREL and they provide the virtual ground plane with the kit

I connect a receiver (as described before) and a transmitter to separate USB ports on the computer. I tried having a common USB hub for them but it only worked fine in my fastest computer (Quad processor) running Vista. In my old "HomeAutomation" PC running XP, I had to use dedicated ports. I do not know why it didn't work with the common USB hub

In the following posts I will show detailed pictures and a schematic of the step-up circuit I used

As I understand it this will control the nexa devices, replacing the tellstick

Yes, and if you have other types and matching pronto codes, those as well

How is it compared to it regarding range and so on?

Much better reach

[krambriw]

The first one

The second one

Here you can see the circuit for the step-up regulator

[krambriw]

...and finally, the "monster"

Please be aware that you shall use a different input on the TX-SAW433/s-ZRFM module depending on the power supply voltage you use!!!!!!

5V power supply: input 3
12V power supply: input 2

The schematic for the step-up regulator circuit (Correction, look at next post!!! ):

And the data sheet:

MAX4193-MAX630.zip

(233.51 KiB) Downloaded 187 times

[krambriw]

This is a correction to the schematic in previous post. Both will work but I actually built it according to the picture below (same components)

It's a matter of taste I suppose

What ever you select, be sure to measure the output from the step-up regulator BEFORE you finally connect it to the transmitter module!!!

[mickelin]

Sweet! Do you use the same values for the signal circuit components in the 12V version as in the 5V?

[krambriw]

Yes, the same

[krambriw]

I have released a new version with the following changes/features
-uses eg.PersistentData to save persistent data instead of the python function pickle
-automatic migration of old weather data during startup
-supports also NetHomeServer new UPM message format
-fixed a bug in the message repeat control function

You find the update in the first post. Upgrade is simply to replace the plugin files

Please not the link from where you now can download new versions (nightly builds) of NetHomeServer

Best regards, Walter

PS Jostein, how is the rain and wind metering working these days?

[krambriw]

It's time for an update of this plugin. This version requires that you download the latest nightly build of NetHomeServer (if you have a rather newer version, it should be enough to replace the home.jar file)

New features are

# 2010-11-09 Added action to trig the alarm buzzer in a NEXA Smoke Detector
# 2010-11-09 Modified the format to support NEXA Smoke Detector events
# 2010-11-09 Added repeat functions to pronto commands

Image1.jpg (7.74 KiB) Viewed 5596 times

With this version you can receive smoke detection events to trigger macros and you can also activate the buzzer in individual detektors. As before, you need a RF Receiver supported by NetHomeServer

To configure, you need to find the address of each detector. This is however rather easy since NetHomeServer also has a new learn function

One caution - never rely on NetHomeServer or EG for performing any critical and real smoke detection functions. The smoke detectors provide the real detection & warning, the NetHomeServer and EG can simply provide additional features when the alarm goes off (like turning lights on, turning power supply off to defined devices like air condition units, televisions etc).

In addition I have introduced a repeat with delay function for the pronto commands

Best regards, Walter

[mickelin]

Walter,

Great update, thanks. Could you please explain how to get the address from the detector ("This is however rather easy since NetHomeServer also has a new learn function"). I have looked for but not found the learn function.

Thanks,
Michael

[krambriw]

Hi,

You can use the latest version of the analysator or you can use use net home itself as you mentioned (use the latest version or a version where you know that NexaSmokeDetector is implemented in).

Use the web gui, define a new NexaSmokeDetector object or navigate to the one already defined. There you should see a configuration view like in the picture below.

Click on "LearnAddress"

Press the test button on the smoke detector

Click on "LearnAddress" again and you should see the address in the Address field

Best regards, Walter