[74_XiaomiBTLESens.pm] Xiaomi Bluetooth Sensoren FlowerSens/Thermometer

Begonnen von CoolTux, 11 Januar 2018, 15:42:45

Vorheriges Thema - Nächstes Thema

Neuhier


rani22

Habe die Lampe ausgesteckt und beim Handy BT deaktiviert.

Habe zwischen durch wieder gültige Werte erhalten. Nach dem ich folgendes gemacht hatte:
root@loxberry:/opt/loxberry# sudo hciconfig hci0  down
root@loxberry:/opt/loxberry# sudo hciconfig hci0  up


2018.12.23 17:30:48 0: Server started with 18 defined entities (fhem.pl:18029/2018-12-22 perl:5.024001 os:linux user:loxberry pid:7807)
2018.12.23 17:32:12 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 7814
2018.12.23 17:32:12 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 7815
2018.12.23 17:32:18 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 7821
2018.12.23 17:32:18 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 7822
2018.12.23 17:32:18 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 7823
2018.12.23 17:32:18 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 7824
2018.12.23 17:32:33 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:34 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:35 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:36 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:37 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:38 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:39 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:40 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:42 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:43 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:44 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:45 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:46 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:47 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:48 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:48 3: XiaomiBTLESens (Floribunda) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:49 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:49 3: XiaomiBTLESens (Floribunda) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:50 3: XiaomiBTLESens (Beaucarnea) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:32:50 3: XiaomiBTLESens (Floribunda) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 17:33:39 3: n_publish_loxone return value: 1
2018.12.23 17:42:16 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 8451
2018.12.23 17:52:50 3: XiaomiBTLESens (TempBad) - defined with BTMAC 4C:65:A8:D2:64:7E
2018.12.23 17:59:19 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 9386
2018.12.23 18:01:22 3: XiaomiBTLESens (OG) - defined with BTMAC 4C:65:A8:DA:82:9C
2018.12.23 18:06:15 3: n_publish_loxone return value: 1
2018.12.23 18:06:15 3: n_publish_loxone return value: 1
2018.12.23 18:06:15 3: n_publish_loxone return value: 1
2018.12.23 18:06:15 3: n_publish_loxone return value: 1
2018.12.23 18:07:08 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 9919
2018.12.23 18:07:08 3: Sub XiaomiBTLESens_Undef (test1) - delete device test1
2018.12.23 18:07:14 3: Sub XiaomiBTLESens_Undef (test2) - delete device test2
2018.12.23 18:07:16 3: XiaomiBTLESens (TempBad) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 18:07:17 3: XiaomiBTLESens (TempBad) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 18:07:18 3: XiaomiBTLESens (TempBad) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 18:07:18 3: Sub XiaomiBTLESens_Undef (test3) - delete device test3
2018.12.23 18:07:19 3: XiaomiBTLESens (TempBad) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 18:07:20 3: XiaomiBTLESens (TempBad) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 18:07:21 3: XiaomiBTLESens (TempBad) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 18:07:22 3: XiaomiBTLESens (TempBad) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 18:07:23 3: XiaomiBTLESens (TempBad) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 18:07:24 3: XiaomiBTLESens (TempBad) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 18:07:26 3: XiaomiBTLESens (TempBad) - ExecGatttool_Run: another gatttool process is running. waiting...
2018.12.23 18:07:26 3: Sub XiaomiBTLESens_Undef (test4) - delete device test4
2018.12.23 18:07:36 3: XiaomiBTLESens (TempRoomPW) - defined with BTMAC 4C:65:A8:D2:2C:0C
2018.12.23 18:08:46 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 9944
2018.12.23 18:09:15 3: XiaomiBTLESens (TempGuestRoom) - defined with BTMAC 4C:65:A8:DA:A1:86
2018.12.23 18:14:31 3: Sub XiaomiBTLESens_Undef (OG) - delete device OG
2018.12.23 18:14:34 3: XiaomiBTLESens (TempOG) - defined with BTMAC 4C:65:A8:DA:82:9C
2018.12.23 18:14:48 3: XiaomiBTLESens (TempOffice) - defined with BTMAC 4C:65:A8:D8:E9:CF
2018.12.23 18:15:53 3: n_publish_loxone return value: 1
2018.12.23 18:15:53 3: n_publish_loxone return value: 1
2018.12.23 18:19:04 3: XiaomiBTLESens (TempBedroom) - defined with BTMAC 4C:65:A8:D6:77:51
2018.12.23 18:25:15 3: n_publish_loxone return value: 1
2018.12.23 18:25:15 3: n_publish_loxone return value: 1


Hat jemand einen Vorschlag das ganze stabiler zu machen?

CoolTux

Das kann in der Tat beim FHEM start etwas hacken. Gerade von man 5 Geräte und mehr hat. Wie schaut es denn nach einer halben Stunde so aus?
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

rani22

Zitat von: CoolTux am 23 Dezember 2018, 19:06:26
Das kann in der Tat beim FHEM start etwas hacken. Gerade von man 5 Geräte und mehr hat. Wie schaut es denn nach einer halben Stunde so aus?
Ohne manuelles hciconfig hci0 stehen alle auf error. Ich lasse es mal über nacht laufen. Hast du Hoffnung, dass sich dies erholt?

CoolTux

Dann kann das aber nicht an der Anzahl liegen. Eher am nicht stabilen BT Stack (Software}
Welche gatttool Version hast Du? welche Distribution?
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

rani22

Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 9.4 (stretch)
Release:        9.4
Codename:       stretch

wie sehe ich welche version von gatttool installiert ist?

CoolTux

Zitat von: rani22 am 23 Dezember 2018, 20:45:04
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 9.4 (stretch)
Release:        9.4
Codename:       stretch

wie sehe ich welche version von gatttool installiert ist?

Das passt schon. Dann weiß ich Bescheid.
Wie sieht es im Gesamtbild aus. Bekommen Deine Pflanzensensoren so gut wie immer Daten und nur die Temperatursensoren bekommen Errors oder klemmen auch die?
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

rani22

Zitat von: CoolTux am 24 Dezember 2018, 07:27:37
Wie sieht es im Gesamtbild aus. Bekommen Deine Pflanzensensoren so gut wie immer Daten und nur die Temperatursensoren bekommen Errors oder klemmen auch die?
Es sind alle Sensoren, jedoch habe ich das Gefühl es betrift komischerweise nicht alle Werte. Bei z.B. Batteriestatus hat es ein OK mit einem relativ aktuellen Zeitstempel. Aber generell ist gestern kurz nach dem ins Bettgehen alles stillgestanden.

2018.12.23 23:32:07 3: n_publish_loxone return value: 1
2018.12.23 23:34:18 3: n_publish_loxone return value: 1
2018.12.23 23:34:49 3: n_publish_loxone return value: 1
2018.12.23 23:52:02 3: n_publish_loxone return value: 1
2018.12.24 01:01:22 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 14998
2018.12.24 02:37:14 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 19638
2018.12.24 04:05:14 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 23737
2018.12.24 09:23:27 3: n_publish_loxone return value: 1
2018.12.24 09:23:27 3: n_publish_loxone return value: 1


Heute morgen habe ich mit dm reset von hci0 wieder ein paar werte erhalten.

edit/

Um 9:49 habe ich noch einmal geresettet. Diesmal hatte ich bei einem Sensor das Verbose auf 5 gestellt:


2018.12.24 09:23:27 3: n_publish_loxone return value: 1
2018.12.24 09:23:27 3: n_publish_loxone return value: 1
2018.12.24 09:26:12 3: n_publish_loxone return value: 1
2018.12.24 09:26:12 3: n_publish_loxone return value: 1
2018.12.24 09:26:25 3: n_publish_loxone return value: 1
2018.12.24 09:26:25 3: n_publish_loxone return value: 1
2018.12.24 09:27:29 3: n_publish_loxone return value: 1
2018.12.24 09:27:29 3: n_publish_loxone return value: 1
2018.12.24 09:27:54 3: n_publish_loxone return value: 1
2018.12.24 09:27:54 3: n_publish_loxone return value: 1
2018.12.24 09:27:54 3: n_publish_loxone return value: 1
2018.12.24 09:29:17 3: n_publish_loxone return value: 1
2018.12.24 09:31:35 3: n_publish_loxone return value: 1
2018.12.24 09:40:19 4: XiaomiBTLESens (TempBedroom) - Run CreateParamGatttool with mod: write
2018.12.24 09:40:19 5: XiaomiBTLESens (TempBedroom) - Write XiaomiBTLESens_ExecGatttool_Run TempBedroom|4C:65:A8:D6:77:51|write|0x10|0100
2018.12.24 09:40:19 4: XiaomiBTLESens (TempBedroom) - stateRequestTimer: Call Request Timer
2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 0
2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 1
2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 2
2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 3
2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 4
2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 09:40:20 4: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool result connect error,Invalid argument (22)

2018.12.24 09:40:20 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Done: gatttool return string: TempBedroom|4C:65:A8:D6:77:51|error|write|0x10|{"gtResult":"Invalid argument (22)"}
2018.12.24 09:40:20 4: XiaomiBTLESens (TempBedroom) - ProcessingErrors
2018.12.24 09:40:20 4: XiaomiBTLESens (TempBedroom) - WriteReadings: Readings were written
2018.12.24 09:46:53 4: XiaomiBTLESens (TempBedroom) - Run CreateParamGatttool with mod: write
2018.12.24 09:46:53 5: XiaomiBTLESens (TempBedroom) - Write XiaomiBTLESens_ExecGatttool_Run TempBedroom|4C:65:A8:D6:77:51|write|0x10|0100
2018.12.24 09:46:53 4: XiaomiBTLESens (TempBedroom) - stateRequestTimer: Call Request Timer
2018.12.24 09:46:54 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 0
2018.12.24 09:46:59 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 09:46:59 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 1
2018.12.24 09:46:59 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 09:46:59 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 2
2018.12.24 09:46:59 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 09:46:59 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 3
2018.12.24 09:47:00 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 09:47:00 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 4
2018.12.24 09:47:00 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 09:47:00 4: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool result connect error,Invalid argument (22)

2018.12.24 09:47:00 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Done: gatttool return string: TempBedroom|4C:65:A8:D6:77:51|error|write|0x10|{"gtResult":"Invalid argument (22)"}
2018.12.24 09:47:00 4: XiaomiBTLESens (TempBedroom) - ProcessingErrors
2018.12.24 09:47:00 4: XiaomiBTLESens (TempBedroom) - WriteReadings: Readings were written
2018.12.24 09:50:39 3: n_publish_loxone return value: 1
2018.12.24 09:50:39 3: n_publish_loxone return value: 1
2018.12.24 09:50:39 3: n_publish_loxone return value: 1
2018.12.24 09:52:58 4: XiaomiBTLESens (TempBedroom) - Run CreateParamGatttool with mod: write
2018.12.24 09:52:58 5: XiaomiBTLESens (TempBedroom) - Write XiaomiBTLESens_ExecGatttool_Run TempBedroom|4C:65:A8:D6:77:51|write|0x10|0100
2018.12.24 09:52:58 4: XiaomiBTLESens (TempBedroom) - stateRequestTimer: Call Request Timer
2018.12.24 09:52:59 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 0
2018.12.24 09:53:09 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result Characteristic value was written successfully
Notification handle = 0x000e value,54 3d 32 30 2e 31 20 48 3d 35 35 2e 38 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 35 2e 37 00
Notification handle = 0x000e value,54 3d 32 30 2e 31 20 48 3d 35 35 2e 37 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 36 2e 30 00
Notification handle = 0x000e value,54 3d 32 30 2e 33 20 48 3d 35 35 2e 37 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 35 2e 39 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 35 2e 37 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 35 2e 38 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 35 2e 37 00

2018.12.24 09:53:09 4: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool result Characteristic value was written successfully
Notification handle = 0x000e value,54 3d 32 30 2e 31 20 48 3d 35 35 2e 38 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 35 2e 37 00
Notification handle = 0x000e value,54 3d 32 30 2e 31 20 48 3d 35 35 2e 37 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 36 2e 30 00
Notification handle = 0x000e value,54 3d 32 30 2e 33 20 48 3d 35 35 2e 37 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 35 2e 39 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 35 2e 37 00
Notification handle = 0x000e value,54 3d 32 30 2e 32 20 48 3d 35 35

CoolTux

Setze mal Deine Intervalle unterschiedlicher. Die Pflanzensensor lässt Du jede Stunde abfragen und die Temperatursensoren je nach Raum etwas strecken.
Ich denke du rufst auch zu oft ab.
Generell reicht alle 5 min bei den Temperatursensoren. Das Strecker du noch bei unwichtigen Orten. Badezimmer auf 7 mm in Wohnzimmer auf 4 wegen meiner und Küche auf 9 min. Küche ist eh immer warm denke ich.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

rani22

Das hat nicht wirklich was geholfen. nach ein paar abfragen ist Schluss.

2018.12.24 10:36:12 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Done: gatttool return string: TempBedroom|4C:65:A8:D6:77:51|ok|write|0x10|{"gtResult":"54 3d 32 30 2e 33 20 48 3d 35 35 2e 34 00 "}
2018.12.24 10:36:12 4: XiaomiBTLESens (TempBedroom) - ProcessingNotification
2018.12.24 10:36:12 4: XiaomiBTLESens (TempBedroom) - ProcessingNotification: handle 0x10
2018.12.24 10:36:12 4: XiaomiBTLESens (TempBedroom) - Thermo/Hygro Sens Handle0x10
2018.12.24 10:36:13 3: n_publish_loxone return value: 1
2018.12.24 10:36:13 3: n_publish_loxone return value: 1
2018.12.24 10:36:13 4: XiaomiBTLESens (TempBedroom) - WriteReadings: Readings were written
2018.12.24 10:36:37 3: n_publish_loxone return value: 1
2018.12.24 10:36:37 3: n_publish_loxone return value: 1
2018.12.24 10:52:22 4: XiaomiBTLESens (TempBedroom) - Run CreateParamGatttool with mod: write
2018.12.24 10:52:22 5: XiaomiBTLESens (TempBedroom) - Write XiaomiBTLESens_ExecGatttool_Run TempBedroom|4C:65:A8:D6:77:51|write|0x10|0100
2018.12.24 10:52:22 4: XiaomiBTLESens (TempBedroom) - stateRequestTimer: Call Request Timer
2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 0
2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 1
2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 2
2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 3
2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 4
2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 10:52:23 4: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool result connect error,Invalid argument (22)

2018.12.24 10:52:23 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Done: gatttool return string: TempBedroom|4C:65:A8:D6:77:51|error|write|0x10|{"gtResult":"Invalid argument (22)"}
2018.12.24 10:52:23 4: XiaomiBTLESens (TempBedroom) - ProcessingErrors
2018.12.24 10:52:23 4: XiaomiBTLESens (TempBedroom) - WriteReadings: Readings were written
2018.12.24 11:06:34 4: XiaomiBTLESens (TempBedroom) - Run CreateParamGatttool with mod: write
2018.12.24 11:06:34 5: XiaomiBTLESens (TempBedroom) - Write XiaomiBTLESens_ExecGatttool_Run TempBedroom|4C:65:A8:D6:77:51|write|0x10|0100
2018.12.24 11:06:34 4: XiaomiBTLESens (TempBedroom) - stateRequestTimer: Call Request Timer
2018.12.24 11:06:34 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 0
2018.12.24 11:06:41 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 11:06:41 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 1
2018.12.24 11:06:41 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 11:06:41 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 2
2018.12.24 11:06:41 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 11:06:41 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 3
2018.12.24 11:06:42 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 11:06:42 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 4
2018.12.24 11:06:42 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Invalid argument (22)

2018.12.24 11:06:42 4: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool result connect error,Invalid argument (22)

2018.12.24 11:06:42 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Done: gatttool return string: TempBedroom|4C:65:A8:D6:77:51|error|write|0x10|{"gtResult":"Invalid argument (22)"}
2018.12.24 11:06:42 4: XiaomiBTLESens (TempBedroom) - ProcessingErrors
2018.12.24 11:06:42 4: XiaomiBTLESens (TempBedroom) - WriteReadings: Readings were written
2018.12.24 11:24:38 4: XiaomiBTLESens (TempBedroom) - Run CreateParamGatttool with mod: write
2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - Write XiaomiBTLESens_ExecGatttool_Run TempBedroom|4C:65:A8:D6:77:51|write|0x10|0100
2018.12.24 11:24:38 4: XiaomiBTLESens (TempBedroom) - stateRequestTimer: Call Request Timer
2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 0
2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Too many levels of symbolic links (40)

2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 1
2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Too many levels of symbolic links (40)

2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 2
2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Too many levels of symbolic links (40)

2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 3
2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Too many levels of symbolic links (40)

2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: call gatttool with command: timeout 10 gatttool -i hci0 -b 4C:65:A8:D6:77:51 --char-write-req -a 0x10 -n 0100 --listen 2>&1 /dev/null and loop 4
2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool loop result connect error,Too many levels of symbolic links (40)

2018.12.24 11:24:38 4: XiaomiBTLESens (TempBedroom) - ExecGatttool_Run: gatttool result connect error,Too many levels of symbolic links (40)

2018.12.24 11:24:38 5: XiaomiBTLESens (TempBedroom) - ExecGatttool_Done: gatttool return string: TempBedroom|4C:65:A8:D6:77:51|error|write|0x10|{"gtResult":"Too many levels of symbolic links (40)"}
2018.12.24 11:24:38 4: XiaomiBTLESens (TempBedroom) - ProcessingErrors
2018.12.24 11:24:38 4: XiaomiBTLESens (TempBedroom) - WriteReadings: Readings were written

CoolTux

OK dann schalte bitte mal nur die 3 Temposensoren und die 2 Pflanzensensoren ein und schaue dann mal.
Möglich das Du Dir einen zweiten BT Stick besorgen musst um das ganze auf zu teilen.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

rani22

Ich habe nun noch ein Systemupdate gemacht. Die Config etwas aufgeräumt und neu gestartet.
Mit 5 BLE sensoren scheint es nun zu laufen:

2018.12.24 13:03:24 1: Including /opt/loxberry/config/plugins/fhem/fhem.cfg
2018.12.24 13:03:24 3: telnetPort: port 7072 opened
2018.12.24 13:03:24 3: WEB: port 8083 opened
2018.12.24 13:03:24 3: WEBphone: port 8084 opened
2018.12.24 13:03:24 3: WEBtablet: port 8085 opened
2018.12.24 13:03:24 2: eventTypes: loaded 79 events from /opt/loxberry/data/plugins/fhem/eventTypes.txt
2018.12.24 13:03:24 3: XiaomiBTLESens (Floribunda) - defined with BTMAC C4:7C:8D:61:9C:D0
2018.12.24 13:03:24 3: XiaomiBTLESens (Floribunda) - set interval to 1750
2018.12.24 13:03:24 3: XiaomiBTLESens (Beaucarnea) - defined with BTMAC C4:7C:8D:61:7C:FF
2018.12.24 13:03:24 3: XiaomiBTLESens (Beaucarnea) - set interval to 1800
2018.12.24 13:03:24 3: XiaomiBTLESens (TempBath) - defined with BTMAC 4C:65:A8:D2:64:7E
2018.12.24 13:03:24 3: XiaomiBTLESens (TempBath) - set interval to 622
2018.12.24 13:03:24 3: XiaomiBTLESens (TempRoomPW) - defined with BTMAC 4C:65:A8:D2:2C:0C
2018.12.24 13:03:24 3: XiaomiBTLESens (TempRoomPW) - set interval to 1022
2018.12.24 13:03:24 3: XiaomiBTLESens (TempOffice) - defined with BTMAC 4C:65:A8:D8:E9:CF
2018.12.24 13:03:24 3: XiaomiBTLESens (TempOffice) - set interval to 822
2018.12.24 13:03:24 1: Including /opt/loxberry/data/plugins/fhem/fhem.save
2018.12.24 13:03:24 1: usb create starting
2018.12.24 13:03:25 3: Probing ZWDongle device /dev/serial1
2018.12.24 13:03:25 3: Probing CUL device /dev/ttyAMA0
2018.12.24 13:03:25 3: Probing TCM_ESP3 device /dev/ttyAMA0
2018.12.24 13:03:26 3: Probing ZWDongle device /dev/ttyAMA0
2018.12.24 13:03:26 3: Probing FRM device /dev/ttyAMA0
2018.12.24 13:03:38 1: usb create end
2018.12.24 13:03:38 0: Featurelevel: 5.9
2018.12.24 13:03:38 0: Server started with 17 defined entities (fhem.pl:18029/2018-12-22 perl:5.024001 os:linux user:loxberry pid:1057)
2018.12.24 13:03:41 3: n_publish_loxone return value: 1
2018.12.24 13:03:41 3: n_publish_loxone return value: 1
2018.12.24 13:03:41 3: n_publish_loxone return value: 1
2018.12.24 13:03:46 3: n_publish_loxone return value: 1
2018.12.24 13:03:46 3: n_publish_loxone return value: 1
2018.12.24 13:03:51 3: n_publish_loxone return value: 1
2018.12.24 13:03:51 3: n_publish_loxone return value: 1
2018.12.24 13:14:13 3: n_publish_loxone return value: 1
2018.12.24 13:25:13 3: n_publish_loxone return value: 1
2018.12.24 13:25:13 3: n_publish_loxone return value: 1
2018.12.24 13:25:59 3: n_publish_loxone return value: 1
2018.12.24 13:33:30 3: n_publish_loxone return value: 1
2018.12.24 13:33:30 3: n_publish_loxone return value: 1
2018.12.24 13:33:30 3: n_publish_loxone return value: 1
2018.12.24 13:38:21 3: n_publish_loxone return value: 1
2018.12.24 13:39:03 3: n_publish_loxone return value: 1
2018.12.24 13:39:03 3: n_publish_loxone return value: 1
2018.12.24 13:46:03 3: n_publish_loxone return value: 1
2018.12.24 13:46:03 3: n_publish_loxone return value: 1
2018.12.24 13:47:27 3: n_publish_loxone return value: 1
2018.12.24 13:47:27 3: n_publish_loxone return value: 1
2018.12.24 13:51:22 3: n_publish_loxone return value: 1
2018.12.24 13:52:09 3: n_publish_loxone return value: 1
2018.12.24 13:52:09 3: n_publish_loxone return value: 1
2018.12.24 14:02:24 3: n_publish_loxone return value: 1
2018.12.24 14:05:31 3: n_publish_loxone return value: 1
2018.12.24 14:05:31 3: n_publish_loxone return value: 1
2018.12.24 14:07:23 3: n_publish_loxone return value: 1
2018.12.24 14:07:23 3: n_publish_loxone return value: 1
2018.12.24 14:07:23 3: n_publish_loxone return value: 1
2018.12.24 14:09:51 3: n_publish_loxone return value: 1
2018.12.24 14:09:51 3: n_publish_loxone return value: 1
2018.12.24 14:10:53 3: n_publish_loxone return value: 1
2018.12.24 14:17:18 3: n_publish_loxone return value: 1
2018.12.24 14:24:33 3: n_publish_loxone return value: 1
2018.12.24 14:24:33 3: n_publish_loxone return value: 1
2018.12.24 14:26:34 3: n_publish_loxone return value: 1
2018.12.24 14:26:34 3: n_publish_loxone return value: 1
2018.12.24 14:27:49 3: n_publish_loxone return value: 1
2018.12.24 14:27:49 3: n_publish_loxone return value: 1
2018.12.24 14:40:26 3: n_publish_loxone return value: 1
2018.12.24 14:40:27 3: n_publish_loxone return value: 1
2018.12.24 14:40:27 3: n_publish_loxone return value: 1
2018.12.24 14:40:40 3: n_publish_loxone return value: 1
2018.12.24 14:40:40 3: n_publish_loxone return value: 1
2018.12.24 14:44:24 3: n_publish_loxone return value: 1
2018.12.24 14:44:24 3: n_publish_loxone return value: 1
2018.12.24 14:44:57 3: n_publish_loxone return value: 1
2018.12.24 14:50:49 3: n_publish_loxone return value: 1


Hast du eine empfehlung, welchen BT-Stick ich kaufen soll und wie ich die aufteilung machen kann?

CoolTux

Sagen wir mal so. Ich würde kein 5 Euro Teil kaufen. Meine haben immer um die 14 Euro gekostet und ich bin zufrieden damit. Mit der Aufteilung mach es doch einfach halb halb.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

rani22

So wies aussieht lag es nicht an der Anzahl Sensoren. Ich habe nun seit 20h ohne Probleme alle 8 Sensoren am laufen.


Raspberry Pi3 B+
Linux loxberry 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
Release:        9.6
Codename:       stretch



# Xiaomi BLE Sensors
# Flora Sensors
define Floribunda XiaomiBTLESens C4:7C:8D:61:9C:D0
attr Floribunda event-on-change-reading fertility,lux,moisture,temperature
attr Floribunda interval 1750
attr Floribunda loxone true
attr Floribunda model flowerSens
attr Floribunda room XiaomiBTLESens
attr Floribunda verbose 3
define Beaucarnea XiaomiBTLESens C4:7C:8D:61:7C:FF
attr Beaucarnea event-on-change-reading moisture,temperature
attr Beaucarnea interval 1800
attr Beaucarnea loxone true
attr Beaucarnea model flowerSens
attr Beaucarnea room XiaomiBTLESens
attr Beaucarnea verbose 3
# Temperature and Humidity Sensors
define TempBath XiaomiBTLESens 4C:65:A8:D2:64:7E
attr TempBath event-on-change-reading humidity,temperature
attr TempBath interval 622
attr TempBath loxone true
attr TempBath model thermoHygroSens
attr TempBath room XiaomiBTLESens
attr TempBath verbose 3
define TempRoomPW XiaomiBTLESens 4C:65:A8:D2:2C:0C
attr TempRoomPW event-on-change-reading humidity,temperature
attr TempRoomPW interval 1022
attr TempRoomPW loxone true
attr TempRoomPW model thermoHygroSens
attr TempRoomPW room XiaomiBTLESens
attr TempRoomPW verbose 3
define TempOffice XiaomiBTLESens 4C:65:A8:D8:E9:CF
attr TempOffice event-on-change-reading humidity,temperature
attr TempOffice interval 822
attr TempOffice loxone true
attr TempOffice model thermoHygroSens
attr TempOffice room XiaomiBTLESens
attr TempOffice verbose 3
define TempDG XiaomiBTLESens 4C:65:A8:DA:82:9C
attr TempDG event-on-change-reading humidity,temperature
attr TempDG interval 520
attr TempDG loxone true
attr TempDG model thermoHygroSens
attr TempDG room XiaomiBTLESens
attr TempDG verbose 3
define TempBedroom XiaomiBTLESens 4C:65:A8:D6:77:51
attr TempBedroom event-on-change-reading humidity,temperature
attr TempBedroom interval 850
attr TempBedroom loxone true
attr TempBedroom model thermoHygroSens
attr TempBedroom room XiaomiBTLESens
attr TempBedroom verbose 3
define TempGuestRoom XiaomiBTLESens 4C:65:A8:DA:A1:86
attr TempGuestRoom event-on-change-reading humidity,temperature
attr TempGuestRoom interval 955
attr TempGuestRoom loxone true
attr TempGuestRoom model thermoHygroSens
attr TempGuestRoom room XiaomiBTLESens
attr TempGuestRoom verbose 3

CoolTux

Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net