TP-Link Plugin v 0.9.9 / v1.0

Plugins that users have built. NOTE: plugins that were developed for Indigo versions older than 2022.1 will have to be updated to work with Indigo 2022.1 (Python 3 - see this blog post for details). If the plugin listed here is not in the Plugin Store (which will show updated plugins) then you will need to ask on the appropriate thread below if it has been updated and where you get get the update.
vvrangler
Posts: 39
Joined: Mon Sep 01, 2014 11:50 am

Re: TP-Link Plugin v 0.9.9 / v1.0

Post by vvrangler »

I have a TP-Link KL135 dimmable color bulb and each time it communicates I get these errors in the log.

Code: Select all

TP-Link Devices                 Pantry Bulb found set to On, brightness 2
   Error                           device "Pantry Bulb" state key Hue not defined (ignoring update request)
   Error                           device "Pantry Bulb" state key Saturation not defined (ignoring update request)
   Error                           device "Pantry Bulb" state key colorTemp not defined (ignoring update request)
Anyone else seeing this or know how to resolve it?
User avatar
jtburgess
Posts: 78
Joined: Wed Jan 17, 2018 7:00 pm
Location: NJ

Re: TP-Link Plugin v 0.9.9 / v1.0

Post by jtburgess »

TP-Link Devices Pantry Bulb found set to On, brightness 2
Error device "Pantry Bulb" state key Hue not defined (ignoring update request)
Error device "Pantry Bulb" state key Saturation not defined (ignoring update request)
Error device "Pantry Bulb" state key colorTemp not defined (ignoring update request)
That’s odd, a color bulb without hue, saturation and color?
They must have changed to a different coding (RGB?)

I’m leaving for Texas tomorrow and won’t be able to look at it for a week.

While I’m gone, could you please collect some data for me.

Click on “Show Events Log Folder” in the top left of the log window, then open the com.*.TP-Link-Device folder, then double-click plug-in.log. This will open it with Console, which follows the end as it grows.
Look for a message with XML that starts {‘system’: {‘get_sysinfo’: etc.

If you don’t see that message, set the plug-in config to have log level set to THREADDEBUG (or it may say DeepDebug).
You’ll definitely see that message then. :)

Copy at least that entire message . You can copy a bigger chunk of the log, as long as it has that “sysinfo” message.

Send me an email with that copied log fragment, and then you can set the log level back to normal. I will be checking email.
Post Reply

Return to “User Plugins”