I have finally removed the remaining X10 controllers having replaced the outside light controllers two days ago and the main room lighting dimmers today. Time will tell if any of these suffer from interference being 2.4GHz Zigbee but so far, so good. All of the X10 stuff is destined to go on eBay but it doesn’t seem to sell well – I guess I waited far too long to update everything here.
It’s not a major setup, one Zigbee controller / hub or whatever it’s called – USB and currently stuck in the front port of the server, two dimmers, two bulbs, and three relays.
The setup is Mosquitto and Zigbee2mqtt on the server and Homebridge on a Pi. The server is due to be replaced by another Pi shortly to save space and watts. So now Siri rules our lighting – well some of it! Be nice to Siri…
I have always dabbled in home automation, pretty much since before it even became a thing. Most of the control was, and mostly still is via X10 devices and controllers which use mains signalling. This is rather old fashioned now and, being mains signalling is susceptible to interference. At one stage the outdoor light, which are controlled via an X10 appliance module in the workshop were very intermittent, until I discovered the wall-wart on one of the internal cameras was injecting awful noise that caused a scanner AM to buzz wildly when held near any mains outlet in the house!
Anyway, that isn’t radio related, but this is… enter Zigbee. I have not read very far into this yet but it uses 2.4GHz among other frequencies for its signalling and there are lots of modules available. I plan to change our two dimmers to Zigbee and it will be pretty much plug and play. Apart from removing the mains signalling path the modules communicate both ways, so the controller can see their status as well as control them. Some of the newer X10 modules do this but very few of them and none of the ones I have.
The current setup here is a Raspberry Pi running Homebridge which appears in the Apple Home app and can respond to commands via Siri. The X10 lighting controllers are handled via shell scripts which are called by a Homebridge plugin. But with no status return, if the lights are switched on by a switch or, in the case of the garden and outdoor lights via a script which calculates dusk and dawn the Home app has no clue as to their state. With Zigbee it will.
There is a little way to go yet but everything appears to work. The Homebridge software has a plugin that communicates with software on the server which in turn works via a Zigbee 2.4GHz USB dongle. Basically, with very little work new devices feed their names all the way back to the Home app. All I need now is some more!
I plan to use the FT817 portable but also for VHF and UHF FT8 and other digimodes, so I wanted to upgrade the standard oscillator to the TCXO version (Yaesu’s TCXO-9). But these are scarce, at least in the UK. I’ve searched for a while and got nowhere so I ended up buying one from Wimo in Germany as they had them in stock.
The original TC1 unit (left) and the TCXO-9 (right) are, of course identical in size and sit on 7 pins. There are at least two variants of the TCXO-9 and I guess this one is the newer of the two.
The unit is easy to install. Obviously – or it should be! – disconnect the battery, wear an anti-static bracelet or take appropriate measures, then the old unit simply pulls off of the 7 pin connections and the new unit presses in to replaced it. With the set back together and given a little time to warm up, and set up for CW it holds steady just 2 hertz high. That should be good enough for data modes!
I seem to have a lot of stalled projects currently. And then I got a kit of parts to build another Minitiouner… so I did that, and still have the same number of stalled projects! Oh well…
The build went as well as the first one I constructed, very easy to put together and test. When connected to the Windows PC the test software all runs fine. This will go into the box I had for the previous Minitiouner the board of which is now inside the (stalled!) Portsdown.
When we got our house way back in the last millennium it had a fairly good doorbell consisting of two tubular bells, one of which was about 18 inches long. This sounded all over the house but eventually the solenoid last its sparkle and the doorbell went from ding-dong, to dong, to a little tinny ding. So we went through a couple or three battery powered bells which were pretty pathetic and ate batteries. Eventually we settled on a wireless type from eBay and this worked well, and had two plug-in mains operated bells. But the doorbell push itself, sat out in the Yorkshire wilderness that is our drive eventually failed. A new set of radio doorbells was acquired from eBay, and this time the range was a lot better reaching all the way to the workshop. Slowly the range decreased and recently the outside bell push has had issues relating to condensation. No matter what I tried I ended up having to take it apart, clean the battery and put it back in time for the parcel person. Then then tags that held it together decided to go away on holiday and never return.
The original doorbell way back when was AC driven, 6V or so from a bell transformer and it looked as if it had been in for many decades. So, given that these new fangled units are either too weak to be of any audible use or fail regularly or both I made up a little box with an 8V transformer and wired this to an actual bells, not a ding-dong. The bell push outside is now just a switch. Being AC it will probably fair better but I have a space switch just in case.
So how is this radio related? Well, first off I have a relay wired across the bell as I plan to connect this to our Homebridge Pi to generate doorbell alarms on our iPhones. Given this relay I took the previous wireless bell push apart, unsoldered the push and wired this to a n/o contact.
So now the doorbell rings the bell and also triggers the radio bells. There, a radio project! Well, ok, it was only unsoldering a switch…
Slowly coming together. Yesterday I decided to attack the front panel with a drill and mount the rotary encoder, switches and the little Arduino board which I programmed earlier. This is for tuning the Langstone. For some reason my drill press insists on making triangular holes – if I wanted a triangular hole I’d never manage of course. So I’ve resorted to making a smaller hole and using a round file. Anyway, everything went into place, although the Arduino board has no mounting holes so I’ve tie-wrapped a piece of plastic under it as an insulator and used a decent (hopefully!) sticky pad to secure the board inside the front panel.
So far, so good. Here it is receiving the Allstar microHub…
I need to sort the microphone out. The USB audio dongles seem to be constructed for stereo input so I wired the same to the front panel. Plugging the headset in gives no audio, presumably its all shorting out. I can make it work by ‘adjusting’ the plug (pulling it out until it works!) so I need to re-wire or make a little adapter.
There are a couple of fans in the case and so far it seems to be keeping nice and cool. Next steps include making the GPIO breakout board and possibly the band switching stuff.
Edit: of course I have a mono to stereo adapter plug, I just never looked in the junk box! Mic input now working fine…
I’ve been looking for some time for an affordable (i.e. used) and useful ranged (i.e. not cheap!) spectrum analyser. Obviously I want DC to light but don’t need it and don’t want to sell the house for a bit of test gear. I have a TinySA which is good to 960MHz but I will need a higher frequency range as I fiddle more with microwaves.
The ultimate, e.g. a Rigol or Siglent LCD type device is just far too expensive. Nice to have yes but something one would need to be using all the time in order to justify it. Then I came across Satsagen – http://www.albfer.com/en/2020/02/21/satsagen-2/
Satsagen runs under Windows and by default uses an Adalm Pluto as its interface to the real world. The software even does the necessary to upgrade the Pluto to the ‘full’ range of 70MHz to 6GHz (you can do this easily by hand but it’s nice of the software to do it anyway). The software has three basic function too – spectrum analyser, spectrum analyser with tracking, and generator. So, one PC, one Pluto, Satsagen and you get a pretty decent 70MHz to 6GHz spectrum analyser, tracking generator and signal generator.
I have not yet delved into all the functionality and only carried out a couple of quick tests on a handheld and on my 70MHz transverter, plus a very quick test of a FPV transmitter (TS832) up at 5.6GHz.
It will work with other devices such as the HackRF and the RTL dongle but it seems so useful I purchased a Pluto just for it (yeah, ok, I can use it for other stuff too but hey)
The PiBox is almost completed. It’s taken far too long due to all sorts of silly things like having to get fans because a dry run indicated the poor little boards were getting a bit hot, having to get bolts for the fans because I had none long enough, and having to get a connector for the 1-wire (actually 3 wires!) lead from the central heating sensors.
So, there is is. Two fans on the left, 5V PSU bottom right, gigabit Ethernet switch above that, then the Pi’s: top is the PiStar with the DVMega board which has coax to the rear panel and then a dummy load, middle is the ASD-B and central heating monitor Pi, and the bottom is a general purpose one with various bits on such as rtl_tcp. The lower two boards have USB-A sockets on the rear of the case for the two SDR sticks, one for the ADS-B antenna and one to attach to a Discone for general use.
But there is an issue. I had originally intended this to sit in the shack but those fans are just too annoying. Not loud, but constant. I suspect the box will end up in the loft. Or maybe a re-think. I may fiddle with running the fans from one (or two) of the Pi’s and set up some temperature control to turn them on and off. It may even be that I am rather too ‘sensitive’ to the temperature range as others seem happy running their boards a lot hotter than I do mine.