forked from home-assistant/core
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Merge latest dev #2
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fix and clean lametric * Add missing DEPENDENCIES in notify platform. * Remove not needed method in component manager class. * Don't overwrite notify DOMAIN. * Return consistently depending on found devices in setup of component. * Get new token if token expired * Add debug log for getting new token * Clean up
* Support presence detection using Hitron Coda router * at least 2 spaces before inline comment * Update hitron_coda.py * rewrote authentication code, it actually works now * make line slightly shorter to comply with hound * Removed hardcoded IP address * Fix string formatting, add timeout, and use generator * Update hitron_coda.py * Update hitron_coda.py * Update hitron_coda.py * typo * update .coveragerc * Update stale URL
* Better int types support * type * Added optional register order * Fix white spaces * Fix line length * Fix line too long * Fix trailing whitespace * Stylistc code fixes
* pad packets to multiple of 4 characters This fixes sending commands, see #7669 * Update broadlink.py * removed whitespace
With the default timeout of 10 seconds, the log gets filled up with "component is taking more than 10 seconds" errors. This should probably be fixed in some other way, but for now this reduces the problem a bit.
* Fix sound for lametric notify * Remove not used method
* Implementation of `state_template` for the Universal media_player * add tracking to entities in state template * use normal config_validation * fix tests, use defaults in platform schema, remove extra keys * and test the new option `state_template` * lint fixes * no need to check attributes against None * use `async_added_to_hass` and call `async_track_state_change` from `hass.helpers`
* Added option to set installation giid * Changed where giid config var is being checked * Style fix * Fix style
* Add code to enable discovery for mqtt cover * Fix pylint error
…em-wide unit_system setting. (#10346)
Everything logged with "warning" or "error" is stored and exposed via the HTTP API, that can be used by the frontend.
* Unique identity Use unique ID for generating keys and store them in config. Fallback to old id so existing installs will still work. * Remove Timeouts they don't really work. this should be fixed in pytradfri I think. * import uuid only when necessary * more selective import * lint * use load_json and save_json from util.json * remove unnecessary imports * use async configurator functions * async configurator calls * thou shalt not mixup the (a)syncs * again: no asyncs in the syncs! last warning... * Update tradfri.py
* Update cloud * Fix tests * Lint
* Reduce update calls to API. Add signal strength monitor. * Fix lint errors * Fix indent * Update pyarlo version and review fixes * Fix lint errors * Remove staticmethod * Clean up attributes * Update arlo.py
The frontend will not have this panel.
* Fix ValueError exception structure = '>{:c}'.format(data_types[register.get(CONF_DATA_TYPE)][register.get(CONF_COUNT)]) give: ValueError: Unknown format code 'c' for object of type 'str' * Minor typo
* Fix Hikvision switch bug * Added comment about last working version
* Support script execution for Alexa * Use PowerController for the script component
* New sensor viaggiatreno. I've messed up the previous PR so here it is in a new one. Should include also all corrections from @pvizeli * fixes from PR 10522 * fixed import order * requested changes from MartinHjelmare
* Update modbus.py * Fix blank linea and whitespaces * Fix visual indent * Fix visual indent * fix multiple statements on one line * Typo * Disable pylint check # pylint: disable=super-init-not-called * Fix code style
* Device tracker for meraki AP * styles fix * fix again * again * and again :) * fix hide if away * docs and optimization * tests and fixes * styles * styles * styles * styles * styles fix. Hope last * clear track new * changes * fix accuracy error and requested changes * remove meraki from .coveragerc * tests and minor changes * remove location
In a case where either (a) an incorrect source name is used, or (b) the TV isn't currently queryable (e.g. it's off), we get tracebacks because we assume the source that we are being asked to select exists in self._source_list. This makes the lookup code a little more rugged, and adds in a warning message (in place of the current exception).
* Added Vera scenes * Fixed flake8 issues * Fixed comments * Moved vera to use hass.data * Made requested changes
* initial commit of shuffle option for sonos * added test * Small adjustments to adhere to review requests * Removed unnessesary setting of variable. Use shuffle state from soco instead
* Add Canary component * Made some change to how canary data is updated and stored * Updated to use py-canary:0.1.2 * Addressed flake8 warnings * Import canary API locally * Import canary API locally again * Addressed pylint errors * Updated requirements_all.txt * Fixed incorrect unit of measurement for air quality sensor * Added tests for Canary component and sensors * Updated canary component to handle exception better when initializing * Fixed tests * Fixed tests again * Addressed review comments * Fixed houndci error * Addressed comment about camera force update * Addressed comment regarding timeout when fetching camera image * Updated to use py-canary==0.2.2 * Increased update frequency to 30 seconds * Added support for Canary alarm control panel * Address review comments * Fixed houndci error * Fixed lint errors * Updated test to only test setup component / platform * Fixed flake error * Fixed failing test * Uptake py-canary:0.2.3 * canary.alarm_control_panel DISARM is now mapped to canary PRIVACY mode * Fixed failing tests * Removed unnecessary methods * Removed polling in canary camera component and update camera info when getting camera image * Added more tests to cover Canary sensors * Address review comments * Addressed review comment in tests * Fixed pylint errors * Excluded canary alarm_control_panel and camera from coverage calculation
* Support new LIFX products * Remove lint
* Updated snips to listen on new mqtt topic and use rawValue if value not present in slot * Too late at night * Trying to make minor changes via web * Update test_snips.py * Update __init__.py * Updated wrong branch cause I'm a monkey
All mochad devices are sharing a single socket interface. When multiple threads are issuing requests to the mochad daemon at the same time the write read cycle might get crossed between the threads. This is normally not an issue for 1-way X10 devices because as long as the request issued successfully and data is read over the socket then we know as much as mochad will tell us (since there is no ACK from the request for most X10 devices). However, where it does matter is on the device __init__() because we're relying on the mochad daemon's internal state to take an educated guess at the device's state to intialize things with. When there are multiple devices being initialized at the same time the wires can get crossed between and the wrong device state may be read. To address this potential issue this commit adds locking using a semaphore around all pairs of send_cmd() and read_data() (which is what pymochad.device.Device.get_status() does internally) calls to the mochad controller to ensure we're only ever dealing with a single request at a time. Fixes mtreinish/pymochad#4
* Added force_update for REST sensor * Linting error
* Add support for Logitech UE Smart Radios. * Removed full stops to please Hound's line limit. * Updated with requested changes. * Fix Pylint Flake8 problem. * Updated with requested changes.
…ggers (i.e. PyCharm) (#11034)
* Added support for cover in tellstick * Fixed comments from PR * Fixed comments from PR * Address comments
* Add caldav component * Code review - 1 * Code review - 2 * Sort imports
* Introduce a new Hue component that knows how to talk to a Hue bridge, but doesn't actually set up lights. * Refactor the hue lights platform to use the HueBridge class from the hue component. * Reimplement support for multiple bridges * Auto discover bridges. * Provide some migration support by showing a persistent notification. * Address most feedback from code review. * Call load_platform from inside HueBridge.setup passing the bridge id. Not only this looks nicer, but it also nicely solves additional bridges being added after initial setup (e.g. pairing a second bridge should work now, I believe it required a restart before). * Add a unit test for hue_activate_scene * Address feedback from code review. * After feedback from @andrey-git I was able to find a way to not import phue in tests, yay! * Inject a mock phue in a couple of places
* add custom bypass status to total connect * remove logger line
…uel consumption property (#11051)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.