Caprice ceiling fan voice control - Part 1 of 2

The Mission

To enable voice control for the fans and lights of our new Mercator Caprice ceiling fans.

The Steps

Step 1. Figure out the radio frequency (RF) commands for the fans
Step 2. Set up an RF sender on one of my Raspberry PIs
Step 3. Develop a script to control the fan
Step 4. Configure voice control via Alexa

Step 1 - Determine the RF commands

I purchased a DVB-T 820T2 radio tuner. Like this one on ebay.

I used my Windows desktop, and installed the USB dongle and the Universal Radio Hacker (URH) software from here. (These would work on my Raspberry Pi3, but required quite a bit of memory and were a bit slow).

1. Determine fan radio frequency

I fired up the URH Spectrum Analyzer.
I knew the fans were likely be around 433 MHz or 315 MHz.
Once running press a button on the remote, I could see a signal spike.

Ok so close to 433 Mhz.

2. Analyse and decode the signals

This probably took the longest amount of time, but decoding the signal was pretty fun.
This time I started the URH Record Signal function.
I recorded the stop and light buttons on two of my remotes (for different fans).
This was to get enough information to compare the commands from the different remotes and determine the header and command information. I expected the signal to be structured something like:

[fan_id][command][end]

  • fan_id - identifies a specific fan
  • command - the command to send, e.g. toggle the light
  • end - Some sort of pattern to indicate the end of a command
I saved the signal, closed the Record Signal screen, and URH displays the Interpretation detail.
Below shows 4 button clicks.
Helpfully URH does some useful analysis, detecting the modulation (ASK in this case) and takes a punt on the bit length - 300 ns in this case. (How long a on or off bit is in nano-seconds). It also then decodes the radio signal from an analog signal into a digital representation, i.e. a 0 or a 1.

If you zoom in on a click you'll see it basically repeats the same pattern a number of times depending on how long the button was pressed for.

Let's take a closer look.

So it's pretty straight forward:
No signal (off) = 0
A signal (on) = 1

And each individual 0 and 1 is evenly spaced (i.e. it lasts 300 ns).

So ignoring the no signal at the start this looks like:
100 101 101 101 100

This matches URH's analysis shown in the picture.
Note: In some cases URH guessed the wrong length, so I had to adjust it manually.

Great - so we now have a bunch of 0's and 1's to make sense of.

3. Determine the command signals

Ok so here is the toggle light and stop commands for fan A, and fan B.
I recorded all the commands for fan A to look at the patterns.
The result was I could divide the bits into the following.

<fan_id: Fan A or B>                             <command: light>   <end>
100101101101100101101101101100101101101101100101 101100100101101101 1011011
101101100100101101100101100100101100100100100101 101100100101101101 1011011


<fan_id: Fan A or B>                             <command: stop>    <end>
100101101101100101101101101100101101101101100101 101101100101101101 1011011
101101100100101101100101100100101100100100100101 101101100101101101 1011011

Looking in more detail we can see the signals repeat the pattern 100 and 101.
So assuming 100 = 1 and 101 = 0 we can simply the commands a bit further.

<fan_id>         <command> <end>
1000100001000010 011000    001
0011001011011110 011000    001

1000100001000010 001000    001
0011001011011110 001000    001

So we end up with:
  • Fan Identifier = 16 bits (65,536 possibilities - this aligned to the manual that sates 65,000 possible unique ids)
  • Command = 6 bits
  • End = 3 bits
Here are the commands I ended up with for my script:
#Commands
cmd_stop='001000'
cmd_light='011000' #light toggle
cmd_breeze='011100'
cmd_mode='110100' #reverse
cmd_s1='110000'
cmd_s2='100110'
cmd_s3='010000'
cmd_s4='010100'
cmd_s5='100101'
cmd_s6='100000'
cmd_off='111100' #light and fan off
cmd_on=cmd_s3
Note: I tested all possible command combinations and found one very useful command which turns the fan and light off.

Step 2 - Set up an RF sender on one of my Raspberry PIs

I purchased a RF wireless sender and receiver like the following.

I only used the sender (the 3 pin item on the left).







I connected this and connected the data pin to GPIO pin 22 on the Raspberry Pi3.
You can find plenty of information online on how to do this.

I also made a simple antenna from some Cat 6 wire, you can see this below.

Steps 3 and 4 are continued here.

Comments

Post a Comment

Popular posts from this blog

Experience with Optus 4G wireless broadband

Image
Some background, where I try not to gripe about NBN... O NBN!, wherefore art thou NBN! That pretty much sums up my experience over the last year, having relocated from Sydney with a decent NBN connection, to an ADSL1 connection in the Gold Coast. I was then left waiting for either an ADSL2 port to free up (not likely to happen) or NBN to finally arrive. NBN was expected here in Dec-18 and is now due in Dec-19.... So with NBN delayed another year, I was well and truly over my current connection. For the record I had 6 Mbps download and 0.3 Mbps upload. So uploading a picture to facebook would kill my internet. It's hard to believe this can be sold in Australia as an adequate service.... right not griping, moving on. Thankfully this is all behind me with the introduction of Optus's 4G wireless broadband plans, which were released in November 2018 replacing the Vividwireless service. Based on our usage of around 380 GB per month, I selected the the $80 500 GB plan. The
Read more

Port Forwarding on Optus 4G B525 router

Image
The port forwarding or "Virtual Server" settings are not available in the Optus customised web UI. However the underlying XML based API of the router still supports the function, at least for my B525s 65a model. So I've documented a couple of ways you can interact with the router API and set up port forwarding. Important!: Port forwarding will only work when the other device can access the private 10.*.*.* Optus IP Address of the router. I use it so my Optus mobile can access my home network. If you wanted to expose a service to the general internet then this likely won't work. Option 1 - Use the python API I've developed at  https://github.com/jinxo13/HuaweiB525Route r For those with scripting or programming experience Option 2 - Use Chrome and the Servistate plugin to interact with the B525's API directly I've provided a step by step guide - no programming experience is required Option 1 - Use the Python API Step 1 - Check the curre
Read more

Huawei B525 Python API

Image
As mentioned in my last post I was tinkering with the Optus provided Huawei B525 router features. I've now manged to implement a few commands and MAC filtering via a Python2 API. You can read more here:  https://github.com/jinxo13/HuaweiB525Router So far I'm using it to: Monitor my usage (I have a 500 GB cap) Implement time scheduling for my kids devices Here's my usage display in Grafana. I run OpenHab and persist the data from the Router using the python API into an Influxdb database that Grafana uses. Here's my current Grafana display: The API will work with the following model: B525s-65a And may work with these others: B618s-22d B715s-23c So far I've got MAC filtering implemented and a few API's to get traffic and other information. Currently supported calls: GET Requests ---------- getInfo() => api/device/information getTraffic() => api/monitoring/traffic-statistics getStats() => api/monitoring/month_
Read more