Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. ioBroker.upnp - please test

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    ioBroker.upnp - please test

    This topic has been deleted. Only users with topic management privileges can see it.
    • sigi234
      sigi234 Forum Testing Most Active @Jey Cee last edited by sigi234

      @Jey-Cee
      NEIN, kann Ihn denn nicht jemand übernehmen?☹
      Ach sehe gerade bluefox hat es ja schon getan.........

      Jey Cee 1 Reply Last reply Reply Quote 0
      • Jey Cee
        Jey Cee Developer @sigi234 last edited by

        @sigi234 das übernehmen ist nicht das Problem, die Basis ist einfach mies.

        sigi234 1 Reply Last reply Reply Quote 0
        • sigi234
          sigi234 Forum Testing Most Active @Jey Cee last edited by

          @Jey-Cee sagte in ioBroker.upnp - please test:

          das übernehmen ist nicht das Problem, die Basis ist einfach mies.

          Ist einer meiner Lieblingsadapter..........

          Jey Cee 1 Reply Last reply Reply Quote 0
          • Jey Cee
            Jey Cee Developer @sigi234 last edited by

            @sigi234 sagte in ioBroker.upnp - please test:

            Ist einer meiner Lieblingsadapter..........

            Was machst du alles damit?

            sigi234 1 Reply Last reply Reply Quote 0
            • sigi234
              sigi234 Forum Testing Most Active @Jey Cee last edited by

              @Jey-Cee sagte in ioBroker.upnp - please test:

              @sigi234 sagte in ioBroker.upnp - please test:

              Ist einer meiner Lieblingsadapter..........

              Was machst du alles damit?

              IT Status :

              Screenshot (3336).png

              Jey Cee 1 Reply Last reply Reply Quote 1
              • Jey Cee
                Jey Cee Developer @sigi234 last edited by

                @sigi234 das ist doch aber nur info von der Fritz Box oder?

                sigi234 1 Reply Last reply Reply Quote 0
                • sigi234
                  sigi234 Forum Testing Most Active @Jey Cee last edited by

                  @Jey-Cee sagte in ioBroker.upnp - please test:

                  @sigi234 das ist doch aber nur info von der Fritz Box oder?

                  Nein, Daten kommen vom Adapter

                  1 Reply Last reply Reply Quote 0
                  • crunchip
                    crunchip Forum Testing Most Active last edited by

                    vllt kann mir hier jemand helfen, hatte schon einen Thread eröffnet aber bisher keine Hilfe.

                    2019-07-07 00:49:31.614 - error: upnp.0 uncaught exception: Cannot read property 'match' of undefined
2019-07-07 00:49:31.615 - error: upnp.0 TypeError: Cannot read property 'match' of undefined
at setNewState (/opt/iobroker/node_modules/iobroker.upnp/main.js:1390:28)
at Socket.adapter.getState (/opt/iobroker/node_modules/iobroker.upnp/main.js:1361:17)
at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)
at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
at WS. (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
2019-07-07 00:49:32.647 - error: Caught by controller[0]: TypeError: Cannot read property 'match' of undefined
2019-07-07 00:49:32.647 - error: Caught by controller[0]: at setNewState (/opt/iobroker/node_modules/iobroker.upnp/main.js:1390:28)
2019-07-07 00:49:32.647 - error: Caught by controller[0]: at Socket.adapter.getState (/opt/iobroker/node_modules/iobroker.upnp/main.js:1361:17)
2019-07-07 00:49:32.647 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
2019-07-07 00:49:32.647 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)
2019-07-07 00:49:32.647 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at WS. (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
2019-07-07 00:49:32.648 - error: Caught by controller[0]: at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
2019-07-07 00:49:32.648 - error: host.IoBroker instance system.adapter.upnp.0 terminated with code 6 (uncaught exception)
2019-07-07 00:49:32.648 - info: host.IoBroker Restart adapter system.adapter.upnp.0 because enabled
                    Bluefox 1 Reply Last reply Reply Quote 0
                    • Bluefox
                      Bluefox @crunchip last edited by

                      @crunchip Version upnp?

                      sigi234 crunchip 2 Replies Last reply Reply Quote 0
                      • sigi234
                        sigi234 Forum Testing Most Active @Bluefox last edited by sigi234

                        @Bluefox

                        version 1.0.12 laut Thread

                        1 Reply Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @Bluefox last edited by

                          @Bluefox ja wie @sigi234 schon geschrieben

                          Jey Cee 1 Reply Last reply Reply Quote 0
                          • Jey Cee
                            Jey Cee Developer @crunchip last edited by

                            @crunchip kannst du mal den Adapter löschen und von Github neu installieren? Der Fehler sollte jetzt abgefangen werden und im Log wird ausgegeben bei welchem Objekt das Passiert.

                            crunchip 3 Replies Last reply Reply Quote 0
                            • crunchip
                              crunchip Forum Testing Most Active @Jey Cee last edited by

                              @Jey-Cee ok, werd ich laufe des Tages mal machen und berichten

                              1 Reply Last reply Reply Quote 0
                              • crunchip
                                crunchip Forum Testing Most Active @Jey Cee last edited by

                                @Jey-Cee hab nun istalliert von git
                                was mir noch eingefallen ist, früher wurden die sky receiver mit gelistet, die aber seit der umstellung auf community nicht mehr im Verzeichnisbaum erscheinen
                                nur im log zu sehen unendlich fortlaufend

                                
upnp.0	2019-07-09 16:36:39.575	info	Found new device: http://192.168.xxx.xx:49153/description17.xml
upnp.0	2019-07-09 16:36:37.771	info	Found new device: http://192.168.xxx.xx:49153/description8.xml
                                Jey Cee 1 Reply Last reply Reply Quote 0
                                • Jey Cee
                                  Jey Cee Developer @crunchip last edited by

                                  @crunchip die Meldung hat nix mit dem Fehler zu tun. Wohin gehören den die IP Adressen? Er scheint die Geräte zu finden kann sie aber nicht anlegen und deshalb kommt die Meldung immer wieder.

                                  Du kannst auch die XML datei im Browser aufrufen, da steht drin zu welchem Gerät/Dienst sie gehört, das hilft vielleicht auch weiter.

                                  crunchip 1 Reply Last reply Reply Quote 0
                                  • crunchip
                                    crunchip Forum Testing Most Active @Jey Cee last edited by crunchip

                                    @Jey-Cee das sind meine beiden sky -receiver.
                                    wie gesagt, mit dem alten upnp Adapter wurden diese beiden angelegt, seit der Umstellung des Adapters wird nichts mehr angelegt
                                    aufrufen kann ich da nichts
                                    7798db0d-a492-426d-98d0-3dfc38e256f7-image.png

                                    Jey Cee 1 Reply Last reply Reply Quote 0
                                    • Jey Cee
                                      Jey Cee Developer @crunchip last edited by

                                      @crunchip und da haben wir das problem, warum die nicht erkannt werden. Der Zugriff auf die XML ist notwendig um die Geräte an zu legen.

                                      1 Reply Last reply Reply Quote 0
                                      • crunchip
                                        crunchip Forum Testing Most Active @Jey Cee last edited by

                                        @Jey-Cee so sehen nun meine Fehler aus
                                        einzigste ist, das nun nicht mehr jeden Tag, die Fehlermeldungen kommen

                                        2019-07-15 07:54:51.629 - error: upnp.0 uncaught exception: Cannot read property 'LastChange' of undefined
2019-07-15 07:54:51.630 - error: upnp.0 TypeError: Cannot read property 'LastChange' of undefined
at setNewState (/opt/iobroker/node_modules/iobroker.upnp/main.js:1384:70)
at Socket.adapter.getState (/opt/iobroker/node_modules/iobroker.upnp/main.js:1361:17)
at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)
at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
at WS. (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
2019-07-15 07:54:52.664 - error: Caught by controller[0]: TypeError: Cannot read property 'LastChange' of undefined
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at setNewState (/opt/iobroker/node_modules/iobroker.upnp/main.js:1384:70)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Socket.adapter.getState (/opt/iobroker/node_modules/iobroker.upnp/main.js:1361:17)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
2019-07-15 07:54:52.665 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2019-07-15 07:54:52.666 - error: Caught by controller[0]: at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
2019-07-15 07:54:52.666 - error: Caught by controller[0]: at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
2019-07-15 07:54:52.666 - error: Caught by controller[0]: at WS. (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
2019-07-15 07:54:52.666 - error: Caught by controller[0]: at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
2019-07-15 07:54:52.666 - error: host.IoBroker instance system.adapter.upnp.0 terminated with code 6 (uncaught exception)
2019-07-15 07:54:52.666 - info: host.IoBroker Restart adapter system.adapter.upnp.0 because enabled
2019-07-15 07:55:22.691 - info: host.IoBroker instance system.adapter.upnp.0 started with pid 30593
2019-07-15 07:55:24.266 - info: upnp.0 starting. Version 1.0.13 in /opt/iobroker/node_modules/iobroker.upnp, node: v10.16.0
2019-07-15 07:55:24.300 - info: upnp.0 Auto discover: false
                                        Bluefox 1 Reply Last reply Reply Quote 0
                                        • A
                                          Andre R. last edited by

                                          kann ich die Geräte die ich nicht brauche unter Objekte eigentlich löschen?

                                          sigi234 1 Reply Last reply Reply Quote 0
                                          • SBorg
                                            SBorg Forum Testing Most Active last edited by

                                            Ich sag mal Jein. Löschen an sich stellt kein Problem dar, nur wenn das entsprechende Gerät selbst UPnP macht, werden sie erneut angelegt 😉

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            411
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            adapter test
                                            18
                                            196
                                            19451
                                            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