You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,7 +165,7 @@ remove the brightness component from the config.
165
165
|`name`| The name of your RGB accessory. It will appear in the Home app | "RGB Light" |
166
166
|`service`|`"Light"` or `"Switch"`||
167
167
|`timeout`_(optional)_| Time (in milli seconds) until the accessory will be marked as "Not Responding" if it is unreachable.| 5000 |
168
-
|`http_method`_(optional)_| The HTTP method used for set requests. | "GET" |
168
+
|`http_method`_(optional)_| The HTTP method used for set requests only. Get HTTP requests are fixed to 'GET' for now. | "GET" |
169
169
|`username`_(optional)_| Username if http authentication is enabled on the RGB device ||
170
170
|`password`_(optional)_| Password if http authentication is enabled on the RGB device ||
171
171
|`notificationID`_(optional)_| Identifier to use when device sends push notifications. See [Push notifications](#push-responses-device-pushes-updates)||
@@ -226,7 +226,7 @@ This can be realized by supplying the `notificationID` as part of this accesory'
226
226
Your device should then push the `On``characteristic` towards the notification server.
227
227
E.g. a POST request towards `http://<homebridge-host>:<notification-server-port>/<notificationID>` with the following
0 commit comments