BME680 sensor will not be detected on 0.81.5 anymore works with 0.81.2

[albertstuder]

**Home Assistant release with the issue:0.81.5

**Last working Home Assistant release (if known):0.81.2

**Operating environment (Hass.io/Docker/Windows/etc.):Hass.io

**Component/platform:https://www.home-assistant.io/components/sensor.bme680/

**Description of problem:Sensor BME680 not detected at 0x77 Works with 0.81.2

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: 0
  longitude: 0
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 0
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: UTC
  # Customization file
  customize: !include customize.yaml

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123
http:
  # Secrets are defined in the file secrets.yaml
  api_password: xxxxx
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url: example.duckdns.org:8123
# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
# updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Enables a map showing the location of tracked devices
map:

# Track the sun
sun:

# Sensors
sensor:
  # Weather prediction
  - platform: yr

# Sensor BME680
sensor 1:
  - platform: bme680

# Text to speech
tts:
  - platform: google

# Cloud
cloud:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

Traceback (if applicable):

**Additional information:

[timothybrown]

I just re-enabled the HA BME680 module as a test and it’s working fine for me at 0x77 on 0.81.4. (As an aside, I’ve switched to using a custom Python script that uses the Bosch BSEC library to talk to the sensor and then submits the data to an MQTT broker which HA picks up. I found the underlying library the HA module uses to be very basic and the temperature and humidity values have huge offsets. The Bosch library provides much more realistic IAQ, temperature and humidity values. I’ll be uploading it to GitHub soon.)

Edit 1: I’ll check it on 0.81.5 as well, though I don’t see what could have broken it between releases.

Have you tried running i2cdetect -y 1 from the command line and verifying the sensor actually shows up?

If you run lsmod do you see the I2C module loaded?

Edit 2: It’s working fine for me on 0.81.5 as well. Edit 3: 0.81.6 is working too.

[albertstuder]

I have installed hassos_rpi3-64-1.12.img.gz on a new SD card and go access with ssh to core-ssh: what would be the command to execute the i2cdetect -y 1 in the core-ssh: terminal. I did not update the working 0.81.2 card to keep it running. The new setup has 0.8.15 which is not working and no update available to 0.81.6 available.

[timothybrown]

Sorry, I must have misread your initial post and thought you were on Hassbian. Let me throw Hass.io on a spare Pi and see if I can write up some instructions for installing i2ctools on it. It’s a pretty critical package for debugging I2C issues.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍