<commit_before># Philips Hue Client

This gem allows you to utilize the [Philips Hue
API](http://developers.meethue.com) to interact with your Hue Lights.


## Installation

Add this line to your application's Gemfile:

```ruby
gem 'hue-client'
```

And then execute:

    $ bundle

Or install it yourself as:

    $ gem install hue-client

## Usage

> NOTE: Currently under development. The notes below describe future capabilities.

This gem will support access to all aspects of your Hue Lighting System:

* **Portal/Bridge** management.
* **User/Whitelist* management.
* **Lights** management.
* **Groups** management.
* **Schedules** management.
* **Scenes** management.

### Configuration
You can specify your configuration if known ahead of time. Things like
your bridge `ip_address` and `username` are needed for all requests.

```ruby
Hue.configure do |c|
  c.ip_address '10.0.1.1' # Default will be the address of the bridge in use
  c.username 'my-username' # Default will be a random hex
  c.logger Logger.new('my-file.log') # Default is $stdout
end
```

### Connection
When connecting, the gem will utilize the _portal discovery_ endpoint to
discover the bridges on your network. This configuration will be cached
locally for later requests.

### Routing
The Hue API does not support
[Hypermedia](http://en.wikipedia.org/wiki/HATEOAS). Instead of littering
the code with URL building, all supported routes will be added to a
`Routing` file and can be used within the _resource_ objects. <commit_msg>fixing missing *<commit_after># Philips Hue Client

This gem allows you to utilize the [Philips Hue
API](http://developers.meethue.com) to interact with your Hue Lights.


## Installation

Add this line to your application's Gemfile:

```ruby
gem 'hue-client'
```

And then execute:

    $ bundle

Or install it yourself as:

    $ gem install hue-client

## Usage

> NOTE: Currently under development. The notes below describe future capabilities.

This gem will support access to all aspects of your Hue Lighting System:

* **Portal/Bridge** management.
* **User/Whitelist** management.
* **Lights** management.
* **Groups** management.
* **Schedules** management.
* **Scenes** management.

### Configuration
You can specify your configuration if known ahead of time. Things like
your bridge `ip_address` and `username` are needed for all requests.

```ruby
Hue.configure do |c|
  c.ip_address '10.0.1.1' # Default will be the address of the bridge in use
  c.username 'my-username' # Default will be a random hex
  c.logger Logger.new('my-file.log') # Default is $stdout
end
```

### Connection
When connecting, the gem will utilize the _portal discovery_ endpoint to
discover the bridges on your network. This configuration will be cached
locally for later requests.

### Routing
The Hue API does not support
[Hypermedia](http://en.wikipedia.org/wiki/HATEOAS). Instead of littering
the code with URL building, all supported routes will be added to a
`Routing` file and can be used within the _resource_ objects. 
{'fraction_non_alphanumeric': 0.09379128137384413, 'fraction_numerical': 0.0033025099075297227, 'mean_word_length': 4.323374340949034, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 2, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '999635', 'n_tokens_mistral': 887, 'n_tokens_neox': 852, 'n_words': 388}