-
-
Notifications
You must be signed in to change notification settings - Fork 29.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Miflora not working (not getting sensor data) #10790
Comments
Works fine for me on 2017-11-25 16:58:06 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.miflora
2017-11-25 16:58:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.mi_flora_moisture, old_state=None, new_state=<state sensor.mi_flora_moisture=unknown; unit_of_measurement=%, friendly_name=Mi Flora Moisture @ 2017-11-25T16:58:06.670874+01:00>>
2017-11-25 16:58:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.mi_flora_light_intensity, old_state=None, new_state=<state sensor.mi_flora_light_intensity=unknown; unit_of_measurement=lux, friendly_name=Mi Flora Light intensity @ 2017-11-25T16:58:06.671482+01:00>> Can you check if your sensor is detected? $ bluetoothctl
[NEW] Controller A3:A3:A0:B4:B4:B4 localhost.localdomain [default]
[NEW] Device C4:C5:E4:32:45:A4 Flower mate
Agent registered
[CHG] Device C4:C5:E4:32:45:A4 RSSI: -52 |
Yeap
(I have tired moving it closer no luck) |
Have you tried to disable the Bluetooth LE tracker? Also, keep in mind that it can take a while till the Mi Flora sensors are populated. |
I have no differnce and it been up for days now. Is there a way of getting more debug info. All I get is Updating miflora sensor took longer than the scheduled update interval 0:00:30 |
I get the same error message since 0.58 but if I look at my influxdb values still come in rather frequently. |
I have seen this problem in recent updates. With hassio afer a restart of bluetooth container I get data for a while until it gets stuck again Later edit: Also found the below stacktrace in logs after a period of not working
|
Miflora python modules just been released to 0.2 which may help fix this due to the backend change. |
So upgrading to 0.2 worked. I had to alter miflora.py with simple modifications and I had to hard code gatttool location. I don't have hass installed from git so I can't set up a pull request. Also dealing with a pull request is prob more work than just fixing the code. :) I wait for a proper fix but this should fix it :) |
Any chance the fix would go into next HA release? |
I just added a pull request to get the new version number in. @tactmaster edit
|
Home Assistant release (
hass --version
):0.58.0
Python release (
python3 --version
):Python 3.5.3
Component/platform:
RPi 2 Stretch - venv
with CSR Bluetooth 4.0 dongle
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Description of problem:
Does read miflora device at all.
Updating miflora sensor took longer than the scheduled update interval 0:00:30
12:16 helpers/entity_component.py (WARNING)
using miflora https://github.com/open-homeautomation/miflora/
works.
I have tired changing the timeout however I am not sure that behaves correctly.
Expected:
returns values for the sensor
Problem-relevant
configuration.yaml
entries and steps to reproduce:Additional info:
this maybe a repeat of #3458 however I not sure gatttool seems to working fine for me
The text was updated successfully, but these errors were encountered: