[Edit] I now offer limited numbers of pre-built units in my shop.
Here is a small home-automation project that I have been working in my free time. I wanted to control my home-made air source heat pump system (based on Daikin FTX71GV / RX71GV ) from anywhere with Internet access. That would allow me to control my house’s heating/cooling remotely and more interestingly I could create scripts that turn the heating up/down based on outside temperature, time of day, inside average temperature and other criteria. All this to make a more efficient energy use, therefore a greener energy plan.
My Daikin uses an ARC433** series remote control, so the analysis was done for that particular IR remote.
I had a NaNode laying around, so the hardware part was pretty much figured out. Just needed an 940nm IR diode, couple resistors, a transistor and I was all set.
Next, I had to decode the IR protocol of Daikin air condifioners. That was quite a challenge as it turned out. To do this I needed to capture the IR signal and reverse-engineer it. Since I have no oscilloscope, I used my sound card as described in this article. I used audacity and spent few days poking by eyes analyzing the waveform. There are few articles on the Internet that helped me also, but none was about the IR protocol for my specific Daikin model. As it seems, there are at least three protocols used by that manufacturer.
The IR frame is split in two parts 3000us apart. Quite strange approach, I think it it done to confuse universal IR learning devices. In fact I also tried to learn the codes using a SilverCrest universal remote, but it fails due to the gap between transmissions.
So after I had the IR protocol figured out, I had to put up the software. I used Ken Shirriff’s IR library and modified it so that it takes Daikin’s protocol.
For Ethernet connectivity I useJCW’s EtherCard library, of course modifying it a bit because of some limitations it has. Basically the restrictions I needed to avoid are the progmem based DNS lookup and no custom HTTP headers management. Another challenge was to deal with the RAM usage, the library has the TCP buffer taking most of the ATMega’s RAM plus it is a single-packet implementation. That means that a page cannot exceed 1100 bytes (that’s the buffer size).. I finally managed to squeeze in all the UI and was left with 196 bytes of RAM free. Funny when you think of the amount of functionality that 30K of compiled sketch code can hold vs modern software resource usage.
So here is what I came up with as features list:
- IPv4 only supported; IP, Gateway and DNS configurable via the web UI.
- The module responds to ICMP (ping)requests
- Option to reset to default values via a button press during start up (use in case you forget the network settings)
- HTTP server
- Web UI, optimized for use via mobile phone by using JQuery;
- Option for basic HTML UI
- HTTP listen port is configurable
- Basic HTTP authenticatication can be enabled for password protection of the web UI. Useful to prevent unauthorized access to the module
- Manual remote control
- Set On/Off state
- Set temperature
- Set mode (heat, cool, dry, auto)
- Set aux functions (Powerful, Silent, Normal operation)
- Set fan (1 bar, 3 bars,5 bars, night mode, auto)
- Schedule timers – 10 user configurable timers via the UI; This is something quite useful because my Daikin doesn’t have scheduler built in.
- Day(s) to activate Monday-Friday, Weekends,Every day, individual day of week
- Minute (in 15 min intervals)
- Time synchronization via NTP (Network Time Protocol; Time is needed if using the schedule. I use NTP because I don’t have a RTC on the NaNode plus seems less hassle to maintain.
- NTP server configurable (as IP or site)
- Timezone takes positive and negative values
- Support for DynDNS dynamic DNS service. This is a bit of feature creep, but wanted to give it a try. So I have a fully functional DynDNS client now 🙂
- The module can be controlled with HTTP GET requests. In combination with JSON feedback, you can use the module from your own web scripts
The project turned out too specific – for a particular model of AC. For the future I’d like to take a different approach – learning IR codes rather than decoding and using for a specific model. Learning a code will be simply memorizing the pulse widths and compressing them. AC remote controls send “state” in one command, therefore learning is quite useful. The user may then put a name to the learned code i.e. “heating, temp=21deg, fan=low”. The learned codes will be stored on SD card.
You may browse my code at github. It is quite dirty because I had quite some hard time to deal with the limited RAM after the TCP buffer ate 1100 bytes out of it..
If you find the code useful, you may consider a small donation 😉 [paypal-donation]
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.