pi_mote 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: be461efcc380ccb5d91c8aa845031a615ded2851
-  data.tar.gz: 0ef99f7c00934f8977b3d8b0fd024b0783529e8b
+SHA256:
+  metadata.gz: d8fdebfe73c4fcdfceac47f151e5f31b3c2e1d7ac8fd5427186b736a7ed42146
+  data.tar.gz: 4b2d8f47ed027bdfbdc84fc8dc0d6ec9e9441fdecc406de44a7a2d0375c993fa
 SHA512:
-  metadata.gz: 3adac4a8c229deaee11e2da5b4f19acb3d9a0f3ffa773eb0cafc0f22971cf2b87566b5b5917807d784ff435d859b2e1b5cb671800f46425d163a664b62d850f5
-  data.tar.gz: 501848cfdc1d2054835f5986e03ca1681d17c8059a9f92ea9b035802b95fed6d79be4f77951428b6a1185bca6e1f8bef7668183c82b80801493e5914cc8de8aa
+  metadata.gz: 154a3080770d772b1aad74034c20a3b79b20b1f29637cadc599af98eed0aee59b42a8f819fcfcaa25495e5f13370fac1b63c43285324b603b30a8431345dfe3b
+  data.tar.gz: '08a4d59dfbb45a7aa9bb6b34d9e74728809c7e02ade5cb88653bbe948f7a81e828f96ea56d6bedd48411b283d2c6384f8595c9a7daa0ce3675bd70d813290a2e'

data/lib/pi_mote.rb

@@ -0,0 +1,66 @@
+require 'rpi_gpio'
+require 'pi_mote/version'
+
+module PiMote
+  class Sockets
+    ON_SIGNALS = {
+      0 => %w(high high low high),
+      1 => %w(high high high high),
+      2 => %w(low high high high),
+      3 => %w(high low high high),
+      4 => %w(low low high high)
+    }.freeze
+
+    OFF_SIGNALS = {
+      0 => %w(high high low low),
+      1 => %w(high high high low),
+      2 => %w(low high high low),
+      3 => %w(high low high low),
+      4 => %w(low low high low)
+    }.freeze
+
+    # Pin numbers in this method comes from energenie manual
+    def initialize(given_opt = {})
+      @opt = {
+        signal_pins: [17, 22, 23, 27],
+        on_off_pin: 24,
+        enable_pin: 25,
+        board_numbering: :bcm
+      }
+
+      @opt = @opt.merge(given_opt) if defined? given_opt
+      RPi::GPIO.set_numbering @opt[:board_numbering]
+
+      @opt[:signal_pins].map do |pin|
+        RPi::GPIO.setup pin, as: :output, initialize: :low
+      end
+      RPi::GPIO.setup @opt[:on_off_pin], as: :output, initialize: :low
+      RPi::GPIO.setup @opt[:enable_pin], as: :output, initialize: :low
+    end
+
+    def change_plug_state(socket, signals_hash)
+      socket_signals = signals_hash[socket]
+      @opt[:signal_pins].zip(socket_signals).each do |pin, signal|
+        RPi::GPIO.send("set_#{signal}", pin)
+      end
+      sleep(0.1)
+      RPi::GPIO.set_high @opt[:enable_pin]
+      sleep(0.25)
+      RPi::GPIO.set_low @opt[:enable_pin]
+    end
+
+    def switch_on(socket = 0)
+      change_plug_state(socket, ON_SIGNALS)
+    end
+
+    def switch_off(socket = 0)
+      change_plug_state(socket, OFF_SIGNALS)
+    end
+
+    def cleanup
+      @opt[:signal_pins].each { |pin| RPi::GPIO.clean_up pin }
+      RPi::GPIO.clean_up @opt[:enable_pin]
+      RPi::GPIO.clean_up @opt[:on_off_pin]
+    end
+  end
+end

data/lib/pi_mote/version.rb

@@ -0,0 +1,3 @@
+module PiMote
+  VERSION = "0.1.1"
+end

metadata

@@ -1,57 +1,57 @@
 --- !ruby/object:Gem::Specification
 name: pi_mote
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Can Eldem
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-03-09 00:00:00.000000000 Z
+date: 2021-02-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: bundler
+  name: rpi_gpio
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.0'
-  type: :development
+        version: 0.5.0
+  type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.0'
+        version: 0.5.0
 - !ruby/object:Gem::Dependency
-  name: rake
+  name: bundler
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '2.1'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '2.1'
 - !ruby/object:Gem::Dependency
-  name: minitest
+  name: rspec
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '3.10'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '3.10'
 description: Ruby library for pi mite raspberry pi
 email:
 - eldemcan@gmail.com
@@ -59,18 +59,8 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".gitignore"
-- ".ruby-version"
-- ".travis.yml"
-- CODE_OF_CONDUCT.md
-- Gemfile
-- LICENSE
-- LICENSE.txt
-- README.md
-- Rakefile
-- bin/console
-- bin/setup
-- pi_mote.gemspec
+- lib/pi_mote.rb
+- lib/pi_mote/version.rb
 homepage: https://github.com/eldemcan/pi-mote-ruby
 licenses:
 - MIT
@@ -90,8 +80,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.6.14.3
+rubygems_version: 3.0.3
 signing_key: 
 specification_version: 4
 summary: Control your pi mote with ruby

data/.gitignore

@@ -1,50 +0,0 @@
-*.gem
-*.rbc
-/.config
-/coverage/
-/InstalledFiles
-/pkg/
-/spec/reports/
-/spec/examples.txt
-/test/tmp/
-/test/version_tmp/
-/tmp/
-
-# Used by dotenv library to load environment variables.
-# .env
-
-## Specific to RubyMotion:
-.dat*
-.repl_history
-build/
-*.bridgesupport
-build-iPhoneOS/
-build-iPhoneSimulator/
-
-## Specific to RubyMotion (use of CocoaPods):
-#
-# We recommend against adding the Pods directory to your .gitignore. However
-# you should judge for yourself, the pros and cons are mentioned at:
-# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
-#
-# vendor/Pods/
-
-## Documentation cache and generated files:
-/.yardoc/
-/_yardoc/
-/doc/
-/rdoc/
-
-## Environment normalization:
-/.bundle/
-/vendor/bundle
-/lib/bundler/man/
-
-# for a library or gem, you might want to ignore these files since the code is
-# intended to run in multiple environments; otherwise, check them in:
-# Gemfile.lock
-# .ruby-version
-# .ruby-gemset
-
-# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
-.rvmrc

data/.ruby-version

@@ -1 +0,0 @@
-2.4.5

data/.travis.yml

@@ -1,7 +0,0 @@
----
-sudo: false
-language: ruby
-cache: bundler
-rvm:
-  - 2.4.5
-before_install: gem install bundler -v 2.0.1

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at eldemcan@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -1,6 +0,0 @@
-source "https://rubygems.org"
-
-# Specify your gem's dependencies in pi_mote.gemspec
-gemspec
-
-gem 'rpi_gpio', '~> 0.3.3'

data/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2018 Can Eldem
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

data/LICENSE.txt

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2019 Can Eldem
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

data/README.md

@@ -1,53 +0,0 @@
-# Pi Mote ruby
-Energenie [Pi-mote](https://energenie4u.co.uk/catalogue/product/ENER002-2PI) ruby api for Raspberry Pi.
-
-## Installation
-
-Add this line to your application's Gemfile:
-
-```ruby
-gem 'pi_mote'
-```
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install pi_mote
-
-# Dependency
-
-You need to install [rpi gpio](https://github.com/ClockVapor/rpi_gpio) library.
-If you encounter problems related with permissions you can change ownership of `/dev/gpiomem` folder with `sudo chown root.gpio /dev/gpiomem
-sudo chmod g+rw /dev/gpiomem` chmod one will give write permissions.
-
-# Usage
-
-```ruby
-sc = PiMote.new
-sc.switch_on(socket_number)
-sc.switch_off(socket_number)
-
-sc.switch_on # all sockets on
-sc.switch_off # all sockets on
-```
-
-## Development
-
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
-
-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).
-
-## Contributing
-
-Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/pi_mote. 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.
-
-## License
-
-The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
-
-## Code of Conduct
-
-Everyone interacting in the PiMote project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/celdem/pi_mote/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -1,10 +0,0 @@
-require "bundler/gem_tasks"
-require "rake/testtask"
-
-Rake::TestTask.new(:test) do |t|
-  t.libs << "test"
-  t.libs << "lib"
-  t.test_files = FileList["test/**/*_test.rb"]
-end
-
-task :default => :test

data/bin/console

@@ -1,14 +0,0 @@
-#!/usr/bin/env ruby
-
-require "bundler/setup"
-require "pi_mote"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require "irb"
-IRB.start(__FILE__)

data/bin/setup

@@ -1,8 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-IFS=$'\n\t'
-set -vx
-
-bundle install
-
-# Do any other automated setup that you need to do here

data/pi_mote.gemspec

@@ -1,42 +0,0 @@
-
-lib = File.expand_path("../lib", __FILE__)
-$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-require "pi_mote/version"
-
-Gem::Specification.new do |spec|
-  spec.name          = "pi_mote"
-  spec.version       = PiMote::VERSION
-  spec.authors       = ["Can Eldem"]
-  spec.email         = ["eldemcan@gmail.com"]
-
-  spec.summary       = %q{Control your pi mote with ruby}
-  spec.description   = %q{Ruby library for pi mite raspberry pi}
-  spec.homepage      = "https://github.com/eldemcan/pi-mote-ruby"
-  spec.license       = "MIT"
-
-  # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
-  # to allow pushing to a single host or delete this section to allow pushing to any host.
-  # if spec.respond_to?(:metadata)
-  #   spec.metadata["allowed_push_host"] = "TODO: Set to 'http://mygemserver.com'"
-
-  #   spec.metadata["homepage_uri"] = spec.homepage
-  #   spec.metadata["source_code_uri"] = "TODO: Put your gem's public repo URL here."
-  #   spec.metadata["changelog_uri"] = "TODO: Put your gem's CHANGELOG.md URL here."
-  # else
-  #   raise "RubyGems 2.0 or newer is required to protect against " \
-  #     "public gem pushes."
-  # end
-
-  # Specify which files should be added to the gem when it is released.
-  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
-  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
-    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
-  end
-  spec.bindir        = "exe"
-  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
-  spec.require_paths = ["lib"]
-
-  spec.add_development_dependency "bundler", "~> 2.0"
-  spec.add_development_dependency "rake", "~> 10.0"
-  spec.add_development_dependency "minitest", "~> 5.0"
-end