Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. English
  3. Error/Bug
  4. Tapo / Tp-link

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.0k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.8k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.0k

Tapo / Tp-link

Tapo / Tp-link

Scheduled Pinned Locked Moved Error/Bug
5 Posts 3 Posters 750 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    Bvelkov
    wrote on last edited by
    #1

    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.

    arteckA 1 Reply Last reply
    0
    • B Bvelkov

      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.

      arteckA Offline
      arteckA Offline
      arteck
      Developer Most Active
      wrote on last edited by
      #2

      @bvelkov LOG from Adaper in debug mode maybee..

      zigbee hab ich, zwave auch, nuc's genauso und HA auch

      B 1 Reply Last reply
      0
      • arteckA arteck

        @bvelkov LOG from Adaper in debug mode maybee..

        B Offline
        B Offline
        Bvelkov
        wrote on last edited by
        #3

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

        Marc BergM 1 Reply Last reply
        0
        • B Bvelkov

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

          Marc BergM Offline
          Marc BergM Offline
          Marc Berg
          Most Active
          wrote on last edited by Marc Berg
          #4

          @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?

          NUC10I3+Ubuntu+Docker+ioBroker+influxDB2+Node Red+RabbitMQ+Grafana

          Pi-hole, Traefik, Checkmk, Conbee II+Zigbee2MQTT, ESPSomfy-RTS, LoRaWAN, Arduino, KiCad

          Benutzt das Voting im Beitrag, wenn er euch geholfen hat.

          B 1 Reply Last reply
          0
          • Marc BergM 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 Offline
            B Offline
            Bvelkov
            wrote on last edited by
            #5

            @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
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            Support us

            ioBroker
            Community Adapters
            Donate

            461

            Online

            32.4k

            Users

            81.3k

            Topics

            1.3m

            Posts
            Community
            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
            ioBroker Community 2014-2025
            logo
            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Recent
            • Tags
            • Unread 0
            • Categories
            • Unreplied
            • Popular
            • GitHub
            • Docu
            • Hilfe