legrego / homeassistant-combustion

Integrate Combustion thermometers with Home Assistant

🔥 Combustion BLE Integration

Integrate Combustion predictive probes into Home Assistant.

This integration will set up the following platforms.

Platform	Description
binary_sensor	Show battery status from probes on your Meatnet.
sensor	Show temperature data from probes on your Meatnet.

Installation

1. Using the tool of choice open the directory (folder) for your HA configuration (where you find configuration.yaml).
2. If you do not have a custom_components directory (folder) there, you need to create it.
3. In the custom_components directory (folder) create a new folder called combustion.
4. Download all the files from the custom_components/combustion/ directory (folder) in this repository.
5. Place the files you downloaded in the new directory (folder) you created.
6. Restart Home Assistant
7. Ensure you have a Combustion device turned on, and within bluetooth range of Home Assistant .
8. In the HA UI go to "Configuration" -> "Integrations" to see your discovered Combustion device.

Configuration

There is currently no configuration required for this integration. Once the integration discovers your Combustion device(s), it will prompt you to add them on the Integrations page.

Supported devices

This integration supports reading temperature and battery data from Combustion's Predictive Thermometer.

This integration can read data from a probe directly, or via a Meatnet repeater such as the Range-Extending Booster or Range-Extending Display.

This integration will not display information about the repeater itself, only the probes connected to it.

Contributions are welcome!

If you want to contribute to this please read the Contribution guidelines

Credits

Combustion, Inc. for their wonderful documentation and code samples.

---

homeassistant-combustion's Issues

Sensor values retain last value before combustion inc devices go offline

System Health details

System Information

version	core-2024.2.2
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.1
os_name	Linux
os_version	6.1.74-haos
arch	x86_64
timezone	Australia/Sydney
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	5000
Installed Version	1.34.0
Stage	running
Available Repositories	1408
Downloaded Repositories	21
HACS Data	ok

Home Assistant Cloud

logged_in	true
subscription_expiration	July 17, 2024 at 10:00 AM
relayer_connected	true
relayer_region	ap-southeast-1
remote_enabled	false
remote_connected	false
alexa_enabled	true
google_enabled	true
remote_server	ap-southeast-1-0.ui.nabu.casa
certificate_status	ready
instance_id	e1feeba07ad74976b9bb4cd4293d2541
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 11.5
update_channel	stable
supervisor_version	supervisor-2024.02.0
agent_version	1.6.0
docker_version	24.0.7
disk_total	30.8 GB
disk_used	11.4 GB
healthy	true
supported	true
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Studio Code Server (5.15.0), Advanced SSH & Web Terminal (17.1.0), Mosquitto broker (6.4.0), Node-RED (17.0.7), openWakeWord (1.8.2), ESPHome (2023.12.9), Samba share (12.3.0), eufy-security-ws (1.7.1)

Dashboards

dashboards	5
resources	18
views	6
mode	storage

Recorder

oldest_recorder_run	February 18, 2024 at 10:50 AM
current_recorder_run	February 19, 2024 at 8:26 PM
estimated_db_size	208.75 MiB
database_engine	sqlite
database_version	3.44.2

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

Cards in Home assistant are still showing the last read values, rather than an indication that the devices are offline

Reproduction steps

1.Create entity card
2. add Temps
3.Connect devices, let it do whatever you need with them
4 let the combustion devices turn off
5 values remain

Debug logs

.

Diagnostics dump

No response

Track battery state

Track the battery state of each connected probe. Probes report OK/Low status, so the best we can do is a binary sensor.

Add combustion brand images

Add brand images for your integration to https://github.com/home-assistant/brands

Disable individual temperature sensors by default

We create sensors for each of the 8 thermistors in each probe, in addition to the 3 virtual sensors (Core, Surface, Ambient).

This creates a lot of visual noise. We should disable the 8 individual thermistor sensors by default, leaving only the 3 virtual sensors.

Don't use advertised address in device creation.

Only register devices when we have a valid serial number in the payload

Add to HACS

Add this component to the default HACS repository for easier installation.

Add basic test suite

Setup basic test suite for discovery config flow.

not detecting probe on raspberry pi

Hello,
I Installed your addon per the directions, and the integration shows up on my list, but no devices are being detected. I'm running HASSOS on a Raspberry Pi 4.

Extract BLE communications into dedicated package.

BLE comms should not be included in this repository, but should instead be a standalone package that this component can leverage.