Neuentw. Modulpaket zu UPnP: Controller, Device, DLNA(Renderer-Ersatz)

[Fhemotto]

Hallo Markus

Vielen Dank für die viele Arbeit am neuen Modul.

Beobachte dies schon eine Weile.

Habe bis jetzt 98_DLNAClient und 98_DLNARenderer parallel verwendet, für meine Bedürfnisse soweit OK und funktionell.
(Auch wenn's nicht empfohlen ist, funktionierte aber)

Habe nun einen Schnellschuss gewagt, und mal eben die beide XXXController installiert.
Als erstes was unklar/auffällt: (auch wenn noch Beta Status, würde eventuell neu Einsteigern auch helfen)
Beschreibung der Attribute: (Für manchen selbsterklären, aber nicht für alle. Besonders der Syntax ist nicht sofort ersichtlich)

UPNP_Controller:
-   acceptedUDNs ?
-   envNamespace ?
-   envPrefix ?
-   ignoreUDNs ?
-   ignoreIPs ?
-   searchterm ?
-   usedonlyIPs ?
   
DLNAController:
-   channel_01 bis channel_10 ?
-   multiRoomGroups ?
-   ttsLanguage ?

Einige Beschreibungen sind im Text versteckt. z.B.
,,set-Befehl searchterm mit dem Parameter upnp:rootdevice ausführt"
Könnte man dies eventuell in den ersten Threads mit aufnehmen oder am besten gleich im Modul, Hilfetext bei Attributauswahl (Also Attribut auswählen ... Hilfetext erscheint)

Ansonsten hatte ich jede Menge Logeinträge, die ich aber noch in Ruhe(Device bezogen) analysieren müsste.
Hier ein kleiner Ausschnitt.

Code Auswählen Erweitern


2022.03.17 15:52:14 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:14 3: UPNPController: start searching by type with search term: upnp:rootdevice
2022.03.17 15:52:14 3: DLNAController: DLNA_82b03b99_3b3b_99b9_9032_99093bb9328b address changed; services initially subscribed
2022.03.17 15:52:15 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:17 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:18 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:18 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:18 3: todoist (Todoist_Baumarkt): Error Message: Response was damaged or empty. See log for details.
2022.03.17 15:52:18 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:18 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:19 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:19 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:19 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:19 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:19 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 15:52:20 3: DLNAController: DLNA_fa095ecc_e13e_40e7_8e6c_9CC7A60FA3AE address changed; services initially subscribed

2022.03.17 16:12:33 3: DLNAController: DLNA_5c244e2a_0a7a_1123_0080_0006785af082 services initially subscribed
2022.03.17 16:12:33 2: autocreate: define FileLog_DLNA_5c244e2a_0a7a_1123_0080_0006785af082 FileLog ./log/DLNA_5c244e2a_0a7a_1123_0080_0006785af082-%Y.log DLNA_5c244e2a_0a7a_1123_0080_0006785af082
2022.03.17 16:12:33 1: readingsUpdate(UPNP_Controller,192.168.155.69_60006-zz_1,uuid:9770b2e5-65ba-170c-0080-0006785af082) missed to call readingsBeginUpdate first.
2022.03.17 16:12:33 1: stacktrace:
2022.03.17 16:12:33 1:     main::readingsBulkUpdate            called by fhem.pl (4962)
2022.03.17 16:12:33 1:     main::readingsBulkUpdateIfChanged   called by ./FHEM/98_UPNPController.pm (674)
2022.03.17 16:12:33 1:     main::UPNPController_child          called by ./FHEM/98_UPNPController.pm (654)
2022.03.17 16:12:33 1:     main::UPNPController_parent         called by ./FHEM/98_UPNPController.pm (588)
2022.03.17 16:12:33 1:     main::UPNPController_addedDevice    called by ./FHEM/98_UPNPController.pm (499)
2022.03.17 16:12:33 1:     main::UPNPController_discoverCallback called by ./FHEM/98_UPNPController.pm (474)
2022.03.17 16:12:33 1:     main::__ANON__                      called by FHEM/lib/UPnP/ControlPoint.pm (1068)
2022.03.17 16:12:33 1:     UPnP::ControlPoint::Search::deviceAdded called by FHEM/lib/UPnP/ControlPoint.pm (427)
2022.03.17 16:12:33 1:     UPnP::ControlPoint::_deviceAdded    called by FHEM/lib/UPnP/ControlPoint.pm (548)
2022.03.17 16:12:33 1:     UPnP::ControlPoint::_receiveSSDPEvent called by FHEM/lib/UPnP/ControlPoint.pm (238)
2022.03.17 16:12:33 1:     UPnP::ControlPoint::handleOnce      called by ./FHEM/98_UPNPController.pm (255)
2022.03.17 16:12:33 1:     (eval)                              called by ./FHEM/98_UPNPController.pm (254)
2022.03.17 16:12:33 1:     main::UPNPController_Read           called by fhem.pl (3930)
2022.03.17 16:12:33 1:     main::CallFn                        called by fhem.pl (780)
2022.03.17 16:12:33 1: readingsUpdate(UPNP_Controller,192.168.155.69_60006-zz_1-friendlyName,AiosServices) missed to call readingsBeginUpdate first.
2022.03.17 16:12:33 1: stacktrace:
2022.03.17 16:12:33 1:     main::readingsBulkUpdate            called by fhem.pl (4962)
2022.03.17 16:12:33 1:     main::readingsBulkUpdateIfChanged   called by ./FHEM/98_UPNPController.pm (628)
2022.03.17 16:12:33 1:     main::UPNPController_parent         called by ./FHEM/98_UPNPController.pm (675)
2022.03.17 16:12:33 1:     main::UPNPController_child          called by ./FHEM/98_UPNPController.pm (654)
2022.03.17 16:12:33 1:     main::UPNPController_parent         called by ./FHEM/98_UPNPController.pm (588)
2022.03.17 16:12:33 1:     main::UPNPController_addedDevice    called by ./FHEM/98_UPNPController.pm (499)
2022.03.17 16:12:33 1:     main::UPNPController_discoverCallback called by ./FHEM/98_UPNPController.pm (474)
2022.03.17 16:12:33 1:     main::__ANON__                      called by FHEM/lib/UPnP/ControlPoint.pm (1068)
2022.03.17 16:12:33 1:     UPnP::ControlPoint::Search::deviceAdded called by FHEM/lib/UPnP/ControlPoint.pm (427)
2022.03.17 16:12:33 1:     UPnP::ControlPoint::_deviceAdded    called by FHEM/lib/UPnP/ControlPoint.pm (548)
2022.03.17 16:12:33 1:     UPnP::ControlPoint::_receiveSSDPEvent called by FHEM/lib/UPnP/ControlPoint.pm (238)
2022.03.17 16:12:33 1:     UPnP::ControlPoint::handleOnce      called by ./FHEM/98_UPNPController.pm (255)
2022.03.17 16:12:33 1:     (eval)                              called by ./FHEM/98_UPNPController.pm (254)
2022.03.17 16:12:33 1:     main::UPNPController_Read           called by fhem.pl (3930)
2022.03.17 16:12:33 1:     main::CallFn                        called by fhem.pl (780)
2022.03.17 16:12:33 1: readingsUpdate(UPNP_Controller,192.168.155.69_60006-zz_1-manufacturer,Denon) missed to call readingsBeginUpdate first.
2022.03.17 16:12:33 1: stacktrace:

...

Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1102.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1107.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1113.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1102.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1107.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1113.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1102.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1107.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1113.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1102.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1107.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1113.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1102.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1107.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1113.
...

2022.03.17 17:05:14 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 17:05:14 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 17:05:15 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1102.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1107.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1113.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
...

Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1102.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1107.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1113.
2022.03.17 17:05:45 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 17:05:45 3: UPNPController: subscription for service RenderingControl of device 192.168.155.67_8888 failed:
2022.03.17 17:06:48 3: UPNPController: destroying controlpoint of device UPNP_Controller
2022.03.17 17:06:49 3: UPNPController: start searching by type with search term: ssdp:all
...

Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1102.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1107.
Use of uninitialized value in concatenation (.) or string at ./FHEM/98_DLNAController.pm line 1113.
Argument "16.0 C (measured)" isn't numeric in sprintf at ./FHEM/33_readingsGroup.pm line 1450.
2022.03.17 17:09:43 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.155.44_7676_2 failed: , try to subscribe
2022.03.17 17:09:43 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.44_7676_2 failed: , try to subscribe
2022.03.17 17:09:43 1: ERROR evaluating {UPNPController_renewSubscriptionsfinished('UPNP_Controller|192.168.155.44_7676_2-zs-AVTransport')}: Can't call method "timeout" on an undefined value at ./FHEM/98_UPNPController.pm line 769.

2022.03.17 17:10:43 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.44_7676_2 failed: Can't call method "renew" on unblessed reference at ./FHEM/98_UPNPController.pm line 834.
, try to subscribe
2022.03.17 17:11:43 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.44_7676_2 failed: Can't call method "renew" on unblessed reference at ./FHEM/98_UPNPController.pm line 834.
, try to subscribe
...

2022.03.17 17:49:30 3: UPNPController: UPNPSocket-UPNP_Controller-37469, handleOnce failed, junk '
' after XML element

2022.03.17 17:49:30 1: Timeout for MilightBridge_DoPing reached, terminated process 28802
2022.03.17 17:49:31 3: UPNPController: UPNPSocket-UPNP_Controller-37469, handleOnce failed, junk '
' after XML element

2022.03.17 17:49:32 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.69_60006-zz failed: , try to subscribe
2022.03.17 17:49:35 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.155.69_60006-zz failed: , try to subscribe
2022.03.17 17:49:35 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.44_7676_2 failed: Can't call method "renew" on unblessed reference at ./FHEM/98_UPNPController.pm line 834.
...
2022.03.17 18:01:36 2: autocreate: define FileLog_DLNA_2ac811da_1dd2_11b2_988d_000982195dd8 FileLog ./log/DLNA_2ac811da_1dd2_11b2_988d_000982195dd8-%Y.log DLNA_2ac811da_1dd2_11b2_988d_000982195dd8
2022.03.17 18:01:49 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.69_60006-zz failed: , try to subscribe
2022.03.17 18:01:52 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.155.69_60006-zz failed: , try to subscribe
2022.03.17 18:01:52 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.44_7676_2 failed: Can't call method "renew" on unblessed reference at ./FHEM/98_UPNPController.pm line 834.
, try to subscribe
Use of uninitialized value in subtraction (-) at ./FHEM/98_UPNPController.pm line 862.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
2022.03.17 18:02:08 2: autocreate: define DLNA_4fd13ed5_55d3_449f_97bc_e9d4e963b485 DLNAController uuid:4fd13ed5-55d3-449f-97bc-e9d4e963b485 192.168.155.68_9197
2022.03.17 18:02:09 3: DLNAController: DLNA_4fd13ed5_55d3_449f_97bc_e9d4e963b485 services initially subscribed
2022.03.17 18:02:09 2: autocreate: define FileLog_DLNA_4fd13ed5_55d3_449f_97bc_e9d4e963b485 FileLog ./log/DLNA_4fd13ed5_55d3_449f_97bc_e9d4e963b485-%Y.log DLNA_4fd13ed5_55d3_449f_97bc_e9d4e963b485
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
2022.03.17 18:02:19 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.44_7676_2 failed: Can't call method "renew" on unblessed reference at ./FHEM/98_UPNPController.pm line 834.
, try to subscribe
Use of uninitialized value in subtraction (-) at ./FHEM/98_UPNPController.pm line 862.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
2022.03.17 18:02:51 3: DLNAController: DLNA_a2612702_b645_4f92_8aef_b82f3952d361 address changed; services initially subscribed
2022.03.17 18:02:51 3: UPNPController: UPNPSocket-UPNP_Controller-37469, handleOnce failed, Can't use string ("") as an ARRAY ref while "strict refs" in use at FHEM/lib/UPnP/ControlPoint.pm line 584.

2022.03.17 18:02:51 3: UPNPController: UPNPSocket-UPNP_Controller-37469, handleOnce failed, Can't use string ("") as an ARRAY ref while "strict refs" in use at FHEM/lib/UPnP/ControlPoint.pm line 584.

Use of uninitialized value $value in string eq at fhem.pl line 4961.
Use of uninitialized value $value in string eq at fhem.pl line 4961.
2022.03.17 18:02:51 3: UPNPController: UPNPSocket-UPNP_Controller-37469, handleOnce failed, Can't use string ("") as an ARRAY ref while "strict refs" in use at FHEM/lib/UPnP/ControlPoint.pm line 584.

2022.03.17 18:02:51 3: UPNPController: UPNPSocket-UPNP_Controller-37469, handleOnce failed, Can't use string ("") as an ARRAY ref while "strict refs" in use at FHEM/lib/UPnP/ControlPoint.pm line 584.
...

2022.03.17 18:06:12 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.44_7676_2 failed: Can't call method "renew" on unblessed reference at ./FHEM/98_UPNPController.pm line 834.
, try to subscribe
2022.03.17 18:06:15 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.69_60006-zz failed: , try to subscribe
Use of uninitialized value $usn in pattern match (m//) at FHEM/lib/UPnP/ControlPoint.pm line 312.
Use of uninitialized value $usn in pattern match (m//) at FHEM/lib/UPnP/ControlPoint.pm line 316.
Use of uninitialized value $udn in hash element at FHEM/lib/UPnP/ControlPoint.pm line 411.
Use of uninitialized value $location in concatenation (.) or string at FHEM/lib/UPnP/ControlPoint.pm line 381.
400-URL-Absolute-Error! Location: "", Content: "400 URL missing
" at ./FHEM/98_UPNPController.pm line 255.
Use of uninitialized value $location in concatenation (.) or string at FHEM/lib/UPnP/ControlPoint.pm line 382.
Loading device description failed with error: 400 URL missing (Location: ) at ./FHEM/98_UPNPController.pm line 255.
2022.03.17 18:06:18 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.155.69_60006-zz failed: , try to subscribe
Argument "Second-infinite" isn't numeric in addition (+) at ./FHEM/98_UPNPController.pm line 862.
Argument "Second-infinite" isn't numeric in addition (+) at ./FHEM/98_UPNPController.pm line 862.
Use of uninitialized value in subtraction (-) at ./FHEM/98_UPNPController.pm line 862.
2022.03.17 18:06:21 3: UPNPController: subscription for service RenderingControl of device 192.168.155.69_60006-zz failed:
2022.03.17 18:06:56 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.155.48_32572 failed: , try to subscribe
2022.03.17 18:06:56 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.48_32572 failed: , try to subscribe
2022.03.17 18:06:56 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.155.44_7676_2 failed: Can't call method "renew" on unblessed reference at ./FHEM/98_UPNPController.pm line 834.
, try to subscribe



Weitere Fragen:
Könnte man im UPNP_Controller z.B. mit ,,get"  eine Liste der Geräte erzeugen,
mit nur z.B. IP; udn;  friendlyName? Habe gefühlt 100 readings momentan.

Hier auch mein device List:

Code Auswählen Erweitern


Internals:
   FD         30
   FUUID      62332b4f-f33f-3c5f-4eb1-6bbb7d116fd4d1c5
   NAME       UPNP_Controller
   NR         655
   NTFY_ORDER 50-UPNP_Controller
   STATE      initialized
   TYPE       UPNPController
   UDN        0
   VERSION    v0.0.4
   READINGS:
     2022-03-17 15:52:14   192.168.155.10_49000-UDN uuid:95802409-bccb-40e7-8e6c-444E6D556DA1
     2022-03-17 15:52:14   192.168.155.10_49000-friendlyName FRITZ!Box 7590 (UI)
     2022-03-17 15:52:14   192.168.155.10_49000-location http://192.168.155.10:49000/l2tpv3.xml
     2022-03-17 15:52:14   192.168.155.10_49000-manufacturer AVM Berlin
     2022-03-17 15:52:14   192.168.155.10_49000-modelDescription FRITZ!Box 7590 (UI)
     2022-03-17 15:52:14   192.168.155.10_49000-modelName FRITZ!Box 7590 (UI)
     2022-03-17 15:52:14   192.168.155.10_49000-modelNumber 1und1
     2022-03-17 15:52:14   192.168.155.10_49000-presence online
     2022-03-17 15:52:14   192.168.155.10_49000-presentationURL http://192.168.155.10
     2022-03-17 15:52:14   192.168.155.10_49000-zs-l2tpv31 urn:schemas-any-com:service:l2tpv3:1
     2022-03-17 15:52:18   192.168.155.10_49000_1-UDN uuid:535502409-bccb-40e7-8e6c-444E6D556DA1
     2022-03-17 15:52:18   192.168.155.10_49000_1-friendlyName FRITZ!Box 7590 (UI)
     2022-03-17 15:52:18   192.168.155.10_49000_1-location http://192.168.155.10:49000/avmnexusdesc.xml
     2022-03-17 15:52:18   192.168.155.10_49000_1-manufacturer AVM Berlin
     2022-03-17 15:52:18   192.168.155.10_49000_1-modelDescription FRITZ!Box 7590 (UI)
     2022-03-17 15:52:18   192.168.155.10_49000_1-modelName FRITZ!Box 7590 (UI)
     2022-03-17 15:52:18   192.168.155.10_49000_1-modelNumber 1und1
     2022-03-17 15:52:18   192.168.155.10_49000_1-presence online
     2022-03-17 15:52:18   192.168.155.10_49000_1-presentationURL http://192.168.155.10
     2022-03-17 15:52:18   192.168.155.10_49000_1-zs-avmnexus urn:schemas-any-com:service:avmnexus:1
     2022-03-17 15:52:21   192.168.155.10_49000_2-UDN uuid:fa095ecc-e13e-40e7-8e6c-444e6d556da1
     2022-03-17 15:52:21   192.168.155.10_49000_2-friendlyName AVM FRITZ!Mediaserver
     2022-03-17 15:52:21   192.168.155.10_49000_2-location http://192.168.155.10:49000/MediaServerDevDesc.xml
     2022-03-17 15:52:21   192.168.155.10_49000_2-manufacturer AVM Berlin
     2022-03-17 15:52:21   192.168.155.10_49000_2-modelDescription FRITZ!Box 7590 (UI)
     2022-03-17 15:52:21   192.168.155.10_49000_2-modelName FRITZ!Box 7590 (UI)
     2022-03-17 15:52:21   192.168.155.10_49000_2-modelNumber 1und1
     2022-03-17 15:52:21   192.168.155.10_49000_2-presence online
     2022-03-17 15:52:21   192.168.155.10_49000_2-presentationURL http://fritz.box
     2022-03-17 15:52:21   192.168.155.10_49000_2-zs-AVM_ServerStatus urn:avm.de:service:AVM_ServerStatus:1
     2022-03-17 15:52:21   192.168.155.10_49000_2-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 15:52:21   192.168.155.10_49000_2-zs-ContentDirectory urn:schemas-upnp-org:service:ContentDirectory:1
     2022-03-17 15:52:21   192.168.155.10_49000_2-zs-X_MS_MediaReceiverRegistrar urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
     2022-03-17 15:52:21   192.168.155.10_49000_3-UDN uuid:123402409-bccb-40e7-8e6c-444E6D556DA1
     2022-03-17 15:52:21   192.168.155.10_49000_3-friendlyName FRITZ!Box 7590 (UI)
     2022-03-17 15:52:21   192.168.155.10_49000_3-location http://192.168.155.10:49000/fboxdesc.xml
     2022-03-17 15:52:21   192.168.155.10_49000_3-manufacturer AVM Berlin
     2022-03-17 15:52:21   192.168.155.10_49000_3-modelDescription FRITZ!Box 7590 (UI)
     2022-03-17 15:52:21   192.168.155.10_49000_3-modelName FRITZ!Box 7590 (UI)
     2022-03-17 15:52:21   192.168.155.10_49000_3-modelNumber 1und1
     2022-03-17 15:52:21   192.168.155.10_49000_3-presence online
     2022-03-17 15:52:21   192.168.155.10_49000_3-presentationURL http://192.168.155.10
     2022-03-17 15:52:21   192.168.155.10_49000_3-zs-fritzbox urn:schemas-any-com:service:fritzbox:1
     2022-03-17 15:52:19   192.168.155.20_49000-UDN uuid:123402409-bccb-40e7-8e6c-CCCE1EE6B537
     2022-03-17 15:52:19   192.168.155.20_49000-friendlyName repeater1750-1
     2022-03-17 15:52:19   192.168.155.20_49000-location http://192.168.155.20:49000/fboxdesc.xml
     2022-03-17 15:52:19   192.168.155.20_49000-manufacturer AVM Berlin
     2022-03-17 15:52:19   192.168.155.20_49000-modelDescription FRITZ!WLAN Repeater 1750E
     2022-03-17 15:52:19   192.168.155.20_49000-modelName FRITZ!WLAN Repeater 1750E
     2022-03-17 15:52:19   192.168.155.20_49000-modelNumber avm
     2022-03-17 15:52:19   192.168.155.20_49000-presence online
     2022-03-17 15:52:19   192.168.155.20_49000-presentationURL http://192.168.155.20
     2022-03-17 15:52:19   192.168.155.20_49000-zs-fritzbox urn:schemas-any-com:service:fritzbox:1
     2022-03-17 15:52:19   192.168.155.21_49000-UDN uuid:123402409-bccb-40e7-8e6c-1CED6F60A3C3
     2022-03-17 15:52:19   192.168.155.21_49000-friendlyName FRITZ!Repeater 2400
     2022-03-17 15:52:19   192.168.155.21_49000-location http://192.168.155.21:49000/fboxdesc.xml
     2022-03-17 15:52:19   192.168.155.21_49000-manufacturer AVM Berlin
     2022-03-17 15:52:19   192.168.155.21_49000-modelDescription FRITZ!Repeater 2400
     2022-03-17 15:52:19   192.168.155.21_49000-modelName FRITZ!Repeater 2400
     2022-03-17 15:52:19   192.168.155.21_49000-modelNumber avm
     2022-03-17 15:52:19   192.168.155.21_49000-presence online
     2022-03-17 15:52:19   192.168.155.21_49000-presentationURL http://192.168.155.21
     2022-03-17 15:52:19   192.168.155.21_49000-zs-fritzbox urn:schemas-any-com:service:fritzbox:1
     2022-03-17 15:52:20   192.168.155.25_49000-UDN uuid:297bf8b4-0cd9-11df-bb1b-9CC7A60FA3AE
     2022-03-17 15:52:20   192.168.155.25_49000-friendlyName FRITZ!WLAN Repeater N/G
     2022-03-17 15:52:20   192.168.155.25_49000-location http://192.168.155.25:49000/configd.xml
     2022-03-17 15:52:20   192.168.155.25_49000-manufacturer AVM Berlin
     2022-03-17 15:52:20   192.168.155.25_49000-modelDescription FRITZ!WLAN Repeater N/G 68.04.88
     2022-03-17 15:52:20   192.168.155.25_49000-modelName FRITZ!WLAN Repeater N/G
     2022-03-17 15:52:20   192.168.155.25_49000-modelNumber avm
     2022-03-17 15:52:20   192.168.155.25_49000-presence online
     2022-03-17 15:52:20   192.168.155.25_49000-presentationURL http://fritz.repeater
     2022-03-17 15:52:20   192.168.155.25_49000-zs-configd urn:schemas-avm-de:service:configd:1
     2022-03-17 15:52:20   192.168.155.25_49000_1-UDN uuid:22617c0d-cb0f-4fb9-a31f-9CC7A60FA3AE
     2022-03-17 15:52:20   192.168.155.25_49000_1-friendlyName AVM Audiobruecke
     2022-03-17 15:52:20   192.168.155.25_49000_1-location http://192.168.155.25:49000/aura.xml
     2022-03-17 15:52:20   192.168.155.25_49000_1-manufacturer AVM Berlin
     2022-03-17 15:52:20   192.168.155.25_49000_1-modelDescription AVM Audiobruecke
     2022-03-17 15:52:20   192.168.155.25_49000_1-modelName FRITZ!WLAN Repeater N/G
     2022-03-17 15:52:20   192.168.155.25_49000_1-modelNumber 0.9.4
     2022-03-17 15:52:20   192.168.155.25_49000_1-presence online
     2022-03-17 15:52:20   192.168.155.25_49000_1-presentationURL http://fritz.repeater
     2022-03-17 15:52:20   192.168.155.25_49000_1-zs-aura urn:schemas-any-com:service:aura:1
     2022-03-17 15:52:19   192.168.155.25_49200-UDN uuid:fa095ecc-e13e-40e7-8e6c-9CC7A60FA3AE
     2022-03-17 15:52:19   192.168.155.25_49200-friendlyName AVM FRITZ!MediaRenderer
     2022-03-17 15:52:19   192.168.155.25_49200-location http://192.168.155.25:49200/MediaRendererDevDesc.xml
     2022-03-17 15:52:19   192.168.155.25_49200-manufacturer AVM Berlin
     2022-03-17 15:52:19   192.168.155.25_49200-modelDescription FRITZ!MediaRenderer
     2022-03-17 15:52:19   192.168.155.25_49200-modelName FRITZ!WLAN Repeater N/G
     2022-03-17 15:52:19   192.168.155.25_49200-modelNumber avm
     2022-03-17 15:52:19   192.168.155.25_49200-presence online
     2022-03-17 15:52:19   192.168.155.25_49200-presentationURL http://fritz.repeater
     2022-03-17 17:06:57   192.168.155.25_49200-zs-AVTransport subscription committed, timeout: 1800
     2022-03-17 15:52:19   192.168.155.25_49200-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 17:06:57   192.168.155.25_49200-zs-RenderingControl subscription committed, timeout: 1800
     2022-03-17 18:01:36   192.168.155.43_1543-UDN uuid:297036dc-1dd2-11b2-989d-6014b31a2652
     2022-03-17 18:01:36   192.168.155.43_1543-friendlyName TV:Loewe bild 1.32
     2022-03-17 18:01:36   192.168.155.43_1543-location http://192.168.155.43:1543/happy
     2022-03-17 18:01:36   192.168.155.43_1543-manufacturer LOEWE
     2022-03-17 18:01:36   192.168.155.43_1543-modelDescription Loewe DR+ Server SL3xx Multiroom Version 2
     2022-03-17 18:01:36   192.168.155.43_1543-modelName Loewe TV
     2022-03-17 18:01:36   192.168.155.43_1543-modelNumber 2.1
     2022-03-17 18:01:36   192.168.155.43_1543-presence online
     2022-03-17 18:01:36   192.168.155.43_1543-presentationURL /web
     2022-03-17 18:01:36   192.168.155.43_1543-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 18:01:36   192.168.155.43_1543-zs-ContentDirectory urn:schemas-upnp-org:service:ContentDirectory:1
     2022-03-17 18:01:36   192.168.155.43_1543-zs-X_ServiceManager urn:schemas-awox-com:service:X_ServiceManager:1
     2022-03-17 18:01:35   192.168.155.43_1545-UDN uuid:2ac811da-1dd2-11b2-988d-000982195dd8
     2022-03-17 18:01:35   192.168.155.43_1545-friendlyName TV:Loewe bild 1.32
     2022-03-17 18:01:35   192.168.155.43_1545-location http://192.168.155.43:1545/happy
     2022-03-17 18:01:35   192.168.155.43_1545-manufacturer LOEWE
     2022-03-17 18:01:35   192.168.155.43_1545-modelDescription Loewe TV
     2022-03-17 18:01:35   192.168.155.43_1545-modelName Loewe TV
     2022-03-17 18:01:35   192.168.155.43_1545-modelNumber 2.1
     2022-03-17 18:01:35   192.168.155.43_1545-presence online
     2022-03-17 18:01:35   192.168.155.43_1545-presentationURL /web
     2022-03-17 18:01:36   192.168.155.43_1545-zs-AVTransport SID: uuid:e64520e8-a613-11ec-8ba2-6014b31a2652 timeout: 300 property: LastChange
     2022-03-17 18:01:35   192.168.155.43_1545-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 18:01:36   192.168.155.43_1545-zs-RenderingControl SID: uuid:e6382546-a613-11ec-8ba2-6014b31a2652 timeout: 300 property: LastChange
     2022-03-17 18:01:35   192.168.155.43_1545-zs-X_ServiceManager urn:schemas-awox-com:service:X_ServiceManager:1
     2022-03-17 16:11:24   192.168.155.44_7676-UDN uuid:08f0d180-0096-1000-82d5-0c8910b67f18
     2022-03-17 16:11:24   192.168.155.44_7676-friendlyName [TV]Samsung LED55
     2022-03-17 16:11:24   192.168.155.44_7676-location http://192.168.155.44:7676/smp_2_
     2022-03-17 16:11:24   192.168.155.44_7676-manufacturer Samsung Electronics
     2022-03-17 16:11:24   192.168.155.44_7676-modelDescription Samsung DTV MainTVServer2
     2022-03-17 16:11:24   192.168.155.44_7676-modelName UE55F8000
     2022-03-17 16:11:24   192.168.155.44_7676-modelNumber 1.0
     2022-03-17 16:11:24   192.168.155.44_7676-presence online
     2022-03-17 16:11:24   192.168.155.44_7676-zs-MainTVAgent2 urn:samsung.com:service:MainTVAgent2:1
     2022-03-17 16:11:25   192.168.155.44_7676_1-UDN uuid:0bebc201-00c8-1000-87c7-0c8910b67f18
     2022-03-17 16:11:25   192.168.155.44_7676_1-friendlyName [TV]Samsung LED55
     2022-03-17 16:11:25   192.168.155.44_7676_1-location http://192.168.155.44:7676/smp_8_
     2022-03-17 16:11:25   192.168.155.44_7676_1-manufacturer Samsung Electronics
     2022-03-17 16:11:25   192.168.155.44_7676_1-modelDescription Samsung TV RCR
     2022-03-17 16:11:25   192.168.155.44_7676_1-modelName UE55F8000
     2022-03-17 16:11:25   192.168.155.44_7676_1-modelNumber 1.0
     2022-03-17 16:11:25   192.168.155.44_7676_1-presence online
     2022-03-17 16:11:25   192.168.155.44_7676_1-zs-MultiScreenService urn:samsung.com:service:MultiScreenService:1
     2022-03-17 16:11:27   192.168.155.44_7676_2-UDN uuid:0bebc200-00c8-1000-87c7-0c8910b67f18
     2022-03-17 16:11:27   192.168.155.44_7676_2-friendlyName [TV]Samsung LED55
     2022-03-17 16:11:27   192.168.155.44_7676_2-location http://192.168.155.44:7676/smp_16_
     2022-03-17 16:11:27   192.168.155.44_7676_2-manufacturer Samsung Electronics
     2022-03-17 16:11:27   192.168.155.44_7676_2-modelDescription Samsung TV DMR
     2022-03-17 16:11:27   192.168.155.44_7676_2-modelName UE55F8000
     2022-03-17 16:11:27   192.168.155.44_7676_2-modelNumber AllShare1.0
     2022-03-17 16:11:27   192.168.155.44_7676_2-presence online
     2022-03-17 18:17:28   192.168.155.44_7676_2-zs-AVTransport subscription renewal failed
     2022-03-17 16:11:27   192.168.155.44_7676_2-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 16:11:28   192.168.155.44_7676_2-zs-RenderingControl SID: uuid:0ee6b280-00fa-1000-b849-0c8910b67f18 timeout: 1800 property: LastChange
     2022-03-17 16:11:30   192.168.155.44_7676_3-UDN uuid:0e4e1c00-00f0-1000-b849-0c8910b67f18
     2022-03-17 16:11:30   192.168.155.44_7676_3-friendlyName [TV]Samsung LED55
     2022-03-17 16:11:30   192.168.155.44_7676_3-location http://192.168.155.44:7676/smp_26_
     2022-03-17 16:11:30   192.168.155.44_7676_3-manufacturer Samsung Electronics
     2022-03-17 16:11:30   192.168.155.44_7676_3-modelDescription Samsung TV NS
     2022-03-17 16:11:30   192.168.155.44_7676_3-modelName UE55F8000
     2022-03-17 16:11:30   192.168.155.44_7676_3-modelNumber 1.0
     2022-03-17 16:11:30   192.168.155.44_7676_3-presence online
     2022-03-17 16:11:30   192.168.155.44_7676_3-zs-dial urn:dial-multiscreen-org:service:dial:1
     2022-03-17 15:11:16   192.168.155.48_32572-UDN uuid:a2612702-b645-4f92-8aef-b82f3952d361
     2022-03-17 15:11:16   192.168.155.48_32572-friendlyName Arkuda DMR on iPhone11
     2022-03-17 15:11:16   192.168.155.48_32572-location http://192.168.155.48:32572/dmr/device.xml
     2022-03-17 15:11:16   192.168.155.48_32572-manufacturer Arkuda Digital
     2022-03-17 15:11:16   192.168.155.48_32572-modelDescription Arkuda DMR
     2022-03-17 15:11:16   192.168.155.48_32572-modelName Arkuda Digital Media Renderer
     2022-03-17 18:02:51   192.168.155.48_32572-presence online
     2022-03-17 18:02:51   192.168.155.48_32572-zs-AVTransport subscription committed, timeout: Second-infinite
     2022-03-17 15:11:16   192.168.155.48_32572-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 18:02:51   192.168.155.48_32572-zs-RenderingControl SID: uuid:12341234-1234-1234-1234-123412348000 timeout: Second-infinite property: LastChange
     2022-03-17 15:11:17   192.168.155.48_32572_1-UDN uuid:f6d8b548-e672-475f-b0bc-08486651f22a
     2022-03-17 15:11:17   192.168.155.48_32572_1-friendlyName Arkuda DMS on iPhone11
     2022-03-17 15:11:17   192.168.155.48_32572_1-location http://192.168.155.48:32572/dms/device.xml
     2022-03-17 15:11:17   192.168.155.48_32572_1-manufacturer Arkuda Digital
     2022-03-17 15:11:17   192.168.155.48_32572_1-modelDescription Arkuda DMS (Lite)
     2022-03-17 15:11:17   192.168.155.48_32572_1-modelName Arkuda Digital Media Server
     2022-03-17 15:11:17   192.168.155.48_32572_1-presence online
     2022-03-17 15:11:17   192.168.155.48_32572_1-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 15:11:17   192.168.155.48_32572_1-zs-ContentDirectory urn:schemas-upnp-org:service:ContentDirectory:1
     2022-03-17 18:02:11   192.168.155.55_2869-UDN uuid:118c4cbf-361a-4b24-b1a2-3fc97dbafff8
     2022-03-17 18:02:11   192.168.155.55_2869-friendlyName KAROLA: unserhaus:
     2022-03-17 18:02:11   192.168.155.55_2869-location http://192.168.155.55:2869/upnphost/udhisapi.dll?content=uuid:118c4cbf-361a-4b24-b1a2-3fc97dbafff8
     2022-03-17 18:02:11   192.168.155.55_2869-manufacturer Microsoft Corporation
     2022-03-17 18:02:11   192.168.155.55_2869-modelName Windows Media Player Sharing
     2022-03-17 18:02:11   192.168.155.55_2869-modelNumber 12.0
     2022-03-17 18:05:36   192.168.155.55_2869-presence offline
     2022-03-17 18:02:11   192.168.155.55_2869-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 18:02:11   192.168.155.55_2869-zs-ContentDirectory urn:schemas-upnp-org:service:ContentDirectory:1
     2022-03-17 18:02:11   192.168.155.55_2869-zs-X_MS_MediaReceiverRegistrar urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
     2022-03-17 18:04:45   192.168.155.55_2869_1-UDN uuid:2b5f162e-e9c0-4a8a-b567-8d88b32e026e
     2022-03-17 18:04:45   192.168.155.55_2869_1-friendlyName unserhaus (KAROLA : Windows Media Player)
     2022-03-17 18:04:45   192.168.155.55_2869_1-location http://192.168.155.55:2869/upnphost/udhisapi.dll?content=uuid:2b5f162e-e9c0-4a8a-b567-8d88b32e026e
     2022-03-17 18:04:45   192.168.155.55_2869_1-manufacturer Microsoft Corporation
     2022-03-17 18:04:45   192.168.155.55_2869_1-modelDescription Windows Media Player Renderer
     2022-03-17 18:04:45   192.168.155.55_2869_1-modelName Windows Media Player
     2022-03-17 18:04:45   192.168.155.55_2869_1-modelNumber 12
     2022-03-17 18:05:18   192.168.155.55_2869_1-presence offline
     2022-03-17 18:05:18   192.168.155.55_2869_1-zs-AVTransport subscribed but offline
     2022-03-17 18:04:45   192.168.155.55_2869_1-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 18:05:18   192.168.155.55_2869_1-zs-RenderingControl subscribed but offline
     2022-03-17 15:52:14   192.168.155.67_8888-UDN uuid:82b03b99-3b3b-99b9-9032-99093bb9328b
     2022-03-17 15:52:14   192.168.155.67_8888-friendlyName HT-R693
     2022-03-17 15:52:14   192.168.155.67_8888-location http://192.168.155.67:8888/upnp_descriptor_0
     2022-03-17 15:52:14   192.168.155.67_8888-manufacturer ONKYO
     2022-03-17 15:52:14   192.168.155.67_8888-modelDescription AV Receiver
     2022-03-17 15:52:14   192.168.155.67_8888-modelName HT-R693
     2022-03-17 15:52:14   192.168.155.67_8888-modelNumber HT-R693
     2022-03-17 17:07:15   192.168.155.67_8888-presence online
     2022-03-17 15:52:14   192.168.155.67_8888-presentationURL http://192.168.155.67/
     2022-03-17 15:52:14   192.168.155.67_8888-zs-AVTransport urn:schemas-upnp-org:service:AVTransport:1
     2022-03-17 15:52:14   192.168.155.67_8888-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 17:07:15   192.168.155.67_8888-zs-RenderingControl subscription failed, maybe offline
     2022-03-17 18:01:28   192.168.155.68_7676-UDN uuid:1e6e4b51-691b-46d9-b3f0-9521c90e7882
     2022-03-17 18:01:28   192.168.155.68_7676-friendlyName [TV] Samsung 6 Series (50)
     2022-03-17 18:01:28   192.168.155.68_7676-location http://192.168.155.68:7676/rcr/
     2022-03-17 18:01:28   192.168.155.68_7676-manufacturer Samsung Electronics
     2022-03-17 18:01:28   192.168.155.68_7676-modelDescription Samsung DTV RCR
     2022-03-17 18:01:28   192.168.155.68_7676-modelName UE50MU6179
     2022-03-17 18:01:28   192.168.155.68_7676-modelNumber 1.0
     2022-03-17 18:01:28   192.168.155.68_7676-presence online
     2022-03-17 18:01:28   192.168.155.68_7676-zs-MultiScreenService urn:samsung.com:service:MultiScreenService:1
     2022-03-17 18:01:28   192.168.155.68_7678-UDN uuid:4adc875c-36a6-4660-9274-39109c48bac4
     2022-03-17 18:01:28   192.168.155.68_7678-friendlyName [TV] Samsung 6 Series (50)
     2022-03-17 18:01:28   192.168.155.68_7678-location http://192.168.155.68:7678/nservice/
     2022-03-17 18:01:28   192.168.155.68_7678-manufacturer Samsung Electronics
     2022-03-17 18:01:28   192.168.155.68_7678-modelDescription Samsung DTV RCR
     2022-03-17 18:01:28   192.168.155.68_7678-modelName UE50MU6179
     2022-03-17 18:01:28   192.168.155.68_7678-modelNumber 1.0
     2022-03-17 18:01:28   192.168.155.68_7678-presence online
     2022-03-17 18:01:28   192.168.155.68_7678-zs-dial urn:dial-multiscreen-org:service:dial:1
     2022-03-17 18:02:09   192.168.155.68_9119-UDN uuid:c3d9eacb-53d9-4c5e-87d3-b51ef8692715
     2022-03-17 18:02:09   192.168.155.68_9119-friendlyName [TV] Samsung 6 Series (50)
     2022-03-17 18:02:09   192.168.155.68_9119-location http://192.168.155.68:9119/screen_sharing
     2022-03-17 18:02:09   192.168.155.68_9119-manufacturer Samsung Electronics
     2022-03-17 18:02:09   192.168.155.68_9119-modelDescription Samsung TV ScreenSharing
     2022-03-17 18:02:09   192.168.155.68_9119-modelName UE50MU6179
     2022-03-17 18:02:09   192.168.155.68_9119-modelNumber AllShare1.0
     2022-03-17 18:02:09   192.168.155.68_9119-presence online
     2022-03-17 18:02:09   192.168.155.68_9119-zs-ScreenSharingService urn:samsung.com:service:ScreenSharingService:1
     2022-03-17 18:02:08   192.168.155.68_9197-UDN uuid:4fd13ed5-55d3-449f-97bc-e9d4e963b485
     2022-03-17 18:02:08   192.168.155.68_9197-friendlyName [TV] Samsung 6 Series (50)
     2022-03-17 18:02:08   192.168.155.68_9197-location http://192.168.155.68:9197/dmr
     2022-03-17 18:02:08   192.168.155.68_9197-manufacturer Samsung Electronics
     2022-03-17 18:02:08   192.168.155.68_9197-modelDescription Samsung TV DMR
     2022-03-17 18:02:08   192.168.155.68_9197-modelName UE50MU6179
     2022-03-17 18:02:08   192.168.155.68_9197-modelNumber AllShare1.0
     2022-03-17 18:02:08   192.168.155.68_9197-presence online
     2022-03-17 18:02:09   192.168.155.68_9197-zs-AVTransport SID: uuid:bcded5c8-5bb4-419a-a497-024c679abf8f timeout: 1800 property: LastChange
     2022-03-17 18:02:08   192.168.155.68_9197-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 18:02:09   192.168.155.68_9197-zs-RenderingControl SID: uuid:4a8d7659-62b9-4436-baab-a1b3d5581e2b timeout: 1800 property: LastChange
     2022-03-17 18:02:08   192.168.155.68_9197-zs-StreamSplicing urn:schemas-rvualliance-org:service:StreamSplicing:1
     2022-03-17 16:12:33   192.168.155.69_60006-UDN uuid:5b6e4da8-7610-1db3-0080-0006785af082
     2022-03-17 16:12:33   192.168.155.69_60006-friendlyName Denon AVC-X3700H
     2022-03-17 16:12:33   192.168.155.69_60006-location http://192.168.155.69:60006/upnp/desc/aios_device/aios_device.xml
     2022-03-17 16:12:33   192.168.155.69_60006-manufacturer Denon
     2022-03-17 16:12:33   192.168.155.69_60006-modelName Denon AVC-X3700H
     2022-03-17 16:12:33   192.168.155.69_60006-modelNumber Aios 4.025
     2022-03-17 16:12:34   192.168.155.69_60006-presence online
     2022-03-17 16:12:33   192.168.155.69_60006-zz uuid:5c244e2a-0a7a-1123-0080-0006785af082
     2022-03-17 16:12:33   192.168.155.69_60006-zz-UDN uuid:5c244e2a-0a7a-1123-0080-0006785af082
     2022-03-17 16:12:33   192.168.155.69_60006-zz-friendlyName Denon AVC-X3700H
     2022-03-17 16:12:33   192.168.155.69_60006-zz-location http://192.168.155.69:60006/upnp/desc/aios_device/aios_device.xml
     2022-03-17 16:12:33   192.168.155.69_60006-zz-manufacturer Denon
     2022-03-17 16:12:33   192.168.155.69_60006-zz-modelName Denon AVC-X3700H
     2022-03-17 16:12:33   192.168.155.69_60006-zz-modelNumber Aios 4.025
     2022-03-17 18:06:18   192.168.155.69_60006-zz-presence offline
     2022-03-17 17:07:35   192.168.155.69_60006-zz-zs-AVTransport SID: uuid:5bbaafbc-a60c-11ec-9c05-ded4000eaa40 timeout: 300 property: LastChange
     2022-03-17 16:12:33   192.168.155.69_60006-zz-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 18:06:18   192.168.155.69_60006-zz-zs-RenderingControl subscription failed, maybe offline
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1 uuid:9770b2e5-65ba-170c-0080-0006785af082
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1-UDN uuid:9770b2e5-65ba-170c-0080-0006785af082
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1-friendlyName AiosServices
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1-location http://192.168.155.69:60006/upnp/desc/aios_device/aios_device.xml
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1-manufacturer Denon
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1-modelName Denon AVC-X3700H
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1-modelNumber Aios 4.025
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1-presence online
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1-zs-ErrorHandler urn:schemas-denon-com:service:ErrorHandler:1
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1-zs-GroupControl urn:schemas-denon-com:service:GroupControl:1
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1-zs-ZoneControl urn:schemas-denon-com:service:ZoneControl:2
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1 uuid:6f740e74-1950-2a64-3cf6-6a07909df587
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1-UDN uuid:6f740e74-1950-2a64-3cf6-6a07909df587
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1-friendlyName Denon AVC-X3700H
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1-location http://192.168.155.69:60006/upnp/desc/aios_device/aios_device.xml
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1-manufacturer Denon
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1-modelName Denon AVC-X3700H
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1-modelNumber Aios 4.025
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1-presence online
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1-zs-ACT urn:schemas-denon-com:service:ACT:1
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1 uuid:5b23b783-945d-c57d-43b8-d683b4d40e39
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1-UDN uuid:5b23b783-945d-c57d-43b8-d683b4d40e39
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1-friendlyName Denon AVC-X3700H
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1-location http://192.168.155.69:60006/upnp/desc/aios_device/aios_device.xml
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1-manufacturer Denon
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1-modelDescription Shares User defined folders and files to other Universal Plug and Play media devices.
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1-modelName Denon AVC-X3700H
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1-modelNumber Aios 4.025
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1-presence online
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 16:12:34   192.168.155.69_60006-zz_1_1_1-zs-ContentDirectory urn:schemas-upnp-org:service:ContentDirectory:1
     2022-03-17 17:59:20   192.168.155.80_58645-UDN uuid:4c25f5b6-16c1-9453-ffff-fffffdb31fce
     2022-03-17 17:59:20   192.168.155.80_58645-friendlyName SamsTab
     2022-03-17 17:59:20   192.168.155.80_58645-location http://192.168.155.80:58645/dev/4c25f5b6-16c1-9453-ffff-fffffdb31fce/desc.xml
     2022-03-17 17:59:20   192.168.155.80_58645-manufacturer Bubblesoft
     2022-03-17 17:59:20   192.168.155.80_58645-modelDescription BubbleUPnP Media Server
     2022-03-17 17:59:20   192.168.155.80_58645-modelName BubbleUPnP Media Server
     2022-03-17 17:59:20   192.168.155.80_58645-modelNumber 3.4.18
     2022-03-17 17:59:20   192.168.155.80_58645-presence online
     2022-03-17 17:59:20   192.168.155.80_58645-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 17:59:20   192.168.155.80_58645-zs-ContentDirectory urn:schemas-upnp-org:service:ContentDirectory:1
     2022-03-17 17:59:20   192.168.155.80_58645-zs-X_MS_MediaReceiverRegistrar urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
     2022-03-17 17:59:20   192.168.155.80_58645_1-UDN uuid:4c25f5b6-16c1-9453-ffff-ffffedb83a8e
     2022-03-17 17:59:20   192.168.155.80_58645_1-friendlyName SamsTab
     2022-03-17 17:59:20   192.168.155.80_58645_1-location http://192.168.155.80:58645/dev/4c25f5b6-16c1-9453-ffff-ffffedb83a8e/desc.xml
     2022-03-17 17:59:20   192.168.155.80_58645_1-manufacturer Bubblesoft
     2022-03-17 17:59:20   192.168.155.80_58645_1-modelDescription BubbleUPnP Media Renderer
     2022-03-17 17:59:20   192.168.155.80_58645_1-modelName BubbleUPnP Media Renderer
     2022-03-17 17:59:20   192.168.155.80_58645_1-modelNumber 3.4.18
     2022-03-17 17:59:20   192.168.155.80_58645_1-presence online
     2022-03-17 17:59:21   192.168.155.80_58645_1-zs-AVTransport SID: uuid:e6ec1fca-9bcf-459d-9d9e-764192d36697 timeout: 86400 property: LastChange
     2022-03-17 17:59:20   192.168.155.80_58645_1-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 17:59:20   192.168.155.80_58645_1-zs-RenderingControl SID: uuid:78e986c5-e31a-49e3-827d-b9f74a035ab1 timeout: 86400 property: LastChange
     2022-03-17 18:01:11   192.168.155.86_58645-UDN uuid:049ab94d-6b3f-4c4c-9a07-8b362bf6c04f
     2022-03-17 18:01:11   192.168.155.86_58645-friendlyName BubbleUPnP (Lenovo TB-X606XA)
     2022-03-17 18:01:11   192.168.155.86_58645-location http://192.168.155.86:58645/dev/049ab94d-6b3f-4c4c-9a07-8b362bf6c04f/desc.xml
     2022-03-17 18:01:11   192.168.155.86_58645-manufacturer Bubblesoft
     2022-03-17 18:01:11   192.168.155.86_58645-modelDescription BubbleUPnP Media Renderer
     2022-03-17 18:01:11   192.168.155.86_58645-modelName BubbleUPnP Media Renderer
     2022-03-17 18:01:11   192.168.155.86_58645-modelNumber 3.5.9
     2022-03-17 18:05:47   192.168.155.86_58645-presence offline
     2022-03-17 18:05:47   192.168.155.86_58645-zs-AVTransport subscribed but offline
     2022-03-17 18:01:11   192.168.155.86_58645-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 18:05:47   192.168.155.86_58645-zs-RenderingControl subscribed but offline
     2022-03-17 18:01:12   192.168.155.86_58645_1-UDN uuid:7c7321bf-5dfd-40e2-bcd3-7c1919be5050
     2022-03-17 18:01:12   192.168.155.86_58645_1-friendlyName BubbleUPnP Media Server (Lenovo TB-X606XA)
     2022-03-17 18:01:12   192.168.155.86_58645_1-location http://192.168.155.86:58645/dev/7c7321bf-5dfd-40e2-bcd3-7c1919be5050/desc.xml
     2022-03-17 18:01:12   192.168.155.86_58645_1-manufacturer Bubblesoft
     2022-03-17 18:01:12   192.168.155.86_58645_1-modelDescription BubbleUPnP Media Server
     2022-03-17 18:01:12   192.168.155.86_58645_1-modelName BubbleUPnP Media Server
     2022-03-17 18:01:12   192.168.155.86_58645_1-modelNumber 3.5.9
     2022-03-17 18:05:47   192.168.155.86_58645_1-presence offline
     2022-03-17 18:01:12   192.168.155.86_58645_1-zs-ConnectionManager urn:schemas-upnp-org:service:ConnectionManager:1
     2022-03-17 18:01:12   192.168.155.86_58645_1-zs-ContentDirectory urn:schemas-upnp-org:service:ContentDirectory:1
     2022-03-17 18:01:12   192.168.155.86_58645_1-zs-X_MS_MediaReceiverRegistrar urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
     2022-03-17 18:05:37   last_event      service: 192.168.155.86_58645-zs-AVTransport event: LastChange value: <Event xmlns="urn:schemas-upnp-org:metadata-1-0/AVT/"><InstanceID val="0"><TransportState val="STOPPED"/><CurrentTransportActions val="Play"/></InstanceID></Event>
     2022-03-17 17:06:49   state           initialized
   helper:
Attributes:
   envNamespace <undef>
   envPrefix  s
   room       DLNAController
   userattr   acceptedUDNs defaultRoom envNamespace envPrefix ignoreUDNs




Die erzeugten Filelogs haben den Namen der uuid-Bezeichnung. Könnten man diese nicht nach dem
friendlyNamen erzeugen? (etwas unübersichtlich)

Billd im Anhang.

Noch eine Frage:
Wie im Bild zu sehen, online/offline in gelb/blau
wo ist der Unterschied.

Ich hoffe ich komme demnächst zum weiteren Testen.

Vielen Dank nochmals.

Update:
Bei vielen Geräten fehlt der Set Befehl      Play /Stop/ Speak usw.
Somit erst einmal für mich nicht verwendbar.

[KölnSolar]

Ich fang mal hinten an.

online/offline in gelb/blau
wo ist der Unterschied.

keine Ahnung wo das bei Dir herkommt. Farben gibt es keine.

Die erzeugten Filelogs haben den Namen der uuid-Bezeichnung.

Das ist halt autocreate. Filelogs dann automatisch anlegen zu lassen halte ich für sinnfrei. Friendly names können mehrfach vorhanden sein. uuids nicht.

Zu den listings: Ich kann nicht jedermanns Zoo analysieren, da ich nicht weiß, welcher Zustand gerade vorherrschte. Daher bitte selber den UPNPController verstehen und dann konkret zu einzelnen devices die Fragen posten. Ich sehe die Fritte u. den Repeater und 2 Samsungs, die ich auch habe und fast problemlos funktionieren sollten. Fast, weil die 7590 u, der Repeater "junk" messages erzeugen könnten. War im Renderer auch schon so und hier haben wir zumindest einen workaround. Loewe, Denon, Onkyo kann ich gar nichts zu sagen und Arkuda und bubbleUPNP sind wohl Software Media Server/Renderer.

Könnte man im UPNP_Controller z.B. mit ,,get"  eine Liste der Geräte erzeugen,
mit nur z.B. IP; udn;  friendlyName? Habe gefühlt 100 readings momentan.

Nein. Halte ich auch nicht für sinnvoll. Zuerst ist man neugierig, blättert über die readings, lernt die UPNP devices kennen und dann guckt man sich das nie wieder an. Es gibt ja quasi nichts einzustellen. Es sei denn, man sucht nach Fehlern. Dann macht aber eh der Einsatz der selektiven Attribute Sinn.
Die meisten Anwender werden vermutlich DLNA nutzen wollen. Manche aber auch einfach nur den presence state oder nur mal gucken, was das eigene Netz so alles hergibt. Wenige werden auch services nutzen, zu denen es kein Modul(wie den DLNAController) gibt: Bsp: nächtliche disconnects mit neuer externer IP der Fritte.

Beschreibung der Attribute: (Für manchen selbsterklären, aber nicht für alle. Besonders der Syntax ist nicht sofort ersichtlich)

Für Dich als DLNARenderer-Nutzer sollte das ja alles nicht fremd sein. Neue Attribute gibt es kaum(nur searchterm fällt mir in Deiner Liste auf). Und natürlich wird die help erstellt. Aber erst, wenn die Funktionalität steht. Jetzt ist in der Regel alles in den 4 ersten Posts ausführlich beschrieben(z.B. searchterm)

Habe bis jetzt 98_DLNAClient und 98_DLNARenderer parallel verwendet, für meine Bedürfnisse soweit OK und funktionell.

Für welche Geräte denn ? Sollten mit UPNP-/DLNAController genauso funktionieren. Nur besser.  Und für viel mehr devices. Hast Du meine DLNARenderer-Version benutzt, die schon einige Verbesserungen gegenüber der offiziell verteilten besitzt ?

Ich hoffe ich komme demnächst zum weiteren Testen.

Als "Kenner" der Materie würde ich mit wenigen IPs(AVM, Samsung) beginnen, um einfach die Funktionalität gegenüber dem DLNARenderer zu verifizieren. Und dann device für device ausbauen. Als letztes die Software Renderer. Gibt es nicht für Onkyo u. Denon eigene Module ähnlich dem Samsung ?

Have fun
Markus

[Fhemotto]

Danke Markus

Zu:
,,Beschreibung der Attribute:"
War mir nur so aufgefallen, und hatte ja bereits geschrieben das es noch ,,Beta" ist.
Ging mir um eventuell neue Nutzer die über diesen Thread stolpern und mit den Attributen nichts anfangen können.

Der Listing Auszug war auch nicht gedacht zum Analysieren eher als Hinweis, das neue Nutzer
mit diversen Einträgen konfrontiert werden.
Auch hier hatte ich geschrieben, ich will mich damit (mit einzelnen Geräten, Stück für Stück )
so wie du es auch ähnlich vorgeschlagen hast, beschäftigen.

ZU:
,,Für welche Geräte denn ? Sollten mit UPNP-/DLNAController genauso funktionieren. Nur besser.   Und für viel mehr devices. Hast Du meine DLNARenderer-Version benutzt, die schon einige Verbesserungen gegenüber der offiziell verteilten besitzt ?"

Ich nutzt die modifizierte Variante von dir.
Wollte aber ,,mit der Zeit gehen, und nicht unbedingt die alten Module" für ewig weiter verwenden.

Mehrwehrt: !?
Hatte ich erhofft. eventuell zukünftig bzw. mehr Geräte im Netz zu erkennen.
oder auch funktionell die Anwesenheitserkennung (der Geräte) zu nutzen (für was auch immer in der Zukunft).

Leider habe ich gerade festgestellt (siehe auch update in meinem Post)
,,Bei vielen Geräten fehlt der Set Befehl      Play /Stop/ Speak usw.
Somit erst einmal für mich nicht verwendbar."

Trotzdem vielen Dank für die Antworten und viel Erfolg bei der weiteren Entwicklung.

[KölnSolar]

Guten Morgen,

Leider habe ich gerade festgestellt (siehe auch update in meinem Post)
,,Bei vielen Geräten fehlt der Set Befehl      Play /Stop/ Speak usw.
Somit erst einmal für mich nicht verwendbar."

Eine sehr generische Aussage, die so nicht stimmen kann. Deine Samsungs werden, richtig angewendet, problemlos laufen. Und auch die anderen DLNA-Geräte dürften nicht das geschilderte Problem aufweisen.

Vorstellen kann ich mir folgende falsche Historie und Fehlinterpretation.
define des UPNPControllers, Anpassung von Attributen, was ein "redefine" auslöst. Absichtlich bleiben readings und nun gar obsolete DLNA devices erhalten. Sie sind aber entweder nun ausgeschlossen worden oder noch nicht wieder neu im UPNPController angelegt worden. Weder in solchen Fällen, noch wenn ein device offline ist, macht es Sinn sich die Auswahlbox anzusehen. Denn dort werden nur Befehle zu "aktiven" services angeboten. Das ist z.B. eine der Verbesserungen gegenüber dem Renderer. Denn dort wurde einfach alles angeboten, was das Modul kann, nicht aber die Fähigkeiten des einzelnen devices berücksichtigt.

Und was immer klar sein muss: Parallelbetrieb mit Alt-DLNA-Modulen verbietet sich. Keine Ahnung, was das alles für Nebenwirkungen(oder auch nicht) haben kann, Könnte ich mir in Deinem Fall als allgemeine Problemursache vorstellen. Deshalb läuft bei mir seit über einem Jahr produktiv nur noch UPNP-/DLNAController. Problemlos.

Aktuell geht es nur noch darum, Probleme von devices zu erkennen/beseitigen, auf die ich keinen Zugriff habe und das leidige Thema der (nur noch seltenen) freezes in den Griff zu bekommen. Aber auch dazu ist der aktuelle Entwicklungsstand schon bedeutend besser als DLNA-Altmodule. Und natürlich das nie richtig zu Ende gedachte multiroom Thema des DLNARenderers.
Grüße Markus

[Fhemotto]

Hallo Markus

So wie mein erster Test ein Schnellschuss war, war wohl meine Antwort auch einer.

Ich werde natürlich weiter testen, eventuell kam dies falsch rüber, weil ich nicht alle Befehle
sofort gesehen habe. Sorry

Dazu aber nun eine Timing-Frage:
Wenn ein Gerät Online geht, sind dann die Set-Befehle sofort verfügbar, also mit senden vom Gerät (Hallo hier bin ich) oder werden diese erst abgefragt?.
(Oder Freigegeben, wenn zu vor vorhanden, oder, oder ...)

Den alten DLNA-Module hatte ich zuvor alle entfernt ( inklusive restart)

Nun muss ich aber nochmal kurz zu den Attributen fragen:
attr UPNP_Controller envNamespace <undef>
attr UPNP_Controller envPrefix s
Diese sind ja speziell für die Samsungs, werden aber im UPNPController gesetzt,
also haben Auswirkung auf alle DLNAController!?
Mit welchen Besonderheiten eventuell Einschränkungen ist bei anderen Devices zu rechnen?
(ist schon ewig her, als ich mich damit beschäftigte/ gelesen habe)

Danke

[KölnSolar]

Dazu aber nun eine Timing-Frage

Technisch sieht es so aus, dass die Optionen im Augenblick des Aufrufs der FHEM-Seite anhand der Fähigkeiten des devices ermittelt werden. Die Fähigkeit des devices wiederum wird einmalig nach jedem FHEM-Neustart, redefine.... ermittelt und dann dauerhaft hinterlegt. Bedeutet im Praxisbetrieb: nur kurzzeitig kann evtl. der Befehlsumfang eingeschränkt sein. Im normalen laufenden Betrieb steht aber permanent der zum device passende Umfang zur Verfügung, nachdem das device einmalig online war. 

Den alten DLNA-Module hatte ich zuvor alle entfernt ( inklusive restart)

Sehr gut. 

Diese sind ja speziell für die Samsungs, werden aber im UPNPController gesetzt,
also haben Auswirkung auf alle DLNAController!?

Das kann ich Dir so genau gar nicht sagen. Wir brauchen sie genauso, wie ich sie beim DLNARenderer eingeführt hatte, um Samsung devices betreiben zu können. Evtl. Negativauswirkungen wurden weder dort noch hier bisher gemeldet. Ich persönlich habe bei Repeater,WindowsMediaplayer,miniDLNA und den nicht-DLNA-devices Fritte,IPCam keine Auswirkungen. Beim DLNARenderer hatte ich den usern, die ohne die Attribute mit mir fremden devices Probleme hatten, immer empfohlen mal die beiden (eigentlich) speziellen Samsung-Attribute auszuprobieren. Also Versuch macht kluch und wenn ein device nicht so will wie es sollte, gehen wir dem gemeinsam auf die Spur. 

Grüße Markus

[RockFan]

OT

egal. Anfänger, weil so unspezifisch ? Ich finde ihn schon.... ;)Hölle. Ich hab so 10. Meistens Plots.Du musst das Attribut setzen

Code Auswählen Erweitern

attr Deinfreezemondevice fm_logFile ./log/freeze-%Y%m%d.logDann bekommt man tägliche files für die Analyse. Obacht, die werden bei Dir groß. Nicht, dass die Platte platzt.
Grüße Markus

Hallo Markus,

ich habe nun ein Thema aufgemacht: https://forum.fhem.de/index.php/topic,126826.0.html
Danke für Deine Einschätzung und für das Angebot!

Viele Grüße
Dieter

[mumpitzstuff]

Code Auswählen Erweitern

2022.04.04 22:59:39 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

2022.04.04 23:03:32 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

2022.04.04 23:07:09 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

2022.04.04 23:11:02 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

2022.04.04 23:14:39 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

2022.04.04 23:16:57 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:17:32 1: RMDIR: ./restoreDir/save/2022-03-16
2022.04.04 23:17:57 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:17:57 5: UPNPController: renew subscription for service AVTransport of device 192.168.178.115_8080 300
2022.04.04 23:17:57 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:17:57 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.178.115_8080 failed: , try to subscribe
2022.04.04 23:17:57 5: UPNPController: renew subscription for service RenderingControl of device 192.168.178.115_8080 300
2022.04.04 23:17:58 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:17:58 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.178.115_8080 failed: , try to subscribe
2022.04.04 23:17:58 5: UPNPController: renew subscription for service AVTransport of device 192.168.178.44_8080 300
2022.04.04 23:17:58 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:17:58 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.178.44_8080 failed: , try to subscribe
2022.04.04 23:17:58 5: UPNPController: renew subscription for service RenderingControl of device 192.168.178.44_8080 300
2022.04.04 23:17:58 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:17:58 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.178.44_8080 failed: , try to subscribe
2022.04.04 23:17:58 5: UPNPController: renewSubscriptionsfinished name UPNP_Controller, readingname 192.168.178.44_8080-zs-RenderingControl
2022.04.04 23:17:58 4: UPNPController: subscribe: reading  192.168.178.44_8080-zs-RenderingControl, uniquedevice 192.168.178.44_8080, service RenderingControl
2022.04.04 23:17:58 5: UPNPController: RenderingControl: urn:upnp-org:serviceId:RenderingControl found. OK.
2022.04.04 23:17:58 4: UPNPController: subscribe: reading  192.168.178.44_8080-zs-RenderingControl, uniquedevice 192.168.178.44_8080, service RenderingControl timeout: 300
2022.04.04 23:18:08 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:18:32 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

2022.04.04 23:19:08 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:20:08 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:21:08 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:22:08 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:22:08 5: UPNPController: renew subscription for service AVTransport of device 192.168.178.115_8080 300
2022.04.04 23:22:08 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:22:08 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.178.115_8080 failed: , try to subscribe
2022.04.04 23:22:08 5: UPNPController: renew subscription for service RenderingControl of device 192.168.178.115_8080 300
2022.04.04 23:22:08 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:22:08 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.178.115_8080 failed: , try to subscribe
2022.04.04 23:22:08 5: UPNPController: renew subscription for service AVTransport of device 192.168.178.44_8080 300
2022.04.04 23:22:09 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

2022.04.04 23:22:13 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 500 Can't connect to 192.168.178.44:8080 (Connection timed out) at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:22:13 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.178.44_8080 failed: , try to subscribe
2022.04.04 23:22:13 5: UPNPController: renew subscription for service RenderingControl of device 192.168.178.44_8080 300
2022.04.04 23:22:13 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:22:13 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.178.44_8080 failed: , try to subscribe
2022.04.04 23:22:13 5: UPNPController: renewSubscriptionsfinished name UPNP_Controller, readingname 192.168.178.44_8080-zs-RenderingControl
2022.04.04 23:22:13 4: UPNPController: subscribe: reading  192.168.178.44_8080-zs-RenderingControl, uniquedevice 192.168.178.44_8080, service RenderingControl
2022.04.04 23:22:13 5: UPNPController: RenderingControl: urn:upnp-org:serviceId:RenderingControl found. OK.
2022.04.04 23:22:14 4: UPNPController: subscribe: reading  192.168.178.44_8080-zs-RenderingControl, uniquedevice 192.168.178.44_8080, service RenderingControl timeout: 300
2022.04.04 23:22:24 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:23:24 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:24:24 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:25:24 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:26:02 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

2022.04.04 23:26:24 5: UPNPController: try to renew subscriptions for services, device UPNP_Controller
2022.04.04 23:26:24 5: UPNPController: renew subscription for service AVTransport of device 192.168.178.115_8080 300
2022.04.04 23:26:24 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:26:24 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.178.115_8080 failed: , try to subscribe
2022.04.04 23:26:24 5: UPNPController: renew subscription for service RenderingControl of device 192.168.178.115_8080 300
2022.04.04 23:26:24 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:26:24 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.178.115_8080 failed: , try to subscribe
2022.04.04 23:26:24 5: UPNPController: renew subscription for service RenderingControl of device 192.168.178.44_8080 300
2022.04.04 23:26:24 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:26:24 3: UPNPController: renewal of subscription for service RenderingControl of device 192.168.178.44_8080 failed: , try to subscribe
2022.04.04 23:26:24 5: UPNPController: renew subscription for service AVTransport of device 192.168.178.44_8080 300
2022.04.04 23:26:24 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

2022.04.04 23:26:24 3: UPNPController: renewal of subscription for service AVTransport of device 192.168.178.44_8080 failed: , try to subscribe
2022.04.04 23:26:24 5: UPNPController: renewSubscriptionsfinished name UPNP_Controller, readingname 192.168.178.44_8080-zs-AVTransport
2022.04.04 23:26:24 4: UPNPController: subscribe: reading  192.168.178.44_8080-zs-AVTransport, uniquedevice 192.168.178.44_8080, service AVTransport
2022.04.04 23:26:24 5: UPNPController: AVTransport: urn:upnp-org:serviceId:AVTransport found. OK.
2022.04.04 23:26:24 4: UPNPController: subscribe: reading  192.168.178.44_8080-zs-AVTransport, uniquedevice 192.168.178.44_8080, service AVTransport timeout: 300


Mein Netzteil ist jetzt wieder da. Was genau muss ich tun, um vernünftige Informationen zu erhalten? Verbose auf 5 setzen bringt nicht viel.

[KölnSolar]

Entweder debugging oder je nach Fehler

2022.04.04 23:14:39 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

verbose 5 z.B. beim "UPNPSocket-UPNP_Controller-1900" device.

2022.04.04 23:17:58 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

sagt ja, was passiert ist. Das ist ein Fehler, der wohl von den devices abhängt, die devices nicht mitspielen. Ich vermute 192.168.178.44 und 192.168.178.115 sind dieselben device Typen ? Welche ? Vestel(Medion) ? Dann sollten wir das hier weiter diskutieren.
Zeitlich passt es ja

2022.04.04 23:22:14 4: UPNPController: subscribe: reading  192.168.178.44_8080-zs-RenderingControl, uniquedevice 192.168.178.44_8080, service RenderingControl timeout: 300

bis 23:27:14 muss das renewal erfolgen, was rechtzeitig

2022.04.04 23:26:24 5: UPNPController: renew subscription for service RenderingControl of device 192.168.178.44_8080 300
2022.04.04 23:26:24 5: UPNPController: warning: Carp, Renewal of subscription failed with error: 412 Precondition Failed at ./FHEM/98_UPNPController.pm line 834.

passiert, das device aber offensichtlich nicht akzeptiert, weil es ja die subscription nie richtig bestätigt hat.
Denn es fehlt ja auch das event LastChange nach der subscription(wenn die nicht kommt, können wir die auch nicht loggen  ). So müsste das reading z.B.

Code Auswählen Erweitern

192.168.178.44_8080-zs-RenderingControl SID: uuid:c1dd05d0-1dd1-11b2-bba2-cdae6be7651d timeout: 300 property: LastChangeaussehen. die SID ist die subscription-ID, die 23:22:14 hätte vom device mitgeteilt werden müssen. Blieb aber aus, weshalb dann auch das renewal fehlschlägt.
Grüße Markus

[mumpitzstuff]

Code Auswählen Erweitern

2022.04.05 08:25:56 4: UPNPController: UPNPSocket-UPNP_Controller-1900, received ssdp event: was checked by discoverCallback for removed or added devices against pending search requests
2022.04.05 08:26:04 5: UPNPController: UPNPSocket-UPNP_Controller-1900, received message on port 1900 starting handleOnce
2022.04.05 08:26:04 4: UPNPController: UPNPSocket-UPNP_Controller-1900, received ssdp event: was checked by discoverCallback for removed or added devices against pending search requests
2022.04.05 08:26:04 5: UPNPController: UPNPSocket-UPNP_Controller-1900, received message on port 1900 starting handleOnce
2022.04.05 08:26:04 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

2022.04.05 08:26:04 4: UPNPController: UPNPSocket-UPNP_Controller-1900, received ssdp event: was checked by discoverCallback for removed or added devices against pending search requests
2022.04.05 08:26:08 5: UPNPController: UPNPSocket-UPNP_Controller-1900, received message on port 1900 starting handleOnce
2022.04.05 08:26:08 4: UPNPController: UPNPSocket-UPNP_Controller-1900, received ssdp event: was checked by discoverCallback for removed or added devices against pending search requests
2022.04.05 08:26:15 5: UPNPController: UPNPSocket-UPNP_Controller-1900, received message on port 1900 starting handleOnce
2022.04.05 08:26:15 4: UPNPController: UPNPSocket-UPNP_Controller-1900, received ssdp event: was checked by discoverCallback for removed or added devices against pending search requests
2022.04.05 08:26:15 5: UPNPController: UPNPSocket-UPNP_Controller-1900, received message on port 1900 starting handleOnce
2022.04.05 08:26:15 4: UPNPController: UPNPSocket-UPNP_Controller-1900, received ssdp event: was checked by discoverCallback for removed or added devices against pending search requests


Die special debug Version muss ich heute Abend in Ruhe installieren.

Die Geräte .44 und .115 sind ähnlich da beides SIRD Geräte sind, es sind jedoch unterschiedliche Geräte. Vermutlich verhalten sie sich aber tatsächlich ähnlich und schalten bestimmte Services ab, je nachdem in welchem Modus sie sich aktuell befinden.

[KölnSolar]

da beides SIRD Geräte sind

Ah, SIRD und nicht Vestel. Nun bin ich wieder im Bilde. Sollen wir das dann lieber in Deinem SIRD-Thread diskutieren/analysieren oder in einem völlig neuen Thread ?

2022.04.05 08:26:04 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'

Mit debug sehen wir dann wenigstens die IP. Vermutlich aber noch nicht viel mehr warum der xml parser "mismatched tag 'head'" meldet. 

Edit: die Meldung kommt aus /usr/share/perl5/XML/Parser/Lite.pm Line 190 oder 201.
        Du könntest in /opt/fhem/FHEM/lib/UPnP/ControlPoint.pm hinter

Code Auswählen Erweitern

sub _createDevice {
my $self = shift;
my $location = shift;
my $device;

# We've found examples of where devices claim to do transfer
# encoding, but wind up sending chunks without chunk size headers.
# This code temporarily disables the TE header in the request.
#push(@LWP::Protocol::http::EXTRA_SOCK_OPTS, SendTE => 0);
my @SOCK_OPTS_Backup = @LWP::Protocol::http::EXTRA_SOCK_OPTS;
_addSendTE();
my $ua = LWP::UserAgent->new(timeout => 20);
my $response = $ua->get($location);

my $base;
if ($response->is_success && $response->content ne '') {
eine Log-Zeile einbauen

Code Auswählen Erweitern

print "UpnP Logging: ControlPoint.pm: Received xml-response is: ".$response->content."\n";
Dann sehen wir (hoffentlich) die xml-response der devices(das dann OHNE den debugModus im UPNPController).

[mumpitzstuff]

Code Auswählen Erweitern

2022.04.05 11:18:23 4: DLNAController DLNA_3DCC7100_F76C_11DD_87AF_002261F129E2: state update from UPNP_Controller, address 192.168.178.102_8080
UpnP Logging: ControlPoint.pm: Received xml-response is: <netRemote>
<friendlyName>SIRD 14 D1</friendlyName>
<version>ir-mmi-FS2026-0500-0688_V2.13.19c.EX72618-1RC9</version>
<webfsapi>http://192.168.178.44:80/fsapi</webfsapi>
</netRemote>

UpnP Logging: ControlPoint.pm: Received xml-response is: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html;charset=UTF-8">
<meta http-equiv="cache-control" content="no-cache">
<meta http-equiv="pragma" content="no-cache">
<meta name="viewport" content="width=520, maximum-scale=2.0">
<link rel="shortcut icon" href="images/favicon.ico">
<link rel="stylesheet" href="css/base/style-screen.css" type="text/css" media="screen">
<link rel="stylesheet" href="css/base/style-handheld.css" type="text/css" media="handheld">
<script type="text/javascript" src="js/jquery-1.6.2.min.js"></script>
<script type="text/javascript" src="js/jsbn.js"></script>
<script type="text/javascript" src="js/prng4.js"></script>
<script type="text/javascript" src="js/rng.js"></script>
<script type="text/javascript" src="js/rsa.js"></script>
<script type="text/javascript" src="common-1.0.3.js"></script>
<title>Internet Radio 2.12</title>
</head>

<body onClick='rng_seed_time();' onKeyPress='rng_seed_time();'>
<input type="hidden" id="input_pin" />
<div id="header">
<!--<a class="logo" href="http://www.frontier-silicon.com/"><img src="images/company_logo.png" alt="Company Logo"></a>-->
<div class="aside">
<div class="new_line">
<label id="main_language" for="input_language" class="line_title">Language:</label>
<select id="input_language" class="line_input" tabindex="3">
<option value="en">English</option>
<!--<option value="test">Test</option>-->
</select>
</div>
</div>
</div>
<ul id="main_navigation">
</ul>
<div id="content">
</div>
<div id="footer">
</div>
<div id="popup_background" class="disable">
<div class="center_box">
<p id="popup_message">Please wait...</p>
</div>
</div>
</body>
</html>

2022.04.05 11:18:35 3: UPNPController: UPNPSocket-UPNP_Controller-1900, handleOnce failed, mismatched tag 'head'


[KölnSolar]

Soso. Ich bin ja beileibe kein xml-Guru.  Aber ich hab mir das mal in Notepad++ gepackt und language=xml angegeben. Und da hat Notepad++ auch seine Probleme. Mir scheints, als ob die Endtags bei den "meta" und "link" Elementen fehlen. Ändere ich das in den beiden mir bekannten Weisen

Code Auswählen Erweitern

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html;charset=UTF-8"/>
<meta http-equiv="cache-control" content="no-cache"/>
<meta http-equiv="pragma" content="no-cache"/>
<meta name="viewport" content="width=520, maximum-scale=2.0"/>
<link rel="shortcut icon" href="images/favicon.ico"/>
<link rel="stylesheet" href="css/base/style-screen.css" type="text/css" media="screen"/>
<link rel="stylesheet" href="css/base/style-handheld.css" type="text/css" media="handheld"/>
<script type="text/javascript" src="js/jquery-1.6.2.min.js"></script>
<script type="text/javascript" src="js/jsbn.js"></script>
<script type="text/javascript" src="js/prng4.js"></script>
<script type="text/javascript" src="js/rng.js"></script>
<script type="text/javascript" src="js/rsa.js"></script>
<script type="text/javascript" src="common-1.0.3.js"></script>
<title>Internet Radio 2.12</title>
</head>

<body onClick='rng_seed_time();' onKeyPress='rng_seed_time();'>
.
.
</body>
</html>
oder

Code Auswählen Erweitern

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html;charset=UTF-8"></meta>
<meta http-equiv="cache-control" content="no-cache"></meta>
<meta http-equiv="pragma" content="no-cache"></meta>
<meta name="viewport" content="width=520, maximum-scale=2.0"></meta>
<link rel="shortcut icon" href="images/favicon.ico"></link>
<link rel="stylesheet" href="css/base/style-screen.css" type="text/css" media="screen"></link>
<link rel="stylesheet" href="css/base/style-handheld.css" type="text/css" media="handheld"></link>
<script type="text/javascript" src="js/jquery-1.6.2.min.js"></script>
<script type="text/javascript" src="js/jsbn.js"></script>
<script type="text/javascript" src="js/prng4.js"></script>
<script type="text/javascript" src="js/rng.js"></script>
<script type="text/javascript" src="js/rsa.js"></script>
<script type="text/javascript" src="common-1.0.3.js"></script>
<title>Internet Radio 2.12</title>
</head>
<body onClick='rng_seed_time();' onKeyPress='rng_seed_time();'>
.
.
</body>
</html>
dann sieht das auch in Notepad++ gut aus.

Und das

Code Auswählen Erweitern

{
    "err": {
        "code": "InvalidTag",
        "msg": "Closing tag 'link' is expected inplace of 'head'.",
        "line": 18
    }
}liefert ein online-xml-editor

Aber was machen wir jetzt damit ? 

Mein erster Ansatz: verlieren wir vielleicht innerhalb von FHEM/UPNP/SOAP/XML die Endtags ? Kannst Du per wireshark oder tcpdump das "Original" xml sehen ?

Edit2: Mit der debug Version würden wir den Ablauf etwas genauer sehen und wenn Du eine kleine Modifikation machst auch das, was wir bei einem read in FHEM bekommen. Du müsstest diese Zeile

Code Auswählen Erweitern

Log3 $hash, 3, "UPNPController:DEBUG $name, received $mtype message IP: $hostIP on port ".$hash->{CD}->sockport." without error but wasn't processed";
so

Code Auswählen Erweitern

Log3 $hash, 3, "UPNPController:DEBUG $name, received $mtype message IP: $hostIP on port ".$hash->{CD}->sockport." content: ".$buf." without error but wasn't processed";
verändern.
Ich hab nämlich den Eindruck, dass es sich gar nicht um eine UPNP-message handelt(seltsamer Inhalt für eine UPNP device description). 

[mumpitzstuff]

https://www.w3schools.com/tags/tag_link.asp


https://www.w3schools.com/tags/tag_meta.asp


Eigentlich würde ich dir Recht geben, aber für Meta und Link innerhalb von Head scheinen andere Gesetze zu gelten.

Der Inhalt selbst kommt mir ebenfalls spanisch vor. Ich muss mal gucken woher der kommt...

[KölnSolar]

LoL
Ist ja gar kein xml, sondern html. 

Ich muss mal gucken woher der kommt

Unbedingt. Da scheint also was auf Port 1900 empfangen und verarbeitet zu werden, was vorher schon aussortiert werden müsste. Mit meiner oben beschriebenen Modifikation sollten wir es einfach erkennen(ohne wireshark,tcpdump).