pi-lights-control 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: fbfc3abb1ce7e062601c6c375716ba4397997a03
4
+ data.tar.gz: 557cb974d3de60fe93a5611745846ef689042691
5
+ SHA512:
6
+ metadata.gz: b73d59592fbc6676e6f666ef19589ba0defc04e2b01a328999d387bc13e63f429d6059b753188b1dd2ca4e8fe8f08ac12fcf8192b5ee7e49226d2606f024213e
7
+ data.tar.gz: 3087fc9ee3c6626fb02bce9b546e741b0c67fd4a287d336d1aa8293576fd9a66cfc4866ca72e0dcf35b527ae82ca0a1c6999cb1d0c8664761c975cd2f991e2ad
data/.gitignore ADDED
@@ -0,0 +1,9 @@
1
+ /.bundle/
2
+ /.yardoc
3
+ /Gemfile.lock
4
+ /_yardoc/
5
+ /coverage/
6
+ /doc/
7
+ /pkg/
8
+ /spec/reports/
9
+ /tmp/
data/.rspec ADDED
@@ -0,0 +1,2 @@
1
+ --format documentation
2
+ --color
data/.travis.yml ADDED
@@ -0,0 +1,5 @@
1
+ sudo: false
2
+ language: ruby
3
+ rvm:
4
+ - 2.3.0
5
+ before_install: gem install bundler -v 1.13.6
data/CHANGELOG.md ADDED
@@ -0,0 +1,7 @@
1
+ # Changelog
2
+
3
+ ## v0.1.0 (2016 Nov 19)
4
+
5
+ * Support power on/off RF commands
6
+ * Support multiple light set syncing
7
+ * Support eight default light programs
@@ -0,0 +1,74 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, gender identity and expression, level of experience,
9
+ nationality, personal appearance, race, religion, or sexual identity and
10
+ orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behavior that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at jpbadger@ucalgary.ca. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at [http://contributor-covenant.org/version/1/4][version]
72
+
73
+ [homepage]: http://contributor-covenant.org
74
+ [version]: http://contributor-covenant.org/version/1/4/
data/Gemfile ADDED
@@ -0,0 +1,4 @@
1
+ source 'https://rubygems.org'
2
+
3
+ # Specify your gem's dependencies in pi-lights-control.gemspec
4
+ gemspec
data/LICENSE.txt ADDED
@@ -0,0 +1,21 @@
1
+ The MIT License (MIT)
2
+
3
+ Copyright (c) 2016 James Badger
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in
13
+ all copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
21
+ THE SOFTWARE.
data/README.md ADDED
@@ -0,0 +1,112 @@
1
+ # Pi Lights Control
2
+
3
+ This gem provides an executable and a library for sending radio frequency commands from a Raspberry Pi connected with a 433.920 MHz transmitter to one or more sets of Home Collection Remote Control Christmas Lights.
4
+
5
+ The gem should be compatible with any Raspberry Pi that has GPIO pins. It has been tested with a 433.920 MHz FS1000A module (pictured below) for Arduino/Raspberry Pi compatible devices. It **will not** build on MacOS as epoll is only supported on Linux.
6
+
7
+ ![FS1000A Receiver/Transmitter Set](https://www.jamesbadger.ca/images/FS1000A.jpg)
8
+
9
+ ## Installation
10
+
11
+ Add this line to your application's Gemfile:
12
+
13
+ ```ruby
14
+ gem 'pi-lights-control'
15
+ ```
16
+
17
+ And then execute:
18
+
19
+ $ bundle
20
+
21
+ Or install it yourself as:
22
+
23
+ $ gem install pi-lights-control
24
+
25
+ ## Usage
26
+
27
+ You can use this gem in two ways, as a Ruby library or as an executable.
28
+
29
+ ### Executable Usage
30
+
31
+ Using the executable from the command line allows you to quickly test the library.
32
+
33
+ TODO
34
+
35
+ ### Library API
36
+
37
+ Alternatively, you can build applications that integrate this library.
38
+
39
+ #### Command Class
40
+
41
+ The `Command` class sets up a single GPIO pin as the output control for a transmitter. It is initialized with the Pin number (defaulting to board numbering). It also supports BCM pin numbering.
42
+
43
+ ```ruby
44
+ c = PiLightsControl::Command.new(12) # => :board numbering
45
+ c = PiLightsControl::Command.new(10, { numbering: :bcm }) # => :bcm numbering
46
+ ```
47
+
48
+ The `Command` class will default to repeating codes six times, as that was a reliable count used in testing. You can however change it:
49
+
50
+ ```ruby
51
+ c = PiLightsControl::Command.new(12)
52
+ c.repeat_count = 8
53
+ ```
54
+
55
+ Turning the lights on or off can be accessed using simple commands:
56
+
57
+ ```ruby
58
+ c = PiLightsControl::Command.new(12)
59
+ c.power_on
60
+ c.power_off
61
+ ```
62
+
63
+ Synchronizing lights will cause any light sets that receive the command to reset to a default state, ensuring all lights are in a "fresh slate".
64
+
65
+ ```ruby
66
+ c = PiLightsControl::Command.new(12)
67
+ c.sync_lights
68
+ ```
69
+
70
+ There are eight different programs that can be configured for the lights.
71
+
72
+ ```ruby
73
+ c = PiLightsControl::Command.new(12)
74
+ c.program(:combination) # Cycles through the other 7 programs
75
+ c.program(:steady) # Lights are continuously on
76
+ c.program(:slow_blink) # Lights are on 1/2 second, then off 1/2 second
77
+ c.program(:fast_blink) # Lights blink on/off much faster
78
+ c.program(:slow_fade) # Lights fade from off to on at a slow rate
79
+ c.program(:fast_fade) # Lights fade from off to on at a fast rate
80
+ c.program(:blink_steady) # Lights blink twice, then are steady for a second or two
81
+ c.program(:step_fade) # Lights fade from off to on but at discrete brightness steps instead of a continuous increase/decrease
82
+ ```
83
+
84
+ ## Roadmap
85
+
86
+ For v0.1.0:
87
+
88
+ * Support power on/off for lights
89
+ * Support all light programs and sync
90
+
91
+ For v0.2.0:
92
+
93
+ * Add executable
94
+
95
+ For v0.3.0:
96
+
97
+ * Any cleanup/refactoring before v1.0
98
+
99
+ ## Development
100
+
101
+ After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
102
+
103
+ To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
104
+
105
+ ## Contributing
106
+
107
+ Bug reports and pull requests are welcome on GitHub at https://github.com/openfirmware/pi-lights-control. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
108
+
109
+ ## License
110
+
111
+ The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
112
+
data/Rakefile ADDED
@@ -0,0 +1,6 @@
1
+ require "bundler/gem_tasks"
2
+ require "rspec/core/rake_task"
3
+
4
+ RSpec::Core::RakeTask.new(:spec)
5
+
6
+ task :default => :spec
data/bin/console ADDED
@@ -0,0 +1,14 @@
1
+ #!/usr/bin/env ruby
2
+
3
+ require "bundler/setup"
4
+ require "pi-lights-control"
5
+
6
+ # You can add fixtures and/or initialization code here to make experimenting
7
+ # with your gem easier. You can also use a different console, if you like.
8
+
9
+ # (If you use this, don't forget to add pry to your Gemfile!)
10
+ # require "pry"
11
+ # Pry.start
12
+
13
+ require "irb"
14
+ IRB.start
data/bin/setup ADDED
@@ -0,0 +1,8 @@
1
+ #!/usr/bin/env bash
2
+ set -euo pipefail
3
+ IFS=$'\n\t'
4
+ set -vx
5
+
6
+ bundle install
7
+
8
+ # Do any other automated setup that you need to do here
@@ -0,0 +1,3 @@
1
+ #!/usr/bin/env ruby
2
+
3
+ require "pi-lights-control"
@@ -0,0 +1,45 @@
1
+ module PiLightsControl
2
+ class Command
3
+ attr_accessor :repeat_count
4
+
5
+ def initialize(pin, options = {})
6
+ RPi::GPIO.set_numbering options[:numbering] || :board
7
+ @repeat_count = 6
8
+ @pin = pin
9
+ end
10
+
11
+ def power_off
12
+ transmit_command(PiLightsControl::COMMAND_TABLE[:power_off])
13
+ end
14
+
15
+ def power_on
16
+ transmit_command(PiLightsControl::COMMAND_TABLE[:power_on])
17
+ end
18
+
19
+ def program(name)
20
+ program_name = "program_#{name.to_s}"
21
+ transmit_command(PiLightsControl::COMMAND_TABLE[program_name.to_sym])
22
+ end
23
+
24
+ def sync_lights
25
+ transmit_command(PiLightsControl::COMMAND_TABLE[:sync_lights])
26
+ end
27
+
28
+ private
29
+
30
+ def transmit_command(command)
31
+ @repeat_count.times do
32
+ command.each do |code|
33
+ high_length = PiLightsControl::CODE_TABLE[code][0]
34
+ low_length = PiLightsControl::CODE_TABLE[code][1]
35
+
36
+ RPi::GPIO.set_high @pin
37
+ sleep(high_length * PiLightsControl::TIME_DELAY / 1000000.0)
38
+
39
+ RPi::GPIO.set_low @pin
40
+ sleep(low_length * PiLightsControl::TIME_DELAY / 1000000.0)
41
+ end
42
+ end
43
+ end
44
+ end
45
+ end
@@ -0,0 +1,3 @@
1
+ module PiLightsControl
2
+ VERSION = "0.1.0"
3
+ end
@@ -0,0 +1,27 @@
1
+ require 'rpi_gpio'
2
+
3
+ require "pi-lights-control/command"
4
+ require "pi-lights-control/version"
5
+
6
+ module PiLightsControl
7
+ CODE_TABLE = {
8
+ 0 => [4, 4],
9
+ 1 => [4, 8],
10
+ 2 => [4, 71],
11
+ 3 => [26, 12]
12
+ }
13
+ COMMAND_TABLE = {
14
+ power_off: [3,0,1,0,1,1,0,0,1,1,1,0,1,0,0,0,1,2],
15
+ power_on: [3,0,1,0,1,1,0,0,1,1,1,0,1,0,0,0,0,2],
16
+ sync_lights: [3,0,0,1,1,0,1,1,1,0,0,0,1,1,1,0,0,2],
17
+ program_combination: [3,0,1,0,1,1,0,0,1,1,1,1,0,0,0,0,0,2],
18
+ program_steady: [3,0,1,0,1,1,0,0,1,1,1,1,0,0,0,0,1,2],
19
+ program_slow_blink: [3,0,1,0,1,1,0,0,1,1,1,1,0,0,0,1,0,2],
20
+ program_fast_blink: [3,0,1,0,1,1,0,0,1,1,1,1,0,0,0,1,1,2],
21
+ program_slow_fade: [3,0,1,0,1,1,0,0,1,1,1,1,0,0,1,0,0,2],
22
+ program_fast_fade: [3,0,1,0,1,1,0,0,1,1,1,1,0,0,1,0,1,2],
23
+ program_blink_steady: [3,0,1,0,1,1,0,0,1,1,1,1,0,0,1,1,0,2],
24
+ program_step_fade: [3,0,1,0,1,1,0,0,1,1,1,1,0,0,1,1,1,2]
25
+ }
26
+ TIME_DELAY = 120 # microseconds
27
+ end
@@ -0,0 +1,29 @@
1
+ # coding: utf-8
2
+ lib = File.expand_path('../lib', __FILE__)
3
+ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
4
+ require 'pi-lights-control/version'
5
+
6
+ Gem::Specification.new do |spec|
7
+ spec.name = "pi-lights-control"
8
+ spec.version = PiLightsControl::VERSION
9
+ spec.authors = ["James Badger"]
10
+ spec.email = ["james@jamesbadger.ca"]
11
+
12
+ spec.summary = %q{Control one model of xmas lights via Raspberry Pi}
13
+ spec.description = %q{Control a specific model of Christmas lights using a Raspberry Pi and a 433.920 MHz transmitter connected via GPIO.}
14
+ spec.homepage = "https://github.com/openfirmware/pi-lights-control"
15
+ spec.license = "MIT"
16
+
17
+ spec.files = `git ls-files -z`.split("\x0").reject do |f|
18
+ f.match(%r{^(test|spec|features)/})
19
+ end
20
+ spec.bindir = "exe"
21
+ spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
22
+ spec.require_paths = ["lib"]
23
+
24
+ spec.add_dependency "rpi_gpio", "~> 0.3.2"
25
+
26
+ spec.add_development_dependency "bundler", "~> 1.13"
27
+ spec.add_development_dependency "rake", "~> 10.0"
28
+ spec.add_development_dependency "rspec", "~> 3.0"
29
+ end
metadata ADDED
@@ -0,0 +1,118 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: pi-lights-control
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.1.0
5
+ platform: ruby
6
+ authors:
7
+ - James Badger
8
+ autorequire:
9
+ bindir: exe
10
+ cert_chain: []
11
+ date: 2016-11-20 00:00:00.000000000 Z
12
+ dependencies:
13
+ - !ruby/object:Gem::Dependency
14
+ name: rpi_gpio
15
+ requirement: !ruby/object:Gem::Requirement
16
+ requirements:
17
+ - - "~>"
18
+ - !ruby/object:Gem::Version
19
+ version: 0.3.2
20
+ type: :runtime
21
+ prerelease: false
22
+ version_requirements: !ruby/object:Gem::Requirement
23
+ requirements:
24
+ - - "~>"
25
+ - !ruby/object:Gem::Version
26
+ version: 0.3.2
27
+ - !ruby/object:Gem::Dependency
28
+ name: bundler
29
+ requirement: !ruby/object:Gem::Requirement
30
+ requirements:
31
+ - - "~>"
32
+ - !ruby/object:Gem::Version
33
+ version: '1.13'
34
+ type: :development
35
+ prerelease: false
36
+ version_requirements: !ruby/object:Gem::Requirement
37
+ requirements:
38
+ - - "~>"
39
+ - !ruby/object:Gem::Version
40
+ version: '1.13'
41
+ - !ruby/object:Gem::Dependency
42
+ name: rake
43
+ requirement: !ruby/object:Gem::Requirement
44
+ requirements:
45
+ - - "~>"
46
+ - !ruby/object:Gem::Version
47
+ version: '10.0'
48
+ type: :development
49
+ prerelease: false
50
+ version_requirements: !ruby/object:Gem::Requirement
51
+ requirements:
52
+ - - "~>"
53
+ - !ruby/object:Gem::Version
54
+ version: '10.0'
55
+ - !ruby/object:Gem::Dependency
56
+ name: rspec
57
+ requirement: !ruby/object:Gem::Requirement
58
+ requirements:
59
+ - - "~>"
60
+ - !ruby/object:Gem::Version
61
+ version: '3.0'
62
+ type: :development
63
+ prerelease: false
64
+ version_requirements: !ruby/object:Gem::Requirement
65
+ requirements:
66
+ - - "~>"
67
+ - !ruby/object:Gem::Version
68
+ version: '3.0'
69
+ description: Control a specific model of Christmas lights using a Raspberry Pi and
70
+ a 433.920 MHz transmitter connected via GPIO.
71
+ email:
72
+ - james@jamesbadger.ca
73
+ executables:
74
+ - pi-lights-control
75
+ extensions: []
76
+ extra_rdoc_files: []
77
+ files:
78
+ - ".gitignore"
79
+ - ".rspec"
80
+ - ".travis.yml"
81
+ - CHANGELOG.md
82
+ - CODE_OF_CONDUCT.md
83
+ - Gemfile
84
+ - LICENSE.txt
85
+ - README.md
86
+ - Rakefile
87
+ - bin/console
88
+ - bin/setup
89
+ - exe/pi-lights-control
90
+ - lib/pi-lights-control.rb
91
+ - lib/pi-lights-control/command.rb
92
+ - lib/pi-lights-control/version.rb
93
+ - pi-lights-control.gemspec
94
+ homepage: https://github.com/openfirmware/pi-lights-control
95
+ licenses:
96
+ - MIT
97
+ metadata: {}
98
+ post_install_message:
99
+ rdoc_options: []
100
+ require_paths:
101
+ - lib
102
+ required_ruby_version: !ruby/object:Gem::Requirement
103
+ requirements:
104
+ - - ">="
105
+ - !ruby/object:Gem::Version
106
+ version: '0'
107
+ required_rubygems_version: !ruby/object:Gem::Requirement
108
+ requirements:
109
+ - - ">="
110
+ - !ruby/object:Gem::Version
111
+ version: '0'
112
+ requirements: []
113
+ rubyforge_project:
114
+ rubygems_version: 2.2.2
115
+ signing_key:
116
+ specification_version: 4
117
+ summary: Control one model of xmas lights via Raspberry Pi
118
+ test_files: []