MQTT2 und Xiaomi Flower Care

[kalleknx]

Hi an alle,

ich nutze die Xiaomi Flower Care Bluetooth LE Sensoren, um die Feuchtigkeit in meinen Blumentöpfen auszulesen.
Mittels https://github.com/ThomDietrich/miflora-mqtt-daemon werden die Informationen an meinen MQTT Server weitergegeben.
Leider wird das Device nicht automatisch in FHEM angelegt (bei meinen shelly devices hat ge geklappt).

Code Auswählen Erweitern

pi@fhem:~ $ mosquitto_sub -h 127.0.0.1 -u xxx -P xxx -t 'miflora/myplant00'
{"light": 1711, "temperature": 13.8, "moisture": 14, "conductivity": 105, "battery": 100}


Das Attribut im MQTT2 Server Device steht auf complex. Ich sehe dort lediglich ein RETAIN reading:

Code Auswählen Erweitern

{"miflora/$announce":"{\u0022myplant00\u0022: {\u0022name_pretty\u0022: \u0022myplant00\u0022, \u0022mac\u0022: \u0022C4:7C:8D:66:45:8A\u0022, \u0022refresh\u0022: 300, \u0022location_clean\u0022: \u0022\u0022, \u0022location_pretty\u0022: \u0022\u0022, \u0022firmware\u0022: \u00222.7.0\u0022, \u0022topic\u0022: \u0022miflora/myplant00\u0022}}","miflora/_announce":"{}"}

Was übersehe ich?
Danke für Eure Hilfe

[rudolfkoenig]

Dass wir zum Helfen mehr Details brauchen.

[kalleknx]

Natürlich 

Code Auswählen Erweitern

2020.04.10 11:47:24 4: Connection accepted from MQTT2_FHEM_Server_192.168.0.26_36117
2020.04.10 11:47:24 5: in:  CONNECT: (16)7(0)(4)MQTT(4)(230)(0)<(0)(0)(0)(17)miflora/$announce(0)(2){}(0)(4)fhem(0)(12)fhemmqttfhem
2020.04.10 11:47:24 4:   MQTT2_FHEM_Server_192.168.0.26_36117  CONNECT V:4 keepAlive:60 LWT:miflora/$announce:{} usr:fhem
2020.04.10 11:47:28 4:   MQTT2_FHEM_Server_192.168.0.183_54678 shellybulb-7918E5 PUBLISH shellies/shellybulb-7918E5/color/0:off
2020.04.10 11:47:28 5: MQTT2_FHEM_Server: dispatch autocreate=complex\000shellybulb_7918E5\000shellies/shellybulb-7918E5/color/0\000off
2020.04.10 11:47:28 4:   MQTT2_FHEM_Server_192.168.0.183_54678 shellybulb-7918E5 PUBLISH shellies/shellybulb-7918E5/color/0/status:{"ison":false,"mode":"white","red":255,"green":31,"blue":31,"white":0,"gain":100,"temp":6465,"brightness":100,"effect":0}
2020.04.10 11:47:28 5: MQTT2_FHEM_Server: dispatch autocreate=complex\000shellybulb_7918E5\000shellies/shellybulb-7918E5/color/0/status\000{"ison":false,"mode":"white","red":255,"green":31,"blue":31,"white":0,"gain":100,"temp":6465,"brightness":100,"effect":0}
2020.04.10 11:47:30 4:   MQTT2_FHEM_Server_192.168.0.26_36117  PUBLISH miflora/$announce:{"myplant00": {"name_pretty": "myplant00", "mac": "C4:7C:8D:66:45:8A", "refresh": 300, "location_clean": "", "location_pretty": "", "firmware": "2.7.0", "topic": "miflora/myplant00"}}
2020.04.10 11:47:30 5: MQTT2_FHEM_Server: dispatch autocreate=complex\000\000miflora/$announce\000{"myplant00": {"name_pretty": "myplant00", "mac": "C4:7C:8D:66:45:8A", "refresh": 300, "location_clean": "", "location_pretty": "", "firmware": "2.7.0", "topic": "miflora/myplant00"}}
2020.04.10 11:47:30 1: reload: Error:Modul 00_MQTT deactivated:
Attempt to reload Net/MQTT/Message.pm aborted.
Compilation failed in require at ./FHEM/00_MQTT.pm line 80.
BEGIN failed--compilation aborted at ./FHEM/00_MQTT.pm line 80.
2020.04.10 11:47:30 0: Attempt to reload Net/MQTT/Message.pm aborted.
Compilation failed in require at ./FHEM/00_MQTT.pm line 80.
BEGIN failed--compilation aborted at ./FHEM/00_MQTT.pm line 80.
2020.04.10 11:47:30 1: reload: Error:Modul 10_MQTT_GENERIC_BRIDGE deactivated:
Can't continue after import errors at ./FHEM/10_MQTT_GENERIC_BRIDGE.pm line 456.
BEGIN failed--compilation aborted at ./FHEM/10_MQTT_GENERIC_BRIDGE.pm line 495.
2020.04.10 11:47:30 0: Can't continue after import errors at ./FHEM/10_MQTT_GENERIC_BRIDGE.pm line 456.
BEGIN failed--compilation aborted at ./FHEM/10_MQTT_GENERIC_BRIDGE.pm line 495.
2020.04.10 11:47:30 0: ERROR: Cannot autoload MQTT_GENERIC_BRIDGE
Übereinstimmungen in Binärdatei (Standardeingabe)