forked from homebridge/HAP-NodeJS
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Fan_accessory.js
91 lines (79 loc) · 2.9 KB
/
Fan_accessory.js
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
var Accessory = require('../').Accessory;
var Service = require('../').Service;
var Characteristic = require('../').Characteristic;
var uuid = require('../').uuid;
// here's a fake hardware device that we'll expose to HomeKit
var FAKE_FAN = {
powerOn: false,
rSpeed: 100,
setPowerOn: function(on) {
if(on){
//put your code here to turn on the fan
FAKE_FAN.powerOn = on;
}
else{
//put your code here to turn off the fan
FAKE_FAN.powerOn = on;
}
},
setSpeed: function(value) {
console.log("Setting fan rSpeed to %s", value);
FAKE_FAN.rSpeed = value;
//put your code here to set the fan to a specific value
},
identify: function() {
//put your code here to identify the fan
console.log("Fan Identified!");
}
}
// This is the Accessory that we'll return to HAP-NodeJS that represents our fake fan.
var fan = exports.accessory = new Accessory('Fan', uuid.generate('hap-nodejs:accessories:Fan'));
// Add properties for publishing (in case we're using Core.js and not BridgedCore.js)
fan.username = "1A:2B:3C:4D:5E:FF";
fan.pincode = "031-45-154";
// set some basic properties (these values are arbitrary and setting them is optional)
fan
.getService(Service.AccessoryInformation)
.setCharacteristic(Characteristic.Manufacturer, "Sample Company")
// listen for the "identify" event for this Accessory
fan.on('identify', function(paired, callback) {
FAKE_FAN.identify();
callback(); // success
});
// Add the actual Fan Service and listen for change events from iOS.
// We can see the complete list of Services and Characteristics in `lib/gen/HomeKitTypes.js`
fan
.addService(Service.Fan, "Fan") // services exposed to the user should have "names" like "Fake Light" for us
.getCharacteristic(Characteristic.On)
.on('set', function(value, callback) {
FAKE_FAN.setPowerOn(value);
callback(); // Our fake Fan is synchronous - this value has been successfully set
});
// We want to intercept requests for our current power state so we can query the hardware itself instead of
// allowing HAP-NodeJS to return the cached Characteristic.value.
fan
.getService(Service.Fan)
.getCharacteristic(Characteristic.On)
.on('get', function(callback) {
// this event is emitted when you ask Siri directly whether your fan is on or not. you might query
// the fan hardware itself to find this out, then call the callback. But if you take longer than a
// few seconds to respond, Siri will give up.
var err = null; // in case there were any problems
if (FAKE_FAN.powerOn) {
callback(err, true);
}
else {
callback(err, false);
}
});
// also add an "optional" Characteristic for spped
fan
.getService(Service.Fan)
.addCharacteristic(Characteristic.RotationSpeed)
.on('get', function(callback) {
callback(null, FAKE_FAN.rSpeed);
})
.on('set', function(value, callback) {
FAKE_FAN.setSpeed(value);
callback();
})