* Add ffmpeg version
* Add ffmpeg stream content type
* Change ffmpeg camera stream content type
* Change ffmpeg stream content type
* Lint
* Add a none guard
* Fix
* Fix
* Update onvif.py
* Fix version match regrex
* Fix regrex
* Upgrade ha-ffmpeg to 1.11
* Lint
* Get ffmpeg version in ffmpeg component setup
* Move sensor.speedtest to the new speedtestdotnet component.
* Split out speedtest.net into a component and sensor platform
* Remove the throttle and add async_track_time_interval
* Add should_poll and cleanup
* Update requirements_all.txt
* Move time interval tracking out of the data class and into the setup method
* Add now=None argument to update
* Change foscam python library to pyfoscam, which is more up to date and has several critical bug fixes.
* Update requirements_all.txt to match.
* Inserting automatically generated requirements.txt
* Revert changes until pyfoscam captures recent bug fixes. The pyfoscam version pulled by pip is currently broken.
* Updated requirements_all.txt based on changing pyfoscam back to libpyfoscam.
The 'Loading [wireless] devices from Mikrotik ([ip address])' message
is incredibly spammy at the info log level, such that in the last 24
hours on my installation, that log message has appeared 6732 times,
versus 70 for every other log message. I've moved this message to the
debug log level as I don't believe it adds anything at the info level,
and makes it harder to diagnose other problems.
* start test setup
test cleanup
test deps
update switch test
actually update test deps
cleanup and remove switch from coveragerc
comment
refactor to use fixtures and shared components
lint
* remove availability part that isn't in zha yet
* review comments and cleanup
* review comments
* add switch back unil post reorg merge
* Add SmartThings Light platform and tests
* Cleaned a few awk comments
* Updates per review feedback
* Switched to super
* Changes per review feedback
* Split out fastdotcom into a component and a sensor platform
* Update .coveragerc
* Switching to async and using a Throttle
* Add the async_track_time_interval call
* Remove the throttle
* Reorder sensor methods and add should_poll property
* Fix issue #16606
Some projectors do not respond to pjlink requests during a short period after the status changes or when its in standby, resulting in pypjlink2 throwing an error. This fix catches these errors. Furthermore, only the status 'on' and 'warm-up' is interpreted as switched on, because 'cooling' is actually a switched off status.
* Update pjlink.py
Improved error handling
* Update pjlink.py
Improved error handling
* Update pjlink.py
Clean up
Daniel Høyer Iversen
Andrew Sayre
Steven Looman
Erik Hendrix
jonudewux
Pascal Vizeli
Jason Hu
emontnemery
Eliseo Martelli
David F. Mulcahey
Paulus Schoutsen
Rohan Kapoor
Paulus Schoutsen
Aaron Bach
David Lie
Jeff Irion
Dane
Peter Nijssen
Diogo Gomes
Till
Fabian Affolter
Ville Skyttä
Oliver Völker
Akın Ömeroğlu
emkay82