Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - acald

Pages: [1]
This has popped up from time to time.  This may be the answer:

Users / 1004 Final Torrent
« on: March 21, 2013, 05:22:02 am »
I've searched and searched for a torrent and couldn't find one so I figured I would create one to help distribute the load of everyone downloading it.  As usual, please leave your torrent clients available as much as possible to help spread the love.

If I've forgotten something guys, please let me know.

My token contribution to an awesome project.

Users / Monster MCC AVL300-S
« on: June 06, 2012, 04:31:35 pm »
Has anybody tried using this Z-Wave enabled remote?  It has a Z-wave extension RF-IR repeater called the Monster Control Omnilink.  It controls many, many Z-wave items and can also take on two different personalities (two different systems/rooms).

Feature requests & roadmap / Radio Thermostat Publishes API
« on: May 25, 2011, 03:52:14 am »
(links to follow)

Radio Thermostat just published the API set for their Wi-Fi connected thermostats. These thermostats work with all kinds of HVAC systems and can connect via Wi-Fi, Z-Wave, and Zig-Bee
Radio Thermostat has two models available the CT-80 ($250) and CT-30 ($140)

The CT-30 is also available for $99 at any Home Depot in the states as the Filtrete Mod#3M-50 and it comes with the Wi-Fi module.

It can be controlled via their web site, iPhone App, Windows Program, or API

I'm trying to figure out how hard it would be to write the interface or how to allow the current interface to control the device.  Maybe some pointers as to which files to start with.  My knowledge of programming is limited but I can handle scripting. According to the opening paragraphs of the API documentation:

The Radio Thermostat API is an HTTP API that enables client programs to query the thermostat state, and to manage/control the thermostat operation. In the HTTP terminology, the thermostat will be a server that will respond to HTTP requests from client devices. The API is designed with a RESTful architecture in mind.
The API is expected to be used by a variety of client applications such as graphical interface applications running on Windows, MAC, or iOS devices. It can also be used by programs such as curl to facilitate control via non-interactive client applications. Further, the HTTP GET APIs can be exercised using a browser.
The Radio Thermostat API provides a set of operations on a typical thermostat device and has been designed to be independent of the underlying implementation of the thermostat.

Any pointers would be greatly appreciated.

Pages: [1]