[Aufruf] ZigBee CC253x Adapter

Kueppert

Da meine Frage scheinbar unter ging:

Wie kann ich denn sehen, was in der Shepherd-DB drin steht? ` Mit PuTTY einloggen, in den Ordner von Adapter gehen und dort die Datei öffnen/editieren

Gesendet von meinem HUAWEI RIO-L01 mit Tapatalk

arteck

~~@AndrK:~~

Halli, hallo,

erst mal an die komplette Entwicklermannschaft vielen Dank für Eure Arbeit!

Ich spiele seit einigen Tagen mit dem zigbee Adapter und komme soweit auch zurecht. Das anlernen von Tradfri Birnen E27 1000lm und einem Tradfri motion sensor hat soweit geklappt. Aber leider will der dumme TRADFRI Driver 10W nicht.

Nach dem Auspacken und an den Strom schließen ist er sofort im pairing mode. Er wird auch gleich vom zigbee adapter gefunden und als "TRADFRI Driver 10W" angelegt. ABER unter Objekte finde ich nur EINEN Eintrag:

000d6ffffea5c04a TRADFRI Driver 10W device

Ich habe alles versucht: Reset des TRADFRI Drivers, Adapter deinstalliert und installiert, inzwischen habe ich 0.8.2a.

Hat jemand eine Ahnung was zu tun ist?

Ich danke Euch

Andrku `

na klar .. ist nicht implementiert.. das hier kennst du aber ??

viewtopic.php?f=24&t=18214

Arnulf

~~@arteck:~~

~~@Arnulf:~~

Da meine Frage scheinbar unter ging:

Wie kann ich denn sehen, was in der Shepherd-DB drin steht? `

na wie jetzt.. das ist doch stink normale Sequenzielle Datei..

oder weiss du nicht wie man Dateien Editiert oder sich anschaut ?? kleiner Tipp .. suche hilft `

Sorry. Bei DB denke ich immer an Treiber oder binär-Datei.

Textdatei kann ich natürlich editieren ;)

AndrK

Hallo Arteck,

danke für die rasche Antwort. Nein, habe ich nicht gekannt. ….. ich habe Dir die Daten gleich eingestellt.

Ciao

AndreK

romgen

~~@Arnulf:~~

Da meine Frage scheinbar unter ging:

Wie kann ich denn sehen, was in der Shepherd-DB drin steht? `

Linux bash (Debian):

nano /opt/ioroker/iobroker-data/zigbee_0/shepherd.db

Ansonsten kannst du die Datei finden mit:

find / -name shepherd.db

Arnulf

Vielen Dank.

Damit habe ich die DB gefunden

Es ist doch sicher nicht normal, dass da die IDs doppelt auftauchen, oder?

Die DB ist 42 Zeilen groß (42 Zeilen, die mit "["id":" beginen habe aber aktuell nur 20 Devices in meiner Adapter-Geräteliste

Muss ich da jetzt Zeilen löschen?

Wenn ja, welche?

Und: Wie öffne ich am Besten die Schreibgeschützte Datei? ioBroker muss sicher vorher gestoppt werden. Oder?

[update]

Hier mal die linken Zeichen der Shepherd-DB.

Vielleicht ist das doch so korrekt. Zumindest könnte die obere Hälfte der normale Eintrag und die untere Hälfte der Index sein

! {"id":24,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":25,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":26,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":17,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":2,"type":"Router","ieeeAddr":"0x00178801030
! {"id":11,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":19,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":20,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":18,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":12,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":21,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":16,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":27,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":5,"type":"Router","ieeeAddr":"0x7cb03eaa00b
! {"id":13,"type":"Router","ieeeAddr":"0x7cb03eaa00
! {"id":14,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b
! {"id":15,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":10,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":22,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":23,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"$indexCreated":{"fieldName":"id","unique":true
! {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b
! {"id":24,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":25,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":26,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":17,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":2,"type":"Router","ieeeAddr":"0x00178801030
! {"id":11,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":19,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":20,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":18,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":12,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":21,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":16,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":27,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":5,"type":"Router","ieeeAddr":"0x7cb03eaa00b
! {"id":13,"type":"Router","ieeeAddr":"0x7cb03eaa00
! {"id":14,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":15,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":10,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":22,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":23,"type":"EndDevice","ieeeAddr":"0x00158d0

[Update]

Ich habe auch die Geräte, die im Adapter gelistet sind mit den Werten in der DB verglichen.

Alles drin. Auch die als Router fungierenden Geräte.

Nur halt eben doppelt

besterquester

Ich habe eine Frage, ich habe den ZigBee Adapter installiert und erfolgreich einige Aqara Sensoren gepaired.

Nun habe ich iobroker restoren und neu aufsetzen müssen.

Ich habe

iobroker stop

iobroker restore

iobroker start

iobroker upload all

Die Sensoren scheinen da zu sein aber sie sind alle nicht verbunden. Muss ich jetzt neu pairen das wäre sehr mühevoll da schon an die Wände verbaut :|

lG Bester
3991_zigbee.png

arteck

~~@Arnulf:~~

Vielen Dank.

Damit habe ich die DB gefunden

Es ist doch sicher nicht normal, dass da die IDs doppelt auftauchen, oder?

Die DB ist 42 Zeilen groß (42 Zeilen, die mit "["id":" beginen habe aber aktuell nur 20 Devices in meiner Adapter-Geräteliste

Muss ich da jetzt Zeilen löschen?

Wenn ja, welche?

Und: Wie öffne ich am Besten die Schreibgeschützte Datei? ioBroker muss sicher vorher gestoppt werden. Oder?

[update]

Hier mal die linken Zeichen der Shepherd-DB.

Vielleicht ist das doch so korrekt. Zumindest könnte die obere Hälfte der normale Eintrag und die untere Hälfte der Index sein

! {"id":24,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":25,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":26,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":17,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":2,"type":"Router","ieeeAddr":"0x00178801030
! {"id":11,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":19,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":20,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":18,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":12,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":21,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":16,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":27,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":5,"type":"Router","ieeeAddr":"0x7cb03eaa00b
! {"id":13,"type":"Router","ieeeAddr":"0x7cb03eaa00
! {"id":14,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b
! {"id":15,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":10,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":22,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":23,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"$indexCreated":{"fieldName":"id","unique":true
! {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b
! {"id":24,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":25,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":26,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":17,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":2,"type":"Router","ieeeAddr":"0x00178801030
! {"id":11,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":19,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":20,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":18,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":12,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":21,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":16,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":27,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":5,"type":"Router","ieeeAddr":"0x7cb03eaa00b
! {"id":13,"type":"Router","ieeeAddr":"0x7cb03eaa00
! {"id":14,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":15,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":10,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":22,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":23,"type":"EndDevice","ieeeAddr":"0x00158d0

[Update]

Ich habe auch die Geräte, die im Adapter gelistet sind mit den Werten in der DB verglichen.

Alles drin. Auch die als Router fungierenden Geräte.

Nur halt eben doppelt `

da ich gearde im Tall der Ahnungslosen bin.. was war dein Problem nochmal ???

arteck

~~@besterquester:~~

Ich habe eine Frage, ich habe den ZigBee Adapter installiert und erfolgreich einige Aqara Sensoren gepaired.

Nun habe ich iobroker restoren und neu aufsetzen müssen.

Ich habe

iobroker stop

iobroker restore

iobroker start

iobroker upload all

Die Sensoren scheinen da zu sein aber sie sind alle nicht verbunden. Muss ich jetzt neu pairen das wäre sehr mühevoll da schon an die Wände verbaut :|

lG Bester `

was heisst restoren.. wie ??

besterquester

~~@arteck:~~

~~@besterquester:~~

Ich habe eine Frage, ich habe den ZigBee Adapter installiert und erfolgreich einige Aqara Sensoren gepaired.

Nun habe ich iobroker restoren und neu aufsetzen müssen.

Ich habe

iobroker stop

iobroker restore

iobroker start

iobroker upload all

Die Sensoren scheinen da zu sein aber sie sind alle nicht verbunden. Muss ich jetzt neu pairen das wäre sehr mühevoll da schon an die Wände verbaut :|

lG Bester `

was heisst restoren.. wie ?? `

ich habe ein backup erstellt mit

$ sudo iobroker backup

Raspi neu aufgesetzt aus einem iobroker minimal image und dann backup über

sudo iobroker restore 0

wieder eingespielt.

vg Bester

arteck

tja dann wirst du wohl neu anlernen müssen…

die Objekte sind da aber nicht die DB.. ich schätze die wird mit dem Backup nicht gesichert

schau mal was hier steht /opt/ioroker/iobroker-data/zigbee_0/shepherd.db

steht da was drin ??

besterquester

ja da steht was drinnen.

{"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0018e1b318","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1547487414,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterLi$
{"$indexCreated":{"fieldName":"id","unique":true,"sparse":false}}
{"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0018e1b318","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1547487432,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterLi$
{"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0002c586d2","nwkAddr":15146,"manufId":4151,"epList":[1],"status":"online","joinTime":1547488316,"endpoints":{"1":{"profId":260,"epId":1,"devId":263,"inClusterList"$
{"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0002c586d2","nwkAddr":15146,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_motion.aq2","epList":[1],"status":"online","joinTime":$
{"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0002c586d2","nwkAddr":15146,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_motion.aq2","epList":[1],"status":"online","joinTime":$
{"id":3,"type":"EndDevice","ieeeAddr":"0x00158d00025583c8","nwkAddr":34269,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488696,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluste$
{"id":3,"type":"EndDevice","ieeeAddr":"0x00158d00025583c8","nwkAddr":34269,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748869$
{"id":3,"type":"EndDevice","ieeeAddr":"0x00158d00025583c8","nwkAddr":34269,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748869$
{"id":4,"type":"EndDevice","ieeeAddr":"0x00158d00023ac6dc","nwkAddr":9281,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488789,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluster$
{"id":4,"type":"EndDevice","ieeeAddr":"0x00158d00023ac6dc","nwkAddr":9281,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":1547488789$
{"id":4,"type":"EndDevice","ieeeAddr":"0x00158d00023ac6dc","nwkAddr":9281,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":1547488789$
{"id":5,"type":"EndDevice","ieeeAddr":"0x00158d00025583a5","nwkAddr":65210,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488879,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluste$
{"id":5,"type":"EndDevice","ieeeAddr":"0x00158d00025583a5","nwkAddr":65210,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748887$
{"id":5,"type":"EndDevice","ieeeAddr":"0x00158d00025583a5","nwkAddr":65210,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748887$
{"id":6,"type":"EndDevice","ieeeAddr":"0x00158d0002b5a2f0","nwkAddr":33900,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488967,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluste$
{"id":6,"type":"EndDevice","ieeeAddr":"0x00158d0002b5a2f0","nwkAddr":33900,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748896$
{"id":6,"type":"EndDevice","ieeeAddr":"0x00158d0002b5a2f0","nwkAddr":33900,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748896$

Ich habe die Temp neu angelernt die Bewegungsmelder hängen an der Wand. Die zeigen immer noch not conected an

g Bester

CKMartens

Das Problem ist gelöst.

Für bluez muste ich den Befehl

setcap cap_net_raw+eip $(eval readlink -f which node)

eingeben danach wurde auch der Zigbee Adapter grün

–------------------------------------------------------------------------------------------------------------------------------------------------------------

Ich bin gerade etwas am Verzweifeln. Nachdem ich heute meinen Server neu aufsetzen musste und iobroker neu instaliert habe bekomme ich den Zigbee nicht mehr zum laufen.

node und nodejs sind v8.15.0

npm ist 6.15

zigbee Adapter ist 0.8.2a von github.com

Server Ubuntu 18.05

ls -la /dev/serial/by-id

gibt folgendes aus:

lrwxrwxrwx 1 root root 13 Jan 14 19:18 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018ED2570-if00 -> ../../ttyACM0

Felherlog:

! ````
zigbee.0 2019-01-14 19:37:34.705 debug User stateChange zigbee.0.info.connection {"val":false,"ack":false,"ts":1547491054701,"q":0,"from":"system.adapter.zigbee.0","lc":1547490902187}
zigbee.0 2019-01-14 19:37:34.113 error Error while starting zigbee-shepherd!. Error: Error: Permission denied, cannot open /dev/ttyACM0
zigbee.0 2019-01-14 19:37:34.113 debug 2019-01-14T18:37:34.109Z zigbee:controller error Error while starting zigbee-shepherd! Error: Error: Permission denied, cannot open /dev/ttyACM0
zigbee.0 2019-01-14 19:37:34.113 debug 2019-01-14T18:37:34.106Z zigbee-shepherd:init zigbee-shepherd booting...
zigbee.0 2019-01-14 19:37:34.113 info Starting zigbee-shepherd
zigbee.0 2019-01-14 19:37:34.113 debug 2019-01-14T18:37:34.105Z zigbee:controller info Starting zigbee-shepherd undefined
zigbee.0 2019-01-14 19:36:34.105 debug Error while starting zigbee-shepherd, attemping to fix... (takes 60 seconds)
zigbee.0 2019-01-14 19:36:34.104 debug 2019-01-14T18:36:34.104Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix... (takes 60 seconds) undefined
zigbee.0 2019-01-14 19:36:34.085 debug 2019-01-14T18:36:34.085Z zigbee-shepherd:init zigbee-shepherd booting...
zigbee.0 2019-01-14 19:36:34.069 info Start on port: /dev/ttyACM0 with panID 6754 channel 11
zigbee.0 2019-01-14 19:36:34.066 info starting. Version 0.8.2-a in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0


Bin mit meinem Latein bisschen am Ende, vor allem da es ja auf dem "alten" System ohne Probleme lief.

AndrK

Hallo CKMartens,

was kommt bei Dir bei

ls -la /dev/ttyACM0

bei mir (Raspi) sehe ich:

crw-rw---- 1 root dialout 166, 0 Jan 14 10:14 /dev/ttyACM0

Gruß

AndrK

Arnulf

~~@arteck:~~

~~@Arnulf:~~

Vielen Dank.

Damit habe ich die DB gefunden

Es ist doch sicher nicht normal, dass da die IDs doppelt auftauchen, oder?

Die DB ist 42 Zeilen groß (42 Zeilen, die mit "["id":" beginen habe aber aktuell nur 20 Devices in meiner Adapter-Geräteliste

Muss ich da jetzt Zeilen löschen?

Wenn ja, welche?

Und: Wie öffne ich am Besten die Schreibgeschützte Datei? ioBroker muss sicher vorher gestoppt werden. Oder?

[update]

Hier mal die linken Zeichen der Shepherd-DB.

Vielleicht ist das doch so korrekt. Zumindest könnte die obere Hälfte der normale Eintrag und die untere Hälfte der Index sein

! {"id":24,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":25,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":26,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":17,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":2,"type":"Router","ieeeAddr":"0x00178801030
! {"id":11,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":19,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":20,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":18,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":12,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":21,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":16,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":27,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":5,"type":"Router","ieeeAddr":"0x7cb03eaa00b
! {"id":13,"type":"Router","ieeeAddr":"0x7cb03eaa00
! {"id":14,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b
! {"id":15,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":10,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":22,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":23,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"$indexCreated":{"fieldName":"id","unique":true
! {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b
! {"id":24,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":25,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":26,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":17,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":2,"type":"Router","ieeeAddr":"0x00178801030
! {"id":11,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":19,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":20,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":18,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":12,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":21,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":16,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":27,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":5,"type":"Router","ieeeAddr":"0x7cb03eaa00b
! {"id":13,"type":"Router","ieeeAddr":"0x7cb03eaa00
! {"id":14,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":15,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":10,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":22,"type":"EndDevice","ieeeAddr":"0x00158d0
! {"id":23,"type":"EndDevice","ieeeAddr":"0x00158d0

[Update]

Ich habe auch die Geräte, die im Adapter gelistet sind mit den Werten in der DB verglichen.

Alles drin. Auch die als Router fungierenden Geräte.

Nur halt eben doppelt `

da ich gearde im Tall der Ahnungslosen bin.. was war dein Problem nochmal ??? `

:D

… dass ich im Moment keine Geräte anlernen kann. Keine Humity-Semsoren und auch heute meinen Aqara-Cube nicht.

Ich hatte die Datenbank in Verdacht. Dass entweder was Falsches drinsteht oder was Altes.

Ich vermute aber, die ist so weit OK

Arnulf

~~@besterquester:~~

ja da steht was drinnen.

{"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0018e1b318","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1547487414,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterLi$
{"$indexCreated":{"fieldName":"id","unique":true,"sparse":false}}
{"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0018e1b318","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1547487432,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterLi$
{"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0002c586d2","nwkAddr":15146,"manufId":4151,"epList":[1],"status":"online","joinTime":1547488316,"endpoints":{"1":{"profId":260,"epId":1,"devId":263,"inClusterList"$
{"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0002c586d2","nwkAddr":15146,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_motion.aq2","epList":[1],"status":"online","joinTime":$
{"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0002c586d2","nwkAddr":15146,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_motion.aq2","epList":[1],"status":"online","joinTime":$
{"id":3,"type":"EndDevice","ieeeAddr":"0x00158d00025583c8","nwkAddr":34269,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488696,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluste$
{"id":3,"type":"EndDevice","ieeeAddr":"0x00158d00025583c8","nwkAddr":34269,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748869$
{"id":3,"type":"EndDevice","ieeeAddr":"0x00158d00025583c8","nwkAddr":34269,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748869$
{"id":4,"type":"EndDevice","ieeeAddr":"0x00158d00023ac6dc","nwkAddr":9281,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488789,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluster$
{"id":4,"type":"EndDevice","ieeeAddr":"0x00158d00023ac6dc","nwkAddr":9281,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":1547488789$
{"id":4,"type":"EndDevice","ieeeAddr":"0x00158d00023ac6dc","nwkAddr":9281,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":1547488789$
{"id":5,"type":"EndDevice","ieeeAddr":"0x00158d00025583a5","nwkAddr":65210,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488879,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluste$
{"id":5,"type":"EndDevice","ieeeAddr":"0x00158d00025583a5","nwkAddr":65210,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748887$
{"id":5,"type":"EndDevice","ieeeAddr":"0x00158d00025583a5","nwkAddr":65210,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748887$
{"id":6,"type":"EndDevice","ieeeAddr":"0x00158d0002b5a2f0","nwkAddr":33900,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488967,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluste$
{"id":6,"type":"EndDevice","ieeeAddr":"0x00158d0002b5a2f0","nwkAddr":33900,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748896$
{"id":6,"type":"EndDevice","ieeeAddr":"0x00158d0002b5a2f0","nwkAddr":33900,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748896$

Ich habe die Temp neu angelernt die Bewegungsmelder hängen an der Wand. Die zeigen immer noch not conected an

g Bester `

Bei dir stehem die IDs ja noch öfter drin als bei mir. Bei mir ist das "nur" zweimal

besterquester

~~@Arnulf:~~

~~@besterquester:~~

ja da steht was drinnen.

{"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0018e1b318","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1547487414,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterLi$
{"$indexCreated":{"fieldName":"id","unique":true,"sparse":false}}
{"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0018e1b318","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1547487432,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterLi$
{"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0002c586d2","nwkAddr":15146,"manufId":4151,"epList":[1],"status":"online","joinTime":1547488316,"endpoints":{"1":{"profId":260,"epId":1,"devId":263,"inClusterList"$
{"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0002c586d2","nwkAddr":15146,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_motion.aq2","epList":[1],"status":"online","joinTime":$
{"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0002c586d2","nwkAddr":15146,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sensor_motion.aq2","epList":[1],"status":"online","joinTime":$
{"id":3,"type":"EndDevice","ieeeAddr":"0x00158d00025583c8","nwkAddr":34269,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488696,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluste$
{"id":3,"type":"EndDevice","ieeeAddr":"0x00158d00025583c8","nwkAddr":34269,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748869$
{"id":3,"type":"EndDevice","ieeeAddr":"0x00158d00025583c8","nwkAddr":34269,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748869$
{"id":4,"type":"EndDevice","ieeeAddr":"0x00158d00023ac6dc","nwkAddr":9281,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488789,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluster$
{"id":4,"type":"EndDevice","ieeeAddr":"0x00158d00023ac6dc","nwkAddr":9281,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":1547488789$
{"id":4,"type":"EndDevice","ieeeAddr":"0x00158d00023ac6dc","nwkAddr":9281,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":1547488789$
{"id":5,"type":"EndDevice","ieeeAddr":"0x00158d00025583a5","nwkAddr":65210,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488879,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluste$
{"id":5,"type":"EndDevice","ieeeAddr":"0x00158d00025583a5","nwkAddr":65210,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748887$
{"id":5,"type":"EndDevice","ieeeAddr":"0x00158d00025583a5","nwkAddr":65210,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748887$
{"id":6,"type":"EndDevice","ieeeAddr":"0x00158d0002b5a2f0","nwkAddr":33900,"manufId":4151,"epList":[1,2,3],"status":"online","joinTime":1547488967,"endpoints":{"1":{"profId":260,"epId":1,"devId":24321,"inCluste$
{"id":6,"type":"EndDevice","ieeeAddr":"0x00158d0002b5a2f0","nwkAddr":33900,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748896$
{"id":6,"type":"EndDevice","ieeeAddr":"0x00158d0002b5a2f0","nwkAddr":33900,"manufId":4151,"manufName":"LUMI","powerSource":"Battery","modelId":"lumi.sens","epList":[1,2,3],"status":"online","joinTime":154748896$

Ich habe die Temp neu angelernt die Bewegungsmelder hängen an der Wand. Die zeigen immer noch not conected an

g Bester `

Bei dir stehem die IDs ja noch öfter drin als bei mir. Bei mir ist das "nur" zweimal `

Hat jemand schon versucht die doppelten zu löschen was passiert dann -> neu paaren :)

arteck

Leute wenn ihr nicht wisst was ihr macht dann lasst es..

ja bei mir stehen die Geräte auch doppelt drin.

arteck

~~@CKMartens:~~

Das Problem ist gelöst.

Für bluez muste ich den Befehl

setcap cap_net_raw+eip $(eval readlink -f which node)

eingeben danach wurde auch der Zigbee Adapter grün

–------------------------------------------------------------------------------------------------------------------------------------------------------------

Ich bin gerade etwas am Verzweifeln. Nachdem ich heute meinen Server neu aufsetzen musste und iobroker neu instaliert habe bekomme ich den Zigbee nicht mehr zum laufen.

node und nodejs sind v8.15.0

npm ist 6.15

zigbee Adapter ist 0.8.2a von github.com

Server Ubuntu 18.05
ls -la /dev/serial/by-id
gibt folgendes aus:
lrwxrwxrwx 1 root root 13 Jan 14 19:18 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018ED2570-if00 -> ../../ttyACM0
Felherlog:

! ````
zigbee.0 2019-01-14 19:37:34.705 debug User stateChange zigbee.0.info.connection {"val":false,"ack":false,"ts":1547491054701,"q":0,"from":"system.adapter.zigbee.0","lc":1547490902187}
zigbee.0 2019-01-14 19:37:34.113 error Error while starting zigbee-shepherd!. Error: Error: Permission denied, cannot open /dev/ttyACM0
zigbee.0 2019-01-14 19:37:34.113 debug 2019-01-14T18:37:34.109Z zigbee:controller error Error while starting zigbee-shepherd! Error: Error: Permission denied, cannot open /dev/ttyACM0
zigbee.0 2019-01-14 19:37:34.113 debug 2019-01-14T18:37:34.106Z zigbee-shepherd:init zigbee-shepherd booting...
zigbee.0 2019-01-14 19:37:34.113 info Starting zigbee-shepherd
zigbee.0 2019-01-14 19:37:34.113 debug 2019-01-14T18:37:34.105Z zigbee:controller info Starting zigbee-shepherd undefined
zigbee.0 2019-01-14 19:36:34.105 debug Error while starting zigbee-shepherd, attemping to fix... (takes 60 seconds)
zigbee.0 2019-01-14 19:36:34.104 debug 2019-01-14T18:36:34.104Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix... (takes 60 seconds) undefined
zigbee.0 2019-01-14 19:36:34.085 debug 2019-01-14T18:36:34.085Z zigbee-shepherd:init zigbee-shepherd booting...
zigbee.0 2019-01-14 19:36:34.069 info Start on port: /dev/ttyACM0 with panID 6754 channel 11
zigbee.0 2019-01-14 19:36:34.066 info starting. Version 0.8.2-a in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0
Bin mit meinem Latein bisschen am Ende, vor allem da es ja auf dem "alten" System ohne Probleme lief. `  

lesen kannst du aber schon oder ??

zigbee-shepherd! Error: Error: Permission denied, cannot open /dev/ttyACM0

CKMartens

> lesen kannst du aber schon oder ??

Selten so freundliche Nachrichten gelesen

Community Forum

NEWS

[Aufruf] ZigBee CC253x Adapter

Support us

601

32.7k

82.4k

1.3m