Announcement

Collapse
No announcement yet.

TPLink Smarthome Plugin

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    Strips only use one IP address and the strip itself handles which plug to fire (on/off). Did you try uninstalling the strip then reinstalling? This could fix your problem.

    Comment


      #32
      Hi James,

      there is a needs fixing true.

      here it is:
      Device Details
      device_version : |19.3.23|19.4.4
      error_count : 0
      tplink_alias : Strip Plug 1
      tplink_ip : 10.241.7.29
      tplink_poll_priority : 3
      tplink_power_change : false
      pollPriority : 3
      DevRef : 483
      MacAddress : D807B62095ED
      needsFixing : True
      Alias : Strip Plug 1
      HSAddress : D807B62095EDJV00
      Hostname : 10.241.7.29
      DeviceType : 0
      OutletNum : 00
      Model : unknown

      Polling frequency: 20 sec1 min2 min

      Get TPLink Detailsoutlets : System.Collections.Generic.List`1[HSPI_TPLinkSmartHome.Devices.TPLinkSmartPlug+child_outlet]
      monthStat : GetPropValue(monthStat) not valid/found
      dayStat : GetPropValue(dayStat) not valid/found
      current : -1
      voltage : -1
      power : -1
      total : -1
      PoweredOn : True
      LedOn : False
      PoweredOnSince : 11/15/2020 8:34:55 PM
      Features : TIM
      NumberOfChildOutlets : 3
      CurrentOutlet : 00
      OnlineStatusChanged : False
      isOnline : True
      IsOn : True
      Hostname : 10.241.7.29
      Port : 9999
      MessageCache : HSPI_TPLinkSmartHome.Messaging.TimeGatedMessageCache
      SoftwareVersion : 1.0.4 Build 200828 Rel.165029
      HardwareVersion : 1.0
      Type : IOT.SMARTPLUGSWITCH
      Model : KP303(UK)
      MacAddress : D8:07:B6:20:95:ED
      DevName : GetPropValue(DevName) not valid/found
      HardwareId : 8A263122E4686102C1C8C805202C33CD
      FirmwareId : n/a
      DeviceId : 800698D27D86BBBBDB49B3FA744A9A791D1920F4
      OemId : 707DC0D8FE3A745AAC776E000DC1CF15
      RSSI : -58
      LocationLatLong :
      Alias : Strip Plug 1
      CurrentTime : 11/15/2020 9:23:10 PM
      Failure to Connect Count : 0

      Comment


        #33
        I’ll try a reinstall and see what happens

        Comment


          #34
          Hi, the reinstall worked! Thanks.
          However I have noticed another anomaly.
          if the device name is changed in kasha (iOS management app) the device will pick up on the new name. However the status page will not.
          deleting and re adding works. It looks like the device name in the status page is set on add and then not updated if it changes.

          cheers!

          Comment


            #35
            [QUOTE=
            However I have noticed another anomaly.
            if the device name is changed in kasha (iOS management app) the device will pick up on the new name. However the status page will not.
            deleting and re adding works. It looks like the device name in the status page is set on add and then not updated if it changes.

            cheers![/QUOTE]

            That's because the plugin is using the MAC address of the Kasa device and not the name behind the scene. If you delete and re-add it will give it the new name as when you deleted it now the plugin doesn't know the MAC address anymore and will accept the changed (new) name

            Comment


              #36
              Thanks! Already done.

              Comment


                #37
                (Reposting here as I didn't get any response in separate thread. Appreciate any inputs)

                HS3 plugin not finding devices after a power outage recovery

                I recently installed this plugin to control a couple Kasa plugs via events. I had a momentary power outage today and when the homeseer started up this plugiin it said 'No devices found' in the log (presumably because the router itself is starting up at the same time). However I would have expected the plugin to poll and re-discover the devices. It didn't. So the automatic events that ran never actually accomplished their tasks via this plugin (to turn off the plugs). Has anyone else experienced this. I had to manually restart this plugin before it was able to discover the devices to control. Let me know if there is a way around it as the events are controlling some aquarium lighting/CO2 in my case and I can't let them run past the allotted time esp. when I am away. thanks



                Date/time=12/27/2020 10:41:45 AM CST
                Version=HS4 Pro Edition 4.1.8.0 (Linux)
                MONO Version=Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:14:25 UTC 2019)

                License=Registered
                Confguration File=/usr/local/HomeSeer/Data/HomeSeerData.json
                Uptime=58 Days 1 Hour 59 Minutes 23 Seconds
                Lan IP=127.0.0.1 (HomeTrollerSELv5)
                Device Count=214
                Event Count=14
                Plugins Enabled=NetCAM:,weatherXML:,Rachio:,SmartThings:,BLLAN:,Z-Wave:,TPLinkSmartHome:
                Modules/Threads=101 Modules, 58 Threads
                Available Threads=199
                HomeSeer Memory Used=125 Mbytes
                Plugins Installed=BLLAN 2.0.45.0,NetCAM 3.0.0.14,Rachio 4.0.1.0,SmartThings 4.0.15.0,TPLinkSmartHome 19.10.7.1,weatherXML 3.0.1.19,Z-Wave 3.0.2.0

                Comment


                  #38
                  I've had power outages (I have a cabin in the local mountains where power is not always consistent) and the plugin did re-established connection to the tplink devices. I do think the plugin might not be able to reconnect if the IP addresses changed. I am focused on my last beta of the HS4 version of the plugin and I will test the power outage scenario. Oh yeah! It does take 10ish minutes for the HS3 plugin to recover so there is that window where events will not run.
                  James

                  Running HS 3 on Win10 .

                  Comment


                    #39
                    Thanks James. Just rebooting the router causes this issue for me. It did not re-establish connection for over 8 hours and I had to rediscover. I will test with static IPs for the plugs and report back. They are currently on DHCP.

                    Also, can I test your HS4 plugin on my Hometroller SEL or is it only available in Windows.

                    Comment


                      #40
                      Yes, I was going to ask, are they static?

                      Remember static address should be outside the range of your DHCP or, if in it, use a DHCP reservation.

                      Sent from my SM-N975U1 using Tapatalk

                      Comment


                        #41
                        Originally posted by vrajkuma View Post
                        Thanks James. Just rebooting the router causes this issue for me. It did not re-establish connection for over 8 hours and I had to rediscover. I will test with static IPs for the plugs and report back. They are currently on DHCP.

                        Also, can I test your HS4 plugin on my Hometroller SEL or is it only available in Windows.
                        I expect and will want that the HS4 version of the plugin will work on Linux. I have not tested it but will in the next day or two. Feel free to download the beta on the HS4 version and I would appreciate anything you find.
                        James

                        Running HS 3 on Win10 .

                        Comment


                          #42
                          Just rebooting the router causes this issue for me.
                          I know that technically I can automatically rediscover the devices' new IP addresses based on their MACs. I will add that to my "kaizen" list.
                          James

                          Running HS 3 on Win10 .

                          Comment

                          Working...
                          X