Connecting the RF mains sockets to the HAH

Operation of the RF sockets from the HAH browser UI does not need any additional scripting.

If you have a multimeter to hand (and have a steady pair of hands) you can check for 12VDC between pin 1 of the RF module and pin 2 of the RF module. Pin 1 is ground. Be careful not to let the probes slip & short out the supply!

Also, see the circuit diagram at http://www.dbzoo.com/livebox/assembly#hah_pcb_assembly_notes

and with power off, buzz out the line from pin 3 on the RF module to pin 19 on the AVR chip.

Sadly, the Lidl socket light does not change colour during training.

Derek.

If you have 13v between pin2 and ground (on the rf board) you have your 15V wire connected-it goes through a 12v voltage regulator.

http://www.packetradio.co.uk/gallery/index.php/HAH/HAH_newpcb  the white wire near the lcd "pot" and connector is the 15v supply to the board (this is from memory)

rf1.on=01020320028A05DC028A05DC0514032004B00C029C401515B155561600
rf1.off=01020320028A05DC028A05DC0514032004B00C029C4015CB1555555540

check for the strings carefully there was a typo a while ago

once you have the RF strings inputed save your settings and reboot the HAH (admin management reboot)

then

the sequence is (i think as i only use 302's) push the button on the plug and hold then go to rf 1 control on the HAH GUI and turn on release button on mains plug.

your HAH should now control the socket on/off.

info from http://www.dbzoo.com/livebox/universalrf

also see this thread someone else had problems but they were rectified:-

http://www.homeautomationhub.com/content/trouble-getting-rf-working

that should do it. no scripting required the way to look at is "if" you had a handheld remote you put the plug into learning (by holding button )then send the on command etc, the HAH takes the place of the handheld remote

the spare components you refer to i belive are a temp sensor and a shoctky diode, both for one wire bus so no relation to RF and unused for the most part.

let us know how you get on

I think you need to be on Build 306/3.4 to ensure that you have the right ATMega software. When you boot up the box, the LCD should read "Booting v 3.4" or something similar. The latest code is required for the URF to work correctly, I believe.

On the top RHS of every HAH web UI page, you should see 'Build: vvv.v/x.x'

vvv.v is the HAH firmware build. x.x is the AVR code version.

If you are either using the old mega8 AVR chip or your AVR isn't talking to the HAH, you will see x.x as 1.0

If you have the newer ATMEGA328P chip, you should see x.x as 3.4

Power cycle the HAH (not just reboot it) and check what the web UI shows. If you have the 328 AVR chip and you see the web UI showing 1.0 ... there is a basic problem with the HAH talking to your PCB.

Derek

So, the LCD shows 'Booting 3.4' because there is code in the sketch that the AVR runs to print this directly to the LCD. This also tells us that you do indeed have the 328 AVR chip with the latest code onboard.

However, the Version that appears on the HAH Web UI is retrieved from the PCB via the HAH sending a 'version' command to the PCB. If there is no reply from the PCB, the version is shown as 1.0 - you absolutely should see 3.4 on the web UI.

The fact that you see the 'Booting ...' message on the LCD gives confidence that the AVR is starting up properly.

So, I'm wondering if the comms to your AVR is connected up properly. Can you read the inputs on the PCB via the web UI. Can you turn the relays on the PCB on and off?

Derek.

Just short one pair of the input connectors together with a piece of wire & then refresh the web UI. You should see the input state change from 'off' to 'on'.

The LCD text shows that comms 'to' the PCB is good. However, the web UI needs comms both 'to & from' the PCB to show that version number correctly.

Off to catch a flight now. Won't be back online 'till later (much later if I go out for a curry!)

Derek.