Skip to content
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

Lost the ability to read temperature #27

Open
jul9000 opened this issue Jan 5, 2017 · 12 comments
Open

Lost the ability to read temperature #27

jul9000 opened this issue Jan 5, 2017 · 12 comments

Comments

@jul9000
Copy link

jul9000 commented Jan 5, 2017

Hi,

I was successfully using HomeBridge with both yeelight and aqara plugins. I had no issues at all until today, when I've decided to change the location of my Xiaomi Temperature and Humidity Sensor. I also wanted to clear the temperature history within the Xiaomi Home app, so I decided to remove the device there. After doing this, I have paired it again. Unfortunately in the iOS Home app the sensor doesn't show the temperature anymore! The weird thing is that the humidity is still there, but the temperature "box" says "No answer".

I have already recreated the whole homebridge setup:

  1. removed all the files in /accessories
  2. removed all the files in /persist
  3. changed the name of the bridge in config.json
    The sensor showed up, shows humidity without problems, but not the temperature.

Another weird thing, is that the Xiaomi Home app shows both the humidity and temperature just fine (so the sensor itself isn't damaged).

What's wrong? Can you help me?

@snOOrz
Copy link
Owner

snOOrz commented Jan 6, 2017 via email

@jul9000
Copy link
Author

jul9000 commented Jan 6, 2017

I've already tried that multiple times, unfortunately without success:

  • tried to remove only the gateway,
  • tried to remove the entire home,
  • tried to reboot the computer hosting homebridge
  • tired to reboot my iphone

What else can I try? Is there a way to access some kind of logs? I've tried to run "homebridge -D", but nothing really happens...

@tru2dagame
Copy link

I got two Temperature and Humidity Sensor. Always got issue with one temperature information. And the other one works well.

@jul9000
Copy link
Author

jul9000 commented Jan 6, 2017

Worst thing is that I had it working just fine, but suddenly it stopped working.

I've also tried to unpair and pair again the sensor with the gateway, using the Xiaomi Home app. The readings shows up just fine there, only the Apple Home app can't get the temperature. I have to say, it's frustrating ;)

It looks like homebridge is able to connect, but doesn't get the correct reading:

  • when homebridge is running the sensor status says: "no response"
  • but when homebridge isn't running the sensor status says: "unavailable"

@snOOrz
Copy link
Owner

snOOrz commented Jan 6, 2017 via email

@jul9000
Copy link
Author

jul9000 commented Jan 6, 2017

Is it possible that negative readings causes this issue? It's quite cold right now in Poland (-12C). I've seen some reports of similar problems in other homebridge plugins.

EDIT: nope, moved the sensor inside, still the same :(

@marcotini
Copy link

You are not alone, also my temperature sensor doesn't working... just the humidity.

@jul9000
Copy link
Author

jul9000 commented Jan 8, 2017

Yep, you can't rely on them too much. Mine was suddenly showing readings yesterday for a couple of hours, then disappeared and reappeared today... I'm wondering what's causing this? Isn't there any way to debug?

Thankfully, communication between the gateway and the Xiaomi app works fine, so all the automation can be handled there :)

@tru2dagame
Copy link

tru2dagame commented Jan 8, 2017 via email

@marcotini
Copy link

Even to me now it's magically work (the only thing I did is unplug and replug the gateway).

@marcotini
Copy link

I found the solution: you need to deselect the option of status (so you don't see the temperature in homepage but just in the right room where the sensor is place).

@jul9000
Copy link
Author

jul9000 commented Jan 18, 2017

Unfortunately, I cannot confirm this solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants