GithubHelp home page GithubHelp logo

jey-cee / iobroker.upnp Goto Github PK

View Code? Open in Web Editor NEW
10.0 3.0 8.0 987 KB

Serves for communication and interaction with all upnp-capable devices.

License: MIT License

JavaScript 96.64% HTML 3.36%
iobroker upnp upnp-listener

iobroker.upnp's People

Contributors

apollon77 avatar dependabot-preview[bot] avatar dependabot[bot] avatar dutchmannl avatar foxriver76 avatar germanbluefox avatar greenkeeper[bot] avatar jey-cee avatar jogibear9988 avatar ldittmar81 avatar snyk-bot avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

iobroker.upnp's Issues

[Bug]: After Update JS-Controller to 3.3.22: LogFile "has to be Type "XXX" but received type "YYY".

Contact Details

xxx

What happened?

Good morning and happy new year. Since the update to JS-Controller 3.3.22 I have a problem with the UPNP adapter among others:

The Logfile is FULL and spammed with the messages that the received type of the DataPoint (DP) ist not the one it has to be. Like, f.e.:
`

upnp.0 2022-01-02 10:55:10.852 info State value to set for "upnp.0.WANDevice_-FRITZ!Box_6490_Cable(kdg).WANDevice.WANCommonInterfaceConfig.ByteSendRate" has to be type "number" but received type "string"
upnp.0 2022-01-02 10:55:10.790 info State value to set for "upnp.0.WANDevice_-FRITZ!Box_6490_Cable(kdg).WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has to be type "number" but received type "string"
upnp.0 2022-01-02 10:55:10.739 info State value to set for "upnp.0.WANDevice_-FRITZ!Box_6490_Cable(kdg).WANDevice.WANCommonInterfaceConfig.PacketSendRate" has to be type "number" but received type "string"
upnp.0 2022-01-02 10:55:10.684 info State value to set for "upnp.0.WANDevice_-FRITZ!Box_6490_Cable(kdg).WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has to be type "number" but received type "string"
upnp.0 2022-01-02 10:55:10.620 info State value to set for "upnp.0.WANDevice_-FRITZ!Box_6490_Cable(kdg).WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has to be type "number" but received type "string"
upnp.0 2022-01-02 10:55:10.560 info State value to set for "upnp.0.WANDevice_-FRITZ!Box_6490_Cable(kdg).WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has to be type "number" but received type "string"
upnp.0 2022-01-02 10:55:10.509 info State value to set for "upnp.0.WANDevice_-FRITZ!Box_6490_Cable(kdg).WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has to be type "number" but received type "string"
upnp.0 2022-01-02 10:55:10.451 info State value to set for "upnp.0.WANDevice_-FRITZ!Box_6490_Cable(kdg).WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has to be type "number" but received type "string"
upnp.0 2022-01-02 10:55:10.359 info State value to set for "upnp.0.WANDevice_-FRITZ!Box_6490_Cable(kdg).WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has to be type "boolean" but received type "string"
upnp.0 2022-01-02 10:55:10.307 info State value to set for "upnp.0.WANDevice_-FRITZ!Box_6490_Cable(kdg).WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has to be type "number" but received type "string"
`

Stopping the instance. Deleting the DPs and restarting, as well as re-creating the DPs did not fix the problem. The DP types actually match what is required. So I don't know what to do anymore. I've read here another Issue with a similar problem (#88 ), but this issue was AUTOMATICALLY closed, because of no further activies.

Hope you can help me (and maybe others).

Greetings

Adapter Version

1.0.19

JS-Controller Version

3.3.22

Node JS Version

12.22.1

NPM Version

6.14.12

Operating System

Debian

Relevant log output

upnp.0
2022-01-02 10:55:10.852	info	State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.ByteSendRate" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.790	info	State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.739	info	State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.PacketSendRate" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.684	info	State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.620	info	State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.560	info	State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.509	info	State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.451	info	State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.359	info	State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has to be type "boolean" but received type "string"

upnp.0
2022-01-02 10:55:10.307	info	State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has to be type "number" but received type "string"

Anything else?

No response

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.upnp

I have also found warnings that may be fixed if possible.

  • [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

Update von js-controller BETA 3.2.2

Hallo, nach einen Update auf JSC BETA 3.2.2 kommt folgendes:

`

upnp.0 2021-01-09 10:09:16.550 warn (14192) State "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.X_AVM_DE_GetIPTVInfos.sid" has no existing object, this might lead to an error in future versions
upnp.0 2021-01-09 10:09:16.550 warn (14192) State "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.GetAddonInfos.sid" has no existing object, this might lead to an error in future versions
upnp.0 2021-01-09 10:09:16.550 warn (14192) State "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.GetCommonLinkProperties.sid" has no existing object, this might lead to an error in future versions
upnp.0 2021-01-09 10:09:16.550 warn (14192) State "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.GetTotalBytesReceived.sid" has no existing object, this might lead to an error in future versions
upnp.0 2021-01-09 10:09:16.550 warn (14192) State "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.GetTotalPacketsReceived.sid" has no existing object, this might lead to an error in future versions
upnp.0 2021-01-09 10:09:16.550 warn (14192) State "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.GetTotalBytesSent.sid" has no existing object, this might lead to an error in future versions
upnp.0 2021-01-09 10:09:16.549 warn (14192) State "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.GetTotalPacketsSent.sid" has no existing object, this might lead to an error in future versions
upnp.0 2021-01-09 10:09:16.549 warn (14192) State "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.X_AVM_DE_GetDsliteStatus.sid" has no existing object, this might lead to an error in future versions

`

Auto discover: undefined

After installing the upnp adapter on a fresh iobroker installation, i get the following messages in the log and no devices will be finding:

upnp.0 2017-03-03 04:16:38.762 info Auto discover: undefined
upnp.0 2017-03-03 04:16:38.740 info starting. Version 0.3.5 in /opt/iobroker/node_modules/iobroker.upnp, node: v6.10.0
host. 2017-03-03 04:16:38.589 info States connected to redis 127.0.0.1:6379
host.ioBroker-BPi 2017-03-03 04:16:31.703 info instance system.adapter.upnp.0 started with pid 2461
host.ioBroker-BPi 2017-03-03 04:16:29.265 info instance system.adapter.upnp.0 terminated with code 0 (OK)

An in-range update of @iobroker/testing is breaking the build 🚨

The devDependency @iobroker/testing was updated from 1.2.3 to 1.2.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@iobroker/testing is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from 6.0.0 to 6.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v6.0.1

6.0.1 / 2019-02-21

The obligatory round of post-major-release bugfixes.

🐛 Fixes

These issues were regressions.

  • #3754 - Mocha again finds test.js when run without arguments (@plroebuck)
  • #3756 - Mocha again supports third-party interfaces via --ui (@boneskull)
  • #3755 - Fix broken --watch (@boneskull)
  • #3759 - Fix unwelcome deprecation notice when Mocha run against languages (CoffeeScript) with implicit return statements; returning a non-undefined value from a describe callback is no longer considered deprecated (@boneskull)

📖 Documentation

Commits

The new version differs by 9 commits.

  • 6d3d6b4 Release v6.0.1
  • 2146ece update CHANGELOG.md for v6.0.1
  • 7c9221d backout deprecation of value returned from suite; closes #3744
  • b7cfceb fix --watch not finding any files to execute; closes #3748
  • b836d73 Upgrade docdash version - issue #3663
  • 7926f47 fix --ui issues, closes #3746
  • 00f2ed9 dev dep upgrades from "npm audit" and "npm upgrade"
  • 34afb1a fix(cli/run.js): Revert default glob to match Mocha-5.2
  • 6d5a0db Bring the example congfiguration file in line with the documentation. (#3751)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Update js-controller 3.3.1 Warn Meldungen

Hallo,

nach einen Update des js-controllers auf V 3.3.1 kommen folgende Warnmeldungen:

`

upnp.0 2021-04-30 06:35:00.364 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.ByteSendRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:35:00.348 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:35:00.333 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.PacketSendRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:35:00.316 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:35:00.300 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:35:00.284 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:35:00.268 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:35:00.253 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:35:00.173 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has wrong type "string" but has to be "boolean"
upnp.0 2021-04-30 06:35:00.157 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:34:00.356 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.ByteSendRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:34:00.339 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:34:00.322 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.PacketSendRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:34:00.308 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:34:00.292 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:34:00.277 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:34:00.259 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:34:00.244 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:34:00.164 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has wrong type "string" but has to be "boolean"
upnp.0 2021-04-30 06:34:00.148 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:33:00.351 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.ByteSendRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:33:00.336 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:33:00.319 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.PacketSendRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:33:00.304 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:33:00.289 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:33:00.277 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:33:00.273 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:33:00.256 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:33:00.177 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has wrong type "string" but has to be "boolean"
upnp.0 2021-04-30 06:33:00.159 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:32:00.342 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.ByteSendRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:32:00.326 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:32:00.312 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.PacketSendRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:32:00.296 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:32:00.276 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:32:00.261 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:32:00.245 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:32:00.230 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:32:00.151 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has wrong type "string" but has to be "boolean"
upnp.0 2021-04-30 06:32:00.134 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:31:00.373 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.ByteSendRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:31:00.359 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:31:00.343 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.PacketSendRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:31:00.326 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:31:00.311 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:31:00.296 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:31:00.280 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:31:00.264 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has wrong type "string" but has to be "number"
upnp.0 2021-04-30 06:31:00.185 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has wrong type "string" but has to be "boolean"
upnp.0 2021-04-30 06:31:00.169 warn (10372) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6590_Cable.WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has wrong type "string" but has to be "number"

`

refactoring: 1.0.4 found new device again and again..

Version 1.0.4 refactoring works well, but don't remember some devices, the most of my network are remembered, but in the logfile are this the hole day.. it never ends...and after some hours iobroker crash - without and error.
the setup of upnp was "new devices - yes, media objects default, yes, subscribe yes.

2019-02-23 12:12:02.087 - info: host.iobroker instance system.adapter.upnp.0 started with pid 2959 2019-02-23 12:12:04.236 - info: upnp.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.upnp, node: v8.15.0 2019-02-23 12:12:04.251 - info: upnp.0 Auto discover: true 2019-02-23 12:12:28.848 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:12:28.919 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:12:28.936 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:12:38.847 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:12:38.956 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:12:38.972 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:12:48.867 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:12:48.995 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:12:49.027 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:12:58.866 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:12:59.025 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:12:59.043 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:12:59.658 - info: upnp.0 Found new device: http://192.168.178.85:60000/upnp/dev/d8f8059a-306e-21c9-ffff-ffffad7a5c5b/desc 2019-02-23 12:13:08.883 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:13:09.060 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:13:09.080 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:13:18.899 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:13:20.119 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:13:20.136 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:13:28.909 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:13:30.156 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:13:30.175 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:13:38.915 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:13:40.190 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:13:40.268 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:13:48.931 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:13:50.230 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:13:50.246 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:13:58.951 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:14:00.286 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:14:00.291 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:14:08.965 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:14:11.627 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:14:11.652 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:14:18.985 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:14:29.003 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:14:29.052 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:14:29.140 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:14:39.012 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:14:39.085 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:14:39.174 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:14:49.025 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:14:49.121 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:14:49.209 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:14:59.041 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:15:00.175 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:15:00.192 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:15:09.067 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:15:10.202 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:15:10.228 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:15:17.288 - info: upnp.0 Found new device: http://192.168.178.83:60000/upnp/dev/2d122f5a-5b60-57f4-ffff-ffff903158e9/desc 2019-02-23 12:15:17.309 - info: upnp.0 Found new device: http://192.168.49.1:60000/upnp/dev/2d122f5a-5b60-57f4-ffff-ffff903158e9/desc 2019-02-23 12:15:17.403 - info: upnp.0 Found new device: http://192.168.178.83:60000/upnp/dev/2d122f5a-5b60-57f4-ffff-ffff903158e9/desc 2019-02-23 12:15:19.066 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:15:20.260 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:15:20.267 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:15:21.650 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:15:58.676 - info: upnp.0 Found new device: http://169.254.47.245:2870/dmr_bdp5510.xml 2019-02-23 12:15:59.271 - info: upnp.0 Found new device: http://169.254.47.245:51000/config.xml 2019-02-23 12:16:17.798 - info: upnp.0 Found new device: http://192.168.178.5:49000/fboxdesc.xml 2019-02-23 12:16:41.274 - info: upnp.0 Found new device: http://192.168.178.29:80/Canon_basic.xml 2019-02-23 12:17:10.040 - info: upnp.0 Found new device: http://192.168.178.4:49000/igddesc.xml 2019-02-23 12:17:11.992 - info: upnp.0 Found new device: http://192.168.178.4:49000/fboxdesc.xml 2019-02-23 12:17:15.042 - info: upnp.0 Found new device: http://192.168.178.4:49000/igd2desc.xml 2019-02-23 12:17:29.273 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:17:30.304 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:17:30.308 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:17:44.646 - info: upnp.0 Found new device: http://192.168.178.2:49000/fboxdesc.xml 2019-02-23 12:17:53.708 - info: upnp.0 Found new device: http://192.168.178.2:49000/igddesc.xml 2019-02-23 12:17:54.682 - info: upnp.0 Found new device: http://192.168.178.2:49000/igd2desc.xml 2019-02-23 12:19:07.077 - info: upnp.0 Found new device: http://192.168.178.3:49000/fboxdesc.xml 2019-02-23 12:19:13.120 - info: upnp.0 Found new device: http://192.168.178.3:49000/igd2desc.xml 2019-02-23 12:19:16.133 - info: upnp.0 Found new device: http://192.168.178.3:49000/igddesc.xml 2019-02-23 12:19:19.621 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 12:21:09.435 - info: upnp.0 Found new device: http://192.168.178.1:49000/MediaServerDevDesc.xml 2019-02-23 12:21:17.564 - info: upnp.0 Found new device: http://192.168.178.1:49000/avmnexusdesc.xml 2019-02-23 12:21:17.574 - info: upnp.0 Found new device: http://192.168.178.1:49000/igddesc.xml 2019-02-23 12:21:17.607 - info: upnp.0 Found new device: http://192.168.178.1:49000/igd2desc.xml 2019-02-23 12:21:17.632 - info: upnp.0 Found new device: http://192.168.178.1:49000/l2tpv3.xml 2019-02-23 12:21:18.430 - info: upnp.0 Found new device: http://192.168.178.1:49000/fboxdesc.xml 2019-02-23 12:21:59.659 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:21:59.718 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:21:59.801 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:22:09.676 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:22:09.753 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:22:09.839 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:22:19.696 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:22:19.791 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:22:19.876 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:22:29.753 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:22:30.144 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:22:30.224 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:22:39.719 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:22:40.169 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:22:40.251 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:22:45.622 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:22:45.682 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:22:48.632 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:22:48.644 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:22:49.741 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:22:50.200 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:22:50.291 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:22:51.629 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:22:51.639 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:22:59.753 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:23:09.767 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:23:09.849 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:23:09.865 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:23:19.785 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:23:19.908 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:23:19.920 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:23:29.800 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:23:29.919 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:23:29.933 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:23:39.815 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:23:39.957 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:23:40.068 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:23:49.834 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:23:49.989 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:23:50.206 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:23:59.847 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:24:00.058 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:24:01.675 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:24:09.866 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:24:10.170 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:24:11.711 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:24:19.888 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:24:20.200 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:24:29.896 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:24:29.938 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:24:30.237 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:24:39.911 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:24:39.972 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:24:40.266 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:24:49.935 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:24:50.012 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:24:59.946 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:25:00.070 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:25:00.118 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:25:09.966 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:25:10.083 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:25:10.089 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:25:19.979 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:25:20.115 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:25:20.120 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:25:29.993 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:25:30.140 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:25:30.161 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:25:40.020 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:25:40.184 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:25:40.190 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:25:50.026 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:25:50.222 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:25:50.250 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:26:00.070 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:26:00.258 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:26:00.264 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:26:10.061 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:26:10.287 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:26:10.393 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:26:12.550 - info: upnp.0 Found new device: http://192.168.178.29:80/Canon_basic.xml 2019-02-23 12:26:12.672 - info: upnp.0 Found new device: http://192.168.178.29:80/Canon_basic.xml 2019-02-23 12:26:12.895 - info: upnp.0 Found new device: http://192.168.178.29:80/Canon_basic.xml 2019-02-23 12:26:17.801 - info: upnp.0 Found new device: http://192.168.178.5:49000/fboxdesc.xml 2019-02-23 12:26:20.079 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:26:30.097 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:26:30.159 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:26:30.163 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:26:40.115 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:26:40.183 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:26:40.206 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:26:50.128 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:26:50.206 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:26:50.218 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:27:00.155 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:27:00.283 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:27:00.288 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:27:10.039 - info: upnp.0 Found new device: http://192.168.178.4:49000/igddesc.xml 2019-02-23 12:27:10.056 - info: upnp.0 Found new device: http://192.168.178.4:49000/igddesc.xml 2019-02-23 12:27:10.159 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:27:10.290 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:27:10.399 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:27:11.997 - info: upnp.0 Found new device: http://192.168.178.4:49000/fboxdesc.xml 2019-02-23 12:27:15.031 - info: upnp.0 Found new device: http://192.168.178.4:49000/igd2desc.xml 2019-02-23 12:27:15.040 - info: upnp.0 Found new device: http://192.168.178.4:49000/igd2desc.xml 2019-02-23 12:27:20.174 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:27:20.323 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:27:30.166 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:27:30.236 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:27:30.359 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:27:40.211 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:27:40.216 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:27:44.634 - info: upnp.0 Found new device: http://192.168.178.2:49000/fboxdesc.xml 2019-02-23 12:27:44.646 - info: upnp.0 Found new device: http://192.168.178.2:49000/fboxdesc.xml 2019-02-23 12:27:44.700 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:27:50.211 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:27:50.236 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:27:54.030 - info: upnp.0 Found new device: http://192.168.178.2:49000/igddesc.xml 2019-02-23 12:27:54.050 - info: upnp.0 Found new device: http://192.168.178.2:49000/igddesc.xml 2019-02-23 12:27:54.672 - info: upnp.0 Found new device: http://192.168.178.2:49000/igd2desc.xml 2019-02-23 12:27:54.732 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:28:00.269 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:28:00.301 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:28:03.653 - info: upnp.0 Found new device: http://192.168.178.85:60000/upnp/dev/d8f8059a-306e-21c9-ffff-ffffad7a5c5b/desc 2019-02-23 12:28:03.719 - info: upnp.0 Found new device: http://192.168.178.85:60000/upnp/dev/d8f8059a-306e-21c9-ffff-ffffad7a5c5b/desc 2019-02-23 12:28:06.816 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:28:10.258 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:28:10.306 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:28:16.847 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:28:20.259 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:28:20.340 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:28:30.170 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:28:30.261 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:28:30.379 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:28:40.195 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:28:40.275 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:28:50.232 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:28:50.248 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:28:50.571 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:29:01.333 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:29:01.338 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:29:01.361 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:29:07.081 - info: upnp.0 Found new device: http://192.168.178.3:49000/fboxdesc.xml 2019-02-23 12:29:10.304 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:29:10.347 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:29:10.420 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:29:13.118 - info: upnp.0 Found new device: http://192.168.178.3:49000/igd2desc.xml 2019-02-23 12:29:13.141 - info: upnp.0 Found new device: http://192.168.178.3:49000/igd2desc.xml 2019-02-23 12:29:16.122 - info: upnp.0 Found new device: http://192.168.178.3:49000/igddesc.xml 2019-02-23 12:29:16.144 - info: upnp.0 Found new device: http://192.168.178.3:49000/igddesc.xml 2019-02-23 12:29:20.335 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:29:20.444 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:29:20.551 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:29:22.929 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 12:29:24.127 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 12:29:24.388 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 12:29:25.151 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 12:29:25.976 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 12:29:27.974 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 12:29:29.252 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 12:29:30.352 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:29:30.473 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:29:30.587 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:29:40.372 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:29:40.511 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:29:40.622 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:29:50.393 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:29:50.554 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:29:50.660 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:30:00.632 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:30:00.655 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:30:00.732 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:30:09.628 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:30:09.642 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:30:10.421 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:30:11.755 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:30:11.760 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:30:12.623 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:30:12.632 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:30:15.624 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:30:15.638 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 12:30:20.439 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:30:20.532 - info: upnp.0 Found new device: http://192.168.178.83:60000/upnp/dev/2d122f5a-5b60-57f4-ffff-ffff903158e9/desc 2019-02-23 12:30:20.540 - info: upnp.0 Found new device: http://192.168.49.1:60000/upnp/dev/2d122f5a-5b60-57f4-ffff-ffff903158e9/desc 2019-02-23 12:30:20.875 - info: upnp.0 Found new device: http://192.168.178.83:60000/upnp/dev/2d122f5a-5b60-57f4-ffff-ffff903158e9/desc 2019-02-23 12:30:28.687 - info: upnp.0 Found new device: http://169.254.47.245:2870/dmr_bdp5510.xml 2019-02-23 12:30:28.765 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:30:28.769 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:30:29.252 - info: upnp.0 Found new device: http://169.254.47.245:51000/config.xml 2019-02-23 12:30:30.458 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 12:31:09.436 - info: upnp.0 Found new device: http://192.168.178.1:49000/MediaServerDevDesc.xml 2019-02-23 12:31:17.568 - info: upnp.0 Found new device: http://192.168.178.1:49000/avmnexusdesc.xml 2019-02-23 12:31:17.649 - info: upnp.0 Found new device: http://192.168.178.1:49000/igddesc.xml 2019-02-23 12:31:17.678 - info: upnp.0 Found new device: http://192.168.178.1:49000/igd2desc.xml 2019-02-23 12:31:17.702 - info: upnp.0 Found new device: http://192.168.178.1:49000/l2tpv3.xml 2019-02-23 12:31:18.422 - info: upnp.0 Found new device: http://192.168.178.1:49000/fboxdesc.xml 2019-02-23 12:32:40.240 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 12:32:40.244 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 12:34:01.431 - info: javascript.0 Stop script script.js.common.Message.upnp 2019-02-23 12:34:01.944 - info: host.iobroker instance system.adapter.upnp.0 terminated with code 0 (OK) 2019-02-23 12:58:06.767 - info: history.0 enabled logging of upnp.0.WANDevice_-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.GetAddonInfos.NewTotalBytesReceived (Count=238), Alias=false 2019-02-23 12:58:06.767 - info: history.0 enabled logging of upnp.0.WANDevice_-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.GetAddonInfos.NewTotalBytesSent (Count=239), Alias=false 2019-02-23 12:58:06.767 - info: history.0 enabled logging of upnp.0.WANDevice_-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.GetAddonInfos.NewPacketReceiveRate (Count=240), Alias=false 2019-02-23 12:58:06.768 - info: history.0 enabled logging of upnp.0.WANDevice_-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.GetAddonInfos.NewPacketSendRate (Count=241), Alias=false 2019-02-23 12:58:06.768 - info: history.0 enabled logging of upnp.0.WANDevice_-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.GetAddonInfos.NewByteReceiveRate (Count=242), Alias=false 2019-02-23 12:58:06.768 - info: history.0 enabled logging of upnp.0.WANDevice_-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.GetAddonInfos.NewByteSendRate (Count=243), Alias=false 2019-02-23 12:58:06.768 - info: history.0 enabled logging of upnp.0.WANDevice_-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.GetCommonLinkProperties.NewLayer1DownstreamMaxBitRate (Count=244), Alias=false 2019-02-23 12:58:06.768 - info: history.0 enabled logging of upnp.0.WANDevice_-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.GetCommonLinkProperties.NewLayer1UpstreamMaxBitRate (Count=245), Alias=false 2019-02-23 12:58:47.738 - info: javascript.0 Start javascript script.js.common.Message.upnp 2019-02-23 12:58:47.740 - info: javascript.0 script.js.common.Message.upnp: registered 0 subscriptions and 1 schedule 2019-02-23 13:00:38.367 - info: host.iobroker instance system.adapter.upnp.0 started with pid 8954 2019-02-23 13:00:39.056 - info: upnp.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.upnp, node: v8.15.0 2019-02-23 13:00:39.082 - info: upnp.0 Auto discover: true 2019-02-23 13:01:03.108 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:01:03.150 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:01:03.259 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:01:09.671 - info: upnp.0 Found new device: http://192.168.178.1:49000/MediaServerDevDesc.xml 2019-02-23 13:01:09.684 - info: upnp.0 Found new device: http://192.168.178.1:49000/MediaServerDevDesc.xml 2019-02-23 13:01:13.139 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:01:13.155 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:01:14.918 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:01:17.578 - info: upnp.0 Found new device: http://192.168.178.1:49000/avmnexusdesc.xml 2019-02-23 13:01:17.589 - info: upnp.0 Found new device: http://192.168.178.1:49000/avmnexusdesc.xml 2019-02-23 13:01:17.593 - info: upnp.0 Found new device: http://192.168.178.1:49000/igddesc.xml 2019-02-23 13:01:17.618 - info: upnp.0 Found new device: http://192.168.178.1:49000/igd2desc.xml 2019-02-23 13:01:17.635 - info: upnp.0 Found new device: http://192.168.178.1:49000/l2tpv3.xml 2019-02-23 13:01:18.422 - info: upnp.0 Found new device: http://192.168.178.1:49000/fboxdesc.xml 2019-02-23 13:01:23.141 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:01:23.172 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:01:30.297 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:01:33.157 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:01:33.218 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:01:43.174 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:01:43.199 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:01:43.226 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:01:53.185 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:01:53.244 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:01:53.248 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:02:03.210 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:02:03.286 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:02:03.299 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:02:13.220 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:02:13.301 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:02:13.320 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:02:23.241 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:02:23.336 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:02:23.353 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:02:33.270 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:02:34.647 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:02:34.707 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:02:43.266 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:02:44.657 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:02:44.739 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:02:53.284 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:02:54.667 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:02:54.779 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:03:03.323 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:03:04.726 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:03:04.815 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:03:13.315 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:03:14.763 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:03:14.847 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:03:23.335 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:03:30.279 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:03:30.323 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:03:33.352 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:03:43.359 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:03:43.392 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:03:43.428 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:03:53.383 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:03:53.406 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:03:53.466 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:04:03.395 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:04:03.401 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:04:03.491 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:04:13.404 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:04:13.425 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:04:13.524 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:04:23.421 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:04:23.443 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:04:24.692 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:04:33.432 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:04:33.464 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:04:34.718 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:04:43.453 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:04:43.540 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:04:44.753 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:04:53.465 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:04:53.576 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:05:00.325 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:05:03.473 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:05:04.671 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:05:13.489 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:05:13.584 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:05:14.682 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:05:23.495 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:05:23.561 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:05:24.706 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:05:33.511 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:05:33.604 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:05:34.735 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:05:43.527 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:05:43.633 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:05:44.774 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:05:53.547 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:05:54.691 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:05:54.825 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:05:57.046 - info: upnp.0 Found new device: http://192.168.178.29:80/Canon_basic.xml 2019-02-23 13:05:57.271 - info: upnp.0 Found new device: http://192.168.178.29:80/Canon_basic.xml 2019-02-23 13:05:57.402 - info: upnp.0 Found new device: http://192.168.178.29:80/Canon_basic.xml 2019-02-23 13:06:03.813 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:06:04.731 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:06:06.934 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:06:13.576 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:06:14.764 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:06:16.968 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:06:17.823 - info: upnp.0 Found new device: http://192.168.178.5:49000/fboxdesc.xml 2019-02-23 13:06:23.581 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:06:30.233 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:06:30.337 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:06:33.621 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:06:43.644 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:06:43.650 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:06:43.654 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:06:47.988 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:06:49.555 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:06:50.697 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:06:51.112 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:06:52.491 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:06:52.890 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:06:53.631 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:06:53.649 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:06:53.676 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:07:03.647 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:07:03.668 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:07:03.710 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:07:09.957 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:07:09.975 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:07:10.047 - info: upnp.0 Found new device: http://192.168.178.4:49000/igddesc.xml 2019-02-23 13:07:11.989 - info: upnp.0 Found new device: http://192.168.178.4:49000/fboxdesc.xml 2019-02-23 13:07:11.997 - info: upnp.0 Found new device: http://192.168.178.4:49000/fboxdesc.xml 2019-02-23 13:07:13.275 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:07:13.287 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:07:13.666 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:07:13.681 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:07:13.748 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:07:15.046 - info: upnp.0 Found new device: http://192.168.178.4:49000/igd2desc.xml 2019-02-23 13:07:15.055 - info: upnp.0 Found new device: http://192.168.178.4:49000/igd2desc.xml 2019-02-23 13:07:15.952 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:07:23.682 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:07:23.700 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:07:23.780 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:07:33.698 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:07:33.725 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:07:33.816 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:07:43.724 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:07:43.761 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:07:43.853 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:07:44.633 - info: upnp.0 Found new device: http://192.168.178.2:49000/fboxdesc.xml 2019-02-23 13:07:44.642 - info: upnp.0 Found new device: http://192.168.178.2:49000/fboxdesc.xml 2019-02-23 13:07:53.705 - info: upnp.0 Found new device: http://192.168.178.2:49000/igddesc.xml 2019-02-23 13:07:53.721 - info: upnp.0 Found new device: http://192.168.178.2:49000/igddesc.xml 2019-02-23 13:07:53.769 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:07:53.794 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:07:53.887 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:07:54.690 - info: upnp.0 Found new device: http://192.168.178.2:49000/igd2desc.xml 2019-02-23 13:08:03.748 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:08:03.826 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:08:03.921 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:08:13.771 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:08:13.868 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:08:13.960 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:08:23.781 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:08:24.727 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:08:24.812 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:08:33.791 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:08:34.729 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:08:38.554 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:08:43.799 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:08:44.774 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:08:48.572 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:08:53.815 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:08:54.834 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:09:00.264 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:09:03.834 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:09:07.090 - info: upnp.0 Found new device: http://192.168.178.3:49000/fboxdesc.xml 2019-02-23 13:09:07.105 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:09:13.132 - info: upnp.0 Found new device: http://192.168.178.3:49000/igd2desc.xml 2019-02-23 13:09:13.156 - info: upnp.0 Found new device: http://192.168.178.3:49000/igd2desc.xml 2019-02-23 13:09:13.171 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:09:13.846 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:09:16.123 - info: upnp.0 Found new device: http://192.168.178.3:49000/igddesc.xml 2019-02-23 13:09:16.141 - info: upnp.0 Found new device: http://192.168.178.3:49000/igddesc.xml 2019-02-23 13:09:23.861 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:09:23.907 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:09:23.911 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:09:33.881 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:09:33.933 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:09:33.940 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:09:43.892 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:09:43.968 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:09:43.980 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:09:53.899 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:09:54.025 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:09:54.030 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:10:03.918 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:10:04.760 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:10:04.766 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:10:13.933 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:10:14.791 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:10:14.829 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:10:23.949 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:10:24.827 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:10:24.853 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:10:33.988 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:10:43.978 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:10:44.000 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:10:44.087 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:10:53.994 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:10:54.029 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:10:54.112 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:11:04.009 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:11:04.066 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:11:04.147 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:11:09.571 - info: upnp.0 Found new device: http://192.168.178.1:49000/MediaServerDevDesc.xml 2019-02-23 13:11:14.030 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:11:14.094 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:11:14.182 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:11:17.581 - info: upnp.0 Found new device: http://192.168.178.1:49000/avmnexusdesc.xml 2019-02-23 13:11:17.597 - info: upnp.0 Found new device: http://192.168.178.1:49000/igddesc.xml 2019-02-23 13:11:17.624 - info: upnp.0 Found new device: http://192.168.178.1:49000/igd2desc.xml 2019-02-23 13:11:17.642 - info: upnp.0 Found new device: http://192.168.178.1:49000/l2tpv3.xml 2019-02-23 13:11:18.421 - info: upnp.0 Found new device: http://192.168.178.1:49000/fboxdesc.xml 2019-02-23 13:11:24.050 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:11:24.128 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:11:24.216 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:11:34.074 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:11:34.165 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:11:34.253 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:11:44.071 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:11:44.874 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:11:44.903 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:11:54.086 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:11:55.024 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:11:55.031 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:12:04.152 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:12:06.999 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:12:07.022 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:12:14.122 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:12:17.069 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:12:17.074 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:12:24.136 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:12:30.269 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:12:30.274 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:12:34.148 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:12:44.165 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:12:44.180 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:12:44.202 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:12:54.193 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:12:54.199 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:12:54.232 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:13:04.196 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:13:04.232 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:13:04.264 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:13:09.935 - info: upnp.0 Found new device: http://192.168.178.85:60000/upnp/dev/d8f8059a-306e-21c9-ffff-ffffad7a5c5b/desc 2019-02-23 13:13:10.089 - info: upnp.0 Found new device: http://192.168.178.85:60000/upnp/dev/d8f8059a-306e-21c9-ffff-ffffad7a5c5b/desc 2019-02-23 13:13:10.240 - info: upnp.0 Found new device: http://192.168.178.85:60000/upnp/dev/d8f8059a-306e-21c9-ffff-ffffad7a5c5b/desc 2019-02-23 13:13:14.211 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:13:14.311 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:13:14.317 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:13:24.226 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:13:24.335 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:13:24.356 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:13:34.244 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:13:34.868 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:13:34.882 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:13:44.262 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:13:44.903 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:13:44.923 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:13:54.270 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:13:54.954 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:13:54.973 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:13:58.728 - info: upnp.0 Found new device: http://169.254.47.245:2870/dmr_bdp5510.xml 2019-02-23 13:13:59.596 - info: upnp.0 Found new device: http://169.254.47.245:51000/config.xml 2019-02-23 13:14:04.284 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:14:06.982 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:14:07.035 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:14:33.954 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:15:27.544 - info: upnp.0 Found new device: http://192.168.178.83:60000/upnp/dev/2d122f5a-5b60-57f4-ffff-ffff903158e9/desc 2019-02-23 13:15:27.554 - info: upnp.0 Found new device: http://192.168.49.1:60000/upnp/dev/2d122f5a-5b60-57f4-ffff-ffff903158e9/desc 2019-02-23 13:15:34.892 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:16:17.824 - info: upnp.0 Found new device: http://192.168.178.5:49000/fboxdesc.xml 2019-02-23 13:16:19.074 - info: upnp.0 Found new device: http://192.168.178.29:80/Canon_basic.xml 2019-02-23 13:17:10.063 - info: upnp.0 Found new device: http://192.168.178.4:49000/igddesc.xml 2019-02-23 13:17:11.999 - info: upnp.0 Found new device: http://192.168.178.4:49000/fboxdesc.xml 2019-02-23 13:17:15.036 - info: upnp.0 Found new device: http://192.168.178.4:49000/igd2desc.xml 2019-02-23 13:17:44.677 - info: upnp.0 Found new device: http://192.168.178.2:49000/fboxdesc.xml 2019-02-23 13:17:53.676 - info: upnp.0 Found new device: http://192.168.178.2:49000/igddesc.xml 2019-02-23 13:17:54.711 - info: upnp.0 Found new device: http://192.168.178.2:49000/igd2desc.xml 2019-02-23 13:18:24.683 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:18:24.815 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:18:24.820 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:19:07.089 - info: upnp.0 Found new device: http://192.168.178.3:49000/fboxdesc.xml 2019-02-23 13:19:13.119 - info: upnp.0 Found new device: http://192.168.178.3:49000/igd2desc.xml 2019-02-23 13:19:16.119 - info: upnp.0 Found new device: http://192.168.178.3:49000/igddesc.xml 2019-02-23 13:20:34.890 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:20:45.002 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:20:45.050 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:20:45.054 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:20:54.913 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:20:55.114 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:20:55.121 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:21:04.934 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:21:09.453 - info: upnp.0 Found new device: http://192.168.178.1:49000/MediaServerDevDesc.xml 2019-02-23 13:21:09.468 - info: upnp.0 Found new device: http://192.168.178.1:49000/MediaServerDevDesc.xml 2019-02-23 13:21:09.476 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:21:09.478 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:21:14.945 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:21:17.570 - info: upnp.0 Found new device: http://192.168.178.1:49000/avmnexusdesc.xml 2019-02-23 13:21:17.581 - info: upnp.0 Found new device: http://192.168.178.1:49000/avmnexusdesc.xml 2019-02-23 13:21:17.583 - info: upnp.0 Found new device: http://192.168.178.1:49000/igddesc.xml 2019-02-23 13:21:17.610 - info: upnp.0 Found new device: http://192.168.178.1:49000/igd2desc.xml 2019-02-23 13:21:17.630 - info: upnp.0 Found new device: http://192.168.178.1:49000/l2tpv3.xml 2019-02-23 13:21:18.419 - info: upnp.0 Found new device: http://192.168.178.1:49000/fboxdesc.xml 2019-02-23 13:21:24.958 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:21:25.017 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:21:25.022 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:21:34.984 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:21:35.049 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:21:35.055 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:21:44.990 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:21:45.074 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:21:45.091 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:21:55.006 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:21:55.110 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:21:55.129 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:21:58.045 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:21:58.064 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:22:01.045 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:22:01.056 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:22:04.045 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:22:04.054 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:22:05.015 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:22:07.102 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:22:07.108 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:22:15.032 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:22:17.133 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:22:17.137 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:22:25.116 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:22:30.523 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:22:30.531 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:22:35.101 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:22:45.092 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:22:45.097 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:22:45.100 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:22:55.100 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:22:55.126 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:22:55.129 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:23:05.103 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:23:05.154 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:23:05.167 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:23:15.115 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:23:15.195 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:23:15.200 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:23:25.169 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:23:25.221 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:23:25.237 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:23:35.144 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:23:35.262 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:23:35.267 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:23:45.159 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:23:55.055 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:23:55.122 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:23:55.189 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:24:05.057 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:24:05.158 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:24:05.190 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:24:15.075 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:24:15.205 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:24:15.297 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:24:25.141 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:24:25.206 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:24:30.583 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:24:35.172 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:24:35.240 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:24:45.179 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:24:45.221 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:24:45.246 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:24:55.129 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:24:55.241 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:24:55.260 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:25:05.167 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:25:05.266 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:25:05.283 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:25:15.284 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:25:15.307 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:25:15.311 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:25:25.300 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:25:25.342 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:25:25.346 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:25:35.321 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:25:35.380 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:25:35.383 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:25:45.330 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:25:45.418 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:25:45.423 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:25:55.348 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:25:55.456 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:25:55.462 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:26:05.358 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:26:07.054 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:26:07.115 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:26:08.470 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:26:09.252 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:26:09.518 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:26:10.031 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:26:11.813 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:26:12.841 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:26:13.097 - info: upnp.0 Found new device: http://192.168.178.81:8080/description.xml 2019-02-23 13:26:15.374 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:26:17.203 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:26:17.216 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:26:17.830 - info: upnp.0 Found new device: http://192.168.178.5:49000/fboxdesc.xml 2019-02-23 13:26:25.390 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:26:30.508 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:26:30.515 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:26:35.408 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:26:45.079 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:26:45.108 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:26:45.422 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:26:50.617 - info: upnp.0 Found new device: http://192.168.178.29:80/Canon_basic.xml 2019-02-23 13:26:50.809 - info: upnp.0 Found new device: http://192.168.178.29:80/Canon_basic.xml 2019-02-23 13:26:55.097 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:26:55.145 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:26:55.436 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:27:05.120 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:27:05.188 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:27:05.448 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:27:10.034 - info: upnp.0 Found new device: http://192.168.178.4:49000/igddesc.xml 2019-02-23 13:27:10.047 - info: upnp.0 Found new device: http://192.168.178.4:49000/igddesc.xml 2019-02-23 13:27:11.990 - info: upnp.0 Found new device: http://192.168.178.4:49000/fboxdesc.xml 2019-02-23 13:27:11.998 - info: upnp.0 Found new device: http://192.168.178.4:49000/fboxdesc.xml 2019-02-23 13:27:15.031 - info: upnp.0 Found new device: http://192.168.178.4:49000/igd2desc.xml 2019-02-23 13:27:15.043 - info: upnp.0 Found new device: http://192.168.178.4:49000/igd2desc.xml 2019-02-23 13:27:15.130 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:27:15.212 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:27:15.473 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:27:25.166 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:27:25.271 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:27:25.474 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:27:35.196 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:27:35.284 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:27:35.525 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:27:44.634 - info: upnp.0 Found new device: http://192.168.178.2:49000/fboxdesc.xml 2019-02-23 13:27:44.644 - info: upnp.0 Found new device: http://192.168.178.2:49000/fboxdesc.xml 2019-02-23 13:27:45.508 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:27:45.535 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:27:45.538 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:27:53.675 - info: upnp.0 Found new device: http://192.168.178.2:49000/igddesc.xml 2019-02-23 13:27:53.689 - info: upnp.0 Found new device: http://192.168.178.2:49000/igddesc.xml 2019-02-23 13:27:54.677 - info: upnp.0 Found new device: http://192.168.178.2:49000/igd2desc.xml 2019-02-23 13:27:55.524 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:27:55.569 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:27:55.572 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:28:05.737 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:28:05.752 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:28:05.755 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:28:10.155 - info: upnp.0 Found new device: http://192.168.178.85:60000/upnp/dev/d8f8059a-306e-21c9-ffff-ffffad7a5c5b/desc 2019-02-23 13:28:10.303 - info: upnp.0 Found new device: http://192.168.178.85:60000/upnp/dev/d8f8059a-306e-21c9-ffff-ffffad7a5c5b/desc 2019-02-23 13:28:10.460 - info: upnp.0 Found new device: http://192.168.178.85:60000/upnp/dev/d8f8059a-306e-21c9-ffff-ffffad7a5c5b/desc 2019-02-23 13:28:15.550 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:28:15.659 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:28:15.665 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:28:25.568 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:28:25.674 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:28:25.679 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:28:28.715 - info: upnp.0 Found new device: http://169.254.47.245:2870/dmr_bdp5510.xml 2019-02-23 13:28:29.654 - info: upnp.0 Found new device: http://169.254.47.245:51000/config.xml 2019-02-23 13:28:35.590 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml 2019-02-23 13:28:45.123 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:28:45.126 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:29:07.078 - info: upnp.0 Found new device: http://192.168.178.3:49000/fboxdesc.xml 2019-02-23 13:29:13.123 - info: upnp.0 Found new device: http://192.168.178.3:49000/igd2desc.xml 2019-02-23 13:29:16.123 - info: upnp.0 Found new device: http://192.168.178.3:49000/igddesc.xml 2019-02-23 13:29:22.048 - info: upnp.0 Found new device: http://192.168.178.39:2869/upnphost/udhisapi.dll?content=uuid:d025603c-1641-42b5-bccd-a3375e87ee37 2019-02-23 13:30:31.762 - info: upnp.0 Found new device: http://192.168.178.83:60000/upnp/dev/2d122f5a-5b60-57f4-ffff-ffff903158e9/desc 2019-02-23 13:30:31.804 - info: upnp.0 Found new device: http://192.168.49.1:60000/upnp/dev/2d122f5a-5b60-57f4-ffff-ffff903158e9/desc 2019-02-23 13:31:09.438 - info: upnp.0 Found new device: http://192.168.178.1:49000/MediaServerDevDesc.xml 2019-02-23 13:31:17.570 - info: upnp.0 Found new device: http://192.168.178.1:49000/avmnexusdesc.xml 2019-02-23 13:31:17.584 - info: upnp.0 Found new device: http://192.168.178.1:49000/igddesc.xml 2019-02-23 13:31:17.622 - info: upnp.0 Found new device: http://192.168.178.1:49000/igd2desc.xml 2019-02-23 13:31:17.655 - info: upnp.0 Found new device: http://192.168.178.1:49000/l2tpv3.xml 2019-02-23 13:31:18.421 - info: upnp.0 Found new device: http://192.168.178.1:49000/fboxdesc.xml 2019-02-23 13:32:55.200 - info: upnp.0 Found new device: http://192.168.178.28:80/plugin/discovery/discovery.xml 2019-02-23 13:32:55.205 - info: upnp.0 Found new device: http://192.168.178.32:80/plugin/discovery/discovery.xml 2019-02-23 13:32:56.154 - info: upnp.0 Found new device: http://192.168.178.34:80/plugin/discovery/discovery.xml

Fehlerlog

Hallo,

bekomme seit neuesten Fehlermeldung:

`

host.Medion 2018-08-13 16:47:10.226 error instance system.adapter.upnp.0 terminated with code 0 (OK)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at WS.Transport.onPacket (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\engine.io-client\lib\transport.js:145:8)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at WS.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at WS. (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\engine.io-client\lib\socket.js:273:10)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Socket.onPacket (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\engine.io-client\lib\socket.js:456:14)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Socket.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Socket. (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-bind\index.js:21:15)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Manager.ondata (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\manager.js:335:16)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Decoder.add (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\socket.io-parser\index.js:251:12)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Decoder.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Decoder. (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-bind\index.js:21:15)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Manager.ondecoded (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\manager.js:345:8)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Manager.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Manager. (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-bind\index.js:21:15)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Socket.onpacket (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\socket.js:244:12)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Socket.onack (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\socket.js:319:9)
Caught 2018-08-13 16:47:10.226 error by controller[0]: at Socket. (C:\ioBroker\node_modules\iobroker.upnp\main.js:1700:44)
Caught 2018-08-13 16:47:10.226 error by controller[0]: TypeError: Cannot read property 'native' of null
upnp.0 2018-08-13 16:47:10.211 info terminating
upnp.0 2018-08-13 16:47:10.211 error at WS.Transport.onPacket (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\engine.io-client\lib\transport.js:145:8)
upnp.0 2018-08-13 16:47:10.211 error at WS.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
upnp.0 2018-08-13 16:47:10.211 error at WS. (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\engine.io-client\lib\socket.js:273:10)
upnp.0 2018-08-13 16:47:10.211 error at Socket.onPacket (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\engine.io-client\lib\socket.js:456:14)
upnp.0 2018-08-13 16:47:10.211 error at Socket.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
upnp.0 2018-08-13 16:47:10.211 error at Socket. (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-bind\index.js:21:15)
upnp.0 2018-08-13 16:47:10.211 error at Manager.ondata (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\manager.js:335:16)
upnp.0 2018-08-13 16:47:10.211 error at Decoder.add (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\socket.io-parser\index.js:251:12)
upnp.0 2018-08-13 16:47:10.211 error at Decoder.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
upnp.0 2018-08-13 16:47:10.211 error at Decoder. (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-bind\index.js:21:15)
upnp.0 2018-08-13 16:47:10.211 error at Manager.ondecoded (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\manager.js:345:8)
upnp.0 2018-08-13 16:47:10.211 error at Manager.Emitter.emit (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
upnp.0 2018-08-13 16:47:10.211 error at Manager. (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\node_modules\component-bind\index.js:21:15)
upnp.0 2018-08-13 16:47:10.211 error at Socket.onpacket (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\socket.js:244:12)
upnp.0 2018-08-13 16:47:10.211 error at Socket.onack (C:\ioBroker\node_modules\iobroker.js-controller\node_modules\socket.io-client\lib\socket.js:319:9)
upnp.0 2018-08-13 16:47:10.211 error at Socket. (C:\ioBroker\node_modules\iobroker.upnp\main.js:1700:44)
upnp.0 2018-08-13 16:47:10.211 error TypeError: Cannot read property 'native' of null
upnp.0 2018-08-13 16:47:10.211 error uncaught exception: Cannot read property 'native' of null
alexa2.0 2018-08-13 16:47:04.871 debug system.adapter.admin.0: logging false

`

DRM Key request

Hallo!
I installed the upnp adapter and discovered some states named >>DRMType<<. Is there a possibility to get the DRM Key of my Samsung Smart TV without rooting the TV? The TV is in the object list. I need the key for encrypting the recorded videos via USB.
Thanks for your answer!
PS: Its a Samsung Smart TV of the F series.

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.upnp

  • [E154] common.dependencies must contain{"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
  • [E506] "admin/jsonCustom.json" not found, but custom support is declared
  • [E605] No actual year found in copyright. Please add "Copyright (c) 2016-2022 Jey Cee [email protected]" at the end of README.md
  • [E701] No actual year found in LICENSE. Please add "Copyright (c) 2016-2022 Jey Cee [email protected]" at the start of LICENSE

I have also found warnings that may be fixed if possible.

  • [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

Fehler jsonConfig

Hallo, Fehler jsonConfig kommt noch immer.

Screenshot (3926)

Plattform: Windows RAM: 16 GB Node.js: 12.22.1 NPM: 6.14.12 JS Controller: 3.3.14 Admin: 5.1.9 Web: 3.4.3 Socket.io: 3.1.4 Script Engine: 5.2.0

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/Jey-Cee/ioBroker.upnp

I have also found warnings that may be fixed if possible.

  • [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

An in-range update of portfinder is breaking the build 🚨


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The dependency portfinder was updated from 1.0.25 to 1.0.26.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

portfinder is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 5 commits.

  • 3709e43 1.0.26
  • e40deb2 Merge pull request #101 from msbit/mkdirp-0.5.5
  • 891ba80 mkdirp: 0.5.5
  • cd08663 Merge pull request #96 from kwiatkk1/repo_url_links_updated
  • 479a8e2 #94: update links after repo moved to a new org

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Adapter crash if section 'USN' is not defined in header

While autodiscover crash the adapter if in the header the section 'USN' is not defined.

2017-12-28 12:19:25.547 - �[32minfo�[39m: upnp.0 ***TEST***{"HOST":"239.255.255.250:1900","CACHE-CONTROL":"max-age=5000","LOCATION":"http://192.168.137.50/upnp/basic_dev.cgi","NTS":"ssdp:alive","SERVER":"HomeMatic","NT":"upnp:rootdevice"} 2017-12-28 12:19:25.609 - �[31merror�[39m: upnp.0 uncaught exception: Cannot read property 'toString' of undefined 2017-12-28 12:19:25.613 - �[31merror�[39m: upnp.0 TypeError: Cannot read property 'toString' of undefined at SsdpServer.<anonymous> (C:\ioBroker\node_modules\iobroker.upnp\main.js:1061:14) at emitOne (events.js:96:13) at SsdpServer.emit (events.js:188:7) at SsdpServer.SSDP._notify (C:\ioBroker\node_modules\iobroker.upnp\node_modules\node-ssdp\lib\index.js:256:12) at SsdpServer.parseCommand [as _parseCommand] (C:\ioBroker\node_modules\iobroker.upnp\node_modules\node-ssdp\lib\index.js:227:12) at SsdpServer.SSDP._parseMessage (C:\ioBroker\node_modules\iobroker.upnp\node_modules\node-ssdp\lib\index.js:210:10) at Socket.onSocketMessage (C:\ioBroker\node_modules\iobroker.upnp\node_modules\node-ssdp\lib\index.js:163:10) at emitTwo (events.js:106:13) at Socket.emit (events.js:191:7) at UDP.onMessage (dgram.js:548:8) 2017-12-28 12:19:25.625 - �[32minfo�[39m: upnp.0 Alive and sid states cleared 2017-12-28 12:19:25.626 - �[32minfo�[39m: upnp.0 cleaned everything up... 2017-12-28 12:19:25.841 - �[32minfo�[39m: upnp.0 terminating

To log the header I've modified the code in main.js:

server.on('advertise-alive', function (headers) { var usn = JSON.stringify(headers['USN']); if (typeof(usn)=="undefined") { adapter.log.info("***TEST***" + JSON.stringify(headers)); } usn = usn.toString();

Repository rename

Repository should be renamed into ioBroker.upnp-discovery

Don't you want to rename into just ioBroker.upnp?

Please check ioBroker.upnp with js-controller 2.0

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

adapter crashing after "upnp.0 firstDevLookup for undefined"

After a fresh install, the adapter seem to collect all necessary information for all of my UPNP devices, but then afterwards crashes with the following backtrace:

[...]
2017-02-18 21:05:46.923  - info: upnp.0 Found 20 devices
2017-02-18 21:05:46.923  - info: upnp.0 firstDevLookup for undefined
2017-02-18 21:05:46.927  - error: upnp.0 uncaught exception: undefined is not a valid uri or options object.
2017-02-18 21:05:46.929  - error: upnp.0 Error: undefined is not a valid uri or options object.
    at request (/opt/iobroker/node_modules/iobroker.upnp/node_modules/request/index.js:46:11)
    at firstDevLookup (/opt/iobroker/node_modules/iobroker.upnp/main.js:171:5)
    at null._onTimeout (/opt/iobroker/node_modules/iobroker.upnp/main.js:135:9)
    at Timer.listOnTimeout (timers.js:92:15)
2017-02-18 21:05:51.593  - ESC[31merrorESC[39m: host.bilbo instance system.adapter.upnp.0 terminated with code 0 (OK)

Please note that in https://github.com/Jey-Cee/ioBroker.upnp/blob/master/main.js#L135 you are calling firstDevLookup() with the adapter.config.rootXMLurl parameter, but here it is actually empty per default, thus undefined. What should I enter here?

refactoring: 1.0.4 update of objects?

Version 1.0.4 - something changed with the update of the objects?
Send - command does not work anymore, and with the button "request" in the objects nothing happens..

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.upnp

I have also found warnings that may be fixed if possible.

  • [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

Migrate custom_m.html to new JsonConfig

We were able to hold the HTML style confog pages - especially for the custom configurations working for many years and admin versions now. With the rewrite of Admin in React we need to break this functionaliyt because it will not be possible to integrate "html snipets" that way as in the past.

Admin5 allows to specify the fields in a JSON format and all the rest is handled by the Admin itsefl. This new format is optional for the normal admin configuration dialog,but mandatory for the custom configuration!!

The JSON format is described in https://github.com/ioBroker/ioBroker.admin/blob/master/src-rx/src/components/JsonConfigComponent/SCHEMA.md and we will also having soon a JSON-Schema for it hopefully. Also Adapters like sql, influxdb, history and telegram are already migrated and could be used to see an example (see admin folder).

If you use special components (Tables or other "non standard field types) or you need support on how to best migrate special needs that are not available in the specification above please open an isue in admin and describe exactly what you need and how it should behave - or implement it in admin react and provide a PR.

You can test it yourself by using the react GUI from Admin 5.

Thank you for your support. It would be awesome if you could find time to check and implement this within the next 2 weeks. Please responde if you can not do that, then we can think about supportive options.

Please use ioBroker/ioBroker.admin#692 for any questions!

Update stable version in repo to 1.0.14

Think about update stable version to 1.0.14

Version: stable=1.0.11 (362 days old) => latest=1.0.14 (213 days old)
Installs: stable=924 (53.26%), latest=627 (36.14%), total=1735
Click to edit

Release script: Action required

Hi, it looks like you are using @alcalzone/release-script to manage your releases.
When updating to the latest version, you need to remove the following line from your .github/workflows/test-and-release.yml if you want the releases to keep working:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/master' &&
      startsWith(github.ref, 'refs/tags/v')

It may also look like this one:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/main' &&
      startsWith(github.ref, 'refs/tags/v')

An in-range update of xml2js is breaking the build 🚨

The dependency xml2js was updated from 0.4.19 to 0.4.20.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

xml2js is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Warnings for obj.common.type

Getting the following errors:

2020-06-03 21:02:10.290 - warn: admin.0 (1082) Object upnp.0.WANDevice-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.TotalBytesReceived is invalid: obj.common.type has an invalid value (ui4) but has to be one of number, string, boolean, array, object, mixed, file, json

2020-06-03 21:02:10.291 - warn: admin.0 (1082) This object will not be created in future versions. Please report this to the developer.

2020-06-03 21:02:14.101 - warn: admin.0 (1082) Object upnp.0.WANDevice_-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.TotalBytesSent is invalid: obj.common.type has an invalid value (ui4) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-06-03 21:02:14.101 - warn: admin.0 (1082) This object will not be created in future versions. Please report this to the developer.

2020-06-03 21:02:42.426 - warn: admin.0 (1082) Object upnp.0.WANConnectionDevice_-_FRITZ!Box_7590.WANDevice.WANConnectionDevice.WANIPConnection.Uptime is invalid: obj.common.type has an invalid value (ui4) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-06-03 21:02:42.426 - warn: admin.0 (1082) This object will not be created in future versions. Please report this to the developer.

2020-06-03 21:02:47.679 - warn: admin.0 (1082) Object upnp.0.WANDevice_-_FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.ByteReceiveRate is invalid: obj.common.type has an invalid value (ui4) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-06-03 21:02:47.680 - warn: admin.0 (1082) This object will not be created in future versions. Please report this to the developer.

2020-06-03 21:02:51.048 - warn: admin.0 (1082) Object upnp.0.WANDevice_-FRITZ!Box_7590.WANDevice.WANCommonInterfaceConfig.ByteSendRate is invalid: obj.common.type has an invalid value (ui4) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-06-03 21:02:51.048 - warn: admin.0 (1082) This object will not be created in future versions. Please report this to the developer.

Adapterversion: 1.0.16
node: v10.20.1
js-controller: 3.0.20

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Remove old custom view from io-package

Hi, because already migrated to system/custom the old definition can be removed

"objects": [
{
"_id": "_design/custom",
"language": "javascript",
"views": {
"state": {
"map": "function(doc) { doc.type === 'state' && doc.common && doc.common.custom && emit(doc._id, doc.common.custom) }"
}
}
}
],

Compatibility check and testing for Node.js 14 and 16

Dear Adapter developer,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

warnings upnp 1.0.15

some warnings at my LG TV:
019-10-25 16:48:20.673 - warn: upnp.0 (29721) Subscription error: {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"192.168.178.82","port":1843} 2019-10-25 16:48:20.673 - warn: upnp.0 (29721) Subscription error: {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"192.168.178.82","port":1843} 2019-10-25 16:48:20.674 - warn: upnp.0 (29721) Subscription error: {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"192.168.178.82","port":1843} 2019-10-25 16:48:20.674 - warn: upnp.0 (29721) Subscription error: {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"192.168.178.82","port":1843}
some warnings at my Canon printer:
2019-10-25 16:43:07.776 - warn: upnp.0 (29721) Subscription error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.178.29","port":80} 2019-10-25 16:43:07.776 - warn: upnp.0 (29721) Subscription error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.178.29","port":80}
hmm and from Fritzbox:
2019-10-25 15:09:15.560 - warn: upnp.0 (29721) 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/soap/encoding/\">\n<s:Body>\n<s:Fault>\n<faultcode>s:Client</faultcode>\n<faultstring>UPnPError</faultstring>\n<detail>\n<UPnPError xmlns=\"urn:schemas-upnp-org:control-1-0\">\n<errorCode>401</errorCode>\n<errorDescription>invalid action</errorDescription>\n</UPnPError>\n</detail>\n</s:Fault>\n</s:Body>\n</s:Envelope>","headers":{"date":"Fri, 25 Oct 2019 13:09:15 GMT","server":"FRITZ!Box 7590 UPnP/1.0 AVM FRITZ!Box 7590 154.07.12","connection":"close","content-length":"433","content-type":"text/xml; charset=\"utf-8\""},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.0.1:49000","port":"49000","hostname":"192.168.0.1","hash":null,"search":null,"query":null,"pathname":"/MediaServer/ServerStatus/Control","path":"/MediaServer/ServerStatus/Control","href":"http://192.168.0.1:49000/MediaServer/ServerStatus/Control"},"method":"POST","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:avm.de:service:AVM_ServerStatus:1#ScanInfo\"","USER-AGENT":"UPnP/1.0, ioBroker.upnp","content-length":259}}} Sent message: {"uri":"http://192.168.0.1:49000/MediaServer/ServerStatus/Control","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:avm.de:service:AVM_ServerStatus:1#ScanInfo\"","USER-AGENT":"UPnP/1.0, ioBroker.upnp"},"method":"POST","body":" \n <s:Envelope s:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\" xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\">\n <s:Body><u:ScanInfo xmlns:u=\"urn:avm.de:service:AVM_ServerStatus:1\"></u:ScanInfo></s:Body>\n </s:Envelope>"} 2019-10-25 15:10:08.026 - warn: upnp.0 (29721) Unexpected answer from upnp service: {"statusCode":500,"body":"<?xml version=\"1.0\" encoding=\"utf-8\"?><s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\" s:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError xmlns=\"urn:schemas-upnp-org:control-1-0\"><errorCode>402</errorCode><errorDescription>Invalid Args</errorDescription></UPnPError></detail></s:Fault></s:Body></s:Envelope>\r\n","headers":{"content-length":"436","content-type":"text/xml; charset=\"utf-8\"","connection":"close","ext":"","server":"Canon IJ-UPnP/1.0 UPnP/1.0 UPnP-Device-Host/1.0"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.29:80","port":"80","hostname":"192.168.178.29","hash":null,"search":null,"query":null,"pathname":"/upnp/control/DPSConnectionManager","path":"/upnp/control/DPSConnectionManager","href":"http://192.168.178.29:80/upnp/control/DPSConnectionManager"},"method":"POST","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-cipa-jp:service:DPSConnectionManager:1#ConnectionRequest\"","USER-AGENT":"UPnP/1.0, ioBroker.upnp","content-length":337}}} Sent message: {"uri":"http://192.168.178.29:80/upnp/control/DPSConnectionManager","headers":{"Content-Type":"text/xml; charset=\"utf-8\"","SOAPAction":"\"urn:schemas-cipa-jp:service:DPSConnectionManager:1#ConnectionRequest\"","USER-AGENT":"UPnP/1.0, ioBroker.upnp"},"method":"POST","body":" \n <s:Envelope s:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\" xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\">\n <s:Body><u:ConnectionRequest xmlns:u=\"urn:schemas-cipa-jp:service:DPSConnectionManager:1\"><PTPResponderIPAddress></PTPResponderIPAddress></u:ConnectionRequest></s:Body>\n </s:Envelope>"}

js-controller 2.0.35, nodejs 10.6.13, npm 6.12.0, admin 3.6.10

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

please check Adapter with js-controller 3.x

`

host.ioB-D10 2020-04-13 11:34:06.032 info "system.adapter.upnp.0" disabled
upnp.0 2020-04-13 11:33:53.367 warn (9502) This value will not be set in future versions. Please report this to the developer.
upnp.0 2020-04-13 11:33:53.366 warn (9502) State value to set is invalid for upnp.0.WANConnectionDevice.WANDevice.WANConnectionDevice.Alive: The state property "expire" has the wrong type "string" (should be "number")!
upnp.0 2020-04-13 11:33:35.665 warn (9502) This object will not be created in future versions. Please report this to the developer.
upnp.0 2020-04-13 11:33:35.664 warn (9502) Object upnp.0.LichtKueche.controllee.basicevent.BinaryState is invalid: obj.common.type has an invalid value (bool) but has to be one of number, string, boolean, array, object, mixed, file, js
upnp.0 2020-04-13 11:33:17.393 warn (9502) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
host.ioB-D10 2020-04-13 11:33:16.188 info instance system.adapter.upnp.0 started with pid 9502
host.ioB-D10 2020-04-13 11:33:16.177 info "system.adapter.upnp.0" enabled

`

[Bug]: Infos after js-controller 3.3.15

Contact Details

[email protected]

What happened?

A bug happened!
Everytime there are Log entries "you should change the type"-> has to be type "number" but received type "string"

Adapter Version

1.0.19

JS-Controller Version

3.3.15

Node JS Version

12.22.6

NPM Version

6.14.15

Operating System

Debian

Relevant log output

`
<html>
<body>
<!--StartFragment-->

upnp.0 | 2021-08-31 21:40:00.781 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.ByteSendRate" has to be type "number" but received type "string"
-- | -- | -- | --
upnp.0 | 2021-08-31 21:40:00.763 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.708 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.PacketSendRate" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.690 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.673 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.620 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.603 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.545 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.400 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has to be type "boolean" but received type "string"
upnp.0 | 2021-08-31 21:40:00.329 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has to be type "number" but received type "string"

<!--EndFragment-->
</body>
</html>`

Anything else?

No response

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.upnp

  • [E154] common.dependencies must contain{"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
  • [E506] "admin/jsonCustom.json" not found, but custom support is declared
  • [E605] No actual year found in copyright. Please add "Copyright (c) 2016-2022 Jey Cee [email protected]" at the end of README.md
  • [E701] No actual year found in LICENSE. Please add "Copyright (c) 2016-2022 Jey Cee [email protected]" at the start of LICENSE

I have also found warnings that may be fixed if possible.

  • [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

[Bug]: Adapter seems to create wrong url

Contact Details

No response

What happened?

As written in https://forum.iobroker.net/topic/51767/vorlage-upnp-media-player/10?_=1643386555921 the adapter seems to create a wrong url.
Attached wanted Objekt AVTransport.

2022-01-28 - 17_18 - Objekte - upnp.0.1__OG_-Salon-_Internetradio.MediaRenderer.AVTransport.txt

Adapter Version

1.0.20

JS-Controller Version

3.3.22

Node JS Version

v14.18.2

NPM Version

6.14.15

Operating System

Ubuntu

Relevant log output

No response

Anything else?

No response

An in-range update of snyk is breaking the build 🚨


🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io


The dependency snyk was updated from 1.320.2 to 1.320.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v1.320.3

1.320.3 (2020-05-13)

Bug Fixes

  • enable mvn plugin logging when running with -d (5414755)
Commits

The new version differs by 6 commits.

  • 6e7fb38 Merge pull request #1119 from snyk/fix/enable-mvn-logging
  • 5414755 fix: enable mvn plugin logging when running with -d
  • 505720d Merge pull request #1117 from snyk/chore/release-notes-review-fix
  • 649c770 chore: release notes preview fix.
  • 6e448ca Merge pull request #1114 from snyk/chore/run-tests-on-linux
  • a67adee chore: update test:acceptance include root tests

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Missing datapoints warning after host update

Describe the bug
The Upnp Adapter is missing datapoints for future version and is creating log warn messages (just like many other adapters)

To Reproduce
Steps to reproduce the behavior:
Install v 1.0.17 with host 3.2.16 and monitor log

Expected behavior
create update containing missing objects

Screenshots & Logfiles

upnp.0 | 2021-04-07 12:52:30.962 | warn | (13013) State "upnp.0.WANDevice_-_FRITZ!Box_Fon_WLAN_7390.WANDevice.WANCommonInterfaceConfig.GetAddonInfos.NewX_AVM_DE_TotalBytesSent64" has no existing object, this might lead to an error in future v

[Bug]: Log-Outpu "Error: Error: Non-whitespace before first tag.Line: 0Column: 1Char: s"

Contact Details

No response

What happened?

After adapter starts, you find the message two times in the log-file:
Error: Error: Non-whitespace before first tag.Line: 0Column: 1Char: s

Adapter Version

1.0.20

JS-Controller Version

3.3.22

Node JS Version

v14.18.2

NPM Version

6.14.15

Operating System

Ubuntu

Relevant log output

upnp.0
	2022-01-25 12:03:31.060	warn	Error: Error: Non-whitespace before first tag. Line: 0 Column: 1 Char: s
upnp.0
	2022-01-25 12:03:30.605	warn	Error: Error: Non-whitespace before first tag. Line: 0 Column: 1 Char: s

Anything else?

No response

Manually add devices located in a routed network

Hi at all,
I want to manage a device in a routed network using the upnp adaptor. Therefor the device must be added manually.
Can you please include the possibility of adding devices manually?
Regards
roadie33

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.