Teemu R.

Add temperature_unit feature to t315

1

Forgot to cherry-pick from the KS240 branch, so let's try again. This could be a good candidate for homeassistant support's `select` platform.

Add script to generate homeassistant dhcp entries

2

``` python -m devtools.generate_ha_dhcp_entries --manifest-file "~/code/home-assistant/homeassistant/components/tplink/manifest.json" ... {'000000': set(), '003192': {'k[lps]*', 'e[sp]*'}, '005f67': {'k[lps]*'}, '1027f5': {'k[lps]*'}, '1c3bf3': {'KP303(UK)', 'lb*', 'k[lps]*', 'KL130(EU)', 'hs*'}, '1c61b4': {'k[lps]*', 'e[sp]*'}, '30de4b': {'p1*', 'P115(EU)'}, '3460f9': {'k[lps]*',...

* [ ] Add `unit` information to features * [ ] Convert existing information to features * [ ] Remove `EmeterStatus` for smartdevice * [ ] Figure out how to...

Extend cli to allow defining --child across all relevant commands

2

At the moment, only `feature` and `command` commands accept `--child`. Other relevant commands (on/off, brightness, color temperature, ..) should also accept defining which device is being controlled, perhaps the best...

With the move towards modularization (#757), we do not need to be so strict on which devicefamilies we accept for smartdevice, and we should let devicefactory construct any SMART device.

With a move towards modularized smartdevice (#757), we can get rid of separate files for different device types. We should probably keep the same interface in place for the time...

Draft PR to make it easy to see & comment on. Fixture thanks to @briadelour (#749).

Update documentation (`design.rst`) concerning the newly added device features.

Guard for empty responses from child devices

3

Saw the device responding with '{}' for an invalid control_child commands, unsure if it's worth to guard against that so leaving this as a draft for now.

This allows seeing the full http comms including headers with the protocols using httpclient. Marked as draft as the http session gets initialized by homeassistant (or by discovery) which is...