Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. SHP-15+Zigbee Adp.: "TS011F" not described in statesMapping.

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    SHP-15+Zigbee Adp.: "TS011F" not described in statesMapping.

    This topic has been deleted. Only users with topic management privileges can see it.
    • Asgothian
      Asgothian Developer @Schmetterfliege last edited by

      @schmetterfliege sagte in SHP-15+Zigbee Adp.: "TS011F" not described in statesMapping.:

      Und:
      Wenn ich über den Zigbee Adapter den Power Plug ein/ausschalte, steht folgendes im log:

      was bedeutet "über den Zigbee Adapter" ausschalten ?

      A.

      1 Reply Last reply Reply Quote 0
      • S
        Schmetterfliege last edited by Schmetterfliege

        @asgothian
        21a3ab0e-adf5-49af-ad33-e99388726e35-image.png
        Darüber 🙂

        EDIT: wenn ich über den physischen Button an dem Gerät schalte, steht nichts in den Logs. Der state im zigbee Adapter (siehe screenshot) wird aber sofort geupdated.

        1 Reply Last reply Reply Quote 0
        • S
          Schmetterfliege last edited by Schmetterfliege

          Hab gerade gesehen dass Zigbee scheinbar abgestürzt ist, warum weiß ich aber nicht zu 100%.
          Mein iobroker lässt mich leider das Log (noch?) nicht runterladen, daher einfach mal so aus dem Browser kopiert:
          Muss leider von unten nach oben gelesen werden 😕

          Kann mir da jemand weiterhelfen und weiß, was da passiert ist?

          
          zigbee.0
          2022-01-13 22:13:50.187	warn	DeviceConfigure:DeviceConfigure failed 0x842e14fffe285173 Remote Control N2, attempt 5 (Error: Bind 0x842e14fffe285173/1 genPowerCfg from '0x00212effff065d89/1' failed (waiting for response TIMEOUT) at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19))
          
          zigbee.0
          2022-01-13 22:12:49.799	info	Configuring 0x842e14fffe285173 Remote Control N2
          
          javascript.0
          2022-01-13 21:58:06.213	info	script.js.Wohnzimmer.Wohnzimmer_Heizung: KEVQU: Balkon Wohnbereich geöffnet
          
          zigbee.0
          2022-01-13 21:54:52.090	warn	DeviceConfigure:DeviceConfigure failed 0x842e14fffe285173 Remote Control N2, attempt 4 (Error: Bind 0x842e14fffe285173/1 genPowerCfg from '0x00212effff065d89/1' failed (waiting for response TIMEOUT) at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19) at runMicrotasks (<anonymous>) at runNextTicks (internal/process/task_queues.js:62:5) at processTimers (internal/timers.js:494:9))
          
          zigbee.0
          2022-01-13 21:53:51.868	info	Configuring 0x842e14fffe285173 Remote Control N2
          
          hue-extended.0
          2022-01-13 20:58:58.262	info	Attempt 1x - Successfully set Bad Kevin.
          
          hue-extended.0
          2022-01-13 20:56:05.324	info	Attempt 1x - Successfully set Bad Kevin.
          
          zigbee.0
          2022-01-13 20:32:49.050	warn	DeviceAvailability:Stopping to ping 0x84ba20fffe77b835 TS011F after 4 ping attempts
          
          zigbee.0
          2022-01-13 20:29:01.986	warn	DeviceConfigure:DeviceConfigure failed 0x842e14fffe285173 Remote Control N2, attempt 3 (Error: Bind 0x842e14fffe285173/1 genPowerCfg from '0x00212effff065d89/1' failed (waiting for response TIMEOUT) at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19))
          
          zigbee.0
          2022-01-13 20:28:01.493	info	Configuring 0x842e14fffe285173 Remote Control N2
          
          sonoff.0
          2022-01-13 20:24:54.257	info	Client [Wohnzimmer Sideboard] reconnected. Old secret 1642070506761_3379. New secret 1642101894254_3674
          
          sonoff.0
          2022-01-13 20:24:50.112	info	Client [Schlafzimmer_TV] reconnected. Old secret 1642070503612_6846. New secret 1642101890111_5336
          
          sonoff.0
          2022-01-13 20:24:39.443	info	Client [Nachttisch Tamara] reconnected. Old secret 1642070518106_1636. New secret 1642101879442_9980
          
          sonoff.0
          2022-01-13 20:24:38.331	info	Client [Vitrinenlicht] reconnected. Old secret 1642070504959_7204. New secret 1642101878330_8129
          
          sonoff.0
          2022-01-13 20:24:34.355	info	Client [Wohnwand] reconnected. Old secret 1642070508982_6725. New secret 1642101874351_7033
          
          zigbee.0
          2022-01-13 19:53:09.352	warn	DeviceConfigure:DeviceConfigure failed 0x842e14fffe285173 Remote Control N2, attempt 2 (Error: Bind 0x842e14fffe285173/1 genPowerCfg from '0x00212effff065d89/1' failed (waiting for response TIMEOUT) at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19))
          
          zigbee.0
          2022-01-13 19:52:09.335	info	Configuring 0x842e14fffe285173 Remote Control N2
          
          zigbee.0
          2022-01-13 19:51:49.345	warn	DeviceConfigure:DeviceConfigure failed 0x842e14fffe285173 Remote Control N2, attempt 1 (Error: Bind 0x842e14fffe285173/1 genPowerCfg from '0x00212effff065d89/1' failed (waiting for response TIMEOUT) at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19) at runNextTicks (internal/process/task_queues.js:62:5) at processTimers (internal/timers.js:494:9))
          
          zigbee.0
          2022-01-13 19:50:48.344	info	Configuring 0x842e14fffe285173 Remote Control N2
          
          zigbee.0
          2022-01-13 19:50:48.341	warn	DeviceAvailability:Failed to ping 0x84ba20fffe77b835 TS011F
          
          zigbee.0
          2022-01-13 19:50:48.339	warn	DeviceConfigure:DeviceConfigure failed 0x84fd27fffe1f8f8c TRADFRI on/off switch, attempt 1 (Error: Bind 0x84fd27fffe1f8f8c/1 genOnOff from '901' failed (waiting for response TIMEOUT) at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19))
          
          zigbee.0
          2022-01-13 19:49:47.334	info	Configuring 0x84fd27fffe1f8f8c TRADFRI on/off switch
          
          zigbee.0
          2022-01-13 19:49:47.331	warn	DeviceConfigure:DeviceConfigure failed 0x84ba20fffe77b835 TS011F, attempt 1 (Error: Read 0x84ba20fffe77b835/1 genBasic(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received) at DeconzAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:641:23) at runNextTicks (internal/process/task_queues.js:62:5) at processTimers (internal/timers.js:494:9))
          
          zigbee.0
          2022-01-13 19:48:47.027	info	debug devices set to []
          
          zigbee.0
          2022-01-13 19:48:46.888	info	Zigbee started
          
          zigbee.0
          2022-01-13 19:48:46.888	warn	config :{"port":"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2253809-if00","panID":"6754","extPanID":"DDDDDDDDDDDDDDDD","channel":"11","disableLed":false,"precfgkey":"abcdef01234567899876543210fedcba","countDown":"60","adapterType":"deconz","debugHerdsman":false,"transmitPower":null,"extPanIdFix":true,"disablePing":false,"external":"","startWithInconsistent":false}
          
          zigbee.0
          2022-01-13 19:48:46.887	info	0x84ba20fffe80c9ba (addr 37695): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
          
          zigbee.0
          2022-01-13 19:48:46.885	info	0x540f57fffe8971d1 (addr 40423): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
          
          zigbee.0
          2022-01-13 19:48:46.883	info	0x804b50fffe606093 (addr 21921): ICPSHC24-30EU-IL-1 - IKEA TRADFRI driver for wireless control (30 watt) (Router)
          
          zigbee.0
          2022-01-13 19:48:46.881	info	0x842e14fffe285173 (addr 60803): E2001/E2002 - IKEA STYRBAR remote control N2 (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.880	info	0x842e14fffe89313a (addr 26171): E2001/E2002 - IKEA STYRBAR remote control N2 (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.878	info	0xb4e3f9fffeaae8c8 (addr 59871): ICPSHC24-30EU-IL-1 - IKEA TRADFRI driver for wireless control (30 watt) (Router)
          
          zigbee.0
          2022-01-13 19:48:46.877	info	0x84fd27fffe1f8f8c (addr 8187): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.875	info	0x84fd27fffe1f8f5d (addr 43353): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.871	info	0x84ba20fffe77b200 (addr 29486): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
          
          zigbee.0
          2022-01-13 19:48:46.870	info	0x84ba20fffe77b835 (addr 487): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
          
          zigbee.0
          2022-01-13 19:48:46.867	info	0x804b50fffef8cf51 (addr 60471): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.866	info	0x00158d0005cf4ea4 (addr 42668): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.865	info	0x84fd27fffe245425 (addr 308): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.863	info	0x00158d00044eefbe (addr 41589): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.862	info	0x00158d00073c0c65 (addr 815): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.860	info	0x00158d000774f2cb (addr 13799): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.859	info	0x00158d000774f2c9 (addr 16865): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.858	info	0x00158d00077dce21 (addr 56764): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.856	info	0x00158d000774f31c (addr 31399): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.855	info	0x00158d00075f6607 (addr 3323): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.852	info	0x00158d00077dce53 (addr 62480): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.850	info	0x00158d000774f34a (addr 13527): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.849	info	0x00158d00019f3736 (addr 26600): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.847	info	0x00158d0001e4e9e3 (addr 29911): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.846	info	0x00158d000774f35a (addr 23883): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.843	info	0x00158d00076565a1 (addr 35956): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.837	info	0x00178801089de95e (addr 39138): 929002240401 - Philips Hue smart plug - EU (Router)
          
          zigbee.0
          2022-01-13 19:48:46.835	info	0x00178801089def32 (addr 26711): 929002240401 - Philips Hue smart plug - EU (Router)
          
          zigbee.0
          2022-01-13 19:48:46.834	info	0x00158d0005cf8b49 (addr 43071): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.832	info	0x00158d0003f0f373 (addr 46914): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.831	info	0x00158d000282eec7 (addr 19057): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.829	info	0x00158d000412fc1e (addr 39417): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.828	info	0x00158d00041d8697 (addr 26015): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.826	info	0x00158d000163f2bc (addr 63165): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.824	info	0x00158d000283e64e (addr 18527): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.822	info	0x00158d000283e67b (addr 50956): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.820	info	0x00158d00051e1633 (addr 39535): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.818	info	0x00158d00051dfd12 (addr 48749): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.817	info	0x00158d00052debfb (addr 30191): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.815	info	0x00158d0005221c37 (addr 57703): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.814	info	0x00158d0005221fbe (addr 11411): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.813	info	0x00158d0005221c38 (addr 31581): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.809	info	0x00158d000309a45a (addr 35075): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.806	info	0x00158d000410e8ca (addr 1223): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.804	info	0x00158d000411103a (addr 26950): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.786	info	0x00158d000410e87b (addr 32835): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
          
          zigbee.0
          2022-01-13 19:48:46.781	info	Configuring 0x84ba20fffe77b835 TS011F
          
          zigbee.0
          2022-01-13 19:48:46.586	info	Currently 46 devices are joined:
          
          zigbee.0
          2022-01-13 19:48:46.576	info	Unable to set transmit power, unsupported function.
          
          zigbee.0
          2022-01-13 19:48:46.399	info	--> transmitPower : normal
          
          zigbee.0
          2022-01-13 19:48:46.388	info	Unable to disable LED, unsupported function.
          
          zigbee.0
          2022-01-13 19:48:46.367	info	Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":88,"maintrel":0,"revision":"0x26580700"}}
          
          zigbee.0
          2022-01-13 19:48:46.334	info	Installed Version: ioBroker/ioBroker.zigbee
          
          zigbee.0
          2022-01-13 19:48:45.775	warn	extension DelayedAction
          
          zigbee.0
          2022-01-13 19:48:45.774	warn	extension DeviceEvent
          
          zigbee.0
          2022-01-13 19:48:45.774	warn	extension DeviceConfigure
          
          zigbee.0
          2022-01-13 19:48:45.773	warn	extension DeviceAvailability
          
          zigbee.0
          2022-01-13 19:48:45.773	warn	4 extensions initialized
          
          zigbee.0
          2022-01-13 19:48:45.771	info	Starting Zigbee npm ...
          
          zigbee.0
          2022-01-13 19:48:45.654	info	starting. Version 1.6.11 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.20.0, js-controller: 3.3.21
          host.raspberrypi
          2022-01-13 19:48:41.359	info	instance system.adapter.zigbee.0 started with pid 15729
          host.raspberrypi
          2022-01-13 19:48:11.308	info	Restart adapter system.adapter.zigbee.0 because enabled
          host.raspberrypi
          2022-01-13 19:48:11.307	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          host.raspberrypi
          2022-01-13 19:48:11.307	error	Caught by controller[1]: at Parser.EventEmitter.emit (domain.js:483:12)
          host.raspberrypi
          2022-01-13 19:48:11.306	error	Caught by controller[1]: at Parser.emit (events.js:314:20)
          host.raspberrypi
          2022-01-13 19:48:11.306	error	Caught by controller[1]: at Driver.onParsed (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:784:14)
          host.raspberrypi
          2022-01-13 19:48:11.306	error	Caught by controller[1]: at Driver.EventEmitter.emit (domain.js:483:12)
          host.raspberrypi
          2022-01-13 19:48:11.306	error	Caught by controller[1]: at Driver.emit (events.js:314:20)
          host.raspberrypi
          2022-01-13 19:48:11.305	error	Caught by controller[1]: at Driver.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:63:59)
          host.raspberrypi
          2022-01-13 19:48:11.305	error	Caught by controller[1]: at processFrame (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/frameParser.ts:405:59)
          host.raspberrypi
          2022-01-13 19:48:11.305	error	Caught by controller[1]: at parseFrame (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/frameParser.ts:458:32)
          host.raspberrypi
          2022-01-13 19:48:11.305	error	Caught by controller[1]: at parseGreenPowerDataIndication (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/frameParser.ts:313:33)
          host.raspberrypi
          2022-01-13 19:48:11.304	error	Caught by controller[1]: at DataView.getUint32 (<anonymous>)
          host.raspberrypi
          2022-01-13 19:48:11.304	error	Caught by controller[1]: RangeError: Offset is outside the bounds of the DataView
          host.raspberrypi
          2022-01-13 19:48:11.291	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
          
          zigbee.0
          2022-01-13 19:48:10.644	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
          
          zigbee.0
          2022-01-13 19:48:10.640	info	terminating
          
          zigbee.0
          2022-01-13 19:48:10.494	info	Zigbee: disabling joining new devices.
          
          zigbee.0
          2022-01-13 19:48:10.353	info	cleaned everything up...
          
          zigbee.0
          2022-01-13 19:48:10.288	error	Offset is outside the bounds of the DataView
          
          zigbee.0
          2022-01-13 19:48:10.288	error	RangeError: Offset is outside the bounds of the DataView at DataView.getUint32 (<anonymous>) at parseGreenPowerDataIndication (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/frameParser.ts:313:33) at parseFrame (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/frameParser.ts:458:32) at processFrame (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/frameParser.ts:405:59) at Driver.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:63:59) at Driver.emit (events.js:314:20) at Driver.EventEmitter.emit (domain.js:483:12) at Driver.onParsed (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:784:14) at Parser.emit (events.js:314:20) at Parser.EventEmitter.emit (domain.js:483:12)
          
          zigbee.0
          2022-01-13 19:48:10.228	error	unhandled promise rejection: Offset is outside the bounds of the DataView
          
          zigbee.0
          2022-01-13 19:48:10.224	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          
          info.0
          2022-01-13 19:20:27.453	info	cpu Temp res = {"main":43.816,"cores":[],"max":43.816,"socket":[],"chipset":null}
          
          info.0
          2022-01-13 19:20:27.299	info	State value to set for "info.0.sysinfo.cpu.info.cache-l3" has to be type "number" but received type "string"
          
          info.0
          2022-01-13 19:20:27.292	info	State value to set for "info.0.sysinfo.cpu.info.cache-l2" has to be type "number" but received type "string"
          
          info.0
          2022-01-13 19:20:27.286	info	State value to set for "info.0.sysinfo.cpu.info.cache-l1i" has to be type "number" but received type "string"
          
          info.0
          2022-01-13 19:20:27.238	info	State value to set for "info.0.sysinfo.cpu.info.cache-l1d" has to be type "number" but received type "string"
          
          info.0
          2022-01-13 19:20:27.185	info	State value to set for "info.0.sysinfo.cpu.info.speed" has to be type "string" but received type "number"
          
          info.0
          2022-01-13 19:20:26.622	info	Reading/updating systemdata.
          
          hue-extended.0
          2022-01-13 19:13:39.979	info	Attempt 1x - Successfully set Bad Kevin.
          
          hue-extended.0
          2022-01-13 19:06:18.482	info	Attempt 1x - Successfully set Bad Kevin.
          
          zigbee.0
          2022-01-13 15:50:55.730	warn	Device '0x84fd27fffe1f8f5d' announced itself
          
          zigbee.0
          2022-01-13 12:15:39.375	warn	Device '0x84fd27fffe1f8f5d' announced itself
          
          zigbee.0
          2022-01-13 12:10:23.250	warn	Device '0x804b50fffef8cf51' announced itself
          

          Asgothian 1 Reply Last reply Reply Quote 0
          • Asgothian
            Asgothian Developer @Schmetterfliege last edited by

            @schmetterfliege
            Da hat die deconz Stick ein “malformed packet” bekommen und konnte damit nicht umgehen. Welches Geräte dafür verantwortlich ist kann das log nicht zeigen.

            A.

            S 1 Reply Last reply Reply Quote 0
            • S
              Schmetterfliege @Asgothian last edited by

              @asgothian

              habe so ein bisschen die Sorge dass es das neueste Update ist das dafür sorgt.
              Vorher hatte ich diesen Crash noch nie, und auch dass da einige Geräte die ganze Zeit warnings ausgeben ist erst seit dem.
              Kann aber natürlich auch an den Ikea Remote Controls liegen.

              Kann ich irgendwas tun um bessere Infos zu liefern?

              Asgothian 1 Reply Last reply Reply Quote 0
              • Asgothian
                Asgothian Developer @Schmetterfliege last edited by

                @schmetterfliege wenn das ganze öfter auftrittt kannst du den Adapter im debug und mit zigbee herdsman debug info Aktiv in der Konfiguration.

                Warnung - das log kann dabei sehr groß werden. Wenn du den Fehler also nicht triggern kannst dann wird das schwierig.

                A.

                S 1 Reply Last reply Reply Quote 0
                • S
                  Schmetterfliege @Asgothian last edited by

                  @asgothian
                  Okay, dann werde ich es mal beobachten und falls ich ein Muster erkenne Debug aktivieren 🙂

                  Yodameister 1 Reply Last reply Reply Quote 0
                  • Yodameister
                    Yodameister @Schmetterfliege last edited by

                    @schmetterfliege @Asgothian

                    Hallo Ihr Lieben, ich beiße mir auch gerade die Zähne aus an Blitzwolf bw-shp13 , Adapter ist 1.6.15 ( mit 1.6.16 habe ich das auch probiert ).
                    er findet das Gerät TS011F aber mehr nicht.

                    2022-03-09 17_12_24-instances - ubuntu und 3 weitere Seiten - Persönlich – Microsoft​ Edge.png

                    kann mir jemand auf die Sprünge helfen ?

                    Asgothian 1 Reply Last reply Reply Quote 0
                    • Asgothian
                      Asgothian Developer @Yodameister last edited by

                      @yodameister

                      Willkommen in der Welt von TuYa.

                      Poste mal den Dialog den du bekommst wenn du das blaue i clicks. (Screen Shot 2022-03-09 at 18.34.23 .png )

                      A.

                      Yodameister 1 Reply Last reply Reply Quote 0
                      • Yodameister
                        Yodameister @Asgothian last edited by Yodameister

                        @asgothian

                        hier die Meldung vom Kopplungsvorgang
                        2022-03-09 18_44_05-instances - ubuntu und 1 weitere Seite - Persönlich – Microsoft​ Edge.png

                        und hier die andere
                        2022-03-09 18_44_48-instances - ubuntu und 1 weitere Seite - Persönlich – Microsoft​ Edge.png

                        Adapter ist nun 1.6.16 und sofort grün , knapp 50 Devices aus allen Gattungen , läuft absolut top und stabil

                        im ersten Bild steht > not described in statesMapping ????

                        !!!!!!!!!! Mir würde reines schalten ohne Energieverbrauch schon reichen !!!!!!!

                        Yodameister 1 Reply Last reply Reply Quote 0
                        • Yodameister
                          Yodameister @Yodameister last edited by Yodameister

                          Edit : Ich bin weiter , habe die manufacturer: _TZ3000_amdymr7l in die Tuya.js mit eingetragen bei Plug 1

                          Darauf wurden sie sofort erkannt und ich kann auch schalten !! Den Rest habe ich noch nicht ausprobiert

                          hmmm , ich habe wohl an der falschen Stelle eingetragen , Schalten geht aber sagt > ohne Messung

                          2022-03-09 20_20_58-zigbee-0 - ubuntu und 2 weitere Seiten - Persönlich – Microsoft​ Edge.png

                          arteck Asgothian 2 Replies Last reply Reply Quote 0
                          • arteck
                            arteck Developer Most Active @Yodameister last edited by

                            @yodameister scho mal unter ausschliessen probiert ?

                            1 Reply Last reply Reply Quote 0
                            • Asgothian
                              Asgothian Developer @Yodameister last edited by

                              @yodameister

                              Die Änderungen sind bereits in den Zigbee-Herdsman-Converters vorhanden, so das eine Installation von Github die Steckdose auch unterstützen sollte.

                              @arteck

                              Sobald eine Meldung "..." not described in statesMapping... im Log auftaucht bewirkt ein Eintrag in die Ausschlussliste nichts. Geräte die nicht im statesMapping auftauchen werden automatisch über die Exposes genommen.

                              A.

                              arteck Yodameister 4 Replies Last reply Reply Quote 0
                              • arteck
                                arteck Developer Most Active @Asgothian last edited by

                                @asgothian jo hast ja auch recht.. vergess ich immer ..

                                1 Reply Last reply Reply Quote 0
                                • Yodameister
                                  Yodameister @Asgothian last edited by

                                  @asgothian

                                  Hatte ich im Vorfeld auch versucht , ich war auf 1.6.16 und habe trotzdem über Katze von Github den Adapter installiert. Dann hat er auch eine Steckdose wohl erkannt und der Adapter startete
                                  im Loop ständig neu. Das konnte ich auch nur beheben indem ich ein Backup zurück gespielt habe.

                                  Ich kann baer gerne nochmal versuchen das ganze erneut durchzuführen , ich berichte !!

                                  1 Reply Last reply Reply Quote 0
                                  • Yodameister
                                    Yodameister @Asgothian last edited by

                                    @asgothian

                                    host.ubuntu
                                    2022-03-10 17:50:03.534 warn Do not restart adapter system.adapter.zigbee.0 because restart loop detected
                                    host.ubuntu
                                    2022-03-10 17:50:03.534 info Restart adapter system.adapter.zigbee.0 because enabled
                                    host.ubuntu
                                    2022-03-10 17:50:03.534 error instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                    host.ubuntu
                                    2022-03-10 17:50:03.534 error Caught by controller[1]: at TLSSocket.emit (domain.js:475:12)
                                    host.ubuntu
                                    2022-03-10 17:50:03.534 error Caught by controller[1]: at TLSSocket.emit (events.js:400:28)
                                    host.ubuntu
                                    2022-03-10 17:50:03.534 error Caught by controller[1]: at TLSSocket.socketOnData (_http_client.js:515:22)
                                    host.ubuntu
                                    2022-03-10 17:50:03.534 error Caught by controller[1]: at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17)
                                    host.ubuntu
                                    2022-03-10 17:50:03.534 error Caught by controller[1]: at HTTPParser.parserOnIncomingClient (_http_client.js:647:27)
                                    host.ubuntu
                                    2022-03-10 17:50:03.534 error Caught by controller[1]: at ClientRequest.emit (domain.js:475:12)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[1]: at ClientRequest.emit (events.js:400:28)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[1]: at Object.onceWrapper (events.js:520:26)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[1]: at ClientRequest.<anonymous> (/opt/iobroker/node_modules/@sentry/node/src/transports/base/index.ts:252:22)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[1]: at new SentryError (/opt/iobroker/node_modules/@sentry/utils/src/error.ts:9:5)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[1]: SentryError: HTTP Error (429)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[0]: at processImmediate (internal/timers.js:466:21)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:175:25)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:463:43
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[0]: at Object.convert (/opt/iobroker/node_modules/zigbee-herdsman-converters/converters/fromZigbee.js:5299:36)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[0]: at Object.numericAttributes2Payload (/opt/iobroker/node_modules/zigbee-herdsman-converters/lib/xiaomi.js:140:32)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[0]: at Array.forEach (<anonymous>)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[0]: at /opt/iobroker/node_modules/zigbee-herdsman-converters/lib/xiaomi.js:282:39
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[0]: at buffer2DataObject (/opt/iobroker/node_modules/zigbee-herdsman-converters/lib/xiaomi.js:132:97)
                                    host.ubuntu
                                    2022-03-10 17:50:03.533 error Caught by controller[0]: at JSON.stringify (<anonymous>)
                                    host.ubuntu
                                    2022-03-10 17:50:03.532 error Caught by controller[0]: TypeError: Do not know how to serialize a BigInt

                                    zigbee.0
                                    2022-03-10 17:50:02.957 warn Terminated (UNCAUGHT_EXCEPTION): Without reason

                                    1 Reply Last reply Reply Quote 0
                                    • Yodameister
                                      Yodameister @Asgothian last edited by

                                      @asgothian

                                      Wieder das gleiche , Adapter startet ständig neu , ich habe mal auf Debug gestellt aber das ist riesig

                                      A W 2 Replies Last reply Reply Quote 0
                                      • A
                                        Aragon @Yodameister last edited by

                                        Ich habe auch die TuYA TS011F plug1 und TS011F plug3 seit einer Woche im Einsatz. Zigbee Adapter Version 1.6.16.
                                        Ich kann diese Schalten und mir weden Werte Angezeigt allerdings habe ich festgestellt, dass die Daten alle 60 sekunden versenden oder geholt werden.
                                        Kann ich diesen Abstand verkürzen auf 10 sekunden?
                                        Möchte die Waschmaschine und Trokner über die Steckdosen und den device-reminder Adapter steuern. Der Adapter benötigt die Daten alle 10 sekunden.

                                        J arteck D Asgothian 4 Replies Last reply Reply Quote 0
                                        • J
                                          Jan.S100 @Aragon last edited by

                                          @aragon Der Adapter funktioniert auch mit 60 Sekunden.
                                          Jedenfalls bei mir geht alles.

                                          1 Reply Last reply Reply Quote 0
                                          • arteck
                                            arteck Developer Most Active @Aragon last edited by arteck

                                            @aragon sagte in SHP-15+Zigbee Adp.: "TS011F" not described in statesMapping.:

                                            Möchte die Waschmaschine und Trokner über die Steckdosen und den device-reminder Adapter steuern. Der Adapter benötigt die Daten alle 10 sekunden.

                                            das ist quack... du müllst dir das Netzt zu .... damit du was.. die Waschmaschiene 50 sekunden früher ausräumen kannst..
                                            überlegmal... ob sich das echt lohnt

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            863
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            blitzwolf bw-shp15 conbee 2 zigbee adapter
                                            14
                                            60
                                            4849
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo