Announcement

Collapse
No announcement yet.

TPLink plugin unable to control devices after running for about a day

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    TPLink plugin unable to control devices after running for about a day

    I have a number of TPLink devices being controlled by this plugin (HS300 and HS110 devices). When I restart Homeseer (or the plugin) things work fine for about a day, and then the plugin stops being able to control the devices. I enabled debug logging and am really not capturing anything meaningful. When trying to activate a device, logs do not report anything out of the ordinary and make it look like things are working (but are not).

    And there is a repeating error in the log about invalid IP addresses, but that refers only to a couple TPLink devices (but none of them are working, not just those with errors). Also, through the Kasa app I see that this IP address is valid so am not sure what is going on there. In any case, I have all of my devices assigned static IPs through my router so they are not changing. Not quite sure why I need to restart things every day or two to keep this plugin working. It was not always like this... started maybe a month ago. But nothing has changed with my system (that I can recall). Any help would be appreciated as this is pretty disabling. I am on HS4 (4.2.14.0) and TPLink Plugin 2021.3.23.0.

    I found in the ini file that a number of devices now have 0.0.0.0 listed as their IP address. I manually updated to the correct IP address for that device ID. Seems like a sign that there is something else going on though.

    Oh... I also get an error stating "old app version" when I try to use the plugin to connect through Kasa to discover devices.

    Thank you!



    Snippet of log below:



    8/19/2022 3:43:18 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - new IP = 192.168.86.40. The HS Device will be udpated

    8/19/2022 3:42:50 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - searching form MAC address CC32E5C2457BJV00. MAC search = True

    8/19/2022 3:42:50 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - Device ref: 2668 has an invalid IP: 192.168.86.40

    8/19/2022 3:38:17 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - new IP = 192.168.86.40. The HS Device will be udpated

    8/19/2022 3:37:50 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - searching form MAC address CC32E5C2457BJV00. MAC search = True

    8/19/2022 3:37:50 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - Device ref: 2668 has an invalid IP: 192.168.86.40

    8/19/2022 3:33:15 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - new IP = 192.168.86.40. The HS Device will be udpated

    8/19/2022 3:32:50 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - searching form MAC address CC32E5C2457BJV00. MAC search = True

    8/19/2022 3:32:50 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - Device ref: 2668 has an invalid IP: 192.168.86.40

    8/19/2022 3:28:18 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - new IP = 192.168.86.39. The HS Device will be udpated

    8/19/2022 3:27:50 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - searching form MAC address CC32E5C242D2JV00. MAC search = True

    8/19/2022 3:27:50 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - Device ref: 2656 has an invalid IP: 192.168.86.39

    8/19/2022 3:23:18 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - new IP = 192.168.86.39. The HS Device will be udpated

    8/19/2022 3:22:50 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - searching form MAC address CC32E5C242D2JV00. MAC search = True

    8/19/2022 3:22:50 PM
    HSPI_TPLinkSmartHome4
    Debug
    processBadIP() - Device ref: 2656 has an invalid IP: 192.168.86.39


    Tags: None
    #2
    Originally posted by Keoni View Post
    I have a number of TPLink devices being controlled by this plugin (HS300 and HS110 devices). When I restart Homeseer (or the plugin) things work fine for about a day, and then the plugin stops being able to control the devices. I enabled debug logging and am really not capturing anything meaningful. When trying to activate a device, logs do not report anything out of the ordinary and make it look like things are working (but are not).

    And there is a repeating error in the log about invalid IP addresses, but that refers only to a couple TPLink devices (but none of them are working, not just those with errors). Also, through the Kasa app I see that this IP address is valid so am not sure what is going on there. In any case, I have all of my devices assigned static IPs through my router so they are not changing. Not quite sure why I need to restart things every day or two to keep this plugin working. It was not always like this... started maybe a month ago. But nothing has changed with my system (that I can recall). Any help would be appreciated as this is pretty disabling. I am on HS4 (4.2.14.0) and TPLink Plugin 2021.3.23.0.

    I found in the ini file that a number of devices now have 0.0.0.0 listed as their IP address. I manually updated to the correct IP address for that device ID. Seems like a sign that there is something else going on though.

    Oh... I also get an error stating "old app version" when I try to use the plugin to connect through Kasa to discover devices.

    Thank you!



    I am familiar with the problem. I just haven't had time to tackle it. Can you tell me where you get the "old app version" message?

    James

    Running HS 3 on Win10 .

    Comment

    Previous template Next
    Working...
    X