Skip to content
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

Homematic Support #2366

Closed
wants to merge 224 commits into from
Closed

Homematic Support #2366

wants to merge 224 commits into from

Conversation

danielperna84
Copy link
Contributor

@danielperna84 danielperna84 commented Jun 24, 2016

Description:
Adding bi-directional Homematic support. This includes lots of actors (switches, rollershutters etc.), thermostats and sensors (motion, brightness, shutter contacts etc.). I roughly estimate that we cover more than 60% (maybe even more) of all the currently available Homematic RF products, which are widely spread in Europe (primarily Germany, Austria and Switzerland).
Configuration of devices might be complex, but we'll cover that in the documentation (working on that). Basic setup is described within the component/platform files.
We also have an (experimental) autodetect feature, which discovers and configures every device we're capable of handling, although without friendly names. But for beginners this will quickly show which of their devices are supported and can be manually configured accordingly.

Thanks to @jazzaj for starting the Homematic implementation based on my pyhomematic module.
Thanks to @pvizeli for making radical improvements to my module and jazzajs implementation.
Thanks to @bimbar for support of MAX! Thermostats.

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

Example entry for configuration.yaml (if applicable):

homematic:
  local_ip: "<IP of device running Home Assistant>"
  local_port: <Port for connection with Home Assistant>
  remote_ip: "<IP of Homegear / CCU>"
  remote_port: <Port of Homegear / CCU XML-RPC Server>
  autodetect: "<True/False>" (optional, experimental, detect all devices)

Checklist:

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

If code communicates with devices:

  • Local tests with tox run successfully. Your PR cannot be merged unless tests pass
  • 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.

self._state)
self._data.update({self._state: STATE_UNKNOWN})

def _create_binary_list_from_hm(self):

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

farcy v1.1

  • D210: No whitespaces allowed surrounding docstring text
  • D400: First line should end with a period (not 'r')

@pvizeli
Copy link
Member

pvizeli commented Jun 24, 2016

https://github.com/danielperna84/home-assistant/pull/11 will fix all docstyle issue

danielperna84 and others added 3 commits June 24, 2016 09:28
fix docstring & remove unwanted code from autodetect
@pvizeli
Copy link
Member

pvizeli commented Jun 24, 2016

We have fix all errors from our new modul. All other fails are from HA core...

@pvizeli pvizeli mentioned this pull request Jun 24, 2016
6 tasks
@pvizeli pvizeli deleted the Homematic branch June 26, 2016 19:04
@home-assistant home-assistant locked and limited conversation to collaborators Mar 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants