<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">The dimmable switch mentioned below is actually an HS220, not an HS200.<div class=""><br class=""></div><div class="">—andy</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Begin forwarded message:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Andy Poggio <<a href="mailto:apoggio@pacbell.net" class="">apoggio@pacbell.net</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">Kasa/TPLink Issue List</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">February 20, 2023 at 9:15:50 AM PST<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">XTension <<a href="mailto:xtensionlist@machomeautomation.com" class="">xtensionlist@machomeautomation.com</a>><br class=""></span></div><br class=""><div class=""><div class="">As I’ve been working with 9.5.1, I’ve uncovered a number of issues with the Kasa/TPLink interface and sent out emails describing each issue. I thought I’d put everything I’ve found into one list with the hope that this will speed their resolution. To plagiarize James and paraphrase the Who: meet the new list, same as the old list:<br class=""><br class="">1. Undefined var:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/19/23 11:15:37 AM Entry Kasa light is not responding (name 'lightState' is not defined)<br class="">Just change 'lightState' to ‘light_state'<br class=""><br class="">2. Low brightness after mechanical turn on: I have a smart bulb in a fixture with a mechanical power switch. If I use XTension to turn off the bulb and then the mechanical switch to power cycle the bulb, turning it on, the bulb brightness is 1. This is set to 1 in line 910 of tplink.py. It should be set to the previous brightness setting, or taken from a property of the unit.<br class=""><br class="">3. HS200 dimmable switches: Can turn off but not turn on.<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/20/23 8:40:59 AM Sending ON for "Upstairs bath 1”<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/20/23 8:40:59 AM Upstairs bath 1 is not responding ('SmartDimmer' object has no attribute 'set_light_state’)<br class="">I’m guessing “set_light_state” shouldn’t be called for a dimmer switch; only turn_on, turn_off, and set_brightness should be called.<br class=""><br class="">4. Log entries when mechanically turned off: This is a Kasa/TPLink smart bulb which is screwed into a fixture with a mechanical switch. I get these log entries when the mechanical switch is off. <br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/19/23 9:03:39 AM Tony desk light: Error in _doPoll( Unable to connect to the device: 192.168.0.22)<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/19/23 9:04:37 AM Tony desk light: Error in _doPoll( Unable to connect to the device: 192.168.0.22)<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/19/23 9:05:20 AM Tony desk light: Error in _doPoll( Unable to connect to the device: 192.168.0.22)<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/19/23 9:06:18 AM Tony desk light: Error in _doPoll( Unable to connect to the device: 192.168.0.22)<br class="">This needs to be changed so that it is logged infrequently or only logged when the state changes.<br class=""><br class="">5. Log entries with differing numbers of discovered units: These fill up my log.<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/18/23 10:42:51 AM Kasa-TPLink: 12 Kasa/TP-Link devices were found.<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/18/23 10:42:57 AM Kasa-TPLink: 13 Kasa/TP-Link devices were found.<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/18/23 10:43:34 AM Kasa-TPLink: 10 Kasa/TP-Link devices were found.<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>2/18/23 10:43:39 AM Kasa-TPLink: 13 Kasa/TP-Link devices were found.<br class="">One fix would be to allow this logging to be shutoff.<br class=""><br class=""><br class="">Looking forward to the fixes!<br class=""><br class="">—andy<br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>