All,
I have just been able to get my HAH up and running after all the parts sleeping in their boxes for a week or so.
Anyhow, as I am so new to this (and the forums did not seem to provide an answer I thought I'd enter my first post.
My HAH has the 306 build.
I have my LCD working, my RF module seems to be working wonderfully, and I am controlling 7 BBSB4AW's that had been relegated to the parts draw, and I am also controlling 3 LWRF switches. I have tried both the wall plates (I have quite a few) and the pluging sockets, but currently only have 3 plugin sockets being controlled by the HAH. Will move my others when I feel happy (I'll then have a LWRF wifi-link for sale).
My onboard Ds18b20 seems to be reporting normally, and pachube is being sent the readings.
Now, I built my offboard ds18b20 onto a 3.5mm stereo jack and thought I'd test it, so plugged it in, and after resetting the bus, I get no more unassigned ROMID's. I rebooted HAH and then also did a bus reset, stil nothing.
Then I sat back and thought - did I err by pushing in my 3.5 jack into the connector whilst the HAH was running - did I damage anything?
My onboard is still functioning.
Also the MB 1wire connector has an 4k7 innplace @ R7, do I need another R on the DQ/Vcc legs on the jack? - I have since tried with both, but still no unassigned ROMID.
I had a quick look at /var/log/* but nothing stands out, infact 'mesages' seems the most verbose logfile.
Can anyone give any tips, or suggest diagnostics. Especially the correlation between the onboard working and the possibility of damage by runtime insertion of the offboard sensor?
btw: I am no engineer (in the electrical sense), although I can solder a little, and have a very basic understanding of how electrons move about - so anything that involves complicated o'scopes and multimeters is a little ahead of me ;).
I'll get a few more ds18b20's in a few days, but in the mean time, can anyone help diagnose my problems?