Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. [Aufruf] ZigBee CC253x Adapter

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.8k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.2k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.3k

[Aufruf] ZigBee CC253x Adapter

Scheduled Pinned Locked Moved Tester
1.1k Posts 131 Posters 384.9k Views 7 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • arteckA Offline
    arteckA Offline
    arteck
    Developer Most Active
    wrote on last edited by
    #376

    @modmax:

    @arteck

    Bzgl. battery habe ich gesehen, daß Ilya dort den direkten Wert von Xiaomi nun übernimmt.

    Hatte mich nämlich gewundert, wieso all meine Geräte auf einmal wieder 100% haben.

    Das haste in deinem Repo ja wieder geändert und berechnest den Batteriestatus wieder

    nach der bisherigen Methode (also %-Anzahl zwischen 2,7 und 3,2 Volt) und den Xiaomi-Status

    als battery_sec nach dem was die Xiaomi-Geräte schicken.

    Ist hier geplant, daß wieder anders zu gestalten und nur eine Methode zu verwenden,

    da die Xiaomi-Geräte Ihren Status wohl von 0-3,2V schicken …, wobei die Geräte

    schon bei weniger als 2,7V nicht funktionieren dürften?

    Nur so als Frage .. weil ich mich gestern echt wunderte wieso mit der Version 0.7.7

    nun fast alle Gerät wieder 100% haben und der Rest 99% ...

    MfG Markus `

    mir ist es egal.. es ist nur in meinem Repo.. noch kein PR dafür gestellt..

    sollte man sich vielleicht nur einigen :D

    zigbee hab ich, zwave auch, nuc's genauso und HA auch

    1 Reply Last reply
    0
    • K Offline
      K Offline
      Kueppert
      wrote on last edited by
      #377

      Macht das mit zwischen 2,7 und 3,x nicht mehr Sinn?

      Gesendet von meinem HUAWEI RIO-L01 mit Tapatalk

      UDM Pro, Intel NUC - ioBroker in Proxmox-VM, PiHole+Grafana&Influx+TasmoAdmin in LXCs, Raspberry Pi3 (als CCU), Zigbee-Stick Sonoff, Synology DS918+

      1 Reply Last reply
      0
      • L Offline
        L Offline
        Lars89
        wrote on last edited by
        #378

        Hallo,

        habe seit heute folgendes Problem:

        in der LOG steht````
        host.raspberrypi 2018-10-28 13:12:44.720 info Restart adapter system.adapter.zigbee.0 because enabled
        host.raspberrypi 2018-10-28 13:12:44.720 error instance system.adapter.zigbee.0 terminated with code 7 (Adapter already running)
        host.raspberrypi 2018-10-28 13:12:44.720 error Caught by controller[19]: linkquality: 63 } { cid: 'genBinaryValue', modelId: 'lumi.router' }
        host.raspberrypi 2018-10-28 13:12:44.720 error Caught by controller[19]: presentValue: 146 } },
        host.raspberrypi 2018-10-28 13:12:44.720 error Caught by controller[19]: inactiveText: 'NEIGHBOR',
        host.raspberrypi 2018-10-28 13:12:44.720 error Caught by controller[19]: { description: '108/xxxxxxxxxxxxxx',
        host.raspberrypi 2018-10-28 13:12:44.720 error Caught by controller[19]: data:
        host.raspberrypi 2018-10-28 13:12:44.720 error Caught by controller[19]: { cid: 'genBinaryValue',
        host.raspberrypi 2018-10-28 13:12:44.720 error Caught by controller[19]: data:
        host.raspberrypi 2018-10-28 13:12:44.720 error Caught by controller[19]: report: [Function] } ],
        host.raspberrypi 2018-10-28 13:12:44.720 error Caught by controller[19]: write: [Function],
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: read: [Function],
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: unbind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: bind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: functional: [Function],
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: foundation: [Function],
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: onZclFunctional: null,
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: onZclFoundation: null,
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: onAfIncomingMsgExt: null,
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: onAfIncomingMsg: null,
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: onAfReflectError: null,
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: onAfDataConfirm: null,
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: clusters: [Object],
        host.raspberrypi 2018-10-28 13:12:44.719 error Caught by controller[19]: outClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: inClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: devId: 256,
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: epId: 8,
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: profId: 260,
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: device: [Object],
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: isLocal: [Function],
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: [ Endpoint {
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: endpoints:
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: 2018-10-28T12:12:34.861Z zigbee:controller event attReport { type: 'attReport',
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: linkquality: 63 }
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: presentValue: 146 } },
        host.raspberrypi 2018-10-28 13:12:44.718 error Caught by controller[19]: inactiveText: 'NEIGHBOR',
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: { description: '108/xxxxxxxxxxxxxxxxxx',
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: data:
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: { cid: 'genBinaryValue',
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: data:
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: report: [Function] } ],
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: write: [Function],
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: read: [Function],
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: unbind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: bind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: functional: [Function],
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: foundation: [Function],
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: onZclFunctional: null,
        host.raspberrypi 2018-10-28 13:12:44.717 error Caught by controller[19]: onZclFoundation: null,
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: onAfIncomingMsgExt: null,
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: onAfIncomingMsg: null,
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: onAfReflectError: null,
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: onAfDataConfirm: null,
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: clusters: [Object],
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: outClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: inClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: devId: 256,
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: epId: 8,
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: profId: 260,
        host.raspberrypi 2018-10-28 13:12:44.716 error Caught by controller[19]: device: [Object],
        host.raspberrypi 2018-10-28 13:12:44.715 error Caught by controller[19]: isLocal: [Function],
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: [ Endpoint {
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: endpoints:
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: 2018-10-28T12:12:34.860Z zigbee:controller debug handleMessage { type: 'attReport',
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object]
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: linkquality: 63 } { cid: 'genBinaryValue', modelId: 'lumi.router' }
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: presentValue: 63 } },
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: inactiveText: 'COORD',
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: { description: '0/xxxxxxxxxxxx',
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: data:
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: { cid: 'genBinaryValue',
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: data:
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: report: [Function] } ],
        host.raspberrypi 2018-10-28 13:12:44.712 error Caught by controller[19]: write: [Function],
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: read: [Function],
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: unbind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: bind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: functional: [Function],
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: foundation: [Function],
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: onZclFunctional: null,
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: onZclFoundation: null,
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: onAfIncomingMsgExt: null,
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: onAfIncomingMsg: null,
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: onAfReflectError: null,
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: onAfDataConfirm: null,
        host.raspberrypi 2018-10-28 13:12:44.711 error Caught by controller[19]: clusters: [Object],
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[19]: outClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[19]: inClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[19]: devId: 256,
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[19]: epId: 8,
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[19]: profId: 260,
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[19]: device: [Object],
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[19]: isLocal: [Function],
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[19]: [ Endpoint {
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[19]: endpoints:
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[19]: 2018-10-28T12:12:34.855Z zigbee:controller event attReport { type: 'attReport',
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[18]: linkquality: 63 }
        host.raspberrypi 2018-10-28 13:12:44.710 error Caught by controller[18]: presentValue: 63 } },
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: inactiveText: 'COORD',
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: { description: '0/xxxxxxxxxxxxxxxxx',
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: data:
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: { cid: 'genBinaryValue',
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: data:
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: report: [Function] } ],
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: write: [Function],
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: read: [Function],
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: unbind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: bind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.709 error Caught by controller[18]: functional: [Function],
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: foundation: [Function],
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: onZclFunctional: null,
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: onZclFoundation: null,
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: onAfIncomingMsgExt: null,
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: onAfIncomingMsg: null,
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: onAfReflectError: null,
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: onAfDataConfirm: null,
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: clusters: [Object],
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: outClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: inClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: devId: 256,
        host.raspberrypi 2018-10-28 13:12:44.708 error Caught by controller[18]: epId: 8,
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[18]: profId: 260,
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[18]: device: [Object],
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[18]: isLocal: [Function],
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[18]: [ Endpoint {
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[18]: endpoints:
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[18]: 2018-10-28T12:12:34.853Z zigbee:controller debug handleMessage { type: 'attReport',
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[17]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object]
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[16]: linkquality: 63 } { cid: 'genBinaryValue', modelId: 'lumi.router' }
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[16]: minimumOffTime: 0 } },
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[16]: relinquishDefault: 1,
        host.raspberrypi 2018-10-28 13:12:44.707 error Caught by controller[16]: presentValue: 47,
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: inactiveText: 'PARENT',
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: { description: '49999/xxxxxxxxxxxxxxx',
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: data:
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: { cid: 'genBinaryValue',
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: data:
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: report: [Function] } ],
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: write: [Function],
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: read: [Function],
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: unbind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: bind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.706 error Caught by controller[16]: functional: [Function],
        host.raspberrypi 2018-10-28 13:12:44.705 error Caught by controller[16]: foundation: [Function],
        host.raspberrypi 2018-10-28 13:12:44.705 error Caught by controller[16]: onZclFunctional: null,
        host.raspberrypi 2018-10-28 13:12:44.705 error Caught by controller[16]: onZclFoundation: null,
        host.raspberrypi 2018-10-28 13:12:44.705 error Caught by controller[16]: onAfIncomingMsgExt: null,
        host.raspberrypi 2018-10-28 13:12:44.705 error Caught by controller[16]: onAfIncomingMsg: null,
        host.raspberrypi 2018-10-28 13:12:44.705 error Caught by controller[16]: onAfReflectError: null,
        host.raspberrypi 2018-10-28 13:12:44.705 error Caught by controller[16]: onAfDataConfirm: null,
        host.raspberrypi 2018-10-28 13:12:44.705 error Caught by controller[16]: clusters: [Object],
        host.raspberrypi 2018-10-28 13:12:44.705 error Caught by controller[16]: outClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.705 error Caught by controller[16]: inClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.699 error Caught by controller[16]: devId: 256,
        host.raspberrypi 2018-10-28 13:12:44.699 error Caught by controller[16]: epId: 8,
        host.raspberrypi 2018-10-28 13:12:44.699 error Caught by controller[16]: profId: 260,
        host.raspberrypi 2018-10-28 13:12:44.699 error Caught by controller[16]: device: [Object],
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[16]: isLocal: [Function],
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[16]: [ Endpoint {
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[16]: endpoints:
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[16]: 2018-10-28T12:12:34.850Z zigbee:controller event attReport { type: 'attReport',
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[15]: linkquality: 63 }
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[15]: minimumOffTime: 0 } },
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[15]: relinquishDefault: 1,
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[15]: presentValue: 47,
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[15]: inactiveText: 'PARENT',
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[15]: { description: '49999/xxxxxxxxxxxxxxxxx',
        host.raspberrypi 2018-10-28 13:12:44.698 error Caught by controller[15]: data:
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: { cid: 'genBinaryValue',
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: data:
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: report: [Function] } ],
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: write: [Function],
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: read: [Function],
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: unbind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: bind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: functional: [Function],
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: foundation: [Function],
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: onZclFunctional: null,
        host.raspberrypi 2018-10-28 13:12:44.697 error Caught by controller[15]: onZclFoundation: null,
        host.raspberrypi 2018-10-28 13:12:44.696 error Caught by controller[15]: onAfIncomingMsgExt: null,
        host.raspberrypi 2018-10-28 13:12:44.696 error Caught by controller[15]: onAfIncomingMsg: null,
        host.raspberrypi 2018-10-28 13:12:44.696 error Caught by controller[15]: onAfReflectError: null,
        host.raspberrypi 2018-10-28 13:12:44.696 error Caught by controller[15]: onAfDataConfirm: null,
        host.raspberrypi 2018-10-28 13:12:44.696 error Caught by controller[15]: clusters: [Object],
        host.raspberrypi 2018-10-28 13:12:44.696 error Caught by controller[15]: outClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.696 error Caught by controller[15]: inClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.696 error Caught by controller[15]: devId: 256,
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[15]: epId: 8,
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[15]: profId: 260,
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[15]: device: [Object],
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[15]: isLocal: [Function],
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[15]: [ Endpoint {
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[15]: endpoints:
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[15]: 2018-10-28T12:12:34.848Z zigbee:controller debug handleMessage { type: 'attReport',
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[14]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object]
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[13]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[12]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object]
        host.raspberrypi 2018-10-28 13:12:44.695 error Caught by controller[11]: Sun, 28 Oct 2018 12:12:34 GMT cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 17, srcaddr: 40103, srcendpoint: 8, dstendpoint: 1, wasbroadcast: 0, linkquality: 63, s
        host.raspberrypi 2018-10-28 13:12:44.694 error Caught by controller[10]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0
        host.raspberrypi 2018-10-28 13:12:44.694 error Caught by controller[9]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object]
        host.raspberrypi 2018-10-28 13:12:44.694 error Caught by controller[8]: Sun, 28 Oct 2018 12:12:34 GMT cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 17, srcaddr: 40103, srcendpoint: 8, dstendpoint: 1, wasbroadcast: 0, linkquality: 63, se
        host.raspberrypi 2018-10-28 13:12:44.694 error Caught by controller[7]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0
        host.raspberrypi 2018-10-28 13:12:44.694 error Caught by controller[6]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object]
        host.raspberrypi 2018-10-28 13:12:44.694 error Caught by controller[5]: Sun, 28 Oct 2018 12:12:34 GMT cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 17, srcaddr: 40103, srcendpoint: 8, dstendpoint: 1, wasbroadcast: 0, linkquality: 63, se
        host.raspberrypi 2018-10-28 13:12:44.694 error Caught by controller[4]: linkquality: 63 } { cid: 'genOnOff', modelId: 'lumi.router' }
        host.raspberrypi 2018-10-28 13:12:44.694 error Caught by controller[4]: data: { cid: 'genOnOff', data: { onOff: 0 } },
        host.raspberrypi 2018-10-28 13:12:44.694 error Caught by controller[4]: report: [Function] } ],
        host.raspberrypi 2018-10-28 13:12:44.693 error Caught by controller[4]: write: [Function],
        host.raspberrypi 2018-10-28 13:12:44.693 error Caught by controller[4]: read: [Function],
        host.raspberrypi 2018-10-28 13:12:44.693 error Caught by controller[4]: unbind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.693 error Caught by controller[4]: bind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.693 error Caught by controller[4]: functional: [Function],
        host.raspberrypi 2018-10-28 13:12:44.693 error Caught by controller[4]: foundation: [Function],
        host.raspberrypi 2018-10-28 13:12:44.693 error Caught by controller[4]: onZclFunctional: null,
        host.raspberrypi 2018-10-28 13:12:44.693 error Caught by controller[4]: onZclFoundation: null,
        host.raspberrypi 2018-10-28 13:12:44.693 error Caught by controller[4]: onAfIncomingMsgExt: null,
        host.raspberrypi 2018-10-28 13:12:44.693 error Caught by controller[4]: onAfIncomingMsg: null,
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: onAfReflectError: null,
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: onAfDataConfirm: null,
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: clusters: [Object],
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: outClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: inClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: devId: 256,
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: epId: 8,
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: profId: 260,
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: device: [Object],
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: isLocal: [Function],
        host.raspberrypi 2018-10-28 13:12:44.692 error Caught by controller[4]: [ Endpoint {
        host.raspberrypi 2018-10-28 13:12:44.691 error Caught by controller[4]: endpoints:
        host.raspberrypi 2018-10-28 13:12:44.691 error Caught by controller[4]: 2018-10-28T12:12:34.759Z zigbee:controller event attReport { type: 'attReport',
        host.raspberrypi 2018-10-28 13:12:44.691 error Caught by controller[3]: linkquality: 63 }
        host.raspberrypi 2018-10-28 13:12:44.691 error Caught by controller[3]: data: { cid: 'genOnOff', data: { onOff: 0 } },
        host.raspberrypi 2018-10-28 13:12:44.691 error Caught by controller[3]: report: [Function] } ],
        host.raspberrypi 2018-10-28 13:12:44.691 error Caught by controller[3]: write: [Function],
        host.raspberrypi 2018-10-28 13:12:44.691 error Caught by controller[3]: read: [Function],
        host.raspberrypi 2018-10-28 13:12:44.691 error Caught by controller[3]: unbind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.691 error Caught by controller[3]: bind: [Function],
        host.raspberrypi 2018-10-28 13:12:44.691 error Caught by controller[3]: functional: [Function],
        host.raspberrypi 2018-10-28 13:12:44.690 error Caught by controller[3]: foundation: [Function],
        host.raspberrypi 2018-10-28 13:12:44.690 error Caught by controller[3]: onZclFunctional: null,
        host.raspberrypi 2018-10-28 13:12:44.690 error Caught by controller[3]: onZclFoundation: null,
        host.raspberrypi 2018-10-28 13:12:44.690 error Caught by controller[3]: onAfIncomingMsgExt: null,
        host.raspberrypi 2018-10-28 13:12:44.690 error Caught by controller[3]: onAfIncomingMsg: null,
        host.raspberrypi 2018-10-28 13:12:44.690 error Caught by controller[3]: onAfReflectError: null,
        host.raspberrypi 2018-10-28 13:12:44.690 error Caught by controller[3]: onAfDataConfirm: null,
        host.raspberrypi 2018-10-28 13:12:44.690 error Caught by controller[3]: clusters: [Object],
        host.raspberrypi 2018-10-28 13:12:44.690 error Caught by controller[3]: outClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.689 error Caught by controller[3]: inClusterList: [Array],
        host.raspberrypi 2018-10-28 13:12:44.689 error Caught by controller[3]: devId: 256,
        host.raspberrypi 2018-10-28 13:12:44.689 error Caught by controller[3]: epId: 8,
        host.raspberrypi 2018-10-28 13:12:44.689 error Caught by controller[3]: profId: 260,
        host.raspberrypi 2018-10-28 13:12:44.689 error Caught by controller[3]: device: [Object],
        host.raspberrypi 2018-10-28 13:12:44.689 error Caught by controller[3]: isLocal: [Function],
        host.raspberrypi 2018-10-28 13:12:44.689 error Caught by controller[3]: [ Endpoint {
        host.raspberrypi 2018-10-28 13:12:44.689 error Caught by controller[3]: endpoints:
        host.raspberrypi 2018-10-28 13:12:44.689 error Caught by controller[3]: 2018-10-28T12:12:34.756Z zigbee:controller debug handleMessage { type: 'attReport',
        host.raspberrypi 2018-10-28 13:12:44.689 error Caught by controller[3]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object]
        host.raspberrypi 2018-10-28 13:12:44.688 error Caught by controller[2]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0
        host.raspberrypi 2018-10-28 13:12:44.688 error Caught by controller[1]: Sun, 28 Oct 2018 12:12:34 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object]
        host.raspberrypi 2018-10-28 13:12:44.687 error Caught by controller[0]: Sun, 28 Oct 2018 12:12:34 GMT cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 40103, srcendpoint: 8, dstendpoint: 1, wasbroadcast: 0, linkquality: 63, sec
        host.raspberrypi 2018-10-28 13:12:42.767 info instance system.adapter.zigbee.0 started with pid 23729
        host.raspberrypi 2018-10-28 13:12:12.753 info Restart adapter system.adapter.zigbee.0 because enabled
        host.raspberrypi 2018-10-28 13:12:12.753 error instance system.adapter.zigbee.0 terminated with code 7 (Adapter already running)

        
        Und das wiederholt sich in Dauerschleife in der LOG. Der Adapter macht warum auch immer, immer wieder ein neustart.
        
        Kann damit irgendjemand was anfangen und hat einen Lösungsansatz.
        
        Adapterversion 0.7.6
        
        Gruß Lars
        1 Reply Last reply
        0
        • C Offline
          C Offline
          chr-jordan
          wrote on last edited by
          #379

          @arteck:

          @chr-jordan:

          Ich habe eine Phillips Hue LTW001 (ambience white - dimmbar und Weißtemperatur einstellbar). Diese wird auch noch als Fragezeichen-Kachel angezeigt.

          LTW001

          001788010237052d

          Christopher `

          installiere mal aus meinem Repo..zum testen

          https://github.com/arteck/ioBroker.zigbee `

          Danke arteck mit deiner 0.7.6 funktioniert die Phillips Hue LTW001 . LTW012 (Hue White ambiance E14) gehen auch.

          Schönen Sonntag!

          1 Reply Last reply
          0
          • modmaxM Offline
            modmaxM Offline
            modmax
            wrote on last edited by
            #380

            @lars89

            Starte mal iobroker neu .. nicht nur den Adapter…

            1 Reply Last reply
            0
            • M Offline
              M Offline
              MagicSven
              wrote on last edited by
              #381

              @Tagiwara:

              Wie kann ich denn mit Alexa beispielsweise die Temperatur eines Sensors abfragen? Mit dem original Xiaomi Gateway brauchte ich nur ein Smart Gerät im Cloud Adapter anlegen und konnte das abfragen. Das geht ja aber jetzt nicht mehr (zumindest bei mir nicht).

              Wie macht ihr das? ` Im Cloud Adapter den Temperatur Datenpunkt anlegen und einen Namen vergeben wie z.B. Wohnzimmer.

              "Alexa, wie ist die Temperatur im Wohnzimmer" und schon erhälst du die Antwort.

              Gesendet von meinem SM-G960F mit Tapatalk

              1 Reply Last reply
              0
              • C Offline
                C Offline
                Christian.B
                wrote on last edited by
                #382

                @modmax:

                @lars89

                Starte mal iobroker neu .. nicht nur den Adapter… `
                eine wirklich peinliche Frage. Wie startet man den iobroker richtig neu?

                Ich ziehe immer einmal den Netzstecker von Raspi.

                viele Grüße

                Christian

                1 Reply Last reply
                0
                • C Offline
                  C Offline
                  Christian.B
                  wrote on last edited by
                  #383

                  @Allodo:

                  Jetzt habe ich doch ein Problem mit meinem Rauchmelder (Xiaomi Mijia Honeywell) :(

                  Ich habe gestern mal einen Alarm ausgelöst, um zu sehen, was im iobroker angezeigt wird um darauf reagieren zu können. Leider wird dort gar nix angezeigt, außer dem Batteriestatus und das eine Verbindung besteht. :roll:

                  Der Punkt mit Alarmstatus war leer, wie vor dem Alarm. Ich hätte jetzt damit gerechnet, dass irgendein Eintrag vorhanden ist.

                  Weiß jemand, wie ich die Rauchmelder vernetze? `

                  @Allodo:

                  Für den Rauchmelder scheint wohl ein wichtiger Eintrag zu fehlen.

                  Und zwar genau der, der angibt, ob ein Alarm ausgelöst wurde :shock:

                  Xiaomi Adapter (Habe ich aus einem Video kopiert)

                  Xiaomi Adapter.png

                  Zigbee Adapter

                  Zigbee Adapter.png

                  Habe auch schon mehrfach gepairt (Version 0.7.7), aber der Eintrag will einfach nicht erscheinen :( `

                  Ich wollte einmal meine Erfahrungen zum Xiaomi Mijia Honeywell Rauchmelder aufschreiben.

                  Habe 2 von den Geräten am cc2530 angemeldet.

                  Bei mir verhält es sich so, dass der Status unter Objekte bei einer manuellen Alarmauslösung über den Knopf tatsächlich auf false bleibt. Bei diesem Vorgang sieht man, dass die Aktion erkannt wird da die Einträge "battery,status, voltage" bei Tastendruck alle gleichzeitig kurz grün aufleuchten. Status beleibt jedoch "false".

                  Wenn man aber den Alarm mit echtem Rauch auslöst, wechselt der "status" auf true!

                  Somit habe ich mir ein Skript geschrieben mit dem ich bei Rauch per Telegram informiert werde.

                  Das funktioniert 1a!

                  Dennoch wäre es tatsächlich sehr schön, wenn man bei der manuellen Alarmauslösung die gesamte Kette bis zum Handy oder Ähnliches regelmäßig, ohne echten Rauch zu produzieren, nur durch den Tastendruck überprüfen könnte.

                  Benutze derzeit die zigbee Version 0.7.6

                  viele Grüße

                  Christian

                  1 Reply Last reply
                  0
                  • M Offline
                    M Offline
                    MagicSven
                    wrote on last edited by
                    #384

                    @ Christian, vielen Dank für die Erkenntnis. Das ist sicher für den ein oder anderen ein wichtiger Hinweis

                    Gesendet von meinem SM-G960F mit Tapatalk

                    1 Reply Last reply
                    0
                    • a200A Offline
                      a200A Offline
                      a200
                      wrote on last edited by
                      #385

                      @Christian.B:

                      eine wirklich peinliche Frage. Wie startet man den iobroker richtig neu?

                      Ich ziehe immer einmal den Netzstecker von Raspi. `

                      sudo shutdown -r now
                      
                      

                      oder

                      sudo reboot
                      

                      IoBroker auf QNAP TS-451, Raspi und NUC

                      1 Reply Last reply
                      0
                      • L Offline
                        L Offline
                        Lars89
                        wrote on last edited by
                        #386

                        Hallo, habe den iobroker bzw. den ganzen Raspi öfters neugestartet. Jetzt nach dem gefühlten 300 mal scheint wieder alles zu laufen.

                        Bekomme jetzt nur noch "eine" Fehlermeldung ständig in der LOG:

                        zigbee.0	2018-10-29 18:50:51.602	error	Zigbee publish to 'xxxxxxxxxxxx', genOnOff - off - {} - 3 failed with error Error: AF data request fails, status code: 205\. No network route. Please confirm that the device has (re)joined the n
                        zigbee.0	2018-10-29 18:50:36.494	error	Zigbee publish to 'xxxxxxxxxxxxxx', genLevelCtrl - moveToLevelWithOnOff - {"level":150,"transtime":0} - 3 failed with error Error: Timed out after 30000 ms
                        zigbee.0	2018-10-29 18:50:36.396	error	Zigbee publish to 'xxxxxxxxxxx', genLevelCtrl - moveToLevelWithOnOff - {"level":150,"transtime":0} - 3 failed with error Error: Timed out after 30000 ms
                        zigbee.0	2018-10-29 18:50:36.120	error	Zigbee publish to 'xxxxxxxxxxxxxxx', genOnOff - off - {} - 3 failed with error Error: AF data request fails, status code: 233\. MAC no ack.
                        

                        sind alles OSRAM Lampen, scheinbar gibt es da noch irgendwelche Probleme. Sie Funktionieren alle einwandfrei, und eine Route so wie im Fehler steht,besteht auch auf jedenfalls laut Netzwerkkarte.

                        LG

                        1 Reply Last reply
                        0
                        • modmaxM Offline
                          modmaxM Offline
                          modmax
                          wrote on last edited by
                          #387

                          Den Fehler hatte ich auch mal … da stand mein SmartPlusPlug von OSRAM zu weit weg.

                          Das bedeutete, daß er Befehle annehmen konnte ... aber das Senden der Bestätigung vom Plug zurück zum Coordinator

                          erfolgte nicht "in time"; weil eben zu weit weg ...

                          1 Reply Last reply
                          0
                          • L Offline
                            L Offline
                            Lars89
                            wrote on last edited by
                            #388

                            Danke für die Antwort. Die Lampen sind vielleicht 5 m (durch eine Wand) vom Stick entfernt und die HUE Lampen sind gut 20 m (durch mehrer Wände) weit weg und schmeißen keine Fehlermeldung raus. Die Fehler sind auch nur bei den E27 die GU10 laufen ohne Fehlermeldung.

                            Werde mal gucken ob ich noch weitere Hue E27 bekomme. Dann fliegen die OSRAM raus.

                            LG

                            1 Reply Last reply
                            0
                            • C Offline
                              C Offline
                              Christian.B
                              wrote on last edited by
                              #389

                              @a200:

                              @Christian.B:

                              eine wirklich peinliche Frage. Wie startet man den iobroker richtig neu?

                              Ich ziehe immer einmal den Netzstecker von Raspi. `

                              sudo shutdown -r now
                              
                              

                              oder

                              sudo reboot
                              ```` `  
                              

                              Danke, mit diesen Befehlen habe ich den iobroker auch schon neu gestartet.

                              Warum gibt es eigentlich keinen button: "Neustart" im Iobroker?

                              viele Grüße

                              Christian

                              1 Reply Last reply
                              0
                              • M Offline
                                M Offline
                                MagicSven
                                wrote on last edited by
                                #390

                                @Christian.B:

                                @a200:

                                @Christian.B:

                                eine wirklich peinliche Frage. Wie startet man den iobroker richtig neu?

                                Ich ziehe immer einmal den Netzstecker von Raspi. `

                                sudo shutdown -r now
                                
                                

                                oder

                                sudo reboot
                                ```` `  
                                

                                Danke, mit diesen Befehlen habe ich den iobroker auch schon neu gestartet.

                                Warum gibt es eigentlich keinen button: "Neustart" im Iobroker? ` Gibt es doch.

                                Gehe im iobroker auf Host und klicke dahinter auf Refresh.

                                Dann startet iobroker neu.

                                Gesendet von meinem SM-G960F mit Tapatalk

                                1 Reply Last reply
                                0
                                • C Offline
                                  C Offline
                                  Christian.B
                                  wrote on last edited by
                                  #391

                                  Ah, sehr gut. Vielen Dank!

                                  viele Grüße

                                  Christian

                                  1 Reply Last reply
                                  0
                                  • A Offline
                                    A Offline
                                    Allodo
                                    wrote on last edited by
                                    #392

                                    Wie sieht es denn mit dem fehlenden wichtigen Eintrag bei den Rauchmeldern aus?

                                    Würde diese gerne verbauen, aber wenn der iobroker keine Statusänderung beim Auslösen des Alarms bekommt, sind diese wertlos für mich :(

                                    1 Reply Last reply
                                    0
                                    • arteckA Offline
                                      arteckA Offline
                                      arteck
                                      Developer Most Active
                                      wrote on last edited by
                                      #393

                                      @Allodo:

                                      Wie sieht es denn mit dem fehlenden wichtigen Eintrag bei den Rauchmeldern aus?

                                      Würde diese gerne verbauen, aber wenn der iobroker keine Statusänderung beim Auslösen des Alarms bekommt, sind diese wertlos für mich :( `

                                      das geht.. halt nur bei Rauch..

                                      per Taste nicht. das gibt die Lib nicht her..

                                      zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                      1 Reply Last reply
                                      0
                                      • A Offline
                                        A Offline
                                        Allodo
                                        wrote on last edited by
                                        #394
                                        das geht.. halt nur bei Rauch.. 
                                        per Taste nicht. das gibt die Lib nicht her
                                        

                                        Der Punkt existiert aber gar nicht, egal, ob per Rauch initiiert, oder per Taste. Per Xiaomi Gateway bzw. dessen Adapter gibt es den Punkt (siehe meine Screenshots in meinen vorherigen Post).

                                        1 Reply Last reply
                                        0
                                        • P Offline
                                          P Offline
                                          piscator83
                                          wrote on last edited by
                                          #395

                                          Hallo alle zusammen!

                                          Neu hier, also bitte nicht beißen! :-)

                                          Vllt. bin ich auch zu blöd, aber könnte es sein, dass diese LED noch nicht funktioniert?
                                          9481_osram_gu10_rgb.png

                                          An/Aus; Farben; Warm/Kalt, Dimmen kann das Ding laut Verpackung.

                                          lg

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          425

                                          Online

                                          32.4k

                                          Users

                                          81.5k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe