Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • 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

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Zigbee 1.2.1 pairing geht nicht mehr

NEWS

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

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

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

Zigbee 1.2.1 pairing geht nicht mehr

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
zigbee adapterkein pairing
89 Beiträge 8 Kommentatoren 7.3k Aufrufe 7 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • V vikk88

    @arteck nein binding benutze ich nicht. Das gerät ist der Plug von Osram. Mein Plan war jetzt den zu löschen und gegen einen weiteren Tuya auszutauschen und die ganze Sache weiter zu beobachten. Sollte das Problem weiter bestehen würde ich die 1.1.3 aufspielen.

    @Asgothian ich habe mit dem zigbee Adapter die aktuellste geladen

    4bed9fa0-ac1e-4a48-85cc-152d2873d9d6-image.png

    AsgothianA Offline
    AsgothianA Offline
    Asgothian
    Developer
    schrieb am zuletzt editiert von
    #48

    @vikk88 ok.. danke. Damit geht diese Überlegung den Bach herunter.

    A.

    ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
    "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

    1 Antwort Letzte Antwort
    0
    • V Offline
      V Offline
      vikk88
      schrieb am zuletzt editiert von
      #49

      @Asgothian so heute hat sich die Osram Led wieder resetet. Im Log steht auch failed to execute routing table. Kann es sein das die 1.2.0 Probleme mit Osram Geräten hat?

      zigbee.0	2020-10-01 17:15:34.033	debug	(12265) Publish {"power":0,"current":0,"voltage":235}
      zigbee.0	2020-10-01 17:15:34.012	debug	(12265) Type readResponse device {"type":"device","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":26
      zigbee.0	2020-10-01 17:15:34.011	debug	(12265) Received Zigbee message from '0x842e14fffe1394fe', type 'readResponse', cluster 'haElectricalMeasurement', data '{"rmsVoltage":235,"rmsCurrent":0,"activePower":0}' from endpoint 1 with groupID
      zigbee.0	2020-10-01 17:15:34.009	debug	(12265) handleMessage. {"type":"readResponse","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260,"d
      zigbee.0	2020-10-01 17:15:30.667	debug	(12265) Publish {"power":0,"current":0,"voltage":226}
      zigbee.0	2020-10-01 17:15:30.644	debug	(12265) Type readResponse device {"type":"device","device":{"ID":6,"_type":"Router","_ieeeAddr":"0x842e14fffe51c5c4","_networkAddress":8908,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260
      zigbee.0	2020-10-01 17:15:30.643	debug	(12265) Received Zigbee message from '0x842e14fffe51c5c4', type 'readResponse', cluster 'haElectricalMeasurement', data '{"rmsVoltage":226,"rmsCurrent":0,"activePower":0}' from endpoint 1 with groupID
      zigbee.0	2020-10-01 17:15:30.641	debug	(12265) handleMessage. {"type":"readResponse","device":{"ID":6,"_type":"Router","_ieeeAddr":"0x842e14fffe51c5c4","_networkAddress":8908,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260,"de
      zigbee.0	2020-10-01 17:15:29.684	debug	(12265) convert result {"state":{"state":"OFF","brightness":0}}
      zigbee.0	2020-10-01 17:15:29.228	debug	(12265) convert result {"state":{"state":"OFF","brightness":0}}
      zigbee.0	2020-10-01 17:15:28.985	debug	(12265) target: {"ID":3,"profileID":49246,"deviceID":256,"inputClusters":[4096,0,3,4,5,6,8,64527],"outputClusters":[25],"deviceNetworkAddress":36891,"deviceIeeeAddress":"0x7cb03eaa0a04f888","clusters"
      zigbee.0	2020-10-01 17:15:28.984	debug	(12265) convert state, OFF, {"state":"OFF"}
      zigbee.0	2020-10-01 17:15:28.984	debug	(12265) entity: {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x7cb03eaa0a04f888","_networkAddress":36891,"_manufacturerID":48042,"_endpoints":[{"ID":3,"profileID":49246,"deviceID":2
      zigbee.0	2020-10-01 17:15:28.983	debug	(12265) State changes. dev: 0x7cb03eaa0a04f888 model: AC03641 states: [{"stateDesc":{"id":"state","name":"Switch state","role":"switch","write":true,"read":true,"type":"boolean","inOptions":true},"val
      zigbee.0	2020-10-01 17:15:28.982	debug	(12265) Change state 'state' at device 0x7cb03eaa0a04f888 type 'AC03641'
      zigbee.0	2020-10-01 17:15:28.974	debug	(12265) User stateChange zigbee.0.7cb03eaa0a04f888.state {"val":false,"ack":false,"ts":1601565328967,"q":0,"from":"system.adapter.javascript.0","user":"system.user.admin","lc":1601530034448}
      zigbee.0	2020-10-01 17:15:28.738	debug	(12265) target: {"ID":3,"profileID":49246,"deviceID":256,"inputClusters":[4096,0,3,4,5,6,8,64527],"outputClusters":[25],"deviceNetworkAddress":36891,"deviceIeeeAddress":"0x7cb03eaa0a04f888","clusters"
      zigbee.0	2020-10-01 17:15:28.737	debug	(12265) convert state, OFF, {"state":"OFF"}
      zigbee.0	2020-10-01 17:15:28.737	debug	(12265) entity: {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x7cb03eaa0a04f888","_networkAddress":36891,"_manufacturerID":48042,"_endpoints":[{"ID":3,"profileID":49246,"deviceID":2
      zigbee.0	2020-10-01 17:15:28.736	debug	(12265) State changes. dev: 0x7cb03eaa0a04f888 model: AC03641 states: [{"stateDesc":{"id":"state","name":"Switch state","role":"switch","write":true,"read":true,"type":"boolean","inOptions":true},"val
      zigbee.0	2020-10-01 17:15:28.735	debug	(12265) Change state 'state' at device 0x7cb03eaa0a04f888 type 'AC03641'
      zigbee.0	2020-10-01 17:15:28.728	debug	(12265) User stateChange zigbee.0.7cb03eaa0a04f888.state {"val":false,"ack":false,"ts":1601565328722,"q":0,"from":"system.adapter.javascript.0","user":"system.user.admin","lc":1601530034448}
      zigbee.0	2020-10-01 17:15:24.032	debug	(12265) Publish {"power":0,"current":0,"voltage":238}
      zigbee.0	2020-10-01 17:15:24.009	debug	(12265) Type readResponse device {"type":"device","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":26
      zigbee.0	2020-10-01 17:15:24.007	debug	(12265) Received Zigbee message from '0x842e14fffe1394fe', type 'readResponse', cluster 'haElectricalMeasurement', data '{"rmsVoltage":238,"rmsCurrent":0,"activePower":0}' from endpoint 1 with groupID
      zigbee.0	2020-10-01 17:15:24.006	debug	(12265) handleMessage. {"type":"readResponse","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260,"d
      zigbee.0	2020-10-01 17:15:23.666	debug	(12265) convert result {"state":{"state":"OFF","brightness":0}}
      zigbee.0	2020-10-01 17:15:23.277	debug	(12265) convert result {"state":{"state":"OFF","brightness":0}}
      zigbee.0	2020-10-01 17:15:22.805	debug	(12265) sendTo "getMap" to system.adapter.admin.0 from system.adapter.zigbee.0
      zigbee.0	2020-10-01 17:15:22.804	debug	(12265) getMap result: {"lqis":[{"parent":"0x00124b001936a117","networkAddress":25087,"ieeeAddr":"0x00158d000422fd64","lqi":29,"relationship":1,"depth":1,"status":"online"},{"parent":"0x00124b001936a1
      zigbee.0	2020-10-01 17:15:22.803	debug	(12265) Get map succeeded [{"parent":"0x00124b001936a117","networkAddress":25087,"ieeeAddr":"0x00158d000422fd64","lqi":29,"relationship":1,"depth":1,"status":"online"},{"parent":"0x00124b001936a117","
      zigbee.0	2020-10-01 17:15:22.802	debug	(12265) Routing table succeeded for '0x7cb03eaa0a04f888'
      zigbee.0	2020-10-01 17:15:22.802	debug	(12265) Routing for '0x7cb03eaa0a04f888': {"neighbors":[{"linkquality":54,"networkAddress":11448,"ieeeAddr":"0x842e14fffe1394fe","relationship":2,"depth":1},{"linkquality":42,"networkAddress":0,"ieeeA
      zigbee.0	2020-10-01 17:15:22.801	debug	(12265) Failed to execute routing table for '0x7cb03eaa0a04f888'. "Error: AREQ - ZDO - mgmtRtgRsp after 10000ms\n at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigb
      zigbee.0	2020-10-01 17:15:20.671	debug	(12265) Publish {"power":0,"current":0,"voltage":226}
      zigbee.0	2020-10-01 17:15:20.644	debug	(12265) Type readResponse device {"type":"device","device":{"ID":6,"_type":"Router","_ieeeAddr":"0x842e14fffe51c5c4","_networkAddress":8908,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260
      zigbee.0	2020-10-01 17:15:20.642	debug	(12265) Received Zigbee message from '0x842e14fffe51c5c4', type 'readResponse', cluster 'haElectricalMeasurement', data '{"rmsVoltage":226,"rmsCurrent":0,"activePower":0}' from endpoint 1 with groupID
      zigbee.0	2020-10-01 17:15:20.641	debug	(12265) handleMessage. {"type":"readResponse","device":{"ID":6,"_type":"Router","_ieeeAddr":"0x842e14fffe51c5c4","_networkAddress":8908,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260,"de
      zigbee.0	2020-10-01 17:15:18.974	debug	(12265) target: {"ID":3,"profileID":49246,"deviceID":256,"inputClusters":[4096,0,3,4,5,6,8,64527],"outputClusters":[25],"deviceNetworkAddress":36891,"deviceIeeeAddress":"0x7cb03eaa0a04f888","clusters"
      zigbee.0	2020-10-01 17:15:18.974	debug	(12265) convert state, OFF, {"state":"OFF"}
      zigbee.0	2020-10-01 17:15:18.973	debug	(12265) entity: {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x7cb03eaa0a04f888","_networkAddress":36891,"_manufacturerID":48042,"_endpoints":[{"ID":3,"profileID":49246,"deviceID":2
      zigbee.0	2020-10-01 17:15:18.971	debug	(12265) State changes. dev: 0x7cb03eaa0a04f888 model: AC03641 states: [{"stateDesc":{"id":"state","name":"Switch state","role":"switch","write":true,"read":true,"type":"boolean","inOptions":true},"val
      zigbee.0	2020-10-01 17:15:18.970	debug	(12265) Change state 'state' at device 0x7cb03eaa0a04f888 type 'AC03641'
      zigbee.0	2020-10-01 17:15:18.967	debug	(12265) User stateChange zigbee.0.7cb03eaa0a04f888.state {"val":false,"ack":false,"ts":1601565318962,"q":0,"from":"system.adapter.javascript.0","user":"system.user.admin","lc":1601530034448}
      zigbee.0	2020-10-01 17:15:18.727	debug	(12265) target: {"ID":3,"profileID":49246,"deviceID":256,"inputClusters":[4096,0,3,4,5,6,8,64527],"outputClusters":[25],"deviceNetworkAddress":36891,"deviceIeeeAddress":"0x7cb03eaa0a04f888","clusters"
      zigbee.0	2020-10-01 17:15:18.726	debug	(12265) convert state, OFF, {"state":"OFF"}
      zigbee.0	2020-10-01 17:15:18.726	debug	(12265) entity: {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x7cb03eaa0a04f888","_networkAddress":36891,"_manufacturerID":48042,"_endpoints":[{"ID":3,"profileID":49246,"deviceID":2
      zigbee.0	2020-10-01 17:15:18.725	debug	(12265) State changes. dev: 0x7cb03eaa0a04f888 model: AC03641 states: [{"stateDesc":{"id":"state","name":"Switch state","role":"switch","write":true,"read":true,"type":"boolean","inOptions":true},"val
      zigbee.0	2020-10-01 17:15:18.725	debug	(12265) Change state 'state' at device 0x7cb03eaa0a04f888 type 'AC03641'
      zigbee.0	2020-10-01 17:15:18.713	debug	(12265) User stateChange zigbee.0.7cb03eaa0a04f888.state {"val":false,"ack":false,"ts":1601565318710,"q":0,"from":"system.adapter.javascript.0","user":"system.user.admin","lc":1601530034448}
      zigbee.0	2020-10-01 17:15:18.698	debug	(12265) Publish {"occupancy":false}
      zigbee.0	2020-10-01 17:15:14.032	debug	(12265) Publish {"power":0,"current":0,"voltage":238}
      zigbee.0	2020-10-01 17:15:14.011	debug	(12265) Type readResponse device {"type":"device","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":2
      zigbee.0	2020-10-01 17:15:14.007	debug	(12265) Received Zigbee message from '0x842e14fffe1394fe', type 'readResponse', cluster 'haElectricalMeasurement', data '{"rmsVoltage":238,"rmsCurrent":0,"activePower":0}' from endpoint 1 with groupI
      zigbee.0	2020-10-01 17:15:14.006	debug	(12265) handleMessage. {"type":"readResponse","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260,"
      zigbee.0	2020-10-01 17:15:12.783	debug	(12265) LQI succeeded for '0x7cb03eaa0a04f888'
      zigbee.0	2020-10-01 17:15:12.716	debug	(12265) Publish {"pressure":971.4}
      zigbee.0	2020-10-01 17:15:12.713	debug	(12265) Publish {"humidity":56.2}
      zigbee.0	2020-10-01 17:15:12.698	debug	(12265) Publish {"temperature":21.76}
      zigbee.0	2020-10-01 17:15:12.696	debug	(12265) Type attributeReport device {"type":"device","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profi
      zigbee.0	2020-10-01 17:15:12.695	debug	(12265) Received Zigbee message from '0x00158d0002733e82', type 'attributeReport', cluster 'msPressureMeasurement', data '{"16":9714,"20":-1,"measuredValue":971}' from endpoint 1 with groupID 0
      zigbee.0	2020-10-01 17:15:12.694	debug	(12265) Type attributeReport device {"type":"device","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profi
      zigbee.0	2020-10-01 17:15:12.693	debug	(12265) Received Zigbee message from '0x00158d0002733e82', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":5620}' from endpoint 1 with groupID 0
      zigbee.0	2020-10-01 17:15:12.692	debug	(12265) handleMessage. {"type":"attributeReport","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profileID
      zigbee.0	2020-10-01 17:15:12.690	debug	(12265) handleMessage. {"type":"attributeReport","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profileID
      zigbee.0	2020-10-01 17:15:12.687	debug	(12265) Type attributeReport device {"type":"device","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profi
      zigbee.0	2020-10-01 17:15:12.686	debug	(12265) Received Zigbee message from '0x00158d0002733e82', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2176}' from endpoint 1 with groupID 0
      zigbee.0	2020-10-01 17:15:12.685	debug	(12265) handleMessage. {"type":"attributeReport","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profileID
      zigbee.0	2020-10-01 17:15:12.341	debug	(12265) Routing table succeeded for '0x842e14fffe1394fe'
      zigbee.0	2020-10-01 17:15:12.340	debug	(12265) Routing for '0x842e14fffe1394fe': {"table":[{"destinationAddress":0,"nextHop":0},{"destinationAddress":8908,"status":"ACTIVE","nextHop":8908},{"destinationAddress":50048,"status":"ACTIVE","ne
      zigbee.0	2020-10-01 17:15:12.261	debug	(12265) LQI succeeded for '0x842e14fffe1394fe'
      zigbee.0	2020-10-01 17:15:12.097	debug	(12265) Routing table succeeded for '0x842e14fffe51c5c4'
      zigbee.0	2020-10-01 17:15:12.097	debug	(12265) Routing for '0x842e14fffe51c5c4': {"table":[{"destinationAddress":0,"nextHop":11448},{"destinationAddress":35007,"status":"ACTIVE","nextHop":36891},{"destinationAddress":59922,"status":"ACTIV
      zigbee.0	2020-10-01 17:15:12.001	debug	(12265) LQI succeeded for '0x842e14fffe51c5c4'
      zigbee.0	2020-10-01 17:15:11.942	debug	(12265) sendTo "getBinding" to system.adapter.admin.0 from system.adapter.zigbee.0
      zigbee.0	2020-10-01 17:15:11.942	debug	(12265) getBinding result: []
      zigbee.0	2020-10-01 17:15:11.797	debug	(12265) sendTo "getDevices" to system.adapter.admin.0 from system.adapter.zigbee.0
      
      

      Alle Sensoren die an der Led hingen haben sich auch wieder getrennt
      eb2b975e-b0ce-4d53-98e2-2fa261a1aaad-image.png
      Die BM reagieren aber noch und sind auch aviable. Kommen mir aber träger vor, also brauchen länger um zu schalten

      arteckA 1 Antwort Letzte Antwort
      0
      • V vikk88

        @Asgothian so heute hat sich die Osram Led wieder resetet. Im Log steht auch failed to execute routing table. Kann es sein das die 1.2.0 Probleme mit Osram Geräten hat?

        zigbee.0	2020-10-01 17:15:34.033	debug	(12265) Publish {"power":0,"current":0,"voltage":235}
        zigbee.0	2020-10-01 17:15:34.012	debug	(12265) Type readResponse device {"type":"device","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":26
        zigbee.0	2020-10-01 17:15:34.011	debug	(12265) Received Zigbee message from '0x842e14fffe1394fe', type 'readResponse', cluster 'haElectricalMeasurement', data '{"rmsVoltage":235,"rmsCurrent":0,"activePower":0}' from endpoint 1 with groupID
        zigbee.0	2020-10-01 17:15:34.009	debug	(12265) handleMessage. {"type":"readResponse","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260,"d
        zigbee.0	2020-10-01 17:15:30.667	debug	(12265) Publish {"power":0,"current":0,"voltage":226}
        zigbee.0	2020-10-01 17:15:30.644	debug	(12265) Type readResponse device {"type":"device","device":{"ID":6,"_type":"Router","_ieeeAddr":"0x842e14fffe51c5c4","_networkAddress":8908,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260
        zigbee.0	2020-10-01 17:15:30.643	debug	(12265) Received Zigbee message from '0x842e14fffe51c5c4', type 'readResponse', cluster 'haElectricalMeasurement', data '{"rmsVoltage":226,"rmsCurrent":0,"activePower":0}' from endpoint 1 with groupID
        zigbee.0	2020-10-01 17:15:30.641	debug	(12265) handleMessage. {"type":"readResponse","device":{"ID":6,"_type":"Router","_ieeeAddr":"0x842e14fffe51c5c4","_networkAddress":8908,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260,"de
        zigbee.0	2020-10-01 17:15:29.684	debug	(12265) convert result {"state":{"state":"OFF","brightness":0}}
        zigbee.0	2020-10-01 17:15:29.228	debug	(12265) convert result {"state":{"state":"OFF","brightness":0}}
        zigbee.0	2020-10-01 17:15:28.985	debug	(12265) target: {"ID":3,"profileID":49246,"deviceID":256,"inputClusters":[4096,0,3,4,5,6,8,64527],"outputClusters":[25],"deviceNetworkAddress":36891,"deviceIeeeAddress":"0x7cb03eaa0a04f888","clusters"
        zigbee.0	2020-10-01 17:15:28.984	debug	(12265) convert state, OFF, {"state":"OFF"}
        zigbee.0	2020-10-01 17:15:28.984	debug	(12265) entity: {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x7cb03eaa0a04f888","_networkAddress":36891,"_manufacturerID":48042,"_endpoints":[{"ID":3,"profileID":49246,"deviceID":2
        zigbee.0	2020-10-01 17:15:28.983	debug	(12265) State changes. dev: 0x7cb03eaa0a04f888 model: AC03641 states: [{"stateDesc":{"id":"state","name":"Switch state","role":"switch","write":true,"read":true,"type":"boolean","inOptions":true},"val
        zigbee.0	2020-10-01 17:15:28.982	debug	(12265) Change state 'state' at device 0x7cb03eaa0a04f888 type 'AC03641'
        zigbee.0	2020-10-01 17:15:28.974	debug	(12265) User stateChange zigbee.0.7cb03eaa0a04f888.state {"val":false,"ack":false,"ts":1601565328967,"q":0,"from":"system.adapter.javascript.0","user":"system.user.admin","lc":1601530034448}
        zigbee.0	2020-10-01 17:15:28.738	debug	(12265) target: {"ID":3,"profileID":49246,"deviceID":256,"inputClusters":[4096,0,3,4,5,6,8,64527],"outputClusters":[25],"deviceNetworkAddress":36891,"deviceIeeeAddress":"0x7cb03eaa0a04f888","clusters"
        zigbee.0	2020-10-01 17:15:28.737	debug	(12265) convert state, OFF, {"state":"OFF"}
        zigbee.0	2020-10-01 17:15:28.737	debug	(12265) entity: {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x7cb03eaa0a04f888","_networkAddress":36891,"_manufacturerID":48042,"_endpoints":[{"ID":3,"profileID":49246,"deviceID":2
        zigbee.0	2020-10-01 17:15:28.736	debug	(12265) State changes. dev: 0x7cb03eaa0a04f888 model: AC03641 states: [{"stateDesc":{"id":"state","name":"Switch state","role":"switch","write":true,"read":true,"type":"boolean","inOptions":true},"val
        zigbee.0	2020-10-01 17:15:28.735	debug	(12265) Change state 'state' at device 0x7cb03eaa0a04f888 type 'AC03641'
        zigbee.0	2020-10-01 17:15:28.728	debug	(12265) User stateChange zigbee.0.7cb03eaa0a04f888.state {"val":false,"ack":false,"ts":1601565328722,"q":0,"from":"system.adapter.javascript.0","user":"system.user.admin","lc":1601530034448}
        zigbee.0	2020-10-01 17:15:24.032	debug	(12265) Publish {"power":0,"current":0,"voltage":238}
        zigbee.0	2020-10-01 17:15:24.009	debug	(12265) Type readResponse device {"type":"device","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":26
        zigbee.0	2020-10-01 17:15:24.007	debug	(12265) Received Zigbee message from '0x842e14fffe1394fe', type 'readResponse', cluster 'haElectricalMeasurement', data '{"rmsVoltage":238,"rmsCurrent":0,"activePower":0}' from endpoint 1 with groupID
        zigbee.0	2020-10-01 17:15:24.006	debug	(12265) handleMessage. {"type":"readResponse","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260,"d
        zigbee.0	2020-10-01 17:15:23.666	debug	(12265) convert result {"state":{"state":"OFF","brightness":0}}
        zigbee.0	2020-10-01 17:15:23.277	debug	(12265) convert result {"state":{"state":"OFF","brightness":0}}
        zigbee.0	2020-10-01 17:15:22.805	debug	(12265) sendTo "getMap" to system.adapter.admin.0 from system.adapter.zigbee.0
        zigbee.0	2020-10-01 17:15:22.804	debug	(12265) getMap result: {"lqis":[{"parent":"0x00124b001936a117","networkAddress":25087,"ieeeAddr":"0x00158d000422fd64","lqi":29,"relationship":1,"depth":1,"status":"online"},{"parent":"0x00124b001936a1
        zigbee.0	2020-10-01 17:15:22.803	debug	(12265) Get map succeeded [{"parent":"0x00124b001936a117","networkAddress":25087,"ieeeAddr":"0x00158d000422fd64","lqi":29,"relationship":1,"depth":1,"status":"online"},{"parent":"0x00124b001936a117","
        zigbee.0	2020-10-01 17:15:22.802	debug	(12265) Routing table succeeded for '0x7cb03eaa0a04f888'
        zigbee.0	2020-10-01 17:15:22.802	debug	(12265) Routing for '0x7cb03eaa0a04f888': {"neighbors":[{"linkquality":54,"networkAddress":11448,"ieeeAddr":"0x842e14fffe1394fe","relationship":2,"depth":1},{"linkquality":42,"networkAddress":0,"ieeeA
        zigbee.0	2020-10-01 17:15:22.801	debug	(12265) Failed to execute routing table for '0x7cb03eaa0a04f888'. "Error: AREQ - ZDO - mgmtRtgRsp after 10000ms\n at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigb
        zigbee.0	2020-10-01 17:15:20.671	debug	(12265) Publish {"power":0,"current":0,"voltage":226}
        zigbee.0	2020-10-01 17:15:20.644	debug	(12265) Type readResponse device {"type":"device","device":{"ID":6,"_type":"Router","_ieeeAddr":"0x842e14fffe51c5c4","_networkAddress":8908,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260
        zigbee.0	2020-10-01 17:15:20.642	debug	(12265) Received Zigbee message from '0x842e14fffe51c5c4', type 'readResponse', cluster 'haElectricalMeasurement', data '{"rmsVoltage":226,"rmsCurrent":0,"activePower":0}' from endpoint 1 with groupID
        zigbee.0	2020-10-01 17:15:20.641	debug	(12265) handleMessage. {"type":"readResponse","device":{"ID":6,"_type":"Router","_ieeeAddr":"0x842e14fffe51c5c4","_networkAddress":8908,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260,"de
        zigbee.0	2020-10-01 17:15:18.974	debug	(12265) target: {"ID":3,"profileID":49246,"deviceID":256,"inputClusters":[4096,0,3,4,5,6,8,64527],"outputClusters":[25],"deviceNetworkAddress":36891,"deviceIeeeAddress":"0x7cb03eaa0a04f888","clusters"
        zigbee.0	2020-10-01 17:15:18.974	debug	(12265) convert state, OFF, {"state":"OFF"}
        zigbee.0	2020-10-01 17:15:18.973	debug	(12265) entity: {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x7cb03eaa0a04f888","_networkAddress":36891,"_manufacturerID":48042,"_endpoints":[{"ID":3,"profileID":49246,"deviceID":2
        zigbee.0	2020-10-01 17:15:18.971	debug	(12265) State changes. dev: 0x7cb03eaa0a04f888 model: AC03641 states: [{"stateDesc":{"id":"state","name":"Switch state","role":"switch","write":true,"read":true,"type":"boolean","inOptions":true},"val
        zigbee.0	2020-10-01 17:15:18.970	debug	(12265) Change state 'state' at device 0x7cb03eaa0a04f888 type 'AC03641'
        zigbee.0	2020-10-01 17:15:18.967	debug	(12265) User stateChange zigbee.0.7cb03eaa0a04f888.state {"val":false,"ack":false,"ts":1601565318962,"q":0,"from":"system.adapter.javascript.0","user":"system.user.admin","lc":1601530034448}
        zigbee.0	2020-10-01 17:15:18.727	debug	(12265) target: {"ID":3,"profileID":49246,"deviceID":256,"inputClusters":[4096,0,3,4,5,6,8,64527],"outputClusters":[25],"deviceNetworkAddress":36891,"deviceIeeeAddress":"0x7cb03eaa0a04f888","clusters"
        zigbee.0	2020-10-01 17:15:18.726	debug	(12265) convert state, OFF, {"state":"OFF"}
        zigbee.0	2020-10-01 17:15:18.726	debug	(12265) entity: {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x7cb03eaa0a04f888","_networkAddress":36891,"_manufacturerID":48042,"_endpoints":[{"ID":3,"profileID":49246,"deviceID":2
        zigbee.0	2020-10-01 17:15:18.725	debug	(12265) State changes. dev: 0x7cb03eaa0a04f888 model: AC03641 states: [{"stateDesc":{"id":"state","name":"Switch state","role":"switch","write":true,"read":true,"type":"boolean","inOptions":true},"val
        zigbee.0	2020-10-01 17:15:18.725	debug	(12265) Change state 'state' at device 0x7cb03eaa0a04f888 type 'AC03641'
        zigbee.0	2020-10-01 17:15:18.713	debug	(12265) User stateChange zigbee.0.7cb03eaa0a04f888.state {"val":false,"ack":false,"ts":1601565318710,"q":0,"from":"system.adapter.javascript.0","user":"system.user.admin","lc":1601530034448}
        zigbee.0	2020-10-01 17:15:18.698	debug	(12265) Publish {"occupancy":false}
        zigbee.0	2020-10-01 17:15:14.032	debug	(12265) Publish {"power":0,"current":0,"voltage":238}
        zigbee.0	2020-10-01 17:15:14.011	debug	(12265) Type readResponse device {"type":"device","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":2
        zigbee.0	2020-10-01 17:15:14.007	debug	(12265) Received Zigbee message from '0x842e14fffe1394fe', type 'readResponse', cluster 'haElectricalMeasurement', data '{"rmsVoltage":238,"rmsCurrent":0,"activePower":0}' from endpoint 1 with groupI
        zigbee.0	2020-10-01 17:15:14.006	debug	(12265) handleMessage. {"type":"readResponse","device":{"ID":2,"_type":"Router","_ieeeAddr":"0x842e14fffe1394fe","_networkAddress":11448,"_manufacturerID":4098,"_endpoints":[{"ID":1,"profileID":260,"
        zigbee.0	2020-10-01 17:15:12.783	debug	(12265) LQI succeeded for '0x7cb03eaa0a04f888'
        zigbee.0	2020-10-01 17:15:12.716	debug	(12265) Publish {"pressure":971.4}
        zigbee.0	2020-10-01 17:15:12.713	debug	(12265) Publish {"humidity":56.2}
        zigbee.0	2020-10-01 17:15:12.698	debug	(12265) Publish {"temperature":21.76}
        zigbee.0	2020-10-01 17:15:12.696	debug	(12265) Type attributeReport device {"type":"device","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profi
        zigbee.0	2020-10-01 17:15:12.695	debug	(12265) Received Zigbee message from '0x00158d0002733e82', type 'attributeReport', cluster 'msPressureMeasurement', data '{"16":9714,"20":-1,"measuredValue":971}' from endpoint 1 with groupID 0
        zigbee.0	2020-10-01 17:15:12.694	debug	(12265) Type attributeReport device {"type":"device","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profi
        zigbee.0	2020-10-01 17:15:12.693	debug	(12265) Received Zigbee message from '0x00158d0002733e82', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":5620}' from endpoint 1 with groupID 0
        zigbee.0	2020-10-01 17:15:12.692	debug	(12265) handleMessage. {"type":"attributeReport","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profileID
        zigbee.0	2020-10-01 17:15:12.690	debug	(12265) handleMessage. {"type":"attributeReport","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profileID
        zigbee.0	2020-10-01 17:15:12.687	debug	(12265) Type attributeReport device {"type":"device","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profi
        zigbee.0	2020-10-01 17:15:12.686	debug	(12265) Received Zigbee message from '0x00158d0002733e82', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2176}' from endpoint 1 with groupID 0
        zigbee.0	2020-10-01 17:15:12.685	debug	(12265) handleMessage. {"type":"attributeReport","device":{"ID":10,"_type":"EndDevice","_ieeeAddr":"0x00158d0002733e82","_networkAddress":35564,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profileID
        zigbee.0	2020-10-01 17:15:12.341	debug	(12265) Routing table succeeded for '0x842e14fffe1394fe'
        zigbee.0	2020-10-01 17:15:12.340	debug	(12265) Routing for '0x842e14fffe1394fe': {"table":[{"destinationAddress":0,"nextHop":0},{"destinationAddress":8908,"status":"ACTIVE","nextHop":8908},{"destinationAddress":50048,"status":"ACTIVE","ne
        zigbee.0	2020-10-01 17:15:12.261	debug	(12265) LQI succeeded for '0x842e14fffe1394fe'
        zigbee.0	2020-10-01 17:15:12.097	debug	(12265) Routing table succeeded for '0x842e14fffe51c5c4'
        zigbee.0	2020-10-01 17:15:12.097	debug	(12265) Routing for '0x842e14fffe51c5c4': {"table":[{"destinationAddress":0,"nextHop":11448},{"destinationAddress":35007,"status":"ACTIVE","nextHop":36891},{"destinationAddress":59922,"status":"ACTIV
        zigbee.0	2020-10-01 17:15:12.001	debug	(12265) LQI succeeded for '0x842e14fffe51c5c4'
        zigbee.0	2020-10-01 17:15:11.942	debug	(12265) sendTo "getBinding" to system.adapter.admin.0 from system.adapter.zigbee.0
        zigbee.0	2020-10-01 17:15:11.942	debug	(12265) getBinding result: []
        zigbee.0	2020-10-01 17:15:11.797	debug	(12265) sendTo "getDevices" to system.adapter.admin.0 from system.adapter.zigbee.0
        
        

        Alle Sensoren die an der Led hingen haben sich auch wieder getrennt
        eb2b975e-b0ce-4d53-98e2-2fa261a1aaad-image.png
        Die BM reagieren aber noch und sind auch aviable. Kommen mir aber träger vor, also brauchen länger um zu schalten

        arteckA Offline
        arteckA Offline
        arteck
        Developer Most Active
        schrieb am zuletzt editiert von
        #50

        @vikk88 kann sein das die Lampe kaputt ist.. kannst du da zum Tausch was anderes reinhängen.. an die gleiche stelle ??
        ne tradfri.. oder ne andere osram

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

        V 1 Antwort Letzte Antwort
        0
        • arteckA arteck

          @vikk88 kann sein das die Lampe kaputt ist.. kannst du da zum Tausch was anderes reinhängen.. an die gleiche stelle ??
          ne tradfri.. oder ne andere osram

          V Offline
          V Offline
          vikk88
          schrieb am zuletzt editiert von
          #51

          @arteck den Gedanken hatte ich auch schon, werde mir mal eine tradfri besorgen. Komisch ist nur das ich vor ca. einem halben Jahr an der Stelle eine andere osram hängen hatte. Diese hatte einen Defekt, im log stand auch error und das diese nicht erreichbar war, updaten ging auch nicht. Die aktuelle funktioniert auch noch und wird von den BMs geschaltet.

          L 1 Antwort Letzte Antwort
          0
          • V vikk88

            @arteck den Gedanken hatte ich auch schon, werde mir mal eine tradfri besorgen. Komisch ist nur das ich vor ca. einem halben Jahr an der Stelle eine andere osram hängen hatte. Diese hatte einen Defekt, im log stand auch error und das diese nicht erreichbar war, updaten ging auch nicht. Die aktuelle funktioniert auch noch und wird von den BMs geschaltet.

            L Offline
            L Offline
            Laser
            schrieb am zuletzt editiert von Laser
            #52

            Das Zigbee Problem ist scheinbar wieder da...
            Mein Adapter wird nach einem Update nur noch gelb. (Funktioniere bisher ohne Probleme.)
            Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
            Als Schnittstelle: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CDD4604-if00
            eingetragen.
            Aber auch /dev/ttyACM0 probiert - erfolglos..
            Wie ändere ich die Benutzerrechte auf COM SS?
            Das muß doch über IOBroker funktionieren?

            Thomas BraunT 1 Antwort Letzte Antwort
            0
            • L Laser

              Das Zigbee Problem ist scheinbar wieder da...
              Mein Adapter wird nach einem Update nur noch gelb. (Funktioniere bisher ohne Probleme.)
              Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
              Als Schnittstelle: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CDD4604-if00
              eingetragen.
              Aber auch /dev/ttyACM0 probiert - erfolglos..
              Wie ändere ich die Benutzerrechte auf COM SS?
              Das muß doch über IOBroker funktionieren?

              Thomas BraunT Online
              Thomas BraunT Online
              Thomas Braun
              Most Active
              schrieb am zuletzt editiert von Thomas Braun
              #53

              @laser sagte in Zigbee 1.2.1 pairing geht nicht mehr:

              Wie ändere ich die Benutzerrechte auf COM SS?

              Was soll das sein?
              Und wie sehen die Rechte, die du da jetzt verfummeln willst jetzt aus?

              Linux-Werkzeugkasten:
              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
              NodeJS Fixer Skript:
              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

              L 1 Antwort Letzte Antwort
              0
              • Thomas BraunT Thomas Braun

                @laser sagte in Zigbee 1.2.1 pairing geht nicht mehr:

                Wie ändere ich die Benutzerrechte auf COM SS?

                Was soll das sein?
                Und wie sehen die Rechte, die du da jetzt verfummeln willst jetzt aus?

                L Offline
                L Offline
                Laser
                schrieb am zuletzt editiert von Laser
                #54

                angeblich kann es sein, daß der Benutzer iobroker nicht auf die Schnittstelle für den USB-Stick zugreifen kann.
                Allerdings: "Der Benutzer »iobroker« ist bereits ein Mitglied der Gruppe »dialout«."

                pi@iobroker-pi:~ $ ls -l /dev/ttyACM0 crw-rw---- 1 root dialout 166, 0 19. Feb 18:45 /dev/ttyACM0

                Verfummeln will ich da nichts, nur verstehen, warum ZIGBEE nicht mehr funktioniert...

                Thomas BraunT 1 Antwort Letzte Antwort
                0
                • L Laser

                  angeblich kann es sein, daß der Benutzer iobroker nicht auf die Schnittstelle für den USB-Stick zugreifen kann.
                  Allerdings: "Der Benutzer »iobroker« ist bereits ein Mitglied der Gruppe »dialout«."

                  pi@iobroker-pi:~ $ ls -l /dev/ttyACM0 crw-rw---- 1 root dialout 166, 0 19. Feb 18:45 /dev/ttyACM0

                  Verfummeln will ich da nichts, nur verstehen, warum ZIGBEE nicht mehr funktioniert...

                  Thomas BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  schrieb am zuletzt editiert von Thomas Braun
                  #55

                  @laser sagte in Zigbee 1.2.1 pairing geht nicht mehr:

                  angeblich kann es sein, daß der Benutzer iobroker nicht auf die Schnittstelle für den USB-Stck zugreifen kann.

                  Das ist möglich. Aber das kann man besser sehen, wenn man den Status 'jetzt' kennt.
                  Die Rechte an den /dev-Files gehen aber eigentlich nicht 'kaputt'.
                  Da wird noch irgendwas anders auf die Schnittstelle zugreifen.
                  Schau mit

                  lsof /pfad/zum/gerät
                  

                  nach was das sein könnte.

                  Linux-Werkzeugkasten:
                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                  NodeJS Fixer Skript:
                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                  L 1 Antwort Letzte Antwort
                  0
                  • Thomas BraunT Thomas Braun

                    @laser sagte in Zigbee 1.2.1 pairing geht nicht mehr:

                    angeblich kann es sein, daß der Benutzer iobroker nicht auf die Schnittstelle für den USB-Stck zugreifen kann.

                    Das ist möglich. Aber das kann man besser sehen, wenn man den Status 'jetzt' kennt.
                    Die Rechte an den /dev-Files gehen aber eigentlich nicht 'kaputt'.
                    Da wird noch irgendwas anders auf die Schnittstelle zugreifen.
                    Schau mit

                    lsof /pfad/zum/gerät
                    

                    nach was das sein könnte.

                    L Offline
                    L Offline
                    Laser
                    schrieb am zuletzt editiert von Laser
                    #56

                    lsof /dev/ttyACM0
                    Kommando nicht gefunden

                    Thomas BraunT 1 Antwort Letzte Antwort
                    0
                    • L Laser

                      lsof /dev/ttyACM0
                      Kommando nicht gefunden

                      Thomas BraunT Online
                      Thomas BraunT Online
                      Thomas Braun
                      Most Active
                      schrieb am zuletzt editiert von
                      #57

                      @laser

                      Dann musst du es nachinstallieren.

                      sudo apt update
                      sudo apt install lsof
                      

                      Linux-Werkzeugkasten:
                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                      NodeJS Fixer Skript:
                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                      L 1 Antwort Letzte Antwort
                      0
                      • Thomas BraunT Thomas Braun

                        @laser

                        Dann musst du es nachinstallieren.

                        sudo apt update
                        sudo apt install lsof
                        
                        L Offline
                        L Offline
                        Laser
                        schrieb am zuletzt editiert von
                        #58

                        pi@iobroker-pi:~ $ sudo lsof /dev/ttyACM0
                        COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
                        io.zigbee 5356 iobroker 26uW CHR 166,0 0t0 386 /dev/ttyACM0

                        Thomas BraunT 1 Antwort Letzte Antwort
                        0
                        • L Laser

                          pi@iobroker-pi:~ $ sudo lsof /dev/ttyACM0
                          COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
                          io.zigbee 5356 iobroker 26uW CHR 166,0 0t0 386 /dev/ttyACM0

                          Thomas BraunT Online
                          Thomas BraunT Online
                          Thomas Braun
                          Most Active
                          schrieb am zuletzt editiert von
                          #59

                          @laser
                          Da läuft schon eine Instanz.

                          Linux-Werkzeugkasten:
                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                          NodeJS Fixer Skript:
                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                          L 1 Antwort Letzte Antwort
                          0
                          • Thomas BraunT Thomas Braun

                            @laser
                            Da läuft schon eine Instanz.

                            L Offline
                            L Offline
                            Laser
                            schrieb am zuletzt editiert von
                            #60

                            Soll heißen, es laufen 2 Instanzen von ZigBee?

                            Thomas BraunT 1 Antwort Letzte Antwort
                            0
                            • L Laser

                              Soll heißen, es laufen 2 Instanzen von ZigBee?

                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von
                              #61

                              @laser Nee, eine. Mit der PID 5356.

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              L 1 Antwort Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @laser Nee, eine. Mit der PID 5356.

                                L Offline
                                L Offline
                                Laser
                                schrieb am zuletzt editiert von
                                #62

                                und was tue ich da nun?

                                Thomas BraunT 1 Antwort Letzte Antwort
                                0
                                • L Laser

                                  und was tue ich da nun?

                                  Thomas BraunT Online
                                  Thomas BraunT Online
                                  Thomas Braun
                                  Most Active
                                  schrieb am zuletzt editiert von
                                  #63

                                  @laser
                                  Stoppe die Instanz.
                                  Oder gleich den ganzen iobroker. Dann schauen ob die Datei freigegeben wurde.
                                  Wenn ja -> Restart
                                  Wenn nein -> Prozess killen

                                  sudo kill 5356
                                  

                                  Linux-Werkzeugkasten:
                                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                  NodeJS Fixer Skript:
                                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                  L 1 Antwort Letzte Antwort
                                  0
                                  • Thomas BraunT Thomas Braun

                                    @laser
                                    Stoppe die Instanz.
                                    Oder gleich den ganzen iobroker. Dann schauen ob die Datei freigegeben wurde.
                                    Wenn ja -> Restart
                                    Wenn nein -> Prozess killen

                                    sudo kill 5356
                                    
                                    L Offline
                                    L Offline
                                    Laser
                                    schrieb am zuletzt editiert von Laser
                                    #64

                                    Restart gemacht, auch ganzen Raspi

                                    sudo lsof /dev/ttyACM0
                                    COMMAND    PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
                                    io.zigbee 1295 iobroker   26uW  CHR  166,0      0t0  386 /dev/ttyACM0
                                    
                                    Thomas BraunT 1 Antwort Letzte Antwort
                                    0
                                    • L Laser

                                      Restart gemacht, auch ganzen Raspi

                                      sudo lsof /dev/ttyACM0
                                      COMMAND    PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
                                      io.zigbee 1295 iobroker   26uW  CHR  166,0      0t0  386 /dev/ttyACM0
                                      
                                      Thomas BraunT Online
                                      Thomas BraunT Online
                                      Thomas Braun
                                      Most Active
                                      schrieb am zuletzt editiert von Thomas Braun
                                      #65

                                      @laser

                                      Ja, neue PID. Alles gut.

                                      Bitte Konsolentext in CodeTags setzen, kann man besser lesen.

                                      Linux-Werkzeugkasten:
                                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                      NodeJS Fixer Skript:
                                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                      L 1 Antwort Letzte Antwort
                                      0
                                      • Thomas BraunT Thomas Braun

                                        @laser

                                        Ja, neue PID. Alles gut.

                                        Bitte Konsolentext in CodeTags setzen, kann man besser lesen.

                                        L Offline
                                        L Offline
                                        Laser
                                        schrieb am zuletzt editiert von Laser
                                        #66

                                        Leider funktioniert zigbee noch nicht. Instanz Gelb.
                                        Ist es nun egal, ob ich
                                        /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CDD4604-if00
                                        oder /dev/ttyACM0 verwende?
                                        Bisher ging es mit /dev/ttyACM0 (hatte mir Bildschirmausdruck gemacht)

                                        Thomas BraunT 1 Antwort Letzte Antwort
                                        0
                                        • L Laser

                                          Leider funktioniert zigbee noch nicht. Instanz Gelb.
                                          Ist es nun egal, ob ich
                                          /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CDD4604-if00
                                          oder /dev/ttyACM0 verwende?
                                          Bisher ging es mit /dev/ttyACM0 (hatte mir Bildschirmausdruck gemacht)

                                          Thomas BraunT Online
                                          Thomas BraunT Online
                                          Thomas Braun
                                          Most Active
                                          schrieb am zuletzt editiert von
                                          #67

                                          @laser

                                          Ich würde IMMER den Link aus /dev/serial/by-id nehmen. Der ändert sich nicht (oder ganz selten), /dev/ttyACMx kann wandern.

                                          Linux-Werkzeugkasten:
                                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                          NodeJS Fixer Skript:
                                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                          L 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          770

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe