- SmartThings - home automation system that communicates with devices over ZigBee, Z-Wave, or HTTP
- Smarter Coffee - A WiFi coffee machine that can be controlled with binary commands over TCP sockets and UDP broadcasts
- SmartThingsSmarterCoffee - A Node.js server that converts REST calls from SmartThings to Smarter Coffee binary packets
- Tested on Node.js 7.9.0. It may work on other versions.
- Tested on Mac OS and Raspberry Pi Raspian. Should work on Windows, but I haven't tried it.
- When the server starts, it will discover coffee machine(s) via UDP broadcast. Coffee machine(s) must already be on the same network.
- I'm not sure what will happen if you try to control the machine with the Smarter official app and SmartThings integration at the same time. I never use the official app, it doesn't work on my Android phone.
The Smarter Coffee machine communicates by sending bits over sockets. The makes it impossible to control directly with SmartThings, as SmartThings device handlers can only communicate with LAN devices via HTTP with XML / JSON.
SmartThingsSmarterCoffee converts HTTP calls from SmartThings into binary commands and sends them to the coffee machine.
To contol your coffee machine with SmartThings you'll need:
- this Node.js app, running on a computer. I recommend a Raspberry Pi.
- the companion SmartThings Device Handler. This device handler provides the "on/off" button for your coffee machine in SmartThings
- the companion SmartThings SmartApp. The smart app locates the SmartThingsSmarterCoffee server via UPnP and creates the actual coffee machine device. It also updates the device settings in the case of either SmartThingsSmarterCoffee or the coffee machine IP address changes.
| Component | Ver | Link |
|---|---|---|
| SmartThingsSmarterCoffee | 1.1.2 | https://github.com/petermajor/SmartThingsSmarterCoffee |
| Smarter Manager | 1.1.1 | https://github.com/petermajor/SmartThings/blob/master/apps/SmarterManager.groovy |
| Smarter Coffee | 1.1.0 | https://github.com/petermajor/SmartThings/blob/master/devices/SmarterCoffee.groovy |
- Clone the SmartThingsSmarterCoffee repository into a folder on your server.
- Run
npm installfrom the top folder of the clone to install module dependencies. - Run
node app.jsfrom the top folder of the install to start the app. - Use the SmartThings graph IDE to install the Device Handler (see above).
- Use the SmartThings graph IDE to install the SmartApp (see above).
- Use the SmartThings mobile app to create an instance of the Smarter Manager SmartApp:
- Tap Automation > SmartApps
- Scroll to the bottom and select Add a SmartApp
- Scroll to the bottom and select My Apps
- Find Smarter Manager in list and tap on it
- Wait a min for the SmartApp to discover your Node.js server and the Coffee Machine via UPnP
- Select Coffee Machine and tap the Done button at the top
If the installation completed without errors, you will have a device called Coffee Machine added to your device list.
You can now use that like any other on/off switch in SmartThings, including control with Amazon Echo or Google Home.
NOTE: Do not remote the Smarter Manager app after setup. Doing so will also remove the associated Coffee Machine device.
If you're using a Raspberry Pi, the standard Raspian install has a really, really, really old version of Node installed. I haven't tested SmartThingsSmarterCoffee on that version of Node.js. I would recommend that you follow these instructions to install the latest version Node.js.
You can configure SmartThingsSmarterCoffee to run as a service and start after the Pi boots.
First, create the service definition:
sudo nano /lib/systemd/system/SmartThingsSmarterCoffee.service
Copy and paste this text and save with ctrl-x:
[Unit]
Description=SmartThingsSmarterCoffee
After=multi-user.target
[Service]
Type=simple
ExecStart=/usr/bin/node <path to git repo>/app.js
WorkingDirectory=<path to git repo>
Restart=always
RestartSec=10
Environment=NODE_ENV=production
[Install]
WantedBy=multi-user.target
Then run the additional commands:
sudo systemctl daemon-reload
sudo systemctl enable SmartThingsSmarterCoffee.service
sudo systemctl start SmartThingsSmarterCoffee.service
sudo systemctl status SmartThingsSmarterCoffee.service
If you want to stop the service (until next reboot):
sudo systemctl stop SmartThingsSmarterCoffee.service
You don't need to know this for the SmartThings integration. But if you're using this API to integration your coffee machine with something else it might be useful...
Map of known coffee machines.
Example response:
{
"18fe34f86975": {
"id": "18fe34f86975",
"mac": "18:fe:34:f8:69:75",
"ip": "192.168.1.15",
"name": "Coffee Machine",
"status": {
"isBrewing": false,
"isCarafeDetected": false,
"isGrind": true,
"isHotplateOn": false,
"waterLevel": 2,
"strength": 0,
"cups": 5
}
}
}
Note status can be null if the the device endpoint is called before the device status can be queried.
The server supports more than one machine on the network.
Use the id property to identify which machine you would like to preform operation for.
Gets the status of the specified machine.
Example response:
{
"id": "18fe34f86975",
"mac": "18:fe:34:f8:69:75",
"ip": "192.168.1.15",
"name": "Coffee Machine",
"status": {
"isBrewing": false,
"isCarafeDetected": false,
"isGrind": true,
"isHotplateOn": false,
"waterLevel": 2,
"strength": 0,
"cups": 5
}
}
Note status can be null if the the device endpoint is called before the device status can be queried.
Overrides the default setting for the number of cups to brew.
Payload:
{ "cups": 3 }
cups must be a value between 1 and 12 inclusive.
Overrides the default setting for the strength of coffee to brew.
Payload:
{ "strength": 1 }
strength must be 0 (weak), 1 (medium) or 2 (strong).
Starts brewing coffee.
If the payload is empty then coffee with default settings is brewed.
If the payload is not empty then the settings in the payload are used.
Payload:
{
"cups": 3,
"isGrind": true,
"strength": 2
}
cups must be a value between 1 and 12 inclusive.
isGrind must be true (grind) or false (filter).
strength must be 0 (weak), 1 (medium) or 2 (strong).
Stops brewing if one was in progress.
Payload: none
Sets the machine to 'grind' or 'filter' mode.
Payload:
{ "isGrind": true }
isGrind must be true (grind) or false (filter).
Turns on the hotplate only.
If the payload is empty then hotplate will be turned on for five minutes.
If the payload is not empty then the hotplate will be turned on for the number of mins specified in the payload.
Payload:
{ "mins": 10 }
mins must be a value between 1 and 30 inclusive.
Turns off the hotplate.
Payload: none