Skip to content
  • Home
  • 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
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. UniFi Adapter WLAN schalten funktioniert nicht mehr

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    793

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    18
    1
    6.2k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.5k

UniFi Adapter WLAN schalten funktioniert nicht mehr

Scheduled Pinned Locked Moved Error/Bug
adapter problemunifiwlan
7 Posts 4 Posters 866 Views 4 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.
  • Elektroniker86E Offline
    Elektroniker86E Offline
    Elektroniker86
    wrote on last edited by Elektroniker86
    #1

    Moin,
    seit ein paar Tagen oder Wochen, ich weiß es leider nicht genau kann ich mein Gast WLAN nicht mehr schalten. Vorher hat es immer einwandfrei funktioniert. Könnt Ihr das bei euch ebenfalls feststellen? In den Logs finde ich keine Auffälligkeiten:

    unifi.0
    2022-06-25 15:04:50.836	debug	Update done
    
    unifi.0
    2022-06-25 15:04:50.811	debug	fetchHealth: 5
    
    unifi.0
    2022-06-25 15:04:50.797	debug	fetchNetworks: 7
    
    unifi.0
    2022-06-25 15:04:50.733	debug	fetchWlans: 3
    
    unifi.0
    2022-06-25 15:04:50.398	debug	fetchDevices: 9
    
    unifi.0
    2022-06-25 15:04:50.313	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
    
    unifi.0
    2022-06-25 15:04:50.305	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
    
    unifi.0
    2022-06-25 15:04:50.204	info	State value to set for "unifi.0.default.clients.00:04:20:f6:1a:b2.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:04:50.051	info	State value to set for "unifi.0.default.clients.ac:0b:fb:d6:f8:71.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:04:49.947	info	State value to set for "unifi.0.default.clients.48:d2:24:3a:60:a8.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:04:49.746	info	State value to set for "unifi.0.default.clients.b8:27:eb:64:eb:29.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:04:49.640	debug	fetchClients: 50
    
    unifi.0
    2022-06-25 15:04:49.610	debug	fetchSiteSysinfo: 1
    
    unifi.0
    2022-06-25 15:04:49.566	debug	fetchSites: default
    
    unifi.0
    2022-06-25 15:04:49.544	debug	Login successful
    
    unifi.0
    2022-06-25 15:04:49.376	debug	Update started
    
    unifi.0
    2022-06-25 15:04:27.987	debug	Login successful
    
    unifi.0
    2022-06-25 15:04:20.535	debug	Update done
    
    unifi.0
    2022-06-25 15:04:20.522	debug	fetchHealth: 5
    
    unifi.0
    2022-06-25 15:04:20.508	debug	fetchNetworks: 7
    
    unifi.0
    2022-06-25 15:04:20.445	debug	fetchWlans: 3
    
    unifi.0
    2022-06-25 15:04:20.247	debug	fetchDevices: 9
    
    unifi.0
    2022-06-25 15:04:20.181	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
    
    unifi.0
    2022-06-25 15:04:20.174	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
    
    unifi.0
    2022-06-25 15:04:20.104	info	State value to set for "unifi.0.default.clients.00:04:20:f6:1a:b2.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:04:19.967	info	State value to set for "unifi.0.default.clients.ac:0b:fb:d6:f8:71.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:04:19.872	info	State value to set for "unifi.0.default.clients.48:d2:24:3a:60:a8.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:04:19.711	info	State value to set for "unifi.0.default.clients.b8:27:eb:64:eb:29.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:04:19.665	debug	fetchClients: 50
    
    unifi.0
    2022-06-25 15:04:19.625	debug	fetchSiteSysinfo: 1
    
    unifi.0
    2022-06-25 15:04:19.603	debug	fetchSites: default
    
    unifi.0
    2022-06-25 15:04:19.554	debug	Login successful
    
    unifi.0
    2022-06-25 15:04:19.374	debug	Update started
    
    unifi.0
    2022-06-25 15:04:08.196	debug	Login successful
    
    unifi.0
    2022-06-25 15:03:50.875	debug	Update done
    
    unifi.0
    2022-06-25 15:03:50.849	debug	fetchHealth: 5
    
    unifi.0
    2022-06-25 15:03:50.830	debug	fetchNetworks: 7
    
    unifi.0
    2022-06-25 15:03:50.796	debug	fetchWlans: 3
    
    unifi.0
    2022-06-25 15:03:50.430	debug	fetchDevices: 9
    
    unifi.0
    2022-06-25 15:03:50.341	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
    
    unifi.0
    2022-06-25 15:03:50.334	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
    
    unifi.0
    2022-06-25 15:03:50.225	info	State value to set for "unifi.0.default.clients.00:04:20:f6:1a:b2.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:03:50.044	info	State value to set for "unifi.0.default.clients.ac:0b:fb:d6:f8:71.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:03:49.927	info	State value to set for "unifi.0.default.clients.48:d2:24:3a:60:a8.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:03:49.694	info	State value to set for "unifi.0.default.clients.b8:27:eb:64:eb:29.noted" has to be type "boolean" but received type "string"
    
    unifi.0
    2022-06-25 15:03:49.610	debug	fetchClients: 50
    
    unifi.0
    2022-06-25 15:03:49.589	debug	fetchSiteSysinfo: 1
    
    unifi.0
    2022-06-25 15:03:49.567	debug	fetchSites: default
    
    unifi.0
    2022-06-25 15:03:49.544	debug	Login successful
    
    unifi.0
    2022-06-25 15:03:49.373	debug	Update started
    
    unifi.0
    2022-06-25 15:03:42.780	debug	Login successful
    

    Unbenannt2.PNG Unbenannt1.PNG Unbenannt.PNG

    Vielleicht hat jemand eine Idee?
    Das hatte ich vergessen, Hardware ist die UDM-Pro.

    1 Reply Last reply
    0
    • Elektroniker86E Offline
      Elektroniker86E Offline
      Elektroniker86
      wrote on last edited by
      #2

      Habe mich heute nochmals drangesetzt und die beta (0.6.3) installiert aber es funktioniert immer noch nicht. Beim schalten vom Gast WLAN habe ich nun folgende Error logs!

      
      unifi.0
      2022-11-09 19:01:26.612	error	[updateWlanStatus site default] error: Request failed with status code 400, stack: AxiosError: Request failed with status code 400 at settle (/opt/iobroker/node_modules/node-unifi/node_modules/axios/lib/core/settle.js:19:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/node-unifi/node_modules/axios/lib/adapters/http.js:495:11) at IncomingMessage.emit (node:events:525:35) at IncomingMessage.emit (node:domain:489:12) at endReadableNT (node:internal/streams/readable:1358:12) at processTicksAndRejections (node:internal/process/task_queues:83:21)
      
      unifi.0
      2022-11-09 19:01:26.611	error	Error site default (data): {"meta":{"rc":"error","msg":"api.err.IdInvalid"},"data":[]}
      

      Vielleicht hat jetzt jemand ne Idee?

      System 9S 1 Reply Last reply
      0
      • Elektroniker86E Elektroniker86

        Habe mich heute nochmals drangesetzt und die beta (0.6.3) installiert aber es funktioniert immer noch nicht. Beim schalten vom Gast WLAN habe ich nun folgende Error logs!

        
        unifi.0
        2022-11-09 19:01:26.612	error	[updateWlanStatus site default] error: Request failed with status code 400, stack: AxiosError: Request failed with status code 400 at settle (/opt/iobroker/node_modules/node-unifi/node_modules/axios/lib/core/settle.js:19:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/node-unifi/node_modules/axios/lib/adapters/http.js:495:11) at IncomingMessage.emit (node:events:525:35) at IncomingMessage.emit (node:domain:489:12) at endReadableNT (node:internal/streams/readable:1358:12) at processTicksAndRejections (node:internal/process/task_queues:83:21)
        
        unifi.0
        2022-11-09 19:01:26.611	error	Error site default (data): {"meta":{"rc":"error","msg":"api.err.IdInvalid"},"data":[]}
        

        Vielleicht hat jetzt jemand ne Idee?

        System 9S Offline
        System 9S Offline
        System 9
        wrote on last edited by
        #3

        Hallo, gleiche Problem habe ich leider auch.

        1 Reply Last reply
        0
        • D Offline
          D Offline
          Danilo
          wrote on last edited by
          #4

          Hallo, ich habe auch das Problem, gibt es mittlerweile eine Lösung?

          1 Reply Last reply
          0
          • arteckA Offline
            arteckA Offline
            arteck
            Developer Most Active
            wrote on last edited by arteck
            #5

            @elektroniker86
            226ff8e8-9d94-4cba-8d26-d77d11f7a825-grafik.png

            zieh das mal gerade

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

            Elektroniker86E 1 Reply Last reply
            0
            • arteckA arteck

              @elektroniker86
              226ff8e8-9d94-4cba-8d26-d77d11f7a825-grafik.png

              zieh das mal gerade

              Elektroniker86E Offline
              Elektroniker86E Offline
              Elektroniker86
              wrote on last edited by Elektroniker86
              #6

              @arteck

              Das habe ich bereits gemacht vor längerem sogar aber da ändert sich nichts.
              Wenn ich den Wert unter dem zu schaltenden WLAN bei enabled auf false setze dann geht er wieder nach 1-2 Sekunden auf true. Das WLAN schaltet nicht.

              Unbenannt.JPG

              Folgende Logs:

              
              unifi.0
              2023-01-19 10:14:29.562	error	[updateWlanStatus site default] error: Request failed with status code 400, stack: AxiosError: Request failed with status code 400 at settle (/opt/iobroker/node_modules/node-unifi/node_modules/axios/lib/core/settle.js:19:12) at IncomingMessage.handleStreamEnd (/opt/iobroker/node_modules/node-unifi/node_modules/axios/lib/adapters/http.js:495:11) at IncomingMessage.emit (node:events:525:35) at IncomingMessage.emit (node:domain:489:12) at endReadableNT (node:internal/streams/readable:1358:12) at processTicksAndRejections (node:internal/process/task_queues:83:21)
              
              unifi.0
              2023-01-19 10:14:29.561	error	Error site default (data): {"meta":{"rc":"error","msg":"api.err.IdInvalid"},"data":[]}
              
              
              1 Reply Last reply
              0
              • Elektroniker86E Offline
                Elektroniker86E Offline
                Elektroniker86
                wrote on last edited by
                #7

                Zur Info, das WLAN lässt sich seit dem letzten Adapter Update wieder schalten...

                1 Reply Last reply
                0

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                Support us

                ioBroker
                Community Adapters
                Donate

                555

                Online

                32.8k

                Users

                82.7k

                Topics

                1.3m

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

                • Don't have an account? Register

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