Compare commits
1 commit
6c48eeaf7f
...
c342f4ec46
Author | SHA1 | Date | |
---|---|---|---|
c342f4ec46 |
1 changed files with 6 additions and 6 deletions
12
README.md
12
README.md
|
@ -2,22 +2,20 @@
|
|||
|
||||
Each folder contains a set of rules that can be used with Philips Hue.
|
||||
|
||||
**This is for geeks!** 😉
|
||||
|
||||
## Usage
|
||||
|
||||
See the readmes inside the ruleset folders.
|
||||
See the readme inside the folder.
|
||||
|
||||
## Installation
|
||||
|
||||
The JSON files are raw Hue API requests for maximum flexibility and portability.
|
||||
Identifiers for lights and sensors are parameterized using uppercase letters.
|
||||
Hence, before submitting the configuration files to the bridge,
|
||||
the parameters should be replaced as described below.
|
||||
they should be replaced as described below.
|
||||
|
||||
Some rulesets also require memory sensors.
|
||||
The `BASENAME` and `XX` parameters should be different for
|
||||
every instance of the ruleset.
|
||||
The `BASENAME` and `MAC` parameters should be different for
|
||||
every configuration.
|
||||
|
||||
### Example
|
||||
|
||||
|
@ -58,8 +56,10 @@ for f in DimmerBed/*.rule.json; do cat "$f" | sed "$IDS" | curl "$PREFIX/rules"
|
|||
|
||||
### Advanced Example
|
||||
|
||||
Note that the installation always is the same command.
|
||||
This example requires `jq` for fully automated installation.
|
||||
|
||||
|
||||
```sh
|
||||
install_sensor() {
|
||||
cat $1.sensor.json | sed "$IDS" | \
|
||||
|
|
Loading…
Add table
Reference in a new issue