Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. English
    3. Error/Bug
    4. Tapo / Tp-link

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Tapo / Tp-link

    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      Bvelkov last edited by

      My tapo L530 smart light bulbs stopped working after I updated their firmware. It was working perfectly fine with 1.1.9 but now on 1.3.0 I can't control any of the states. Any suggestions on how to fix it?

      Tried deleting the adapter and the instances and rebooting everything, nothing helped. Tested with an old light bulb that still has the 1.1.9 worked immediately.

      arteck 1 Reply Last reply Reply Quote 0
      • arteck
        arteck Developer Most Active @Bvelkov last edited by

        @bvelkov LOG from Adaper in debug mode maybee..

        B 1 Reply Last reply Reply Quote 0
        • B
          Bvelkov @arteck last edited by

          @arteck Here's the log from the adapter, hope it helps. iobroker.2023-10-02.log.html

          Marc Berg 1 Reply Last reply Reply Quote 0
          • Marc Berg
            Marc Berg Most Active @Bvelkov last edited by Marc Berg

            @bvelkov

            2023-10-02 11:47:40.013 - error: tapo.0 (8466) 111 Error: connect EHOSTUNREACH 192.168.0.167:80
            2023-10-02 11:47:40.015 - info: tapo.0 (8466) Initialized 8022499C86F638445F8EBA45627EB4851D8C46C5
            2023-10-02 11:47:40.015 - error: tapo.0 (8466) 52 - Get Device Info failed
            2023-10-02 11:47:40.355 - info: tapo.0 (8466) Init device 80234DDA2E0CB8AD97C9CF60AB502FD31E7EABC4 type L530 Series with ip 192.168.0.114
            2023-10-02 11:47:43.594 - error: tapo.0 (8466) 111 Error: connect EHOSTUNREACH 192.168.0.114:80
            

            Maybe the bulbs got new IP addresses after the update. Can you see the bulbs in the Wi-Fi router?

            B 1 Reply Last reply Reply Quote 0
            • B
              Bvelkov @Marc Berg last edited by

              @marc-berg not those two, but they rest that I expect to work are there, I tried deleting the cache file hoping it would get the new device list again, also tried deleting the instance and the adapter, but I think that didn't work. Do you know how I can force the cache delete on this instance?

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              Support us

              ioBroker
              Community Adapters
              Donate

              530
              Online

              31.8k
              Users

              80.0k
              Topics

              1.3m
              Posts

              3
              5
              494
              Loading More Posts
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes
              Reply
              • Reply as topic
              Log in to reply
              Community
              Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
              The ioBroker Community 2014-2023
              logo