sqmk / huejay Goto Github PK

See sensors refactor.

This includes brightness, hue, sat, etc.

State is not reset after saving a light or group. Fix!

See subject.

Add new light state model as part of lights and groups.

This will break API, so reserve for v1.0.0.

See subject

The "type" attribute should be modifiable.

New attributes:

• class: Associated with type "Room". This is the name of the room. Assuming this is HomeKit related.

• Retrieve groups
• Create group
• Save group
• Delete group

See subject.

• Retrieve rules
• Create/update rules
• Delete rules

See subject.

Scenes may be easily recalled by using group 0. If a group/id is provided, then that group id is used for the recall instead.

Sample call:

client.scenes.recall(sceneId)
  .then(() => console.log(`Scene ${sceneId} recalled`));

With group id:

client.scenes.recall(sceneId, groupId)
  .then(() => console.log(`Scene ${sceneId} with ${groupId} recalled`));

Support for retrieving bridge data and updating.

Same deal as issue #18.

• Retrieve list of users
• Retrieve user by username
• Delete users

Light objects should allow for retrieving light model objects.

Allow configuring a custom port on the client.

Follow sensors refactor.

See sensors refactor.

I'm not a fan of the client having a 1:1 mapping of commands to calls. Organize the client with properties organizing commands and models.

e.g. client.light.get(), client.sensor.update(sensor);

See subject.

When we run the following code, the first line will cut the " ", the second line will produce an error.

echo jsmin('return /foo /.test(bar);');
echo jsmin('return /foo=/.test(bar);');

Change lastUsedDate > lastUsed.

Change createDate > created.

Support both upnp search and Philips remote api.

See subject.

See sensors refactor.

When creating a user, whitelist retrieval fails if there isn't a user associated with the client.

Rather than request the user from the bridge, return the original passed to create.

• Retrieve sensors
• Scan for new sensors

• Retrieving lights
• Updating lights
• Deleting lights

• Retrieve schedules
• Create schedule
• Update schedule
• Delete schedule

Make sifting through examples nicer.

See subject.

Each sensor type supports a set of buttons/events. Some of these buttons are toggle-able.

New attributes:

• owner - Whitelisted user that created scene
• recycle - true to auto delete, false if not
• locked - true if used by a rule or schedule
• appdata - Custom app data
• picture - Only available via GET
• lastupdated - Created or updated date
• version - Either PUT or POST, may not be necessary to expose in api

Deprecated attributes:

• active - Already not available in huejay

New commands:

• Create scene - Use POST instead of PUT
• Get scene - GET /api//scenes/
• Modify light state - Use PUT /scenes//lights//lightstate
• Modify scene - PUT /api//scenes/, name, lights, storelightstate
• Delete scene - DELETE /api//scenes/

See sensors refactor.

See sensors refactor.

See subject.

Add support for bridge models.

The following parameters are accepted:

• host
• username

See #18.

Like lights, sensors come in various models.

See sensors refactor.

The model shouldn't know a whole lot about bridge fields, logic.

Include a new attributes helper that can be reused in other models.

Since this is a temporary setting, it may be nice to offer a shortcut for touchlink.

• Retrieve scenes
• Create scenes
• Update scene light state

See subject.

Action helpers would improve upcoming schedule and rule refactoring. More details to follow.

See #18.

See subject.

For convenience. Add client.bridge.linkButton.