Git Product home page Git Product logo

hass-yeelightbt's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

hass-yeelightbt's Issues

Yeelight doesn't change color in automations

Light

Yeelight Bedside

Home-assistant installation type

Home Assistant Operating System (HAOS)

Home-assistant version

2022.8.1

Describe the issue

In automations like this:

    - service: light.turn_on
      entity_id:
        - light.bedside_letto
      data:
        brightness: 255
        rgb_color:
          - '{{ (range(0, 255)|random) }}'
          - '{{ (range(0, 255)|random) }}'
          - '{{ (range(0, 255)|random) }}' 

The bedside lights will turn on, but always with the same white colour, not following the random rgb color as other lights do.

Debugging procedure followed:

  • 1- Smartphone will not connect with lamp
  • 2- The Yeelight_bt integration has been removed from HA.
  • 3- HA has access to the bluetooth adapter (followed the installation steps if not on HAOS).
  • 4- No other bluetooth integration are using something else than bleak library for bluetooth. If unsure, disable them.
  • 5- The logging has been changed in HA to allow debugging of this component and bleak.
  • 6- The light has been fully reset so that it is not paired with any device.
  • 7- Restart HA
  • 8- Reinstall the yeelight_bt integration and find the light through a scan.
  • 9- Pairing the lamp succeeded

Any additional comments

No response

Logs from the issue

No response

How many lamps can handle at a time?

I have 3 bedside BT lamps, the scan method is working, i can see all of them, but once they are installed in Home assistant, only 1 is working, the other 2 are not active ¿?

Lamp does not pair

I have HA 2022.8.4 over HAOS 8.4 (rpi3-64 bit)

BT is configured on default interface hci0.

On a resetted lamp cannot connect: discover does not find anything and via mac address the lamp does not start blinking.

How can I solve this issue?

[Bug] light.turn_off service randomly not working

Light

Yeelight Bedside

Yeelight Bt version

Latest

Home-assistant installation type

Home Assistant Operating System (HAOS)

Home-assistant version

2022.9.2

Home-assistant bluetooth integration (2022.8+)

Yes

Describe the issue

Randomly the light.turn_off service doesn't work in scripts and automations. Nothing in the log and checking the automation tracer it says all is working, but the light remains in 'on' state

Debugging procedure followed:

  • 1- Ensure smartphone will not connect with lamp
  • 2- The Yeelight_bt integration has been removed from HA.
  • 3- HA has access to the bluetooth adapter (followed the installation steps if not on HAOS).
  • 4- No other bluetooth integration are using something else than bleak library for bluetooth. If unsure, disable them.
  • 5- The logging has been changed in HA to allow debugging of this component and bleak.
  • 6- The light has been fully reset so that it is not paired with any device.
  • 7- Restart HA
  • 8- Reinstall the yeelight_bt integration and find the light through a scan.
  • 9- Pairing the lamp succeeded

Any additional comments

No response

Logs from the issue

No response

[Bug] failure after Home Assistant Update 2024.1

Light

Yeelight Bedside

Yeelight Bt version

v1.3.0

Home-assistant installation type

Home Assistant Container (docker)

Home-assistant version

2024.1

Home-assistant bluetooth integration (2022.8+)

Yes

Describe the issue

When adding the integration it shows:
{"message":"Invalid handler specified"}

Debugging procedure followed:

  • 1- Ensure smartphone will not connect with lamp
  • 2- The Yeelight_bt integration has been removed from HA.
  • 3- HA has access to the bluetooth adapter (followed the installation steps if not on HAOS).
  • 4- No other bluetooth integration are using something else than bleak library for bluetooth. If unsure, disable them.
  • 5- The logging has been changed in HA to allow debugging of this component and bleak.
  • 6- The light has been fully reset so that it is not paired with any device.
  • 7- Restart HA
  • 8- Reinstall the yeelight_bt integration and find the light through a scan.
  • 9- Pairing the lamp succeeded

Any additional comments

No response

Logs from the issue

Logger: homeassistant.config_entries
Source: config_entries.py:2087
First occurred: 23:36:20 (2 occurrences)
Last logged: 23:46:56

Error occurred loading flow for integration yeelight_bt: cannot import name 'BluetoothScanningMode' from 'homeassistant.components.bluetooth.models' (/usr/src/homeassistant/homeassistant/components/bluetooth/models.py)

[Bug] Deprecated supported features values are used

Light

Yeelight Bedside

Yeelight Bt version

v1.4.0

Home-assistant installation type

Home Assistant Operating System (HAOS)

Home-assistant version

2024.1.6

Home-assistant bluetooth integration (2022.8+)

Yes

Describe the issue

Hey there! 👋

I am reporting that there is a new deprecation warning in the logs:

Entity light.nachttischlampe (<class 'custom_components.yeelight_bt.light.YeelightBT'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 19> and color modes, please create a bug report at https://github.com/hcoohb/hass-yeelightbt/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation

Thank you for your attention, and thank you very much for maintaining this project! ❤️

Cheers,
Felix

Debugging procedure followed:

  • 1- Ensure smartphone will not connect with lamp
  • 2- The Yeelight_bt integration has been removed from HA.
  • 3- HA has access to the bluetooth adapter (followed the installation steps if not on HAOS).
  • 4- No other bluetooth integration are using something else than bleak library for bluetooth. If unsure, disable them.
  • 5- The logging has been changed in HA to allow debugging of this component and bleak.
  • 6- The light has been fully reset so that it is not paired with any device.
  • 7- Restart HA
  • 8- Reinstall the yeelight_bt integration and find the light through a scan.
  • 9- Pairing the lamp succeeded

Any additional comments

No response

Logs from the issue

No response

Yeelight candela

Hi and thanks for your work on this component.

I was able to pair HA with my Yeelight Candela (F8:24:41:C0:3B:7E yeelight_ms).

On / Off works perfectly, and brightness can be set, but the slider always reverts to a brightness of zero. I assume the code to read back the brightness does not work with these type of lamps.

If possible, you could also disable the color temperature and hue pickers, because they are not needed or used on such a lamp.

I'm happy to help with any information you might need!

Possiblity rto use with an ESP32?

Hi,
I use some Esp32 with Home assistant in order to find my mi band.
It will be possible somehow to use this component with esphome ?

Does not pair Candela with esphome bluetooth proy

Light

Yeelight Candela

Yeelight Bt version

don't know very old candela 5 to 6 years

Home-assistant installation type

Home Assistant Container (docker)

Home-assistant version

2023.5.4

Home-assistant bluetooth integration (2022.8+)

Yes

Describe the issue

The candela is found by scan and will be intigrated with 1 device and 1 entity, but can't be turned on by pressing the button.
Is there a new test release which should work ?
esphome blue toot proxy works fine with bluetooth xiaomi miio temperature devices. Also LED BLE works fine.

Debugging procedure followed:

  • 1- Ensure smartphone will not connect with lamp
  • 2- The Yeelight_bt integration has been removed from HA.
  • 3- HA has access to the bluetooth adapter (followed the installation steps if not on HAOS).
  • 4- No other bluetooth integration are using something else than bleak library for bluetooth. If unsure, disable them.
  • 5- The logging has been changed in HA to allow debugging of this component and bleak.
  • 6- The light has been fully reset so that it is not paired with any device.
  • 7- Restart HA
  • 8- Reinstall the yeelight_bt integration and find the light through a scan.
  • 9- Pairing the lamp succeeded

Any additional comments

No response

Logs from the issue

No response

How to find MAC address?

As in the subject, how to find MAC address of my yeelight bedside BT lamps?
I tried to find it inside yeelight app and xiaomi home app, but both do not show the MAC address....
I am running HASSIO 0.114.3 on a RPi 4.

Config flow error

Error occurred loading configuration flow for integration yeelight_bt: cannot import name 'Embedded' from 'construct' (/usr/local/lib/python3.9/site-packages/construct/__init__.py)

Add support for Home Assistant Operating System

Currently this custom component doesn't seem to be compatible with Home Assistant Operating System.
Adding the component and setting it up in the "integrations" menu works but connection to the actual bedside lamp fails.
HAOS uses buildroot, setting permissions as instructed in the ReadMe fails, "setcap" is not available on the host system.

Relevant log entries:

2020-09-14 00:22:18 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for yeelight_bt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-09-14 00:22:21 DEBUG (MainThread) [custom_components.yeelight_bt] async setup.
2020-09-14 00:22:21 DEBUG (MainThread) [custom_components.yeelight_bt]  List entries for domain:
2020-09-14 00:22:21 DEBUG (MainThread) [custom_components.yeelight_bt] [<homeassistant.config_entries.ConfigEntry object at 0x7f4be087fa40>]
2020-09-14 00:22:23 DEBUG (MainThread) [custom_components.yeelight_bt] async setup entry: {'entry_id': '6f68d7bcf5e311eaa0ab4fad0266453c', 'version': 1, 'domain': 'yeelight_bt', 'title': 'Schlafzimmer-Nachttischlampe', 'data': {'name': 'Schlafzimmer-Nachttischlampe', 'mac': 'F8:24:41:E5:CF:89'}, 'options': {}, 'system_options': {'disable_new_entities': False}, 'source': 'user', 'connection_class': 'local_poll', 'unique_id': 'f8:24:41:e5:cf:89'}
2020-09-14 00:22:25 DEBUG (MainThread) [custom_components.yeelight_bt.light] async_setup_entry:setting up the config entry Schlafzimmer-Nachttischlampe with data:{'name': 'Schlafzimmer-Nachttischlampe', 'mac': 'F8:24:41:E5:CF:89'}
2020-09-14 00:22:25 INFO (MainThread) [custom_components.yeelight_bt.light] Initializing Schlafzimmer-Nachttischlampe, F8:24:41:E5:CF:89
2020-09-14 00:22:25 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Creating Yeelight Lamp F8:24:41:E5:CF:89
2020-09-14 00:22:56 DEBUG (SyncWorker_20) [custom_components.yeelight_bt.light] Requesting an update of the lamp status
2020-09-14 00:22:56 DEBUG (SyncWorker_20) [custom_components.yeelight_bt.yeelightbt] Get_state
2020-09-14 00:23:37 WARNING (SyncWorker_20) [custom_components.yeelight_bt.yeelightbt] Could not connect to lamp: error<class 'bluepy.btle.BTLEDisconnectError'>(Failed to connect to peripheral F8:24:41:E5:CF:89, addr type: public), Retrying in 0.1 seconds...
2020-09-14 00:24:18 WARNING (SyncWorker_20) [custom_components.yeelight_bt.yeelightbt] Could not connect to lamp: error<class 'bluepy.btle.BTLEDisconnectError'>(Failed to connect to peripheral F8:24:41:E5:CF:89, addr type: public), Retrying in 0.1 seconds...
2020-09-14 00:24:59 ERROR (SyncWorker_20) [custom_components.yeelight_bt.yeelightbt] Could not connect to lamp: error<class 'bluepy.btle.BTLEDisconnectError'>(Failed to connect to peripheral F8:24:41:E5:CF:89, addr type: public)
2020-09-14 00:24:59 DEBUG (SyncWorker_20) [custom_components.yeelight_bt.yeelightbt] Writing  0x434402000000000000000000000000000000 on handle False
2020-09-14 00:24:59 WARNING (SyncWorker_20) [custom_components.yeelight_bt.yeelightbt] Could not write to lamp: error<class 'bluepy.btle.BTLEInternalError'>(Helper not started (did you call connect()?)), Retrying now...
2020-09-14 00:24:59 DEBUG (SyncWorker_20) [custom_components.yeelight_bt.light] Got state notification from the lamp
2020-09-14 00:25:40 WARNING (SyncWorker_20) [custom_components.yeelight_bt.yeelightbt] Could not connect to lamp: error<class 'bluepy.btle.BTLEDisconnectError'>(Failed to connect to peripheral F8:24:41:E5:CF:89, addr type: public), Retrying in 0.1 seconds...

Problem Status with Remote Home-Assistant

Hello,

Thank you very much for this component which allows me to use both yeelight_bt (XMCDT01YL) of my children with home assistant, however, I have a particular problem, my configuration is as follows:

  • Hassos 5.12 Master instance, core v2021.2.3
  • Hassos 5.12 Secondary instance, core v2021.2.3 with hass-yeelightbt component

I use Remote Home-Assistant which allows bluetooth to be deported to a secondary home assistant instance, my entities go back correctly but the state of my two yeelight_bt poses a problem on the master instance:

When I operate them from the master instance, the state changes from ON, the lamp lights up and immediately after the state goes back to OFF but the lamp stays on.

To turn it off I have to turn it ON again then OFF so that the lamp goes out.

From the secondary instance there is no this problem and everything works fine.

Is it the hass-yeelightbt component which is not fully compatible with the Remote Home-Assistant component?

I don't have an error in the logs and I correctly associated my yellight_bt.

thank you in advance for your help

manifest file on new release

I get this advertisement after upgrading to the latest release of HA

2021-03-08 11:21:48 WARNING (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'yeelight_bt'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'yeelight_bt'

[Bug] Constant Disconnect

Light

None

Yeelight Bt version

1.3.0

Home-assistant installation type

Home Assistant Operating System (HAOS)

Home-assistant version

2023.2

Home-assistant bluetooth integration (2022.8+)

Yes

Describe the issue

I will constantly get the following error

This error originated from a custom integration.

Logger: custom_components.yeelight_bt.yeelightbt
Source: custom_components/yeelight_bt/yeelightbt.py:309
Integration: Yeelight bluetooth (documentation, issues)
First occurred: 4:13:32 PM (1 occurrences)
Last logged: 4:13:32 PM

Send Cmd: BleakError: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Unlikely Error)

It will disconnect and then eventually HAOS will remove one my bluetooth Adapter. I have two Yeelight BLE lamps.

Debugging procedure followed:

  • 1- Ensure smartphone will not connect with lamp
  • 2- The Yeelight_bt integration has been removed from HA.
  • 3- HA has access to the bluetooth adapter (followed the installation steps if not on HAOS).
  • 4- No other bluetooth integration are using something else than bleak library for bluetooth. If unsure, disable them.
  • 5- The logging has been changed in HA to allow debugging of this component and bleak.
  • 6- The light has been fully reset so that it is not paired with any device.
  • 7- Restart HA
  • 8- Reinstall the yeelight_bt integration and find the light through a scan.
  • 9- Pairing the lamp succeeded

Any additional comments

No response

Logs from the issue

This error originated from a custom integration.

Logger: custom_components.yeelight_bt.yeelightbt
Source: custom_components/yeelight_bt/yeelightbt.py:309
Integration: Yeelight bluetooth (documentation, issues)
First occurred: 4:13:32 PM (1 occurrences)
Last logged: 4:13:32 PM

Send Cmd: BleakError: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Unlikely Error)

[Feature] Adding more available entities

Light

Yeelight Bedside

Yeelight Bt version

1.3.0

Home-assistant installation type

Home Assistant Operating System (HAOS)

Home-assistant version

2023.9

Home-assistant bluetooth integration (2022.8+)

Yes

Describe the issue

Not sure if this integration is still being supported, but I was hoping that more available entities would be made available for us. Thanks

Debugging procedure followed:

  • 1- Ensure smartphone will not connect with lamp
  • 2- The Yeelight_bt integration has been removed from HA.
  • 3- HA has access to the bluetooth adapter (followed the installation steps if not on HAOS).
  • 4- No other bluetooth integration are using something else than bleak library for bluetooth. If unsure, disable them.
  • 5- The logging has been changed in HA to allow debugging of this component and bleak.
  • 6- The light has been fully reset so that it is not paired with any device.
  • 7- Restart HA
  • 8- Reinstall the yeelight_bt integration and find the light through a scan.
  • 9- Pairing the lamp succeeded

Any additional comments

No response

Logs from the issue

No response

Will not work with 2022.7

Setup failed for custom integration yeelight_bt: Requirements for yeelight_bt not found: ['bluepy>=1.3.0'].

breaking changes

These integrations rely on the bluepy library, which no longer works in newer versions of Python. bluepy has seen its last update in December 2018 and hasn’t kept up with changes in the Python world.

It is not possible for us to mitigate this issue. If you are using one of these integration, these will no longer work.

If you like to help out to fix or upgrade one of these integrations, we would be grateful. We recommend migrating these integrations onto the Bleak libary instead.

Candela connected but not controllable

Light

Yeelight Candela

Home-assistant installation type

Home Assistant Operating System (HAOS)

Home-assistant version

2022.7.7

Describe the issue

Thanks for spending time on this.

I can find it and pair it, but not operate it. See logs for detail.

Koen

Debugging procedure followed:

  • 1- Smartphone will not connect with lamp
  • 2- The Yeelight_bt integration has been removed from HA.
  • 3- HA has access to the bluetooth adapter (followed the installation steps if not on HAOS).
  • 4- No other bluetooth integration are using something else than bleak library for bluetooth. If unsure, disable them.
  • 5- The logging has been changed in HA to allow debugging of this component and bleak.
  • 6- The light has been fully reset so that it is not paired with any device.
  • 7- Restart HA
  • 8- Reinstall the yeelight_bt integration and find the light through a scan.
  • 9- Pairing the lamp succeeded

Any additional comments

I am not sure if Passive BLE scanner interrupts, but previously it did work a short while with this integrations active.

Logs from the issue

Full logs
2022-08-02 11:35:59 WARNING (SyncWorker_8) [homeassistant.loader] We found a custom integration yeelight_bt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-08-02 11:35:59 ERROR (SyncWorker_8) [homeassistant.loader] The custom integration 'yeelight_bt' does not have a version key in the manifest file and was blocked from loading. See https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions for more details
2022-08-02 11:35:59 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration yeelight_bt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-08-02 11:37:59 DEBUG (MainThread) [custom_components.yeelight_bt.config_flow] Method selected: Scan
2022-08-02 11:38:00 DEBUG (MainThread) [custom_components.yeelight_bt.config_flow] Starting a scan for Yeelight Bt devices
2022-08-02 11:38:00 DEBUG (MainThread) [bleak.backends.bluezdbus.scanner] received D-Bus signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded (/): ['/org/bluez/hci0/dev_F8_24_41_C4_4D_25', {'org.freedesktop.DBus.Introspectable': {}, 'org.bluez.Device1': {'Address': <dbus_next.signature.Variant ('s', F8:24:41:C4:4D:25)>, 'AddressType': <dbus_next.signature.Variant ('s', public)>, 'Name': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'Alias': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'Paired': <dbus_next.signature.Variant ('b', False)>, 'Trusted': <dbus_next.signature.Variant ('b', False)>, 'Blocked': <dbus_next.signature.Variant ('b', False)>, 'LegacyPairing': <dbus_next.signature.Variant ('b', False)>, 'RSSI': <dbus_next.signature.Variant ('n', -60)>, 'Connected': <dbus_next.signature.Variant ('b', False)>, 'UUIDs': <dbus_next.signature.Variant ('as', ['0000fe87-0000-1000-8000-00805f9b34fb'])>, 'Adapter': <dbus_next.signature.Variant ('o', /org/bluez/hci0)>, 'ManufacturerData': <dbus_next.signature.Variant ('a{qv}', {356: <dbus_next.signature.Variant ('ay', b'd\x01%M\xc4A\x01\x00\x00%\x00yl_candela\x00\x00\x00\x00\x00\x00')>})>, 'ServicesResolved': <dbus_next.signature.Variant ('b', False)>}, 'org.freedesktop.DBus.Properties': {}}]
2022-08-02 11:38:28 INFO (MainThread) [custom_components.yeelight_bt.yeelightbt] found Candela with mac: F8:24:41:C4:4D:25, details:{'path': '/org/bluez/hci0/dev_F8_24_41_C4_4D_25', 'props': {'Address': 'F8:24:41:C4:4D:25', 'AddressType': 'public', 'Name': 'yeelight_ms', 'Alias': 'yeelight_ms', 'Paired': False, 'Trusted': False, 'Blocked': False, 'LegacyPairing': False, 'RSSI': -60, 'Connected': False, 'UUIDs': ['0000fe87-0000-1000-8000-00805f9b34fb'], 'Adapter': '/org/bluez/hci0', 'ManufacturerData': {356: b'd\x01%M\xc4A\x01\x00\x00%\x00yl_candela\x00\x00\x00\x00\x00\x00'}, 'ServicesResolved': False}}
2022-08-02 11:39:38 DEBUG (MainThread) [custom_components.yeelight_bt.config_flow] Yeelight UniqueID: f8:24:41:c4:4d:25
2022-08-02 11:39:38 DEBUG (MainThread) [custom_components.yeelight_bt] async setup.
2022-08-02 11:39:38 DEBUG (MainThread) [custom_components.yeelight_bt] List entries for domain:
2022-08-02 11:39:38 DEBUG (MainThread) [custom_components.yeelight_bt] [<homeassistant.config_entries.ConfigEntry object at 0x7f653da0c0>]
2022-08-02 11:39:39 DEBUG (MainThread) [custom_components.yeelight_bt] async setup entry: {'entry_id': '5fff2536532b47687a3cd47247a1e731', 'version': 2, 'domain': 'yeelight_bt', 'title': 'Candela', 'data': {'name': 'Candela', 'mac': 'F8:24:41:C4:4D:25'}, 'options': {}, 'pref_disable_new_entities': False, 'pref_disable_polling': False, 'source': 'user', 'unique_id': 'f8:24:41:c4:4d:25', 'disabled_by': None}
2022-08-02 11:39:40 DEBUG (MainThread) [custom_components.yeelight_bt.light] async_setup_entry:setting up the config entry Candela with data:{'name': 'Candela', 'mac': 'F8:24:41:C4:4D:25'}
2022-08-02 11:39:40 INFO (MainThread) [custom_components.yeelight_bt.light] Initializing YeelightBT Entity: Candela, F8:24:41:C4:4D:25
2022-08-02 11:39:40 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Initializing Yeelight Lamp F8:24:41:C4:4D:25
2022-08-02 11:39:40 DEBUG (MainThread) [custom_components.yeelight_bt.light] YEELIGHT: before first connection ----
2022-08-02 11:39:40 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Initiating new connection
2022-08-02 11:39:41 DEBUG (MainThread) [bleak.backends.bluezdbus.scanner] received D-Bus signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded (/): ['/org/bluez/hci0/dev_F8_24_41_C4_4D_25', {'org.freedesktop.DBus.Introspectable': {}, 'org.bluez.Device1': {'Address': <dbus_next.signature.Variant ('s', F8:24:41:C4:4D:25)>, 'AddressType': <dbus_next.signature.Variant ('s', public)>, 'Name': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'Alias': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'Paired': <dbus_next.signature.Variant ('b', False)>, 'Trusted': <dbus_next.signature.Variant ('b', False)>, 'Blocked': <dbus_next.signature.Variant ('b', False)>, 'LegacyPairing': <dbus_next.signature.Variant ('b', False)>, 'RSSI': <dbus_next.signature.Variant ('n', -58)>, 'Connected': <dbus_next.signature.Variant ('b', False)>, 'UUIDs': <dbus_next.signature.Variant ('as', ['0000fe87-0000-1000-8000-00805f9b34fb'])>, 'Adapter': <dbus_next.signature.Variant ('o', /org/bluez/hci0)>, 'ManufacturerData': <dbus_next.signature.Variant ('a{qv}', {356: <dbus_next.signature.Variant ('ay', b'd\x01%M\xc4A\x01\x00\x00%\x00yl_candela\x00\x00\x00\x00\x00\x00')>})>, 'ServicesResolved': <dbus_next.signature.Variant ('b', False)>}, 'org.freedesktop.DBus.Properties': {}}]
2022-08-02 11:39:43 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Connected: True
2022-08-02 11:39:43 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Request Notify
2022-08-02 11:40:13 ERROR (MainThread) [custom_components.yeelight_bt.yeelightbt] Connection: BleakError: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Connection Rejected Due To Security Reasons)
2022-08-02 11:40:13 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Connect retry 1
2022-08-02 11:40:15 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Client with address F8:24:41:C4:4D:25 got disconnected!
2022-08-02 11:40:15 DEBUG (MainThread) [custom_components.yeelight_bt.light] Got state notification from the lamp
2022-08-02 11:40:15 DEBUG (MainThread) [bleak.backends.bluezdbus.scanner] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_F8_24_41_C4_4D_25): ['org.bluez.Device1', {'RSSI': <dbus_next.signature.Variant ('n', -58)>, 'Name': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'Alias': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'ManufacturerData': <dbus_next.signature.Variant ('a{qv}', {356: <dbus_next.signature.Variant ('ay', b'd\x01%M\xc4A\x01\x00\x00%\x00yl_candela\x00\x00\x00\x00\x00\x00')>})>}, []]
2022-08-02 11:40:17 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Connected: True
2022-08-02 11:40:17 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Request Notify
2022-08-02 11:40:47 ERROR (MainThread) [custom_components.yeelight_bt.yeelightbt] Connection: BleakError: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Connection Rejected Due To Security Reasons)
2022-08-02 11:40:47 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Connect retry 2
2022-08-02 11:40:50 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Client with address F8:24:41:C4:4D:25 got disconnected!
2022-08-02 11:40:50 DEBUG (MainThread) [custom_components.yeelight_bt.light] Got state notification from the lamp
2022-08-02 11:40:50 DEBUG (MainThread) [bleak.backends.bluezdbus.scanner] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_F8_24_41_C4_4D_25): ['org.bluez.Device1', {'RSSI': <dbus_next.signature.Variant ('n', -58)>, 'Name': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'Alias': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'ManufacturerData': <dbus_next.signature.Variant ('a{qv}', {356: <dbus_next.signature.Variant ('ay', b'd\x01%M\xc4A\x01\x00\x00%\x00yl_candela\x00\x00\x00\x00\x00\x00')>})>}, []]
2022-08-02 11:40:52 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Connected: True
2022-08-02 11:40:52 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Request Notify
2022-08-02 11:41:23 ERROR (MainThread) [custom_components.yeelight_bt.yeelightbt] Connection: BleakError: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Connection Rejected Due To Security Reasons)
2022-08-02 11:41:23 DEBUG (MainThread) [custom_components.yeelight_bt.light] YEELIGHT: after first connection ----
2022-08-02 11:41:25 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Client with address F8:24:41:C4:4D:25 got disconnected!
2022-08-02 11:41:25 DEBUG (MainThread) [custom_components.yeelight_bt.light] Got state notification from the lamp
2022-08-02 11:41:53 DEBUG (MainThread) [custom_components.yeelight_bt.light] Requesting an update of the lamp status
2022-08-02 11:41:53 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Send Cmd: Get_state
2022-08-02 11:41:53 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Initiating new connection
2022-08-02 11:41:53 DEBUG (MainThread) [bleak.backends.bluezdbus.scanner] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_F8_24_41_C4_4D_25): ['org.bluez.Device1', {'RSSI': <dbus_next.signature.Variant ('n', -56)>, 'Name': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'Alias': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'ManufacturerData': <dbus_next.signature.Variant ('a{qv}', {356: <dbus_next.signature.Variant ('ay', b'd\x01%M\xc4A\x01\x00\x00%\x00yl_candela\x00\x00\x00\x00\x00\x00')>})>}, []]
2022-08-02 11:41:55 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Connected: True
2022-08-02 11:41:55 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Request Notify
2022-08-02 11:42:25 ERROR (MainThread) [custom_components.yeelight_bt.yeelightbt] Connection: BleakError: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Connection Rejected Due To Security Reasons)
2022-08-02 11:42:25 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Connect retry 1
2022-08-02 11:42:28 DEBUG (MainThread) [custom_components.yeelight_bt.yeelightbt] Client with address F8:24:41:C4:4D:25 got disconnected!
2022-08-02 11:42:28 DEBUG (MainThread) [custom_components.yeelight_bt.light] Got state notification from the lamp
2022-08-02 11:42:28 DEBUG (MainThread) [bleak.backends.bluezdbus.scanner] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_F8_24_41_C4_4D_25): ['org.bluez.Device1', {'RSSI': <dbus_next.signature.Variant ('n', -56)>, 'Name': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'Alias': <dbus_next.signature.Variant ('s', yeelight_ms)>, 'ManufacturerData': <dbus_next.signature.Variant ('a{qv}', {356: <dbus_next.signature.Variant ('ay', b'd\x01%M\xc4A\x01\x00\x00%\x00yl_candela\x00\x00\x00\x00\x00\x00')>})>}, []]

Hassio always lost connection in a few minutes/hours

Hi,
I have the Candela light, always connected to power. It works with this integration well, but in random time hassio lost connection. Candela is still reported like connected, but nothing happens when I try turn it on. The switch automatically return back to off in a few seconds.
Any ideas?

Getting errors after updating to the latest release

I am getting these errors after upgrading to the latest release:

2020-09-27 12:03:20 ERROR (MainThread) [homeassistant.config_entries] Migration handler not found for entry Bedside 1 for yeelight_bt
2020-09-27 12:03:20 ERROR (MainThread) [homeassistant.config_entries] Migration handler not found for entry Bedside 2 for yeelight_bt
2020-09-27 12:03:20 ERROR (MainThread) [homeassistant.config_entries] Migration handler not found for entry Bedside 3 for yeelight_bt

And the lights are not anymore available....

EDIT: After deleting integrations and adding the lights again with the new method scan, the lights are ok again !
But still do not understand if the rgb_color option is valid for these lamps or not....

How to install to Homeassistant Supervisor OS (hosted VM on Synology)

Hello,

I'm on Home Assistant Supervisor OS 2022.10.4 being hosted on VM in Synology. I'm wanting to install your add on, however it doesnt show up in hacs. I've already had hacs installed and went as far as to reinstall it. Still not seeing anything. Now yes, I could install it manually, but need help doing so. How would i go about installing this directly to the OS hosted on a VM? Also do I still need to install bluez as well? Thanks again.

Candle effect

Hi,
Is there any option to implement candle mode (flickering) in yeelight candle intergration?

Lights not anymore available

Suddenly this morning all the Bluetooth yeelights went to unavailable mode without changing anything from my side except upgrade to the latest release from HACS.
Any hints?

Wrong version key

Just updated to the latest release and got this error:

2021-05-17 12:28:52 ERROR (MainThread) [homeassistant.loader] '0.20210517.b01' is not a valid version for custom integration 'ytube_music_player'. Please report this to the maintainer of 'ytube_music_player'

Entity not available: light.xiaomi_candle

Hi!

I was able to follow the instructions on Hassio and everything worked like charm. The discovery found the candle after reseting it and I was able to control it.

However, after a while, I get that error and I have to shut down the candle to get it online again.

This is what I have in the logs:

`Logger: custom_components.yeelight_bt.yeelightbt
Source: custom_components/yeelight_bt/yeelightbt.py:260
Integration: Yeelight bluetooth (documentation, issues)
First occurred: 11:20:00 PM (1 occurrences)
Last logged: 11:20:00 PM

Could not write to lamp: error<class 'bluepy.btle.BTLEDisconnectError'>(Device disconnected), Retrying now...`

Am I doing something wrong?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.