* Fixed attributes that are lists cuasing invalid influx syntax
* Added bool and fixed mixed data type issue
* Fixed changing nearly all data types to float causing some worse influxdb errors. whoops
* Added line to end of file
* Extending efergy component for get the amount of energy consumed
* Changing units from kW to kWh
* Chaning units for Instant Consumption from kWh to kW
* Adding timeout for get and removing pylint config
* Update efergy.py
* Add MAC vendor lookup for device_tracker.
* Test vendor mac lookup and fix device attribute.
* Generate requirements.
* Style.
* Use hyphen instead of underscore to satisfy 'idna'.
https://github.com/kjd/idna/issues/17
* Resort imports.
* Refactor macvendor to use macvendors.com API instead of netaddr library.
* Test vendor lookup using macvendors.com api.
* Remove debugging.
* Correct description.
* No longer needed.
* Device tracker is now an async component. Fix ddwrt tests.
* Fix linting.
* Add test case for error conditions.
* There is no reason to retry failes vendor loopups as they won't be saved to the file anyways at that point.
* Sorry, bad assumption, this only made things worse.
* Wait for async parts during setup component to complete before asserting results.
* Fix linting.
* Is generated when running 'coverage html'.
* Undo isort.
* Make aioclient_mock exception more generic.
* Only lookup mac vendor string with adding new device to known_devices.yaml.
* Undo isort.
* Revert unneeded change.
* Adjust to use new websession pattern.
* Always make sure to cleanup response.
* Use correct function to release response.
* Fix tests.
* Initial Harmony device support, working current activity sensor and switch for each activity
TODO: add new device per hub to send device specific activity
Changes to be committed:
new file: homeassistant/components/harmony.py
new file: homeassistant/components/sensor/harmony.py
new file: homeassistant/components/switch/harmony.py
* ready for beta, I think
Changes to be committed:
modified: homeassistant/components/harmony.py
modified: homeassistant/components/sensor/harmony.py
modified: homeassistant/components/switch/harmony.py
* Changes to be committed:
modified: homeassistant/components/harmony.py
new file: homeassistant/components/remote/__init__.py
new file: homeassistant/components/remote/harmony.py
new file: homeassistant/components/remote/services.yaml
modified: homeassistant/components/sensor/harmony.py
modified: homeassistant/components/switch/harmony.py
Implemented remote component and harmony platform
* streamlined harmony support
* typo
* Initial Harmony device support, working current activity sensor and switch for each activity
TODO: add new device per hub to send device specific activity
Changes to be committed:
new file: homeassistant/components/harmony.py
new file: homeassistant/components/sensor/harmony.py
new file: homeassistant/components/switch/harmony.py
* ready for beta, I think
Changes to be committed:
modified: homeassistant/components/harmony.py
modified: homeassistant/components/sensor/harmony.py
modified: homeassistant/components/switch/harmony.py
* Changes to be committed:
modified: homeassistant/components/harmony.py
new file: homeassistant/components/remote/__init__.py
new file: homeassistant/components/remote/harmony.py
new file: homeassistant/components/remote/services.yaml
modified: homeassistant/components/sensor/harmony.py
modified: homeassistant/components/switch/harmony.py
Implemented remote component and harmony platform
* streamlined harmony support
* typo
* reworked token generation
* delete
* Initial Harmony device support, working current activity sensor and switch for each activity
TODO: add new device per hub to send device specific activity
Changes to be committed:
new file: homeassistant/components/harmony.py
new file: homeassistant/components/sensor/harmony.py
new file: homeassistant/components/switch/harmony.py
* Initial Harmony device support, working current activity sensor and switch for each activity
TODO: add new device per hub to send device specific activity
Changes to be committed:
new file: homeassistant/components/harmony.py
new file: homeassistant/components/sensor/harmony.py
new file: homeassistant/components/switch/harmony.py
* ready for beta, I think
Changes to be committed:
modified: homeassistant/components/harmony.py
modified: homeassistant/components/sensor/harmony.py
modified: homeassistant/components/switch/harmony.py
* ready for beta, I think
Changes to be committed:
modified: homeassistant/components/harmony.py
modified: homeassistant/components/sensor/harmony.py
modified: homeassistant/components/switch/harmony.py
* Changes to be committed:
modified: homeassistant/components/harmony.py
new file: homeassistant/components/remote/__init__.py
new file: homeassistant/components/remote/harmony.py
new file: homeassistant/components/remote/services.yaml
modified: homeassistant/components/sensor/harmony.py
modified: homeassistant/components/switch/harmony.py
Implemented remote component and harmony platform
* streamlined harmony support
* typo
* reworked token generation
* delete
* readded after rebase
* cleaning up style errors
* modified .coveragerc
* moved import statements
* added more debug logging
* Added URL encoding of token received from Logitech
* Corrected import for python 3
* new pyharmony version
* new pyharmony version
* remote tests
* only write config file if not present or sync service is called
* more tests
* more tests
* bumped pyharmony version to work with new auth
* bumped pyharmony version to work with new auth
* style corrections
* harmony local auth and remote demo platform
* style fix
* PR refinements and permission issues
* forgot a blank line
* removed sync test from test_init
* removed sync test from test_init
* visual indent
* send_command test in demo platform
If the mpd client ran into an socket timeout, the socket will raise an
OSError on every further request. This adds OSError to the list of
excptions, that causes a client reconnect.
This fixes#4650
Signed-off-by: Jan Losinski <losinski@wh2.tu-dresden.de>
In media_content_id() the "id" of the current song was returned. as
stated in bug #4652 the id is only the Tracklist-Id in the current
tracklist and is omitted if the track is not part of a tracklist (what
caused the bug in the first place).
To match the semantics described in the dockstring, to return a "Content
ID", this chooses the filename of the current song as id and returns
it.
It also uses get() instead of [] to prevent KeyError.
This fixes bug #4652
Signed-off-by: Jan Losinski <losinski@wh2.tu-dresden.de>
* Add channel switching for philips tvs.
* Disable track buttons when not watching tv.
* Undo isort config.
* Yes it does.
* Just testing some assumption on hound's flake8 behaviour.
* Revert "Just testing some assumption on hound's flake8 behaviour."
This reverts commit ff9940b39e.
* poke
* Introduced support to Amcrest IP Cameras
* Fixed lint issues
* Fixed requirements test
* * Implemented test to verify crendentials during camera setup
* Added persistent_notification in case of error when during Amcrest setup
* Homematic update with HomematicIP/HomematicWired support and multible connections
* fix bug in virtualkey service
* create new service & cleanups
* fix lint
* Pump pyhomematic 0.1.18
* Default dimmable brightness to 255 from 100
Full brightness for ISY dimmers is 255. The current 100 value turns dimmer switches on to just under half brightness. Probably just an oversight from the Sept implementation.
* Brightness change for turn_on, ramp for turn_off.
Per discussion with Teagan42 and jbcodemonkey, the brightness should rightfully be None and not an explicit value. There is a continuing issue that the ISY modules don't respect HA's brightness customization values. A new issue will be opened for this.
Additionally, turn_off was using ISY's fastoff() which didn't respect the ramping time. The default behavior should just be off().