asheliahut / ha-bedjet

BedJet Home Assistant Integration

Home Assistant BedJet

This project contains a climate entity that provides control of a BedJet device.

Installation (HACS) - Recommended

0. Have HACS installed, this will allow you to easily update
1. Add https://github.com/asheliahut/ha-bedjet as a custom repository as Type: Integration
2. Click install under "HA-BedJet", restart your instance.

Installation (Manual)

1. Download this repository as a ZIP (green button, top right) and unzip the archive
2. Copy /custom_components/bedjet to your <config_dir>/custom_components/ directory
   • You will need to create the custom_components folder if it does not exist
   • On Hassio the final location will be /config/custom_components/bedjet
   • On Hassbian the final location will be /home/homeassistant/.homeassistant/custom_components/bedjet

Configuration

Follow the configuration flow in devices & services

Configuration variables:

• mac (Optional): Bluetooth MAC address of your BedJet, if you want to specify. If not specified, this integration will search for all BedJets within range.

Screenshot

ha-bedjet's Issues

Issue with multiple BedJets

Hello,

First of all, thank you very much for this! I have been struggling with an ESPHome project trying to get mine and my wife's BedJets integrated into Home Assistant. A couple of questions: Does this integration support multiple BedJets? If I just leave the configure option blank when I add the integration from "Devices & Services" then it discovers both of my BedJet MAC addresses. I thought everything was working fine but one of the two devices is always offline. It seems random on a HA restart cycle which BedJet will (maybe connect first) and show online while the other is offline no matter what I do until a different reboot cycle will switch which is online and which is offline.

Second question is what format (XX:XX:XX:XX:XX or XX-XX-XX-XX-XX-XX or something else) should the BLE MAC address be in when trying to input a specific MAC in the configuration options?

Thank you very much,
Adam

Always Unavailable

Just got my bedjet and excited when I saw this. Got everything setup, but when adding the bedjet, it's found but the device goes from unavailable to unknown. Getting this in the logs, any insight as to what I may be missing?

Logger: custom_components.bedjet.climate
Source: custom_components/bedjet/climate.py:294
integration: BedJet (documentation)
First occurred: March 8, 2024 at 6:02:09 PM (70 occurrences)
Last logged: 4:06:04 AM

Error "[org.bluez.Error.Failed] br-connection-canceled". Retrying in 10 seconds.
Error "". Retrying in 20 seconds.
Error "No backend with an available connection slot that can reach address B0:B2:1C:C4:F6:FA was found". Retrying in 10 seconds.
Error "No backend with an available connection slot that can reach address B0:B2:1C:C4:F6:FA was found". Retrying in 20 seconds.
Error "No backend with an available connection slot that can reach address B0:B2:1C:C4:F6:FA was found". Retrying in 30 seconds.

Biorhythm

Would it be possible to support Biorhythm modes under the "Preset" menu?

Deprecation warnings for HA Core 2025.1

After updating HA core to 2024.1.1, new messages occur in the server's log warning of features that will be deprecated in HA Core 2025.1. No issues with the custom component at this time; I'm just opening this issue for your awareness. Thank you for your support!

Logger: homeassistant.helpers.entity
Source: helpers/entity.py:1520

Entity None (<class 'custom_components.bedjet.climate.BedjetDeviceEntity'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <ClimateEntityFeature.TARGET_TEMPERATURE|FAN_MODE|PRESET_MODE: 25>, please report it to the author of the 'bedjet' custom integration and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
Entity None (<class 'custom_components.hacs.update.HacsRepositoryUpdateEntity'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <UpdateEntityFeature.INSTALL|PROGRESS|RELEASE_NOTES: 21>, please create a bug report at https://github.com/hacs/integration/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation

Logger: homeassistant.components.climate.const
Source: helpers/deprecation.py:205
Integration: Climate (documentation, issues)

SUPPORT_FAN_MODE was used from bedjet, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.FAN_MODE instead, please report it to the author of the 'bedjet' custom integration
HVAC_MODE_OFF was used from bedjet, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.OFF instead, please report it to the author of the 'bedjet' custom integration
HVAC_MODE_HEAT was used from bedjet, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT instead, please report it to the author of the 'bedjet' custom integration
HVAC_MODE_COOL was used from bedjet, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.COOL instead, please report it to the author of the 'bedjet' custom integration
HVAC_MODE_DRY was used from bedjet, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.DRY instead, please report it to the author of the 'bedjet' custom integration

Logger: homeassistant.const
Source: helpers/deprecation.py:205

TEMP_FAHRENHEIT was used from bedjet, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.FAHRENHEIT instead, please report it to the author of the 'bedjet' custom integration

Fan values don't work well with Homekit

Hi there -- thanks for the integration!

This works great overall. However, Homekit's fan control seems to trigger the min/max cap, so rather than a full range of 0-100, you can only set the fan speed in pre-defined steps (it seems like about 4 steps). This is kind of confusing, as you can drag the fan slider and Homekit thinks the value is set, but the Bedjet doesn't actually respond. If you close/reopen the Home app the slider will update with what the Bedjet's actually set to.

Does the plugin just automatically try to cap the value to the nearest pre-defined step?