Skip to content

Commit

Permalink
Docs updates
Browse files Browse the repository at this point in the history
  • Loading branch information
SphtKr committed Mar 14, 2016
1 parent f5be5dc commit f0c65d9
Showing 1 changed file with 7 additions and 2 deletions.
9 changes: 7 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,8 +41,9 @@ Generally speaking, the following types of devices will work:
* Door/window sensors
* Light sensors (needs work)
* Motion sensors
* :tada: :new: Door Locks (e.g. Danalock)
* :tada: :new: Relative Humidity sensors (e.g. Aeon Labs Multisensor 6...needs testing!)
* Door Locks (e.g. Danalock)
* Relative Humidity sensors (e.g. Aeon Labs Multisensor 6...needs testing!)
* :tada: :new: Window Coverings

Additional devices in progress:

Expand Down Expand Up @@ -149,6 +150,10 @@ There is not really a direct analogue to a `Door/Window` sensor in HomeKit--the
b. You don't get any iOS notifications for state changes, so pick this if you find those annoying.
But, you won't be able to ask Siri about the state of the "Door", and app support for this characteristic has been historically lacking (Eve works great now). Also note that you can invert the value with `Homebridge.ContactSensorState.Invert`, which may result in a more intuitive value being shown.

##### Dimmer or other `switchMultilevel` as `WindowCovering`

If you have a shutter/drapery control that uses a percentage value for open/closed, but is not automatically recognized as such (for instance it is instead shown as a light dimmer), you can specify `Homebridge.Service.Type:WindowCovering` to force it to be recognized correctly. This should not be necessary in most cases.

##### More

There will be additional devices and use cases where this will be used. If you think you have a good use case for this that is not supported by the current code, please submit an issue with the guidelines above.
Expand Down

0 comments on commit f0c65d9

Please sign in to comment.