Deutsches Forum

General
965

Ohne Log wird es jetzt schwierig das Problem zu finden.

966

Hilft das? (wie begrenze ich das auf das Wesentliche?)

2025-12-24 00:02:56.506733 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 47, ‘code’: 200, ‘msg’: <WsMsgEvents.AVAILABLE_ENTITIES: ‘available_entities’>, ‘msg_data’: {‘available_entities’: [{‘entity_id’: ‘http-get’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Get’}}, {‘entity_id’: ‘http-post’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Post’}}, {‘entity_id’: ‘http-patch’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Patch’}}, {‘entity_id’: ‘http-put’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Put’}}, {‘entity_id’: ‘http-delete’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Delete’}}, {‘entity_id’: ‘http-head’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Head’}}, {‘entity_id’: ‘wol’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Wake on LAN’}}, {‘entity_id’: ‘tcp-text’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Text over TCP’, ‘de’: ‘Text über TCP’}}, {‘entity_id’: ‘http-response’, ‘entity_type’: <EntityTypes.SENSOR: ‘sensor’>, ‘device_id’: None, ‘features’: None, ‘name’: {‘en’: ‘HTTP Request Response’, ‘de’: ‘HTTP Anfrage-Antwort’}, ‘device_class’: <DeviceClasses.CUSTOM: ‘custom’>}]}}
2025-12-24 00:02:56.498011 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:47,msg:get_available_entities,msg_data:{}}
2025-12-24 00:02:48.123094 +00:00 custom-intg-requests INFO config DEBUG Ignore saving and storing setup_complete flag during reconfiguration
2025-12-24 00:02:48.122443 +00:00 custom-intg-requests INFO setup ERROR Error during setup
2025-12-24 00:02:48.121714 +00:00 custom-intg-requests INFO setup INFO Setup was aborted with code: IntegrationSetupError.OTHER
2025-12-24 00:02:48.120519 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:event,msg:abort_driver_setup,cat:DEVICE,ts:2025-12-24T00:02:48.117050048Z,msg_data:{error:OTHER}}
2025-12-24 00:02:48.114780 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘STOP’, ‘state’: ‘ERROR’, ‘error’: <IntegrationSetupError.OTHER: ‘OTHER’>}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 00:02:48.114780 +00:00 custom-intg-requests INFO config DEBUG Ignore saving and storing setup_complete flag during reconfiguration
2025-12-24 00:02:48.111876 +00:00 custom-intg-requests INFO ^
2025-12-24 00:02:48.111876 +00:00 custom-intg-requests INFO text: !1pow.0
2025-12-24 00:02:48.111876 +00:00 custom-intg-requests INFO in , line 7, column 25:
2025-12-24 00:02:48.111876 +00:00 custom-intg-requests INFO expected , but found ‘’
2025-12-24 00:02:48.111876 +00:00 custom-intg-requests INFO ^
2025-12-24 00:02:48.111876 +00:00 custom-intg-requests INFO address: 192.168.178.63:50006
2025-12-24 00:02:48.111876 +00:00 custom-intg-requests INFO in , line 6, column 9:
2025-12-24 00:02:48.111876 +00:00 custom-intg-requests INFO setup ERROR The entered configuration is not valid YAML: while parsing a block mapping
2025-12-24 00:02:48.090772 +00:00 custom-intg-requests INFO config DEBUG Get variables from _vars block in custom entities yaml configuration
2025-12-24 00:02:48.024294 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 00:02:47.525369 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 46, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-12-24 00:02:47.519093 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:46,msg:set_driver_user_data,msg_data:{input_values:{custom_entities:Primare_SPA25:\n Features:\n ‘Off’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.0\ \n ‘On’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.1\ \n ‘Toggle’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.t\ \n Simple Commands:\n INPUT_NEXT:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1inp.n\ \n INPUT_PREVIOUS:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1inp.p\ \n DSP_MODE_NEXT:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1sur.n\ \n DSP_MODE_PREVIOUS:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1sur.p\ \n MUTE_TOGGLE:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1mut.t\ \n VOLUME_UP:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1vol.u\ \n VOLUME_DOWN:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1vol.d\ }}}
2025-12-24 00:02:39.049374 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘WAIT_USER_ACTION’, ‘require_user_action’: {‘input’: {‘title’: {‘en’: ‘Custom Entity Configuration’, ‘de’: ‘Eigene Entitäten-Konfiguration’}, ‘settings’: [{‘id’: ‘custom-entities-settings’, ‘label’: {‘en’: ‘Custom entities configuration’, ‘de’: ‘Eigene Entitäten-Konfiguration’}, ‘field’: {‘label’: {‘value’: {‘en’: ‘Create your own remote entities with pre-defined commands. More details can be found in the readme file. If you add new commands or features to an existing entity you need to remove and re-add the entity from the configured entity list afterwards.’, ‘de’: ‘Erstelle deine eigenen Remote Entitäten mit vor-definierten Befehlen. Mehr Details findest du in der Readme-Datei. Wenn du neue Befehle oder Feature zu einer bestehenden Entitäten-Konfiguration hinzufügst, musst du die Entität anschließend aus der konfigurierten Entitäten-Liste entfernen und neu hinzufügen.’}}}}, {‘id’: ‘custom_entities’, ‘label’: {‘en’: ‘Replace this configuration with your own’, ‘de’: ‘Ersetzte diese Konfiguration mit deiner Eigenen’}, ‘field’: {‘textarea’: {‘value’: Entity1:\n Features:\n ‘Off’:\n Type: get\n Parameter: https://192.168.1.102/api/commands/off\n ‘On’:\n Type: wol\n Parameter:\n address:\n - ec:bd:d4:01:e9:39\n - 88:59:b7:25:b9:a5\n port: 12345\n interface: 192.168.1.1\n Toggle:\n Type: get\n Parameter: https://192.168.1.102/api/commands/toggle\n Simple Commands:\n INPUT_1:\n Type: post\n Parameter:\n url: https://httpbin.org/post\n json:\n command: input\n number: 1\n MENU:\n Type: tcp-text\n Parameter:\n address: 192.168.1.101:12345\n text: raw=0xDF 0xAD 0xBE 0xEF 0x00 0xFF\n timeout: 7\n}}}]}}}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 00:02:39.044241 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 00:02:39.042563 +00:00 custom-intg-requests INFO config DEBUG setup_step not found in __storers because it should not be stored in the config file
2025-12-24 00:02:39.042563 +00:00 custom-intg-requests INFO config DEBUG Saved setup_step: handle_custom into config runtime storage
2025-12-24 00:02:39.039764 +00:00 custom-intg-requests INFO config DEBUG setup_step not found in __storers because it should not be stored in the config file
2025-12-24 00:02:39.039764 +00:00 custom-intg-requests INFO config DEBUG Saved setup_step: custom into config runtime storage
2025-12-24 00:02:39.037850 +00:00 custom-intg-requests INFO config DEBUG setup_reconfigure not found in __storers because it should not be stored in the config file
2025-12-24 00:02:39.037850 +00:00 custom-intg-requests INFO config DEBUG Saved setup_reconfigure: True into config runtime storage
2025-12-24 00:02:39.037850 +00:00 custom-intg-requests INFO setup INFO Starting reconfiguration
2025-12-24 00:02:39.037850 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 45, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-12-24 00:02:39.031422 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:45,msg:setup_driver,msg_data:{reconfigure:true,setup_data:{setup_action:custom}}}
2025-12-24 00:02:23.916395 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 44, ‘code’: 200, ‘msg’: <WsMsgEvents.AVAILABLE_ENTITIES: ‘available_entities’>, ‘msg_data’: {‘available_entities’: [{‘entity_id’: ‘http-get’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Get’}}, {‘entity_id’: ‘http-post’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Post’}}, {‘entity_id’: ‘http-patch’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Patch’}}, {‘entity_id’: ‘http-put’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Put’}}, {‘entity_id’: ‘http-delete’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Delete’}}, {‘entity_id’: ‘http-head’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Head’}}, {‘entity_id’: ‘wol’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Wake on LAN’}}, {‘entity_id’: ‘tcp-text’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Text over TCP’, ‘de’: ‘Text über TCP’}}, {‘entity_id’: ‘http-response’, ‘entity_type’: <EntityTypes.SENSOR: ‘sensor’>, ‘device_id’: None, ‘features’: None, ‘name’: {‘en’: ‘HTTP Request Response’, ‘de’: ‘HTTP Anfrage-Antwort’}, ‘device_class’: <DeviceClasses.CUSTOM: ‘custom’>}]}}
2025-12-24 00:02:23.911156 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:44,msg:get_available_entities,msg_data:{}}
2025-12-23 23:50:13.170187 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 43, ‘code’: 200, ‘msg’: <WsMsgEvents.AVAILABLE_ENTITIES: ‘available_entities’>, ‘msg_data’: {‘available_entities’: [{‘entity_id’: ‘http-get’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Get’}}, {‘entity_id’: ‘http-post’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Post’}}, {‘entity_id’: ‘http-patch’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Patch’}}, {‘entity_id’: ‘http-put’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Put’}}, {‘entity_id’: ‘http-delete’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Delete’}}, {‘entity_id’: ‘http-head’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Head’}}, {‘entity_id’: ‘wol’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Wake on LAN’}}, {‘entity_id’: ‘tcp-text’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Text over TCP’, ‘de’: ‘Text über TCP’}}, {‘entity_id’: ‘http-response’, ‘entity_type’: <EntityTypes.SENSOR: ‘sensor’>, ‘device_id’: None, ‘features’: None, ‘name’: {‘en’: ‘HTTP Request Response’, ‘de’: ‘HTTP Anfrage-Antwort’}, ‘device_class’: <DeviceClasses.CUSTOM: ‘custom’>}]}}
2025-12-23 23:50:13.168213 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:43,msg:get_available_entities,msg_data:{}}
2025-12-23 23:47:37.286578 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 42, ‘code’: 200, ‘msg’: <WsMsgEvents.AVAILABLE_ENTITIES: ‘available_entities’>, ‘msg_data’: {‘available_entities’: [{‘entity_id’: ‘http-get’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Get’}}, {‘entity_id’: ‘http-post’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Post’}}, {‘entity_id’: ‘http-patch’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Patch’}}, {‘entity_id’: ‘http-put’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Put’}}, {‘entity_id’: ‘http-delete’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Delete’}}, {‘entity_id’: ‘http-head’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Head’}}, {‘entity_id’: ‘wol’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Wake on LAN’}}, {‘entity_id’: ‘tcp-text’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Text over TCP’, ‘de’: ‘Text über TCP’}}, {‘entity_id’: ‘http-response’, ‘entity_type’: <EntityTypes.SENSOR: ‘sensor’>, ‘device_id’: None, ‘features’: None, ‘name’: {‘en’: ‘HTTP Request Response’, ‘de’: ‘HTTP Anfrage-Antwort’}, ‘device_class’: <DeviceClasses.CUSTOM: ‘custom’>}]}}
2025-12-23 23:47:37.280826 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:42,msg:get_available_entities,msg_data:{}}
2025-12-23 21:38:05.708597 +00:00 custom-intg-requests INFO config DEBUG Ignore saving and storing setup_complete flag during reconfiguration
2025-12-23 21:38:05.707878 +00:00 custom-intg-requests INFO setup ERROR Error during setup
2025-12-23 21:38:05.707159 +00:00 custom-intg-requests INFO setup INFO Setup was aborted with code: IntegrationSetupError.OTHER
2025-12-23 21:38:05.705870 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:event,msg:abort_driver_setup,cat:DEVICE,ts:2025-12-23T21:38:05.702403398Z,msg_data:{error:OTHER}}
2025-12-23 21:38:05.700021 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘STOP’, ‘state’: ‘ERROR’, ‘error’: <IntegrationSetupError.OTHER: ‘OTHER’>}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-23 21:38:05.700021 +00:00 custom-intg-requests INFO config DEBUG Ignore saving and storing setup_complete flag during reconfiguration
2025-12-23 21:38:05.697178 +00:00 custom-intg-requests INFO ^
2025-12-23 21:38:05.697178 +00:00 custom-intg-requests INFO text: !1pow.0
2025-12-23 21:38:05.697178 +00:00 custom-intg-requests INFO in , line 7, column 25:
2025-12-23 21:38:05.697178 +00:00 custom-intg-requests INFO expected , but found ‘’
2025-12-23 21:38:05.697178 +00:00 custom-intg-requests INFO ^
2025-12-23 21:38:05.697178 +00:00 custom-intg-requests INFO address: 192.168.178.63:50006
2025-12-23 21:38:05.697178 +00:00 custom-intg-requests INFO in , line 6, column 9:
2025-12-23 21:38:05.697178 +00:00 custom-intg-requests INFO setup ERROR The entered configuration is not valid YAML: while parsing a block mapping
2025-12-23 21:38:05.676263 +00:00 custom-intg-requests INFO config DEBUG Get variables from _vars block in custom entities yaml configuration
2025-12-23 21:38:05.610454 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-23 21:38:05.109489 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 41, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-12-23 21:38:05.104380 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:41,msg:set_driver_user_data,msg_data:{input_values:{custom_entities:Primare_SPA25:\n Features:\n ‘Off’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.0\ \n ‘On’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.1\ \n ‘Toggle’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.t\ \n Simple Commands:\n INPUT_NEXT:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1inp.n\ \n INPUT_PREVIOUS:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1inp.p\ \n DSP_MODE_NEXT:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1sur.n\ \n DSP_MODE_PREVIOUS:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1sur.p\ \n MUTE_TOGGLE:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1mut.t\ \n VOLUME_UP:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1vol.u\ \n VOLUME_DOWN:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1vol.d\ }}}
2025-12-23 21:37:57.529372 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘WAIT_USER_ACTION’, ‘require_user_action’: {‘input’: {‘title’: {‘en’: ‘Custom Entity Configuration’, ‘de’: ‘Eigene Entitäten-Konfiguration’}, ‘settings’: [{‘id’: ‘custom-entities-settings’, ‘label’: {‘en’: ‘Custom entities configuration’, ‘de’: ‘Eigene Entitäten-Konfiguration’}, ‘field’: {‘label’: {‘value’: {‘en’: ‘Create your own remote entities with pre-defined commands. More details can be found in the readme file. If you add new commands or features to an existing entity you need to remove and re-add the entity from the configured entity list afterwards.’, ‘de’: ‘Erstelle deine eigenen Remote Entitäten mit vor-definierten Befehlen. Mehr Details findest du in der Readme-Datei. Wenn du neue Befehle oder Feature zu einer bestehenden Entitäten-Konfiguration hinzufügst, musst du die Entität anschließend aus der konfigurierten Entitäten-Liste entfernen und neu hinzufügen.’}}}}, {‘id’: ‘custom_entities’, ‘label’: {‘en’: ‘Replace this configuration with your own’, ‘de’: ‘Ersetzte diese Konfiguration mit deiner Eigenen’}, ‘field’: {‘textarea’: {‘value’: Entity1:\n Features:\n ‘Off’:\n Type: get\n Parameter: https://192.168.1.102/api/commands/off\n ‘On’:\n Type: wol\n Parameter:\n address:\n - ec:bd:d4:01:e9:39\n - 88:59:b7:25:b9:a5\n port: 12345\n interface: 192.168.1.1\n Toggle:\n Type: get\n Parameter: https://192.168.1.102/api/commands/toggle\n Simple Commands:\n INPUT_1:\n Type: post\n Parameter:\n url: https://httpbin.org/post\n json:\n command: input\n number: 1\n MENU:\n Type: tcp-text\n Parameter:\n address: 192.168.1.101:12345\n text: raw=0xDF 0xAD 0xBE 0xEF 0x00 0xFF\n timeout: 7\n}}}]}}}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-23 21:37:57.525464 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-23 21:37:57.523029 +00:00 custom-intg-requests INFO config DEBUG setup_step not found in __storers because it should not be stored in the config file
2025-12-23 21:37:57.523029 +00:00 custom-intg-requests INFO config DEBUG Saved setup_step: handle_custom into config runtime storage
2025-12-23 21:37:57.520269 +00:00 custom-intg-requests INFO config DEBUG setup_step not found in __storers because it should not be stored in the config file
2025-12-23 21:37:57.520269 +00:00 custom-intg-requests INFO config DEBUG Saved setup_step: custom into config runtime storage
2025-12-23 21:37:57.520269 +00:00 custom-intg-requests INFO config DEBUG setup_reconfigure not found in __storers because it should not be stored in the config file
2025-12-23 21:37:57.520269 +00:00 custom-intg-requests INFO config DEBUG Saved setup_reconfigure: True into config runtime storage
2025-12-23 21:37:57.520269 +00:00 custom-intg-requests INFO setup INFO Starting reconfiguration
2025-12-23 21:37:57.515550 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 40, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-12-23 21:37:57.515550 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:40,msg:setup_driver,msg_data:{reconfigure:true,setup_data:{setup_action:custom}}}
2025-12-23 21:37:35.829073 +00:00 custom-intg-requests INFO config DEBUG Ignore saving and storing setup_complete flag during reconfiguration
2025-12-23 21:37:35.828362 +00:00 custom-intg-requests INFO setup ERROR Error during setup
2025-12-23 21:37:35.827622 +00:00 custom-intg-requests INFO setup INFO Setup was aborted with code: IntegrationSetupError.OTHER
2025-12-23 21:37:35.826208 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:event,msg:abort_driver_setup,cat:DEVICE,ts:2025-12-23T21:37:35.822803849Z,msg_data:{error:OTHER}}
2025-12-23 21:37:35.820356 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘STOP’, ‘state’: ‘ERROR’, ‘error’: <IntegrationSetupError.OTHER: ‘OTHER’>}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-23 21:37:35.820356 +00:00 custom-intg-requests INFO config DEBUG Ignore saving and storing setup_complete flag during reconfiguration
2025-12-23 21:37:35.817322 +00:00 custom-intg-requests INFO ^
2025-12-23 21:37:35.817322 +00:00 custom-intg-requests INFO text: !1pow.0
2025-12-23 21:37:35.817322 +00:00 custom-intg-requests INFO in , line 7, column 25:
2025-12-23 21:37:35.817322 +00:00 custom-intg-requests INFO expected , but found ‘’
2025-12-23 21:37:35.817322 +00:00 custom-intg-requests INFO ^
2025-12-23 21:37:35.817322 +00:00 custom-intg-requests INFO address: 192.168.178.63:50006
2025-12-23 21:37:35.817322 +00:00 custom-intg-requests INFO in , line 6, column 9:
2025-12-23 21:37:35.817322 +00:00 custom-intg-requests INFO setup ERROR The entered configuration is not valid YAML: while parsing a block mapping
2025-12-23 21:37:35.795711 +00:00 custom-intg-requests INFO config DEBUG Get variables from _vars block in custom entities yaml configuration
2025-12-23 21:37:35.726338 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-23 21:37:35.226750 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 39, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-12-23 21:37:35.220996 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:39,msg:set_driver_user_data,msg_data:{input_values:{custom_entities:Primare_SPA25:\n Features:\n ‘Off’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.0\ \n ‘On’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.1\ \n ‘Toggle’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.t\ \n Simple Commands:\n INPUT_NEXT:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1inp.n\ \n INPUT_PREVIOUS:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1inp.p\ \n DSP_MODE_NEXT:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1sur.n\ \n DSP_MODE_PREVIOUS:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1sur.p\ \n MUTE_TOGGLE:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1mut.t\ \n VOLUME_UP:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1vol.u\ \n VOLUME_DOWN:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1vol.d\ }}}
967

Packe die Text Befehle auch mal in Anführungszeichen

968

Ich suche IR-Codes für den JVC-Projektor DLA-X5500.
Diese Codes funktionieren mit Harmony, aber nicht mit R3.
Kann mir jemand helfen? Bitte nur IR-Codes, keine Integration.

“Stand-By”,“HEX”,“6;0xCE60;16;0”
“Power-On”,“HEX”,“6;0xCEA0;16;0”
“HDMI-1”,“HEX”,“6;0xCE0E;16;0”
“HDMI-2”,“HEX”,“6;0xCE8E;16;0”
“Info”,“HEX”,“6;0xCE2E;16;0”
“Mode-1”,“HEX”,“6;0xCE1B;16;0”
“Mode-2”,“HEX”,“6;0xCE9B;16;0”
“Mode-3”,“HEX”,“6;0xCE5B;16;0”
“Lens-Control”,“HEX”,“6;0xCE0C;16;0”
“Lens-AP.”,“HEX”,“6;0xCE04;16;0”
“Anamo.”,“HEX”,“6;0xCEA3;16;0”
“Hide”,“HEX”,“6;0xCEB8;16;0”
“Curser-Up”,“HEX”,“6;0xCE80;16;0”
“Curser-Left”,“HEX”,“6;0xCE6C;16;0”
“Curser-Right”,“HEX”,“6;0xCE2C;16;0”
“Curser-Down”,“HEX”,“6;0xCE40;16;0”
“Curser-Ok”,“HEX”,“6;0xCEF4;16;0”
“Menu”,“HEX”,“6;0xCE74;16;0”
“Back”,“HEX”,“6;0xCEC0;16;0”
“Natural”,“HEX”,“6;0xCE56;16;0”
“Cinema”,“HEX”,“6;0xCE16;16;0”
“HDR”,“HEX”,“6;0xCEB7;16;0”
“Picture-Mode”,“HEX”,“6;0xCE2F;16;0”
“Color-Profile”,“HEX”,“6;0xCE11;16;0”
“Gamma-Settings”,“HEX”,“6;0xCEAF;16;0”
“MPC”,“HEX”,“6;0xCE0F;16;0”
“C.M.D.”,“HEX”,“6;0xCE51;16;0”
“Advanced-Menu”,“HEX”,“6;0xCECE;16;0”
“Gamma”,“HEX”,“6;0xCEAE;16;0”
“Color-Temp.”,“HEX”,“6;0xCE6E;16;0”
“3D-Format”,“HEX”,“6;0xCE6B;16;0”
“Pic.Adj.”,“HEX”,“6;0xCE4E;16;0”

969

Hm, die Befehle stehen alle in Anführungszeichen. So wie der: text: “!1sur.n”
Oder meinst du den Typ? Type: “tcp-text”

970

Ich meine den Text wie !1sur.n. Bei On und Off steht es laut Log in Anführungszeichen. Außerdem lass den Backslash am Ende von jedem Befehl weg. Das kann auch Probleme geben. Oder hast du da irgendwas anderes mit zusätzlich angegebenen? Das könnte auch dafür sorgen, dass nachher nur noch ein Backslash übrig bleibt. Stell das lieber im Setup global ein auf \r\n.

971

Hallo,
ich habe es nochmal versucht. Leider immer noch dieselbe Fehlermeldung.

Ich habe global auf \r\n gestellt.
Von meinem Konfigurationsfile dieses Mal ein Screenshot, damit nichts verschluckt wird. Jeder Text steht in Anführungszeichen. Hinter dem Text steht kein Backslash, oder was auch immer.

image
image552×1466 26.4 KB

Und hier der Log-File:

2025-12-24 14:46:24.411174 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 59, ‘code’: 200, ‘msg’: <WsMsgEvents.AVAILABLE_ENTITIES: ‘available_entities’>, ‘msg_data’: {‘available_entities’: [{‘entity_id’: ‘http-get’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Get’}}, {‘entity_id’: ‘http-post’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Post’}}, {‘entity_id’: ‘http-patch’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Patch’}}, {‘entity_id’: ‘http-put’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Put’}}, {‘entity_id’: ‘http-delete’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Delete’}}, {‘entity_id’: ‘http-head’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Head’}}, {‘entity_id’: ‘wol’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Wake on LAN’}}, {‘entity_id’: ‘tcp-text’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Text over TCP’, ‘de’: ‘Text über TCP’}}, {‘entity_id’: ‘http-response’, ‘entity_type’: <EntityTypes.SENSOR: ‘sensor’>, ‘device_id’: None, ‘features’: None, ‘name’: {‘en’: ‘HTTP Request Response’, ‘de’: ‘HTTP Anfrage-Antwort’}, ‘device_class’: <DeviceClasses.CUSTOM: ‘custom’>}]}}
2025-12-24 14:46:24.405396 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:59,msg:get_available_entities,msg_data:{}}
2025-12-24 14:46:17.299447 +00:00 custom-intg-requests INFO config DEBUG Ignore saving and storing setup_complete flag during reconfiguration
2025-12-24 14:46:17.298733 +00:00 custom-intg-requests INFO setup ERROR Error during setup
2025-12-24 14:46:17.298040 +00:00 custom-intg-requests INFO setup INFO Setup was aborted with code: IntegrationSetupError.OTHER
2025-12-24 14:46:17.296770 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:event,msg:abort_driver_setup,cat:DEVICE,ts:2025-12-24T14:46:17.293280434Z,msg_data:{error:OTHER}}
2025-12-24 14:46:17.290804 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘STOP’, ‘state’: ‘ERROR’, ‘error’: <IntegrationSetupError.OTHER: ‘OTHER’>}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:46:17.290804 +00:00 custom-intg-requests INFO config DEBUG Ignore saving and storing setup_complete flag during reconfiguration
2025-12-24 14:46:17.288046 +00:00 custom-intg-requests INFO ^
2025-12-24 14:46:17.288046 +00:00 custom-intg-requests INFO ‘On’:
2025-12-24 14:46:17.288046 +00:00 custom-intg-requests INFO in , line 8, column 5:
2025-12-24 14:46:17.288046 +00:00 custom-intg-requests INFO could not find expected ‘:’
2025-12-24 14:46:17.288046 +00:00 custom-intg-requests INFO ^
2025-12-24 14:46:17.288046 +00:00 custom-intg-requests INFO text:!1pow.0
2025-12-24 14:46:17.288046 +00:00 custom-intg-requests INFO in , line 7, column 9:
2025-12-24 14:46:17.288046 +00:00 custom-intg-requests INFO setup ERROR The entered configuration is not valid YAML: while scanning a simple key
2025-12-24 14:46:17.268345 +00:00 custom-intg-requests INFO config DEBUG Get variables from _vars block in custom entities yaml configuration
2025-12-24 14:46:17.200125 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:46:16.695157 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 58, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-12-24 14:46:16.695157 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:58,msg:set_driver_user_data,msg_data:{input_values:{custom_entities:Primare_SPA25:\n Features:\n ‘Off’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text:!1pow.0\n ‘On’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text:!1pow.1\n ‘Toggle’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text:!1pow.t\n Simple Commands:\n INPUT_NEXT:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text:!1inp.n\n INPUT_PREVIOUS:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text:!1inp.p\n DSP_MODE_NEXT:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text:!1sur.n\n DSP_MODE_PREVIOUS:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text:!1sur.p\n MUTE_TOGGLE:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text:!1mut.t\n VOLUME_UP:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text:!1vol.u\n VOLUME_DOWN:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text:!1vol.d\n}}}
2025-12-24 14:45:45.198137 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘WAIT_USER_ACTION’, ‘require_user_action’: {‘input’: {‘title’: {‘en’: ‘Custom Entity Configuration’, ‘de’: ‘Eigene Entitäten-Konfiguration’}, ‘settings’: [{‘id’: ‘custom-entities-settings’, ‘label’: {‘en’: ‘Custom entities configuration’, ‘de’: ‘Eigene Entitäten-Konfiguration’}, ‘field’: {‘label’: {‘value’: {‘en’: ‘Create your own remote entities with pre-defined commands. More details can be found in the readme file. If you add new commands or features to an existing entity you need to remove and re-add the entity from the configured entity list afterwards.’, ‘de’: ‘Erstelle deine eigenen Remote Entitäten mit vor-definierten Befehlen. Mehr Details findest du in der Readme-Datei. Wenn du neue Befehle oder Feature zu einer bestehenden Entitäten-Konfiguration hinzufügst, musst du die Entität anschließend aus der konfigurierten Entitäten-Liste entfernen und neu hinzufügen.’}}}}, {‘id’: ‘custom_entities’, ‘label’: {‘en’: ‘Replace this configuration with your own’, ‘de’: ‘Ersetzte diese Konfiguration mit deiner Eigenen’}, ‘field’: {‘textarea’: {‘value’: Entity1:\n Features:\n ‘Off’:\n Type: get\n Parameter: https://192.168.1.102/api/commands/off\n ‘On’:\n Type: wol\n Parameter:\n address:\n - ec:bd:d4:01:e9:39\n - 88:59:b7:25:b9:a5\n port: 12345\n interface: 192.168.1.1\n Toggle:\n Type: get\n Parameter: https://192.168.1.102/api/commands/toggle\n Simple Commands:\n INPUT_1:\n Type: post\n Parameter:\n url: https://httpbin.org/post\n json:\n command: input\n number: 1\n MENU:\n Type: tcp-text\n Parameter:\n address: 192.168.1.101:12345\n text: raw=0xDF 0xAD 0xBE 0xEF 0x00 0xFF\n timeout: 7\n}}}]}}}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:45:45.193766 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:45:45.191376 +00:00 custom-intg-requests INFO config DEBUG setup_step not found in __storers because it should not be stored in the config file
2025-12-24 14:45:45.191376 +00:00 custom-intg-requests INFO config DEBUG Saved setup_step: handle_custom into config runtime storage
2025-12-24 14:45:45.190326 +00:00 custom-intg-requests INFO config DEBUG setup_step not found in __storers because it should not be stored in the config file
2025-12-24 14:45:45.188499 +00:00 custom-intg-requests INFO config DEBUG Saved setup_step: custom into config runtime storage
2025-12-24 14:45:45.188499 +00:00 custom-intg-requests INFO config DEBUG setup_reconfigure not found in __storers because it should not be stored in the config file
2025-12-24 14:45:45.188499 +00:00 custom-intg-requests INFO config DEBUG Saved setup_reconfigure: True into config runtime storage
2025-12-24 14:45:45.188499 +00:00 custom-intg-requests INFO setup INFO Starting reconfiguration
2025-12-24 14:45:45.183518 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 57, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-12-24 14:45:45.183518 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:57,msg:setup_driver,msg_data:{reconfigure:true,setup_data:{setup_action:custom}}}
2025-12-24 14:44:42.033702 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 56, ‘code’: 200, ‘msg’: <WsMsgEvents.AVAILABLE_ENTITIES: ‘available_entities’>, ‘msg_data’: {‘available_entities’: [{‘entity_id’: ‘http-get’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Get’}}, {‘entity_id’: ‘http-post’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Post’}}, {‘entity_id’: ‘http-patch’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Patch’}}, {‘entity_id’: ‘http-put’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Put’}}, {‘entity_id’: ‘http-delete’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Delete’}}, {‘entity_id’: ‘http-head’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘HTTP Head’}}, {‘entity_id’: ‘wol’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Wake on LAN’}}, {‘entity_id’: ‘tcp-text’, ‘entity_type’: <EntityTypes.MEDIA_PLAYER: ‘media_player’>, ‘device_id’: None, ‘features’: [<Features.SELECT_SOURCE: ‘select_source’>, <Features.MEDIA_TITLE: ‘media_title’>], ‘name’: {‘en’: ‘Text over TCP’, ‘de’: ‘Text über TCP’}}, {‘entity_id’: ‘http-response’, ‘entity_type’: <EntityTypes.SENSOR: ‘sensor’>, ‘device_id’: None, ‘features’: None, ‘name’: {‘en’: ‘HTTP Request Response’, ‘de’: ‘HTTP Anfrage-Antwort’}, ‘device_class’: <DeviceClasses.CUSTOM: ‘custom’>}]}}
2025-12-24 14:44:42.027795 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:56,msg:get_available_entities,msg_data:{}}
2025-12-24 14:44:32.843556 +00:00 custom-intg-requests INFO config DEBUG Ignore saving and storing setup_complete flag during reconfiguration
2025-12-24 14:44:32.842833 +00:00 custom-intg-requests INFO setup ERROR Error during setup
2025-12-24 14:44:32.842115 +00:00 custom-intg-requests INFO setup INFO Setup was aborted with code: IntegrationSetupError.OTHER
2025-12-24 14:44:32.840697 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:event,msg:abort_driver_setup,cat:DEVICE,ts:2025-12-24T14:44:32.837420280Z,msg_data:{error:OTHER}}
2025-12-24 14:44:32.835041 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘STOP’, ‘state’: ‘ERROR’, ‘error’: <IntegrationSetupError.OTHER: ‘OTHER’>}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:44:32.833560 +00:00 custom-intg-requests INFO config DEBUG Ignore saving and storing setup_complete flag during reconfiguration
2025-12-24 14:44:32.831859 +00:00 custom-intg-requests INFO ^
2025-12-24 14:44:32.831859 +00:00 custom-intg-requests INFO address: 192.168.178.63:50006
2025-12-24 14:44:32.831859 +00:00 custom-intg-requests INFO in , line 32, column 16:
2025-12-24 14:44:32.831859 +00:00 custom-intg-requests INFO setup ERROR The entered configuration is not valid YAML: mapping values are not allowed here
2025-12-24 14:44:32.763193 +00:00 custom-intg-requests INFO config DEBUG Get variables from _vars block in custom entities yaml configuration
2025-12-24 14:44:32.695654 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:44:32.196704 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 55, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-12-24 14:44:32.190789 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:55,msg:set_driver_user_data,msg_data:{input_values:{custom_entities:Primare_SPA25:\n Features:\n ‘Off’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.0\n ‘On’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.1\n ‘Toggle’:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1pow.t\n Simple Commands:\n INPUT_NEXT:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1inp.n\n INPUT_PREVIOUS:\n Type: tcp-text\n Parameter:\n address: 192.168.178.63:50006\n text: !1inp.p\n DSP_MODE_NEXT:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1sur.n\n DSP_MODE_PREVIOUS:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1sur.p\n MUTE_TOGGLE:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1mut.t\n VOLUME_UP:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1vol.u\n VOLUME_DOWN:\n Parameter:\n Type: tcp-text\n address: 192.168.178.63:50006\n text: !1vol.d,rq_fire_and_forget:true,rq_response_nomatch_option:full,rq_response_regex:,rq_ssl_verify:false,rq_timeout:15,rq_user_agent:uc-intg-requests,setup_action:custom,tcp_text_response_wait:false,tcp_text_terminator:\r\n,tcp_text_timeout:15}}}
2025-12-24 14:44:11.722019 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘WAIT_USER_ACTION’, ‘require_user_action’: {‘input’: {‘title’: {‘en’: ‘Custom Entity Configuration’, ‘de’: ‘Eigene Entitäten-Konfiguration’}, ‘settings’: [{‘id’: ‘custom-entities-settings’, ‘label’: {‘en’: ‘Custom entities configuration’, ‘de’: ‘Eigene Entitäten-Konfiguration’}, ‘field’: {‘label’: {‘value’: {‘en’: ‘Create your own remote entities with pre-defined commands. More details can be found in the readme file. If you add new commands or features to an existing entity you need to remove and re-add the entity from the configured entity list afterwards.’, ‘de’: ‘Erstelle deine eigenen Remote Entitäten mit vor-definierten Befehlen. Mehr Details findest du in der Readme-Datei. Wenn du neue Befehle oder Feature zu einer bestehenden Entitäten-Konfiguration hinzufügst, musst du die Entität anschließend aus der konfigurierten Entitäten-Liste entfernen und neu hinzufügen.’}}}}, {‘id’: ‘custom_entities’, ‘label’: {‘en’: ‘Replace this configuration with your own’, ‘de’: ‘Ersetzte diese Konfiguration mit deiner Eigenen’}, ‘field’: {‘textarea’: {‘value’: Entity1:\n Features:\n ‘Off’:\n Type: get\n Parameter: https://192.168.1.102/api/commands/off\n ‘On’:\n Type: wol\n Parameter:\n address:\n - ec:bd:d4:01:e9:39\n - 88:59:b7:25:b9:a5\n port: 12345\n interface: 192.168.1.1\n Toggle:\n Type: get\n Parameter: https://192.168.1.102/api/commands/toggle\n Simple Commands:\n INPUT_1:\n Type: post\n Parameter:\n url: https://httpbin.org/post\n json:\n command: input\n number: 1\n MENU:\n Type: tcp-text\n Parameter:\n address: 192.168.1.101:12345\n text: raw=0xDF 0xAD 0xBE 0xEF 0x00 0xFF\n timeout: 7\n}}}]}}}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:44:11.718687 +00:00 custom-intg-requests INFO config DEBUG setup_step not found in __storers because it should not be stored in the config file
2025-12-24 14:44:11.718080 +00:00 custom-intg-requests INFO config DEBUG Saved setup_step: handle_custom into config runtime storage
2025-12-24 14:44:11.714669 +00:00 custom-intg-requests INFO config DEBUG setup_step not found in __storers because it should not be stored in the config file
2025-12-24 14:44:11.714669 +00:00 custom-intg-requests INFO config DEBUG Saved setup_step: custom into config runtime storage
2025-12-24 14:44:11.711680 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:44:11.210135 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 54, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-12-24 14:44:11.206248 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:54,msg:set_driver_user_data,msg_data:{input_values:{rq_fire_and_forget:true,rq_response_nomatch_option:full,rq_response_regex:,rq_ssl_verify:false,rq_timeout:15,rq_user_agent:uc-intg-requests,setup_action:custom,tcp_text_response_wait:false,tcp_text_terminator:\r\n,tcp_text_timeout:15}}}
2025-12-24 14:44:05.056731 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘WAIT_USER_ACTION’, ‘require_user_action’: {‘input’: {‘title’: {‘en’: ‘Setup Actions’, ‘de’: ‘Einrichtungsoptionen’}, ‘settings’: [{‘id’: ‘setup_action’, ‘label’: {‘en’: ‘Choose a setup action’, ‘de’: ‘Wähle eine Einrichtungsoption aus’}, ‘field’: {‘dropdown’: {‘value’: ‘finish’, ‘items’: [{‘id’: ‘finish’, ‘label’: {‘en’: ‘Finish Setup’, ‘de’: ‘Einrichtung abschließen’}}, {‘id’: ‘advanced’, ‘label’: {‘en’: ‘Configure advanced settings’, ‘de’: ‘Erweiterte Einstellungen konfigurieren’}}, {‘id’: ‘custom’, ‘label’: {‘en’: ‘Configure custom entities’, ‘de’: ‘Eigene Entitäten konfigurieren’}}]}}}]}}}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:44:05.053567 +00:00 custom-intg-requests INFO config DEBUG setup_step not found in __storers because it should not be stored in the config file
2025-12-24 14:44:05.052740 +00:00 custom-intg-requests INFO config DEBUG Saved setup_step: action into config runtime storage
2025-12-24 14:44:05.051999 +00:00 custom-intg-requests INFO setup INFO Fire and forget mode activated. Always return OK to the remote
2025-12-24 14:44:05.051209 +00:00 custom-intg-requests INFO config DEBUG Saved rq_fire_and_forget: True into config runtime storage
2025-12-24 14:44:05.050527 +00:00 custom-intg-requests INFO config DEBUG Skip storing rq_fire_and_forget: True into config file as it has not been changed from the default value of True
2025-12-24 14:44:05.049819 +00:00 custom-intg-requests INFO setup INFO HTTP SSL verification deactivated
2025-12-24 14:44:05.049172 +00:00 custom-intg-requests INFO config DEBUG Saved rq_ssl_verify: False into config runtime storage
2025-12-24 14:44:05.048474 +00:00 custom-intg-requests INFO config DEBUG Skip storing rq_ssl_verify: False into config file as it has not been changed from the default value of False
2025-12-24 14:44:05.047782 +00:00 custom-intg-requests INFO setup INFO Http request response option: full
2025-12-24 14:44:05.047176 +00:00 custom-intg-requests INFO config DEBUG Saved rq_response_nomatch_option: full into config runtime storage
2025-12-24 14:44:05.046545 +00:00 custom-intg-requests INFO config DEBUG Skip storing rq_response_nomatch_option: full into config file as it has not been changed from the default value of full
2025-12-24 14:44:05.045843 +00:00 custom-intg-requests INFO setup INFO Http request response regular expression:
2025-12-24 14:44:05.045227 +00:00 custom-intg-requests INFO config DEBUG Saved rq_response_regex: into config runtime storage
2025-12-24 14:44:05.044556 +00:00 custom-intg-requests INFO config DEBUG Skip storing rq_response_regex: into config file as it has not been changed from the default value of
2025-12-24 14:44:05.043864 +00:00 custom-intg-requests INFO setup INFO Http requests user agent: uc-intg-requests
2025-12-24 14:44:05.043221 +00:00 custom-intg-requests INFO config DEBUG Saved rq_user_agent: uc-intg-requests into config runtime storage
2025-12-24 14:44:05.042608 +00:00 custom-intg-requests INFO config DEBUG Skip storing rq_user_agent: uc-intg-requests into config file as it has not been changed from the default value of uc-intg-requests
2025-12-24 14:44:05.041881 +00:00 custom-intg-requests INFO setup INFO Http requests timeout: 15 seconds
2025-12-24 14:44:05.041235 +00:00 custom-intg-requests INFO config DEBUG Saved rq_timeout: 15 into config runtime storage
2025-12-24 14:44:05.040501 +00:00 custom-intg-requests INFO config DEBUG Skip storing rq_timeout: 15 into config file as it has not been changed from the default value of 15
2025-12-24 14:44:05.039691 +00:00 custom-intg-requests INFO setup INFO Text over tcp terminator:
2025-12-24 14:44:05.037782 +00:00 custom-intg-requests INFO into /etc/custom-intg/requests/config.json
2025-12-24 14:44:05.037782 +00:00 custom-intg-requests INFO config DEBUG Stored tcp_text_terminator:
2025-12-24 14:44:05.034442 +00:00 custom-intg-requests INFO into config runtime storage
2025-12-24 14:44:05.034442 +00:00 custom-intg-requests INFO config DEBUG Saved tcp_text_terminator:
2025-12-24 14:44:05.033018 +00:00 custom-intg-requests INFO setup INFO Do not wait for text over tcp response: false
2025-12-24 14:44:05.033018 +00:00 custom-intg-requests INFO config DEBUG Saved tcp_text_response_wait: False into config runtime storage
2025-12-24 14:44:05.030795 +00:00 custom-intg-requests INFO config DEBUG Skip storing tcp_text_response_wait: False into config file as it has not been changed from the default value of False
2025-12-24 14:44:05.030795 +00:00 custom-intg-requests INFO setup INFO Text over tcp timeout: 15 seconds
2025-12-24 14:44:05.029162 +00:00 custom-intg-requests INFO config DEBUG Saved tcp_text_timeout: 15 into config runtime storage
2025-12-24 14:44:05.029162 +00:00 custom-intg-requests INFO config DEBUG Skip storing tcp_text_timeout: 15 into config file as it has not been changed from the default value of 15
2025-12-24 14:44:05.025785 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:44:04.523236 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘resp’, ‘req_id’: 53, ‘code’: 200, ‘msg’: ‘result’, ‘msg_data’: {}}
2025-12-24 14:44:04.519416 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] <-: {kind:req,id:53,msg:set_driver_user_data,msg_data:{input_values:{rq_fire_and_forget:true,rq_response_nomatch_option:full,rq_response_regex:,rq_ssl_verify:false,rq_timeout:15,rq_user_agent:uc-intg-requests,tcp_text_response_wait:false,tcp_text_terminator:\r\n,tcp_text_timeout:15}}}
2025-12-24 14:43:05.133981 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘WAIT_USER_ACTION’, ‘require_user_action’: {‘input’: {‘title’: {‘en’: ‘Advanced Configuration’, ‘de’: ‘Erweiterte Konfiguration’}, ‘settings’: [{‘id’: ‘tcp-text-settings’, ‘label’: {‘en’: ‘Text over TCP:’, ‘de’: ‘Text über TCP:’}, ‘field’: {‘label’: {‘value’: {}}}}, {‘id’: ‘tcp_text_timeout’, ‘label’: {‘en’: ‘Timeout for Text over TCP (max. 30 seconds):’, ‘de’: ‘Timeout für Text über TCP (max. 30 Sekunden):’}, ‘field’: {‘number’: {‘value’: 15, ‘min’: 1, ‘max’: 30, ‘steps’: 1, ‘decimals’: 1, ‘unit’: {‘en’: ‘seconds’, ‘de’: ‘Sekunden’}}}}, {‘id’: ‘tcp_text_response_wait’, ‘label’: {‘en’: ‘Wait for a text over tcp response message:’, ‘de’: ‘Auf eine Text über TCP Antwort warten:’}, ‘field’: {‘checkbox’: {‘value’: False}}}, {‘id’: ‘tcp_text_terminator’, ‘label’: {‘en’: ‘Automatically add a command terminator character at the end of each text over TCP command:’, ‘de’: ‘Automatisch ein Befehlsabschlusszeichen am Ende jedes Text über TCP-Befehls hinzufügen:’}, ‘field’: {‘dropdown’: {‘value’: ‘None’, ‘items’: [{‘id’: ‘None’, ‘label’: {‘en’: ‘No command terminator’, ‘de’: ‘Kein Befehlsabschlusszeichen’}}, {‘id’: ‘\n’, ‘label’: {‘en’: ‘\n’, ‘de’: ‘\n’}}, {‘id’: ‘\r’, ‘label’: {‘en’: ‘\r’, ‘de’: ‘\r’}}, {‘id’: ‘\r\n’, ‘label’: {‘en’: ‘\r\n’, ‘de’: ‘\r\n’}}, {‘id’: ‘;’, ‘label’: {‘en’: ‘;’, ‘de’: ‘;’}}]}}}, {‘id’: ‘http-requests-settings’, ‘label’: {‘en’: ‘Http requests:’, ‘de’: ‘HTTP-Anfragen:’}, ‘field’: {‘label’: {‘value’: {}}}}, {‘id’: ‘rq_timeout’, ‘label’: {‘en’: ‘Timeout for HTTP requests (max. 30 seconds):’, ‘de’: ‘Timeout für HTTP-Anfragen (max. 30 Sekunden):’}, ‘field’: {‘number’: {‘value’: 15, ‘min’: 1, ‘max’: 30, ‘steps’: 1, ‘decimals’: 1, ‘unit’: {‘en’: ‘seconds’, ‘de’: ‘Sekunden’}}}}, {‘id’: ‘rq_user_agent’, ‘label’: {‘en’: ‘HTTP requests user agent:’, ‘de’: ‘HTTP-Anfragen User Agent:’}, ‘field’: {‘text’: {‘value’: ‘uc-intg-requests’}}}, {‘id’: ‘rq_response_regex’, ‘label’: {‘en’: ‘Regular expression for parsing the HTTP request sensor response:’, ‘de’: ‘Regulärer Ausdruck zum Parsen der HTTP-Anfrage-Sensorantwort:’}, ‘field’: {‘text’: {‘value’: ‘’}}}, {‘id’: ‘rq_response_nomatch_option’, ‘label’: {‘en’: ‘Response if no match for the regular expression has been found:’, ‘de’: ‘Antwort, falls keine Übereinstimmung mit dem regulären Ausdruck gefunden wurde:’}, ‘field’: {‘dropdown’: {‘value’: ‘full’, ‘items’: [{‘id’: ‘full’, ‘label’: {‘en’: ‘Full’, ‘de’: ‘Komplett’}}, {‘id’: ‘empty’, ‘label’: {‘en’: ‘Empty’, ‘de’: ‘Leer’}}, {‘id’: ‘error’, ‘label’: {‘en’: ‘Error’, ‘de’: ‘Fehler’}}]}}}, {‘id’: ‘rq_ssl_verify’, ‘label’: {‘en’: ‘Verify HTTP SSL certificates:’, ‘de’: ‘HTTP SSL-Zertifikate verifizieren:’}, ‘field’: {‘checkbox’: {‘value’: False}}}, {‘id’: ‘rq_fire_and_forget’, ‘label’: {‘en’: ‘Ignore HTTP requests errors (fire and forget):’, ‘de’: ‘Fehler bei HTTP-Anfragen ignorieren (Fire and Forget):’}, ‘field’: {‘checkbox’: {‘value’: True}}}]}}}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
2025-12-24 14:43:05.124571 +00:00 custom-intg-requests INFO ucapi.api DEBUG [(‘127.0.0.1’, 43364)] ->: {‘kind’: ‘event’, ‘msg’: <WsMsgEvents.DRIVER_SETUP_CHANGE: ‘driver_setup_change’>, ‘msg_data’: {‘event_type’: ‘SETUP’, ‘state’: ‘SETUP’}, ‘cat’: <EventCategory.DEVICE: ‘DEVICE’>}
972

Du hast bei einigen Befehlen Parameter und Type vertauscht. Versuche es mal mit dieser Konfiguration, die bei mir funktioniert hat (mit dem preformatted text tag wird die Formatierung hier im Forum beibehalten):

Primare_SPA25:
  Features:
    'Off':
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1pow.0"
    'On':
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1pow.1"
    'Toggle':
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1pow.t"
  Simple Commands:
    INPUT_NEXT:
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!linp.n"
    INPUT_PREVIOUS:
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!linp.p"
    DSP_MODE_NEXT:
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1sur.n"
    DSP_MODE_PREVIOUS:
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1sur.p"
    MUTE_TOGGLE:
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1mut.t"
    VOLUME UP:
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1vol.u"
    VOLUME DOWN:
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1vol.d"
Primare C25 remote learning IR codes problem
973

Vielen Dank, das hat funktioniert! :+1:

Trotzdem noch eine Frage, da jetzt ein anderes Problem aufgetaucht ist. Power on, off und toggle tauchen nicht mehr in der Auswahlliste in der Tastenbelegung auf. Dabei hatte das schonmal funktioniert.
Hier ist es nicht mehr zu finden:

Screenshot 2025-12-26 013127
Screenshot 2025-12-26 013127732×1478 48.4 KB

Aber, wenn ich in der Integration selbst in Entität bearbeiten “Umschalten” klicke, dann schaltet der Verstärker problemlos ein und aus. (nachdem ich den Verstärker von “deep standby” auf “normal standby” umgestellt habe. Danke auch für diesen Hinweis!)

Hier meine ich:

Screenshot 2025-12-26 013032
Screenshot 2025-12-26 013032974×1404 53.5 KB

Die Fernbedienung kann also ein und ausschalten. Ich kann nur keine Taste damit belegen. Vielleicht irgendeine Idee?

Hier der Beginn meiner Konfiguration. Der Rest sollte ja egal sein.

Primare_SPA25:
  Features:
    'Off':
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1pow.0"
    'On':
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1pow.1"
    'Toggle':
      Type: tcp-text
      Parameter:
        address: 192.168.178.63:50006
        text: "!1pow.t"
  Simple Commands:
...
974

Bei mir tauchen Ein/Aus/Toggle in der Liste sowohl bei der Benutzeroberfläche als auch der Tastenzuordnung auf:

Bildschirmfoto 2025-12-26 um 14.07.05
Bildschirmfoto 2025-12-26 um 14.07.05750×1816 113 KB

Edit: Ich sehe gerade, dass die 3 Feature Befehle beim Bearbeiten der Entitöt selbst tatsächlich nicht auftauchen. Das muss aber ein Bug in der Firmware/Web Konfiguarator sein, weil z.B. bei auch der LG Integration Ein/Aus/Toggle nicht auftauchen. DIe LG Integration hat noch einen extra Power Befehl aber das ist ein Simple Command und kein Feature-Befehl. Bei meiner Sony ADCP Integration habe ich den Power Toggle Befehl über die Integration gemappt. Da steht dann remote.toggle als Befehl, der aber in der List ebenfalls nicht auftaucht. Sollte man mal bei UC melden.

975

Hallo,

die Aktivitäten auf meiner R3 sind momentan eine Mischung aus R3-Befehlen und Kommandozeilenbefehlen in Batch-Dateien, welche ich per Hotkey aus der R3 mit “Kommando senden” aufrufe (z.B. LCTRL+LALT+Key_4).
Die Batches würde ich gern loswerden und alles in die R3 integrieren.

Die Integration von kennymc ist geladen, die Befehlsübergabe (auch einer Tastenkombination (Win-Hotkey) oder Zahlenfolge (Programmwahl)) an den PC über BT funktioniert prinzipiell gut.

Ich habe allerdings noch nicht verstanden, wie man z.B. einen Befehl für die (Windows 11-) Kommandozeile im web configurator eingibt/parametriert.

Beispiel:
Eine Batch ruft bisher den DVBViewer als Mittler zur PC-internen Satellitenkarte mit Parametern auf
“C:\Programs_noadmin\DVBViewer\DVBViewer.exe” -c:4665733772051556600 -x131

oder, um jenes Programm hart zu beenden (“quiet” mode)
taskkill /IM DVBViewer.exe /T /F 1>nul 2>&1

Wie kann ich diese Befehlszeile(n) konkret in eine Aktivität einbauen?
Die Zeile mit vorangestellter IP (des PC) als HTTP Get funktioniert freilich nicht:

http://192.168.178.69/“C:\Programs_noadmin\DVBViewer\DVBViewer.exe -c:4665733772051556600 -x131”

Die Doku auf github las ich, verstehe aber leider höchstens die Hälfte.
Vielleicht ist dieser Fall schon irgendwo dokumentiert, dann freute ich mich sehr über einen Hinweis oder link.

Vielen Dank!
Gruß, tiki

976

Windows-Kommandozeilenbefehle kannst du mit der Request-Integration nicht ausführen. Es gibt aber auch Programm wie das in der Readme erwähnte Tool zum Senden von Tastaturbefehlen über tcp-Text.

977

Aha, danke!

Eine ähnliche Lösung mit Hilfsprogramm (HTCP_Agent.exe) hat M.A.S.E. hier schon vorgestellt:

https://unfolded.community/t/integration-htpc-system-monitor-controls-integration-pc-full-remote-monitor/3431

Damit ersetze ich aber zunächst die (noch sehr übersichtlichen) Batches durch immerhin nur ein anderes Tool außerhalb der Remote. Abgesehen von der anderen Funktionsweise und ggf. abweichendem Funktionsumfang.
Soweit ich das überblicke, zumindest.

Vereinfachungen sind immer schick. Vielleicht probier ich es mal?

Danke und viele Grüße,
tiki

978

Super, dass du das nochmal getestet hast. Dann weiß ich, dass ich nicht nur wieder irgendeinen Fehler gemacht habe. Was ich nicht verstehe ist, dass es mal funktioniert hat, aber ich bekomme es nicht wieder hin. Ich habe alles neu installiert, ein Werksreset probiert und auch einen anderen Browser - leider ohne Erfolg.

979

Kann ich die Seiten der Benutzeroberfläche einer Entität einem Macro hinzufügen? Oder geht das nur bei einer anderen Entität?

980

Bei den externen remotes geht es oft.

Wenn man wirklich alles nach seinem Willen einrichten will kann man auch eine Aktivität mit nur einer Entität und ohne Start-/Ende-Sequenz erstellen.

Ralf

981

Hallo zusammen,

ich wollte erstmalig zwischen 2 Aktivitäten wechseln. Alles funktioniert wie es soll, bis auf ein Gerät (madVR Envy), dass in beiden Aktivitäten „an“ bleiben soll. Der Envy wird beim Wechsel dennoch ausgeschaltet. Ich bekomme das einfach nicht gelöst… Beide Aktivitäten sind natürlich in der gleichen Gruppe. Es klappt auch bei allen anderen Geräten, diese bleiben an. In den An- und Aus Sequenzen habe ich getrennte Befehle für das Ein- u. Ausschalten des Envy. Er geht beim Wechsel dennoch aus. Vielleicht hat ja jemand noch eine Idee?

Ganz herzlichen Dank!

LG Peter

982

Nutzt du die Integration dafür oder die IR Befehle?
Ich habe die Integration genutzt und es so über IP realisiert. Das klappte bei mir super, die Integration ist wirklich gut.

1 Like
983

Peter, wie ich bereits auf Discord erwähnt habe – ich glaube, du hast die Einstellungen falsch vorgenommen. Deshalb bin ich verwirrt, denn die Screenshots, die du geteilt hast, passen nicht zu meinem Code. Deshalb habe ich immer wieder nachgefragt – bitte teile mir weitere Informationen mit, damit ich dir helfen kann :slight_smile:

984

Danke für Eure Antworten. Meine Screens sind aber aus der Integration bzw. dem Aktivity Setup. Es sind eben die Befehle, die von der Integration zur Verfügung stehen.

Die Integration an sich ist genau wie alle anderen von @M.a.S.e top​:+1:t2:. Lediglich beim switch von einer zur anderen Aktivität soll der Envy „On“ bleiben. Irgendwie wird offensichtlich der Status nicht korrekt erkannt/verarbeitet… IR benutze ich gar nicht​:wink:.

1.2.1. Hat nix geändert (leider log vergessen…:see_no_evil_monkey:).

@Chipito Welche Befehle benutzt Du in den an- u. aus-Sequenzen für den Envy?

Danke Euch​:folded_hands:t3:

LG Peter