NEWS
ioBroker.upnp - please test
-
@sigi234 siehe ersten Beitrag von Bluefox hier, musst die Branch refactoring installieren
Das habe ich gemacht.......
-
@sigi234 dann solltest du jetzt auch die Version 1.0.1 installiert haben.. :-)
Ok Version oben:
upnp.0 2019-02-19 23:01:10.106 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/s upnp.0 2019-02-19 23:01:10.104 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/s upnp.0 2019-02-19 23:01:00.118 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/s upnp.0 2019-02-19 23:01:00.111 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/s upnp.0 2019-02-19 23:00:50.156 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/s upnp.0 2019-02-19 23:00:50.151 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/s upnp.0 2019-02-19 23:00:40.109 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/s upnp.0 2019-02-19 23:00:40.101 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/s upnp.0 2019-02-19 23:00:31.446 info Auto discover: true upnp.0 2019-02-19 23:00:31.446 info starting. Version 1.0.1 in C:/ioBroker/node_modules/iobroker.upnp, node: v8.15.0 upnp.0 2019-02-19 23:00:20.099 warn Sent message: {"uri":"http://192.168.178.1:49000/igdupnp/control/WANCommonIFC1","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-upnp-org:service:WANCommonInterface upnp.0 2019-02-19 23:00:20.099 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/ upnp.0 2019-02-19 23:00:20.096 warn Sent message: {"uri":"http://192.168.178.1:49000/igdupnp/control/WANCommonIFC1","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-upnp-org:service:WANCommonInterface upnp.0 2019-02-19 23:00:20.096 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/ upnp.0 2019-02-19 23:00:10.126 warn Sent message: {"uri":"http://192.168.178.1:49000/igdupnp/control/WANCommonIFC1","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-upnp-org:service:WANCommonInterface upnp.0 2019-02-19 23:00:10.126 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/ upnp.0 2019-02-19 23:00:10.124 warn Sent message: {"uri":"http://192.168.178.1:49000/igdupnp/control/WANCommonIFC1","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-upnp-org:service:WANCommonInterface upnp.0 2019-02-19 23:00:10.124 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/ upnp.0 2019-02-19 23:00:00.476 warn Sent message: {"uri":"http://192.168.178.1:49000/igdupnp/control/WANCommonIFC1","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-upnp-org:service:WANCommonInterface upnp.0 2019-02-19 23:00:00.476 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/ upnp.0 2019-02-19 23:00:00.470 warn Sent message: {"uri":"http://192.168.178.1:49000/igdupnp/control/WANCommonIFC1","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-upnp-org:service:WANCommonInterface upnp.0 2019-02-19 23:00:00.470 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/ upnp.0 2019-02-19 22:59:50.137 warn Sent message: {"uri":"http://192.168.178.1:49000/igdupnp/control/WANCommonIFC1","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-upnp-org:service:WANCommonInterface upnp.0 2019-02-19 22:59:50.137 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/ upnp.0 2019-02-19 22:59:50.135 warn Sent message: {"uri":"http://192.168.178.1:49000/igdupnp/control/WANCommonIFC1","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-upnp-org:service:WANCommonInterface upnp.0 2019-02-19 22:59:50.135 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/ upnp.0 2019-02-19 22:59:40.101 warn Sent message: {"uri":"http://192.168.178.1:49000/igdupnp/control/WANCommonIFC1","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-upnp-org:service:WANCommonInterface upnp.0 2019-02-19 22:59:40.101 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/ upnp.0 2019-02-19 22:59:40.093 warn Sent message: {"uri":"http://192.168.178.1:49000/igdupnp/control/WANCommonIFC1","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-upnp-org:service:WANCommonInterface upnp.0 2019-02-19 22:59:40.093 warn Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\"?>\n<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/ -
@TheDuke schau mal hier z.b.
dann bekommst auch Daten
https://forum.iobroker.net/topic/14802/tutorial-vis-fritzbox-status-up-downloadanzeigeumgestiegen von Proxmox auf Unraid
-
@TheDuke schau mal hier z.b.
dann bekommst auch Daten
https://forum.iobroker.net/topic/14802/tutorial-vis-fritzbox-status-up-downloadanzeige@crunchip sagte in ioBroker.upnp - please test:
@TheDuke schau mal hier z.b.
dann bekommst auch Daten
https://forum.iobroker.net/topic/14802/tutorial-vis-fritzbox-status-up-downloadanzeigeDanke, aber war schon aktiv .
-
Hallo,
mit der Version 0.3.9 lief bei mir alles gut. Nun habe ich die 1.0.1 installiert. Nun bekomme ich keine bzw. sehr wenig in der Anzeige.
Was ist da bei mir noch nicht korrekt? Muss ich zwingend auf js-controller@1.5.7 updaten? Da bin ich leider ein Newbie. Wie muss ich das machen, sorry für die Frage.
Gruß
opossum -
Hallo,
mit der Version 0.3.9 lief bei mir alles gut. Nun habe ich die 1.0.1 installiert. Nun bekomme ich keine bzw. sehr wenig in der Anzeige.Was ist da bei mir noch nicht korrekt? Muss ich zwingend auf js-controller@1.5.7 updaten? Da bin ich leider ein Newbie. Wie muss ich das machen, sorry für die Frage.
Gruß
opossum@opossum nee, der Adapter hat noch'n Bug und legt nicht alle Objekte an. Ist bei mir das gleiche. Oder das selbe? :-)
-
@ilovegym sagte in ioBroker.upnp - please test:
@sigi234 was ist bei dir anders ? Mit der Version 0.3.9 des upnp Adapter bekomme ich diese Einträge auch, mit der Version 1.0 nicht.
Node 8.15, NPM 6.8, js-controller 1.5.7NPM 6.4.1
@sigi234 Habs auch auf einer Testinstallation ganz frisch ausprobiert, mit Node 8.15 und NPM 6.4.1, da ist das gleiche, er steigert sich bei mehr als 50 Devices in stack overflow und das komplette System schmiert ab, iobroker startet dauernd neu.. etc..
-
@all
Ist ja auch eine Testversion....... :wink: -
@Bluefox Guten Morgen, hab V1.0.2 auf einem frisch aufgesetztem Testsystem Linux Mint 19.1, Node 8.15, NPM 6.4.1 installiert, und er legt auch jetzt viel mehr Datenpunkte an, setzt in diesen aber keine Werte.. endet dann in einem RangeError, wie gehabt. Musste die Instanz stoppen, iobroker war dann nicht mehr erreichbar über admin.
hier ein Screenshot
-
@Bluefox Guten Morgen, hab V1.0.2 auf einem frisch aufgesetztem Testsystem Linux Mint 19.1, Node 8.15, NPM 6.4.1 installiert, und er legt auch jetzt viel mehr Datenpunkte an, setzt in diesen aber keine Werte.. endet dann in einem RangeError, wie gehabt. Musste die Instanz stoppen, iobroker war dann nicht mehr erreichbar über admin.
hier ein Screenshot
@ilovegym sagte in ioBroker.upnp - please test:
@Bluefox Guten Morgen, hab V1.0.2 auf einem frisch aufgesetztem Testsystem Linux Mint 19.1, Node 8.15, NPM 6.4.1 installiert, und er legt auch jetzt viel mehr Datenpunkte an, setzt in diesen aber keine Werte.. endet dann in einem RangeError, wie gehabt. Musste die Instanz stoppen, iobroker war dann nicht mehr erreichbar über admin.
Dann warte ich noch mit den update....:relaxed:
-
node 8.15.0 + npm 6.8.0 sieht ganz gut aus. Datenpunkte alle wieder da, lassen sich auch befüllen, nur bekomme ich im 10 Minuten-Rhytmus leider noch den call stack:
2019-02-21 09:39:02.485 - info: upnp.0 Found new device: http://192.168.1.1:49000/igd2desc.xml 2019-02-21 09:39:02.505 - info: upnp.0 Found new device: http://192.168.1.1:49000/igd2desc.xml 2019-02-21 09:39:02.510 - info: upnp.0 Found new device: http://192.168.1.1:49000/igd2desc.xml 2019-02-21 09:39:02.535 - info: upnp.0 Found new device: http://192.168.1.1:49000/igd2desc.xml 2019-02-21 09:39:04.301 - error: upnp.0 uncaught exception: Maximum call stack size exceeded 2019-02-21 09:39:04.301 - error: upnp.0 RangeError: Maximum call stack size exceeded at tryParse (/opt/iobroker/node_modules/socket.io-parser/index.js:336:12) at decodeString (/opt/iobroker/node_modules/socket.io-parser/index.js:325:9) at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:237:14) at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/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/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) at Socket.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:451:14) at WS. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:268:10) at WS.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) at WS.Transport.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:145:8) at WS.Transport.onData (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:137:8) at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:146:10) at WebSocket.onMessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:442:14) at emitTwo (events.js:126:13) at WebSocket.emit (events.js:214:7) at Receiver.ontext (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:841:10) 2019-02-21 09:39:04.307 - info: upnp.0 cleaned everything up... 2019-02-21 09:39:04.307 - info: upnp.0 Alive and sid states cleared 2019-02-21 09:39:04.365 - error: Caught by controller[0]: RangeError: Maximum call stack size exceeded 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at tryParse (/opt/iobroker/node_modules/socket.io-parser/index.js:336:12) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at decodeString (/opt/iobroker/node_modules/socket.io-parser/index.js:325:9) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:237:14) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:322:16) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at Socket.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:451:14) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WS. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:268:10) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WS.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WS.Transport.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:145:8) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WS.Transport.onData (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:137:8) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:146:10) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WebSocket.onMessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:442:14) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at emitTwo (events.js:126:13) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WebSocket.emit (events.js:214:7) 2019-02-21 09:39:04.368 - error: Caught by controller[0]: at Receiver.ontext (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:841:10) 2019-02-21 09:39:04.368 - error: host.Ubuntu instance system.adapter.upnp.0 terminated with code 0 (OK) 2019-02-21 09:39:04.368 - info: host.Ubuntu Restart adapter system.adapter.upnp.0 because enabled 2019-02-21 09:39:34.386 - info: host.Ubuntu instance system.adapter.upnp.0 started with pid 28606 2019-02-21 09:39:36.420 - info: upnp.0 starting. Version 1.0.2 in /opt/iobroker/node_modules/iobroker.upnp, node: v8.15.0 2019-02-21 09:39:36.467 - info: upnp.0 Auto discover: trueLG SBorg ( SBorg auf GitHub)
Projekte: Lebensmittelwarnung.de | WLAN-Wetterstation | PimpMyStation -
@ilovegym sagte in ioBroker.upnp - please test:
@Bluefox Guten Morgen, hab V1.0.2 auf einem frisch aufgesetztem Testsystem Linux Mint 19.1, Node 8.15, NPM 6.4.1 installiert, und er legt auch jetzt viel mehr Datenpunkte an, setzt in diesen aber keine Werte.. endet dann in einem RangeError, wie gehabt. Musste die Instanz stoppen, iobroker war dann nicht mehr erreichbar über admin.
Dann warte ich noch mit den update....:relaxed:
@sigi234 sagte in ioBroker.upnp - please test:
@ilovegym sagte in ioBroker.upnp - please test:
@Bluefox Guten Morgen, hab V1.0.2 auf einem frisch aufgesetztem Testsystem Linux Mint 19.1, Node 8.15, NPM 6.4.1 installiert, und er legt auch jetzt viel mehr Datenpunkte an, setzt in diesen aber keine Werte.. endet dann in einem RangeError, wie gehabt. Musste die Instanz stoppen, iobroker war dann nicht mehr erreichbar über admin.
Dann warte ich noch mit den update....:relaxed:
Edit 1:
Scheint zu funktionieren.........V 1.0.2
-
node 8.15.0 + npm 6.8.0 sieht ganz gut aus. Datenpunkte alle wieder da, lassen sich auch befüllen, nur bekomme ich im 10 Minuten-Rhytmus leider noch den call stack:
2019-02-21 09:39:02.485 - info: upnp.0 Found new device: http://192.168.1.1:49000/igd2desc.xml 2019-02-21 09:39:02.505 - info: upnp.0 Found new device: http://192.168.1.1:49000/igd2desc.xml 2019-02-21 09:39:02.510 - info: upnp.0 Found new device: http://192.168.1.1:49000/igd2desc.xml 2019-02-21 09:39:02.535 - info: upnp.0 Found new device: http://192.168.1.1:49000/igd2desc.xml 2019-02-21 09:39:04.301 - error: upnp.0 uncaught exception: Maximum call stack size exceeded 2019-02-21 09:39:04.301 - error: upnp.0 RangeError: Maximum call stack size exceeded at tryParse (/opt/iobroker/node_modules/socket.io-parser/index.js:336:12) at decodeString (/opt/iobroker/node_modules/socket.io-parser/index.js:325:9) at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:237:14) at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/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/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) at Socket.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:451:14) at WS. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:268:10) at WS.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) at WS.Transport.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:145:8) at WS.Transport.onData (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:137:8) at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:146:10) at WebSocket.onMessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:442:14) at emitTwo (events.js:126:13) at WebSocket.emit (events.js:214:7) at Receiver.ontext (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:841:10) 2019-02-21 09:39:04.307 - info: upnp.0 cleaned everything up... 2019-02-21 09:39:04.307 - info: upnp.0 Alive and sid states cleared 2019-02-21 09:39:04.365 - error: Caught by controller[0]: RangeError: Maximum call stack size exceeded 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at tryParse (/opt/iobroker/node_modules/socket.io-parser/index.js:336:12) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at decodeString (/opt/iobroker/node_modules/socket.io-parser/index.js:325:9) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:237:14) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:322:16) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) 2019-02-21 09:39:04.366 - error: Caught by controller[0]: at Socket.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:451:14) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WS. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:268:10) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WS.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WS.Transport.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:145:8) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WS.Transport.onData (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:137:8) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:146:10) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WebSocket.onMessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:442:14) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at emitTwo (events.js:126:13) 2019-02-21 09:39:04.367 - error: Caught by controller[0]: at WebSocket.emit (events.js:214:7) 2019-02-21 09:39:04.368 - error: Caught by controller[0]: at Receiver.ontext (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:841:10) 2019-02-21 09:39:04.368 - error: host.Ubuntu instance system.adapter.upnp.0 terminated with code 0 (OK) 2019-02-21 09:39:04.368 - info: host.Ubuntu Restart adapter system.adapter.upnp.0 because enabled 2019-02-21 09:39:34.386 - info: host.Ubuntu instance system.adapter.upnp.0 started with pid 28606 2019-02-21 09:39:36.420 - info: upnp.0 starting. Version 1.0.2 in /opt/iobroker/node_modules/iobroker.upnp, node: v8.15.0 2019-02-21 09:39:36.467 - info: upnp.0 Auto discover: true -
@Bluefox Danke für das Update, schon etwas besser, der Adapter läuft durch, allerdings schreibt er keine Werte in die Objekte, und meine 3 Octopi-Raspis mag er einfach nicht, solange diese online sind, hängt er bei den in einer Schleife und erkennt sie jedesmal wieder als neues Device - und kommt dann natürlich zu nix anderes mehr..
Habe die drei jetzt mal runtergefahren, und siehe da, es werden noch mehr Geräte erkannt ( ich hab in den Settings alle 3 Haken an) jetzt keine Schleife mehr, aber noch keine Werte in den Objekten.Logfileauszug von der Schleife:
2019-02-21 23:15:33.713 - debug: upnp.0 Started processTasks with 1 tasks 2019-02-21 23:15:33.713 - debug: upnp.0 firstDevLookup for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.745 - debug: upnp.0 Positive answer for request of the XML file for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.746 - debug: upnp.0 Parsing the XML file for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.746 - debug: upnp.0 Creating objects for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.746 - debug: upnp.0 TypeOfDevice Basic 2019-02-21 23:15:33.746 - debug: upnp.0 Can not find a icon for 192.168.178.32 2019-02-21 23:15:33.746 - debug: upnp.0 Creating root element for device: OctoPrint_instance_on_berrymotion 2019-02-21 23:15:33.746 - debug: upnp.0 Cannot parse answer from 192.168.178.32: TypeError: Cannot read property 'length' of undefined 2019-02-21 23:15:33.749 - debug: upnp.0 All tasks processed 2019-02-21 23:15:33.792 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.792 - debug: upnp.0 Started processTasks with 1 tasks 2019-02-21 23:15:33.792 - debug: upnp.0 firstDevLookup for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.817 - debug: upnp.0 Positive answer for request of the XML file for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.817 - debug: upnp.0 Parsing the XML file for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.817 - debug: upnp.0 Creating objects for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.817 - debug: upnp.0 TypeOfDevice Basic 2019-02-21 23:15:33.817 - debug: upnp.0 Can not find a icon for 192.168.178.28 2019-02-21 23:15:33.817 - debug: upnp.0 Creating root element for device: OctoPrint_instance__Octopi 2019-02-21 23:15:33.818 - debug: upnp.0 Cannot parse answer from 192.168.178.28: TypeError: Cannot read property 'length' of undefined 2019-02-21 23:15:33.821 - debug: upnp.0 All tasks processed 2019-02-21 23:15:33.851 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.851 - debug: upnp.0 Started processTasks with 1 tasks 2019-02-21 23:15:33.851 - debug: upnp.0 firstDevLookup for http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.904 - debug: upnp.0 Positive answer for request of the XML file for http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.904 - debug: upnp.0 Parsing the XML file for http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.904 - debug: upnp.0 Creating objects for http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.904 - debug: upnp.0 TypeOfDevice Basic 2019-02-21 23:15:33.904 - debug: upnp.0 Can not find a icon for 192.168.178.34 2019-02-21 23:15:33.904 - debug: upnp.0 Creating root element for device: OctoPrint_instance_on_gymberry 2019-02-21 23:15:33.904 - debug: upnp.0 Cannot parse answer from 192.168.178.34: TypeError: Cannot read property 'length' of undefined 2019-02-21 23:15:33.908 - debug: upnp.0 All tasks processed 2019-02-21 23:15:39.112 - debug: upnp.0 Started processTasks with 8 tasks 2019-02-21 23:15:39.127 - debug: upnp.0 All tasks processed 2019-02-21 23:15:43.729 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.730 - debug: upnp.0 Started processTasks with 1 tasks 2019-02-21 23:15:43.730 - debug: upnp.0 firstDevLookup for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.780 - debug: upnp.0 Positive answer for request of the XML file for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.782 - debug: upnp.0 Parsing the XML file for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.782 - debug: upnp.0 Creating objects for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.782 - debug: upnp.0 TypeOfDevice Basic 2019-02-21 23:15:43.782 - debug: upnp.0 Can not find a icon for 192.168.178.32 2019-02-21 23:15:43.783 - debug: upnp.0 Creating root element for device: OctoPrint_instance_on_berrymotion 2019-02-21 23:15:43.783 - debug: upnp.0 Cannot parse answer from 192.168.178.32: TypeError: Cannot read property 'length' of undefined 2019-02-21 23:15:43.785 - debug: upnp.0 All tasks processed 2019-02-21 23:15:43.828 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.828 - debug: upnp.0 Started processTasks with 1 tasks 2019-02-21 23:15:43.828 - debug: upnp.0 firstDevLookup for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.853 - debug: upnp.0 Positive answer for request of the XML file for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.853 - debug: upnp.0 Parsing the XML file for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.853 - debug: upnp.0 Creating objects for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.853 - debug: upnp.0 TypeOfDevice Basic 2019-02-21 23:15:43.853 - debug: upnp.0 Can not find a icon for 192.168.178.28 2019-02-21 23:15:43.853 - debug: upnp.0 Creating root element for device: OctoPrint_instance__Octopi 2019-02-21 23:15:43.853 - debug: upnp.0 Cannot parse answer from 192.168.178.28: TypeError: Cannot read property 'length' of undefined 2019-02-21 23:15:43.857 - debug: upnp.0 All tasks processed 2019-02-21 23:15:43.878 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.878 - debug: upnp.0 Started processTasks with 1 tasksund das ging solange so weiter, bis ich die drei runtergefahren hab ( Drucke gerade nicht, daher gings..).
Nehme an, es hat vielleicht damit was zu tun:
019-02-21 23:15:33.818 - debug: upnp.0 Cannot parse answer from 192.168.178.28: TypeError: Cannot read property 'length' of undefined -
@Bluefox Danke für das Update, schon etwas besser, der Adapter läuft durch, allerdings schreibt er keine Werte in die Objekte, und meine 3 Octopi-Raspis mag er einfach nicht, solange diese online sind, hängt er bei den in einer Schleife und erkennt sie jedesmal wieder als neues Device - und kommt dann natürlich zu nix anderes mehr..
Habe die drei jetzt mal runtergefahren, und siehe da, es werden noch mehr Geräte erkannt ( ich hab in den Settings alle 3 Haken an) jetzt keine Schleife mehr, aber noch keine Werte in den Objekten.Logfileauszug von der Schleife:
2019-02-21 23:15:33.713 - debug: upnp.0 Started processTasks with 1 tasks 2019-02-21 23:15:33.713 - debug: upnp.0 firstDevLookup for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.745 - debug: upnp.0 Positive answer for request of the XML file for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.746 - debug: upnp.0 Parsing the XML file for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.746 - debug: upnp.0 Creating objects for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.746 - debug: upnp.0 TypeOfDevice Basic 2019-02-21 23:15:33.746 - debug: upnp.0 Can not find a icon for 192.168.178.32 2019-02-21 23:15:33.746 - debug: upnp.0 Creating root element for device: OctoPrint_instance_on_berrymotion 2019-02-21 23:15:33.746 - debug: upnp.0 Cannot parse answer from 192.168.178.32: TypeError: Cannot read property 'length' of undefined 2019-02-21 23:15:33.749 - debug: upnp.0 All tasks processed 2019-02-21 23:15:33.792 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.792 - debug: upnp.0 Started processTasks with 1 tasks 2019-02-21 23:15:33.792 - debug: upnp.0 firstDevLookup for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.817 - debug: upnp.0 Positive answer for request of the XML file for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.817 - debug: upnp.0 Parsing the XML file for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.817 - debug: upnp.0 Creating objects for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.817 - debug: upnp.0 TypeOfDevice Basic 2019-02-21 23:15:33.817 - debug: upnp.0 Can not find a icon for 192.168.178.28 2019-02-21 23:15:33.817 - debug: upnp.0 Creating root element for device: OctoPrint_instance__Octopi 2019-02-21 23:15:33.818 - debug: upnp.0 Cannot parse answer from 192.168.178.28: TypeError: Cannot read property 'length' of undefined 2019-02-21 23:15:33.821 - debug: upnp.0 All tasks processed 2019-02-21 23:15:33.851 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.851 - debug: upnp.0 Started processTasks with 1 tasks 2019-02-21 23:15:33.851 - debug: upnp.0 firstDevLookup for http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.904 - debug: upnp.0 Positive answer for request of the XML file for http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.904 - debug: upnp.0 Parsing the XML file for http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.904 - debug: upnp.0 Creating objects for http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:33.904 - debug: upnp.0 TypeOfDevice Basic 2019-02-21 23:15:33.904 - debug: upnp.0 Can not find a icon for 192.168.178.34 2019-02-21 23:15:33.904 - debug: upnp.0 Creating root element for device: OctoPrint_instance_on_gymberry 2019-02-21 23:15:33.904 - debug: upnp.0 Cannot parse answer from 192.168.178.34: TypeError: Cannot read property 'length' of undefined 2019-02-21 23:15:33.908 - debug: upnp.0 All tasks processed 2019-02-21 23:15:39.112 - debug: upnp.0 Started processTasks with 8 tasks 2019-02-21 23:15:39.127 - debug: upnp.0 All tasks processed 2019-02-21 23:15:43.729 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.730 - debug: upnp.0 Started processTasks with 1 tasks 2019-02-21 23:15:43.730 - debug: upnp.0 firstDevLookup for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.780 - debug: upnp.0 Positive answer for request of the XML file for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.782 - debug: upnp.0 Parsing the XML file for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.782 - debug: upnp.0 Creating objects for http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.782 - debug: upnp.0 TypeOfDevice Basic 2019-02-21 23:15:43.782 - debug: upnp.0 Can not find a icon for 192.168.178.32 2019-02-21 23:15:43.783 - debug: upnp.0 Creating root element for device: OctoPrint_instance_on_berrymotion 2019-02-21 23:15:43.783 - debug: upnp.0 Cannot parse answer from 192.168.178.32: TypeError: Cannot read property 'length' of undefined 2019-02-21 23:15:43.785 - debug: upnp.0 All tasks processed 2019-02-21 23:15:43.828 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.828 - debug: upnp.0 Started processTasks with 1 tasks 2019-02-21 23:15:43.828 - debug: upnp.0 firstDevLookup for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.853 - debug: upnp.0 Positive answer for request of the XML file for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.853 - debug: upnp.0 Parsing the XML file for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.853 - debug: upnp.0 Creating objects for http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.853 - debug: upnp.0 TypeOfDevice Basic 2019-02-21 23:15:43.853 - debug: upnp.0 Can not find a icon for 192.168.178.28 2019-02-21 23:15:43.853 - debug: upnp.0 Creating root element for device: OctoPrint_instance__Octopi 2019-02-21 23:15:43.853 - debug: upnp.0 Cannot parse answer from 192.168.178.28: TypeError: Cannot read property 'length' of undefined 2019-02-21 23:15:43.857 - debug: upnp.0 All tasks processed 2019-02-21 23:15:43.878 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-21 23:15:43.878 - debug: upnp.0 Started processTasks with 1 tasksund das ging solange so weiter, bis ich die drei runtergefahren hab ( Drucke gerade nicht, daher gings..).
Nehme an, es hat vielleicht damit was zu tun:
019-02-21 23:15:33.818 - debug: upnp.0 Cannot parse answer from 192.168.178.28: TypeError: Cannot read property 'length' of undefinedУчастник @ilovegym написал в ioBroker.upnp - please test:
Kannst du http://192.168.178.28:80/plugin/discovery/discovery.xml Datei zeigen?
Support us
661
Online32.7k
Users82.4k
Topics1.3m
Posts