Thanks to visit codestin.com
Credit goes to github.com

Skip to content

X10 #14741

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 19 commits into from
Jun 21, 2018
Merged

X10 #14741

merged 19 commits into from
Jun 21, 2018

Conversation

teharris1
Copy link
Contributor

Description:

Adding X10 support

Related issue (if applicable): fixes #

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.io#5469

Example entry for configuration.yaml (if applicable):

insteon_plm:
  port: /dev/insteon
  device_override:
    address: 44899f
    cat: 0x00
    subcat: 0x1b
  x10_all_units_off: a
  x10_all_lights_off: b
  x10_all_lights_on: c
  x10_devices:
   - housecode: c
     unitcode: 12
     platform: switch
   - housecode: b
     unitcode: 9
     platform: light
     dim_steps: 64
   - housecode: b
     unitcode: 3
     platform: binary_sensor

Checklist:

  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • New dependencies have been added to the REQUIREMENTS variable (example).
  • New dependencies are only imported inside functions that use them (example).
  • New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
  • New files were added to .coveragerc.

If the code does not interact with devices:

  • Tests have been added to verify that the new code works.

@teharris1
Copy link
Contributor Author

Want to make sure this PR is not lost in the process.

@glyndon
Copy link

glyndon commented Jun 19, 2018

Having tested this personally on a live system I can say that it has been effective in adding the X10 function without impacting legacy Insteon function.

@teharris1
Copy link
Contributor Author

@balloob Sorry to bother you and I am trying to respect the process but this PR has been sitting for almost three weeks with no movement. I don't see any other PRs that have sat this long with no review at all.

@balloob
Copy link
Member

balloob commented Jun 21, 2018

Sorry for the delay, this PR looks great ! I'll tag it for the 0.72 release.

@balloob balloob merged commit be6d1b5 into home-assistant:dev Jun 21, 2018
@balloob balloob added this to the 0.72 milestone Jun 21, 2018
@teharris1
Copy link
Contributor Author

Thank you! This has been one of the biggest complaints from the Insteon community that OpenHAB has X10 support and HA did not so I think this is a very good improvement to help people who want to move from OpenHab.

balloob pushed a commit that referenced this pull request Jun 21, 2018
* Implement X10

* Add X10 after add_device_callback

* Ref device by id not hex and add x10OnOffSwitch name

* X10 services and add sensor device

* Correctly reference X10_HOUSECODE_SCHEMA

* Log adding of X10 devices

* Add X10 All Units Off, All Lights On and All Lights Off devices

* Correct ref to X10 states vs devices

* Add X10 All Units Off, All Lights On and All Lights Off devices

* Correct X10 config

* Debug x10 device additions

* Config x10 from bool to housecode char

* Pass PLM to X10 device create

* Remove PLM to call to add_x10_device

* Unconfuse x10 config and method names

* Correct spelling of x10_all_lights_off_housecode

* Bump insteonplm to 0.10.0 to support X10
@balloob balloob mentioned this pull request Jun 22, 2018
@teharris1 teharris1 deleted the x10 branch June 25, 2018 16:35
@home-assistant home-assistant locked and limited conversation to collaborators Dec 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants