* Remove SPEED_MED from fan
* Add an Amazon Polly TTS platform
* Update boto library version for notify.aws_* platforms to match the tts.amazon_polly req
* Improve log line and add docstring to function
* Simplify config logic
* Remove duplicate logic
* Don't know how this got in here...
* initial options work
* Remove stale config option and only allow supported languages
* Make requested changes
* Polly is only supported in some regions
* Allow filename to contain underscores (for amazon_polly platform name), remove unnecessary default_lang, other small things
* Add options dict to service description
* Update keyboard_remote.py
I added a couple of events: keyboard_remote_connected and keyboard_remote_disconnected, useful to trigger some action (for example: play a sound)
I changed the way the component refers to the keyboard: not by "descriptor", but by name.
The fact is that the udev system doesn't always give a name link in /dev/input/by-id folder and the actual /dev/input/eventX file changes automatically.
For example, if I had my keyboard on /dev/input/event13 and then it disconnected, if something else connects to the system it will get the first input file available, that is /dev/input/event13. If the keyboard then reconnects, it will get /dev/input/event14, thus breaking the configuration.
Now it searches every time for the right input file.
The problem might be that, in case of ha upgrade, the pre-existing configuration won't work. I thing there are some guidelines here, but I am not sure.
I think it's inevitable: the initial idea to use a /dev/input/by-id/ symbolic link was good, but unfortunately it doesn't seem to work with bluetooth devices.
I haven't updated the documentation yet: I'm waiting for some ok about the change in configuration key names.
* Update keyboard_remote.py
That should do the trick.
You are right: device names can be duplicated, thus they're not reliable in case of multiple devices. Unfortunately, the only other information available is the physical address, even more complicated.
But in case you have just one keyboard remote of same model, the name works just fine. I'll put it in the documentation which, once the code is approved, I will promptly update.
* Update keyboard_remote.py
* Update keyboard_remote.py
* Update keyboard_remote.py
* Unwrap logger error
* ASUSWRT: Add IPv6 support when parsing neighbors
The regex for IPv6 should cover most cases, but it doesn't validate
whether IP is correct. It also might fail for some edge cases.
Also, ignore 'duid xx:xx:xx:xx:xx:xx:xx:xx:xx:xx' line in leases.
Closes#2814 - ASUSWRT doesn't support ipv6
* Update asuswrt.py
* Added new platform sky_hub
* added env to virtual environment gitingore
* Removed unuseful imports
* BT home hub 5 renamed to sky hub in the comments
* Added sky_hub to .coveragerc
* Added example configuration in sky_hub docstring
* sky_hub made compliant with test style standards
* homehub functions renamed to skyhub
* Update .gitignore
* Update .coveragerc
* Move isdevice validator under helpers.config_validation.
* Check that all persistence files are set and are unique if any is set
by user. This is necessary to avoid file name clashes.
* Check that a set persistence file has an existing and writable
directory.
* Check that a device is either a valid device file, "mqtt", or a valid
domain name or ip address.
* [image_processing/microsoft_face_verify] face recognition for automation
* Add platform for microsoft face identify
* add unittest for demo
* Add unittest for platform
* add a small sleep before reading the sensor
The read of the sensor might be incorrect if it's read too soon after the setup_input call. It might be isolated to my case where I rely on the the PI internal PULL, but once I added this sleep I never get false initial read. If you think this change is appropriate please merge it.
* Update rpi_gpio.py
* Update rpi_gpio.py
* Update rpi_gpio.py
* Add missing dependency in emulated_hue component.
On first startup after upgrade to 0.36, the emulated_hue componented failed to
start because the http component had installed the modules it depends on, in
this particular case 'aiohttp_cors' was missing.
* Include dependencies for the emulated_hue web server
Emulated_hue uses it's own 'web-server' component to handle hue related
discovery and config, so we need to make sure the required http modules are
made available before we are initialized.
We don't have to depend on the home-assistant http/api component because we do
not need to have the frontend to be initialized to handle emulated_hue, so we
can just import in the same set of requirements as the http component.
* Fix linting error
Adam Mills
John Arild Berentsen
Robbie Trencheny
Johann Kellerman
Daniel Høyer Iversen
fakezeta
John Mihalic
Pascal Vizeli
Hugo Dupras
Daniel Perna
Andrey
Janne Grunau
Gianluca Barbaro
Paulus Schoutsen
thecynic
Oleksii Serdiuk
Alessandro Mogavero
Stu Gott
Nick Touran
Martin Hjelmare
happyleavesaoc
snagytx
Jan Harkes
William Scanlon
Fabian Affolter
David McNett