joshmcarthur
commented
5 years ago I'm running into the same problem.
The Dockerfile I am using:
FROM resin/rpi-raspbian
RUN apt-get update &&\
apt-get install -y git python3 python3-pip bluetooth bluez &&\
git clone https://github.com/ThomDietrich/miflora-mqtt-daemon.git /opt/miflora-mqtt-daemon &&\
mkdir /config
WORKDIR /opt/miflora-mqtt-daemon
RUN pip3 install -r requirements.txt
CMD [ "python3", "./miflora-mqtt-daemon.py", "--config_dir", "/config" ]My config.ini:
# Configuration file for Xiaomi Mi Flora Plant Sensor MQTT Client/Daemon
# Source: https://github.com/ThomDietrich/miflora-mqtt-daemon
#
# Uncomment and adapt all settings as needed.
[General]
# The operation mode of the program. Determines wether retrieved sensor data is published via MQTT or stdout/file.
# Currently supported:
#
# mqtt-json - Publish to an MQTT broker in a proprietary json format (Default)
# mqtt-homie - Publish to an MQTT broker following the Homie MQTT convention
# (https://github.com/marvinroger/homie)
# mqtt-smarthome - Publish to an MQTT broker following the mqtt-smarthome proposal
# (https://github.com/mqtt-smarthome/mqtt-smarthome)
# homeassistant-mqtt - Publish to an MQTT broker following the HomeAssistant discovery format
# (https://www.home-assistant.io/docs/mqtt/discovery/)
# thingsboard-json - Publish to the ThingsBoard MQTT broker
# (https://thingsboard.io)
# wirenboard-mqtt - Publish to the Wiren Board MQTT broker
# (https://wirenboard.com)
# json - Print to stdout as json encoded strings
#
#reporting_method = mqtt-json
reporting_method = json
# The bluetooth adapter that should be used to connect to Mi Flora devices (Default: hci0)
#adapter = hci0
[Daemon]
# Enable or Disable an endless execution loop (Default: true)
#enabled = true
# The period between two measurements in seconds (Default: 300)
#period = 300
[MQTT]
# The hostname or IP address of the MQTT broker to connect to (Default: localhost)
#hostname = localhost
# The TCP port the MQTT broker is listening on (Default: 1883)
#port = 1883
# Maximum period in seconds between ping messages to the broker. (Default: 60)
#keepalive = 60
# The MQTT base topic to publish all Mi Flora sensor data topics under.
# Default depends on the configured reporting_method
#base_topic = miflora # Default for: mqtt-json, mqtt-smarthome
#base_topic = homie # Default for: mqtt-homie
#base_topic = homeassistant # Default for: homeassistant-mqtt
#base_topic = v1/devices/me/telemetry # Default for: thingsboard-json
#base_topic = # Default for: wirenboard-mqtt
# Homie specific: The device ID for this daemon instance (Default: miflora-mqtt-daemon)
#homie_device_id = miflora-mqtt-daemon
# The MQTT broker authentification credentials (Default: no authentication)
#username = user
#password = pwd123
# Enable TLS/SSL on the connection
#tls = false
# Path to CA Certificate file to verify host
#tls_ca_cert =
# Path to TLS client auth key file
#tls_keyfile =
# Path to TLS client auth certificate file
#tls_certfile =
[Sensors]
# Add your Mi Flora sensors here. Each sensor consists of a name and a Ethernet MAC address.
# Additional location information can be added to the name, delimited by an '@'.
# Scan for sensors from the command line with:
# $ sudo hcitool lescan
#
# Examples:
#
#Schefflera@Living = C4:7C:8D:11:22:33
#JapaneseBonsai = C4:7C:8D:44:55:66
#Petunia@Balcony = C4:7C:8D:77:88:99
Veggie@Backgarden = C4:7C:8D:xx:xx:xx(i.e. my modifications are to enable the STDOUT JSON logging while I verify it's working OK, and to add my own Flora MAC)
Output:
docker run -v $PWD:/config --privileged --rm -it --net=host miflora-gateway
Xiaomi Mi Flora Plant Sensor MQTT Client/Daemon
Source: https://github.com/ThomDietrich/miflora-mqtt-daemon
Adding sensor to device list and testing connection ...
Name: "Veggie"
[2019-04-06 03:06:32] Initial connection to Mi Flora sensor "Veggie" (C4:7C:8D:xx:xx:xx) failed.
[2019-04-06 03:06:32] Retrieving data from sensor "Veggie" ...
[2019-04-06 03:07:15] Retrying ...
[2019-04-06 03:07:59] Failed to retrieve data from Mi Flora sensor "Veggie" (C4:7C:8D:xx:xx:xx), success rate: 0%
[2019-04-06 03:07:59] Sleeping (300 seconds) ...@septeven, do you still have the pi zero available to you? Is there a way you could find out what versions of the dependencies you have available? I'm wondering if a dependency has been updated and this is what might be causing this issue.
I have only connected to my Mi Flora once since it arrived yesterday using a Node.js script that was able to connect and read the sensor values correctly.
septeven
aymeric106
Markkuuss
ManuelAbril
cjoha
coccobill1
absolutelyNothing9
analogue
brononius
phenix1990
Hi, I had miflora-mqtt-daemon correctly setup on a pi zero - everything was working perfectly well. Today, I decided to replace my pi zero with a raspberry pi 3b+ so I installed everything again on the new pi, including miflora-mqtt-daemon.
I got the same exact configuration than on the pizero but I can't get my miflora sensor detected though - I have the feeling like if it still binded to the pizero and can't be binded again with another setup ? Any ideas ? I've been completely stucked for hours....
Here is the error showing up when launching python3 /opt/miflora-mqtt-daemon/miflora-mqtt-daemon.py (FYI config.ini is correctly setup, mac-adresses are correctly defined, again - same configuration than the working pizero)
Initial connection to Mi Flora sensor "miflora_plant" (xx:xx:xx:xx:xx:xx) failed.