Hallo

habe es nicht mehr hinbekommen und musste alle Geräte neu anlernen.

Grüße

Norbert

Hallo

ich meinte die Networkmap im Adapter !

Grüße

Norbert

Hallo Arteck

Ja, die Werte stimmen, an der ID habe ich nichts geändert nur den Kanal.

Und der steht wieder auf dem alten Wert.

Mehrfache Reboots habe ich schon gemacht.

Das einzige was ich noch nicht gemacht habe, den PI komplett vom Strom getrennt.

Grüße

Norbert

Hallo

ich teste zur Zeit den Adapter mir dem passenden USB Stick.

Nach anfänglichen Schwierigkeiten lief auch alles soweit, ich verwende zur Zeit Osram Steckdosen uns diverse Xiaomi Adapter.

In der Adaptermap war auch gut zu erkennen wie sich das Netzwerk aufbaute und Router und Client sich verteilten.

Ich habe scheinbar den Fehler gemacht test weise den Kanal zu wechseln, danach redete kein Gerät mehr mit dem Adapter.

Das zurückstellen auf den ursprünglichen Kanal hilft nicht.

Einen Debug Log habe ich angefügt, aber eine Ursache für die Fehlermeldung kann ich nicht erkennen.

Hat jemand evtl. einen Tip für mich wie ich das Netzwerk wieder ans laufen bekomme ohne die Geräte neu Pairen zu müssen.

zigbee.0 2018-09-06 12:36:39.719 debug system.adapter.admin.0: logging true

zigbee.0 2018-09-06 12:34:53.799 debug system.adapter.admin.0: logging true

zigbee.0 2018-09-06 12:34:48.281 debug system.adapter.admin.0: logging false

zigbee.0 2018-09-06 12:34:29.993 debug system.adapter.admin.0: logging true

zigbee.0 2018-09-06 12:34:12.461 debug system.adapter.admin.0: logging false

zigbee.0 2018-09-06 12:33:47.887 error Failed to configure 0x84182600000eecc8

zigbee.0 2018-09-06 12:33:24.478 debug sendTo "getDevices" to system.adapter.admin.0 from system.adapter.zigbee.0

zigbee.0 2018-09-06 12:33:24.476 debug getDevices result: [{"type":"device","common":{"name":"Switch_Plug_1","type":"Plug 01","icon":"img/lightify-plug.png"},"from":"system.adapter.zigbee.0","ts":1536229977468,"_id":"zigbee.0.84182600000e

zigbee.0 2018-09-06 12:33:24.302 debug sendTo "getMap" to system.adapter.admin.0 from system.adapter.zigbee.0

zigbee.0 2018-09-06 12:33:24.299 debug getMap result: []

zigbee.0 2018-09-06 12:33:24.297 debug lqiScan result: . []

zigbee.0 2018-09-06 12:32:58.471 debug system.adapter.admin.0: logging true

zigbee.0 2018-09-06 12:32:58.214 error Failed to configure 0x84182600000eeed6

zigbee.0 2018-09-06 12:32:57.481 debug User stateChange zigbee.0.info.pairingMode {"val":false,"ack":false,"ts":1536229977445,"q":0,"from":"system.adapter.zigbee.0","lc":1536177617114}

zigbee.0 2018-09-06 12:32:57.479 debug User stateChange zigbee.0.info.connection {"val":true,"ack":false,"ts":1536229977350,"q":0,"from":"system.adapter.zigbee.0","lc":1536177617088}

zigbee.0 2018-09-06 12:32:57.442 info (0x00158d00022893f7): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)

zigbee.0 2018-09-06 12:32:57.441 info (0x00158d000201c880): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)

zigbee.0 2018-09-06 12:32:57.440 info (0x00158d0001e5f746): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)

zigbee.0 2018-09-06 12:32:57.439 info (0x00158d0002019f01): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)

zigbee.0 2018-09-06 12:32:57.423 info (0x84182600000eeed6): AB3257001NJ - OSRAM Smart+ plug (Router)

zigbee.0 2018-09-06 12:32:57.422 info (0x00158d000278d8fa): MFKZQ01LM - Xiaomi Mi smart home cube (EndDevice)

zigbee.0 2018-09-06 12:32:57.421 info (0x00158d0001e5f4a1): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)

zigbee.0 2018-09-06 12:32:57.421 info (0x00158d0001d48da9): RTCGQ01LM - Xiaomi MiJia human body movement sensor (EndDevice)

zigbee.0 2018-09-06 12:32:57.419 info (0x00158d000278d70a): MFKZQ01LM - Xiaomi Mi smart home cube (EndDevice)

zigbee.0 2018-09-06 12:32:57.397 info (0x84182600000eecc8): AB3257001NJ - OSRAM Smart+ plug (Router)

zigbee.0 2018-09-06 12:32:57.394 debug {"type":"EndDevice","ieeeAddr":"0x00158d00022893f7","nwkAddr":50032,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_magnet","epList":[1],"status":"online","joinTime":

zigbee.0 2018-09-06 12:32:57.394 debug {"type":"EndDevice","ieeeAddr":"0x00158d000201c880","nwkAddr":63570,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":15362

zigbee.0 2018-09-06 12:32:57.393 debug {"type":"EndDevice","ieeeAddr":"0x00158d0001e5f746","nwkAddr":29769,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_switch","epList":[1],"status":"online","joinTime":

zigbee.0 2018-09-06 12:32:57.393 debug {"type":"EndDevice","ieeeAddr":"0x00158d0002019f01","nwkAddr":16538,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":15362

zigbee.0 2018-09-06 12:32:57.392 debug {"type":"Router","ieeeAddr":"0x84182600000eeed6","nwkAddr":35864,"manufId":48042,"manufName":"OSRAM","powerSource":"Mains (single phase)","modelId":"Plug 01","epList":[3],"status":"offline","joinTime

zigbee.0 2018-09-06 12:32:57.392 debug {"type":"EndDevice","ieeeAddr":"0x00158d000278d8fa","nwkAddr":44715,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_cube","epList":[1,2,3],"status":"online","joinTime

zigbee.0 2018-09-06 12:32:57.391 debug {"type":"EndDevice","ieeeAddr":"0x00158d0001e5f4a1","nwkAddr":30923,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_switch","epList":[1],"status":"online","joinTime":

zigbee.0 2018-09-06 12:32:57.391 debug {"type":"EndDevice","ieeeAddr":"0x00158d0001d48da9","nwkAddr":45750,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_motion","epList":[1],"status":"online","joinTime":

zigbee.0 2018-09-06 12:32:57.390 debug {"type":"EndDevice","ieeeAddr":"0x00158d000278d70a","nwkAddr":48897,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_cube","epList":[1,2,3],"status":"online","joinTime

zigbee.0 2018-09-06 12:32:57.389 debug {"type":"Router","ieeeAddr":"0x84182600000eecc8","nwkAddr":60133,"manufId":48042,"manufName":"OSRAM","powerSource":"Mains (single phase)","modelId":"Plug 01","epList":[3],"status":"offline","joinTime

zigbee.0 2018-09-06 12:32:57.388 debug {"type":"Coordinator","ieeeAddr":"0x00124b0014d9e218","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1536229976}

zigbee.0 2018-09-06 12:32:57.369 debug Current active devices:

zigbee.0 2018-09-06 12:32:57.344 info zigbee-shepherd ready

zigbee.0 2018-09-06 12:32:57.299 info zigbee-shepherd started!

zigbee.0 2018-09-06 12:32:55.735 info Start on port: /dev/ttyACM0 with panID 6754 channel 16

zigbee.0 2018-09-06 12:32:55.726 info starting. Version 0.7.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.11.1

zigbee.0 2018-09-06 12:32:55.573 debug statesDB connected

zigbee.0 2018-09-06 12:32:55.450 debug objectDB connectedze=85]

Ja, Deconz ist ein eigenes Zigbee Gateway der Fa. Dresden Elektronic.

Grüße Norbert

Morgen

soweit ich es dem Internet entnommen habe, liegt das Problem am Xiaomi Gateway.

Die neueren Würfel scheinen auch mit andern Smarthome System nicht zu funktionieren.

Habe es selber zur Zeit mit Deconz aktiv.

Grüße

Norbert

npm install semver@5.0.3 hat es gebracht.

Danach noch die Anpassung der Connfig Datei und der Adapter startet !

Danke !

Hallo

@Dutchman

Ja, habe ich gemacht ändert leider nichts.

@ apollon77

Habe den Log auf Debug gestellt und den Adapter neu gestartet.

Es handelt sich um Homebridge accessories manager 0.30 Adapter.

Grüße und Danke

Norbert

host.iobroker 2018-06-21 10:48:51.316 info Restart adapter system.adapter.ham.0 because enabled

host.iobroker 2018-06-21 10:48:51.316 error instance system.adapter.ham.0 terminated with code 7 (Adapter already running)

Caught 2018-06-21 10:48:51.316 error by controller[1]: at process._fatalException (bootstrap_node.js:307:26)

Caught 2018-06-21 10:48:51.316 error by controller[1]: at process.emit (events.js:188:7)

Caught 2018-06-21 10:48:51.316 error by controller[1]: at emitOne (events.js:101:20)

Caught 2018-06-21 10:48:51.316 error by controller[1]: at process.on.err (/opt/iobroker/node_modules/iobroker.ham/main.js:43:27)

Caught 2018-06-21 10:48:51.316 error by controller[1]: at Object.end (/opt/iobroker/node_modules/iobroker.ham/lib/wrapper-handler.js<emoji seq="1f4af"></emoji>22)

Caught 2018-06-21 10:48:51.316 error by controller[1]: TypeError: Cannot read property 'finish' of undefined

Caught 2018-06-21 10:48:51.316 error by controller[1]: ^

Caught 2018-06-21 10:48:51.316 error by controller[1]: homebridgeWrapper.finish();

Caught 2018-06-21 10:48:51.316 error by controller[1]: /opt/iobroker/node_modules/iobroker.ham/lib/wrapper-handler.js:100

Caught 2018-06-21 10:48:51.316 error by controller[0]: at tryModuleLoad (module.js:453:12) code: 'MODULE_NOT_FOUND' }

Caught 2018-06-21 10:48:51.316 error by controller[0]: at Module.load (module.js:494:32)

Caught 2018-06-21 10:48:51.315 error by controller[0]: at Object.Module._extensions..js (module.js:586:10)

Caught 2018-06-21 10:48:51.315 error by controller[0]: at Module._compile (module.js:577:32)

Caught 2018-06-21 10:48:51.315 error by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/homebridge/plugin.js:3:14)

Caught 2018-06-21 10:48:51.315 error by controller[0]: at require (internal/module.js:20:19)

Caught 2018-06-21 10:48:51.315 error by controller[0]: at Module.require (module.js:504:17)

Caught 2018-06-21 10:48:51.315 error by controller[0]: at Function.Module._load (/opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/node_modules/mock-require/index.js:29:22)

Caught 2018-06-21 10:48:51.315 error by controller[0]: at Function.Module._load (module.js:424:25)

Caught 2018-06-21 10:48:51.315 error by controller[0]: at Function.Module._resolveFilename (module.js:476:15)

Caught 2018-06-21 10:48:51.315 error by controller[0]: { Error: Cannot find module 'semver'

ham.0 2018-06-21 10:48:51.214 info starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.ham, node: v6.14.3

ham.0 2018-06-21 10:48:51.106 debug statesDB connected

ham.0 2018-06-21 10:48:51.086 debug objectDB connected

host.iobroker 2018-06-21 10:48:50.838 info instance system.adapter.ham.0 started with pid 1724</anonymous>

Guten Morgen,

ich wollte mal den Homebridge Adapter testen, bekomme aber im log eine Fehlermeldung die ich nicht beheben kann.

Angeblich läuft bereits eine HAM Adapter, der Fehler bleibt auch nach dem ich den Adapter mehrfach de- & installiert habe.

Hat jemand einen Tip für mich.

Danke und Grüße

Norbert

host.iobroker 2018-06-21 10:27:31.839 error instance system.adapter.ham.0 terminated with code 7 (Adapter already running)

Caught 2018-06-21 10:27:31.839 error by controller[1]: at process._fatalException (bootstrap_node.js:307:26)

Caught 2018-06-21 10:27:31.839 error by controller[1]: at process.emit (events.js:188:7)

Caught 2018-06-21 10:27:31.839 error by controller[1]: at emitOne (events.js:101:20)

Caught 2018-06-21 10:27:31.839 error by controller[1]: at process.on.err (/opt/iobroker/node_modules/iobroker.ham/main.js:43:27)

Caught 2018-06-21 10:27:31.839 error by controller[1]: at Object.end (/opt/iobroker/node_modules/iobroker.ham/lib/wrapper-handler.js<emoji seq="1f4af"></emoji>22)

Caught 2018-06-21 10:27:31.839 error by controller[1]: TypeError: Cannot read property 'finish' of undefined

Caught 2018-06-21 10:27:31.839 error by controller[1]: ^

Caught 2018-06-21 10:27:31.839 error by controller[1]: homebridgeWrapper.finish();

Caught 2018-06-21 10:27:31.839 error by controller[1]: /opt/iobroker/node_modules/iobroker.ham/lib/wrapper-handler.js:100

Caught 2018-06-21 10:27:31.839 error by controller[0]: at tryModuleLoad (module.js:453:12) code: 'MODULE_NOT_FOUND' }

Caught 2018-06-21 10:27:31.839 error by controller[0]: at Module.load (module.js:494:32)

Caught 2018-06-21 10:27:31.839 error by controller[0]: at Object.Module._extensions..js (module.js:586:10)

Caught 2018-06-21 10:27:31.838 error by controller[0]: at Module._compile (module.js:577:32)

Caught 2018-06-21 10:27:31.838 error by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/homebridge/plugin.js:3:14)

Caught 2018-06-21 10:27:31.838 error by controller[0]: at require (internal/module.js:20:19)

Caught 2018-06-21 10:27:31.838 error by controller[0]: at Module.require (module.js:504:17)

Caught 2018-06-21 10:27:31.838 error by controller[0]: at Function.Module._load (/opt/iobroker/node_modules/iobroker.ham/node_modules/homebridge-plugin-wrapper/node_modules/mock-require/index.js:29:22)

Caught 2018-06-21 10:27:31.838 error by controller[0]: at Function.Module._load (module.js:424:25)

Caught 2018-06-21 10:27:31.838 error by controller[0]: at Function.Module._resolveFilename (module.js:476:15)

Caught 2018-06-21 10:27:31.838 error by controller[0]: { Error: Cannot find module 'semver'</anonymous>

Hallo Jey Cee

Danke für die Antwort.

Mhhh..ich hatte massive Probleme mit den Xiaomi Teilen und Deconz (Speziell die runden Taster) wenn ich sie nur per Adapter angelernt hatte.

Das war ein reines Glücksspiel.

Die wurden nur als 0x0000 Device erkannt und dann auch nicht an den Deconz Adapter weitergeleitet.

Aber das ist scheinbar kein Problem von IoBroker und Deinem Adapter, sondern von Deconz selbst.

Ich beobachte das mal weiter, befindet sich ja alles noch in der Entwicklung !

Grüße

Norbert