Yeelight YLKG07YL Bluetooth button supported?

[kroon040]

Hi,

I bought an Yeelink bluetooth YLKG07YL, that should be supported. I grabbed the beacon key by running this. Where the product key is 950

wget https://raw.githubusercontent.com/custom-components/ble_monitor/master/custom_components/ble_monitor/ble_parser/get_beacon_key.py
apt-get install python3-pip libglib2.0-dev
pip3 install bleak asyncio
python3 get_beacon_key.py <MAC> <PRODUCT_ID>

Than I got a beaon key like this 24 length.

beaconKey: 'e917a539fa9c9f03bd9182e7'

Found something on internet that some people extended the key with FFFFFFF to 32 lenght

beaconKey: 'e917a539fa9c9f03bd9182e7FFFFFFFF'

Now I got in tasmota that keyOK.

It still unkown device but I receive messages like this

1x single button click

16:12:57.738 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:12:57","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":262,"RSSI":-64}}
16:12:57.837 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:12:57","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":262,"RSSI":-70}}
16:12:57.938 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:12:57","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":262,"RSSI":-64}}
16:12:58.038 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:12:58","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":262,"RSSI":-69}}

double button click

16:13:59.559 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:13:59","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":518,"RSSI":-63}}
16:13:59.612 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:13:59","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":518,"RSSI":-63}}
16:14:02.999 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:14:02","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":518,"RSSI":-67}}
16:14:03.158 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:14:03","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":518,"RSSI":-63}}
16:14:03.401 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:14:03","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":518,"RSSI":-62}}

Button hold:

16:16:37.316 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:16:37","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":262,"RSSI":-68}}
16:16:37.368 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:16:37","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":262,"RSSI":-69}}
16:16:37.467 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:16:37","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":262,"RSSI":-69}}
16:16:37.566 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:16:37","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":262,"RSSI":-69}}
16:16:37.666 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:16:37","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":262,"RSSI":-70}}

Rotate button clockwise:

16:18:47.022 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:18:47","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":268,"RSSI":-66}}
16:18:47.377 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:18:47","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":268,"RSSI":-66}}
16:18:47.527 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:18:47","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":268,"RSSI":-65}}
16:18:47.877 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:18:47","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":268,"RSSI":-65}}
16:18:47.930 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:18:47","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":268,"RSSI":-65}}
16:18:48.029 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:18:48","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":268,"RSSI":-73}}

Rotate button anti-clockwise:

16:20:21.398 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:20:21","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":-244,"RSSI":-75}}
16:20:21.498 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:20:21","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":-244,"RSSI":-67}}
16:20:21.548 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:20:21","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":-244,"RSSI":-66}}
16:20:23.219 MQT: stat/keuken2/SENSOR = {"Time":"2024-03-09T16:20:23","Unknown553517":{"alias":"button","mac":"dc9758553517","Btn":-244,"RSSI":-65}}

Is this the behavior how it should be? Is this the right way to let the button work, or did I something wrong or is this button newer that's not yet correct supported in tasmota?

[Staars]

The Mi32-legacy driver supports this device.

I just checked the key generator for Berry and it is still working too, which means you can generate the bind key entirely inside Tasmota.

[kroon040]

OK, where can I find the berry app? I thought it shou be up here?

https://github.com/arendst/Tasmota/tree/development/tasmota/berry

[sfromis]

Looks like this one:
https://github.com/Staars/berry-examples/blob/main/bleKeyLegacy.be

[kroon040]

thnx. How can I run this file. I download the file , and saved it on the file system, but nothing. Aslo renamed it to autoexec.be, but also not

[kroon040]

I see in the berry scripting console this message

BRY: failed to load '/autoexec.be' (syntax_error - /autoexec.be:385: unfinished string)

[kroon040]

I now installed the mi 32 blue version

import keyGenLeg in berry scripting console

import keyGenLeg
BRY: Exception> 'import_error' - module 'keyGenLeg' not found
stack traceback:
: in function main

In filesystem I uploaded the file? Do I need more

[mipurel]

Berry console :
load ('bleKeyLegacy.be')
import keyGenLeg

[sfromis]

You should do the import after what the file is named.

[kroon040]

I got it working.

I only try to get it to work with rules but it doesn't trigger. Any idea what goes wrong?

I have this rule

rule1 on YLKG08-553517#Button0=1 do POWER TOGGLE endon

stat/keuken/RESULT = {"Rule1":{"State":"ON","Once":"OFF","StopOnError":"OFF","Length":48,"Free":463,"Rules":"on YLKG08-553517#Button0=1 do POWER TOGGLE endon"}}

I get this as value when push the button

tele/keuken/SENSOR = {"Time":"2024-03-30T18:51:37","YLKG08-553517":{"Button0":1,"RSSI":-65,"MAC":"DC9758553517"}}

But it doesn't trigger

[kroon040]

found the issue. It's a televalue and needs to be tele-YLKG08-553517#Button0=1 do POWER TOGGLE endon

[thanhbigface]

I successfully connected to the device, but when I rotate it it shows wrong key, I am using ESPC3 and flashed Tasmota 14.2.0.3. How can fix it ?

[Staars]

Now it is getting interesting!
As I suggested earlier, there might have been an important change in the dimmer firmware.
Look at this: custom-components/ble_monitor#999 (comment)

For now please change the key manually in the mi32cfg file.
if you have 98B11F6F6E0F8D3D3C9730431A12351B this must become 98B11F6F6E0F30431A12351BFFFFFFFF.

In other words remove the middle 8D3D3C97 and append FFFFFFFF.

If this works, I can make the changes later in the driver code.

[thanhbigface]

It's worked, tks @Staars . What wrong in this key ?

[Staars]

The problem is, that this dimmer creates a 12-byte key internally. With the old dimmer firmware, this was filled up in the middle with some „magic bytes“ and with newer firmwares, it is filled at the tail with 0xff to reach the 16 bytes of a ccm key.
I will try to update my driver with as few friction as possible, but sadly there will be breaking changes for some users - meaning they need to recreate the bindkey.

[thanhbigface]

Yes, how to control the dimmer value when rotating up and down 5 values? Mine when I turn it the numbers are out of order

[sfromis]

What I see is the dimmer not providing even the opportunity for "rotating up and down 5 values", as it is providing rotation speed and direction. If you want a position, you'll have to decide how much to add/subtract when you get a payload for the button being twisted.

[kroon040]

That is right, I had also had to add FFFFFFF to it, I could remember..

I have that made some rules to trigger it. It works on tasmota 14.1

on tele-YLKG08-553517#Button0=1 do POWER TOGGLE endon on tele-YLKG08-553517#Button0=2 do publish cmnd/keuken2/POWER toggle ENDON

on tele-YLKG08-553517#Dimmer=1 do dimmer + endon on tele-YLKG08-553517#Dimmer=2 do dimmer + endon on tele-YLKG08-553517#Dimmer=3 do dimmer + endon on tele-YLKG08-553517#Dimmer=4 do dimmer + endon

on tele-YLKG08-553517#Dimmer=-1 do dimmer - endon on tele-YLKG08-553517#Dimmer=-2 do dimmer - endon on tele-YLKG08-553517#Dimmer=-3 do dimmer - endon on tele-YLKG08-553517#Dimmer=-4 do dimmer - endon

[kroon040]

I noticed one issue with 14.2 , that it doesn't trigger my rules anymore. I upgraded, and I see this in the log with 14.2

0:29:10.004 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:29:09","YLKG08-553517":{"Button0":1,"RSSI":-54,"MAC":"DC9758553517"}}
20:29:37.042 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:29:37","YLKG08-553517":{"Button0":1,"RSSI":-65,"MAC":"DC9758553517"}}
20:29:39.751 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:29:39","YLKG08-553517":{"Dimmer":2,"RSSI":-53,"MAC":"DC9758553517"}}
20:29:40.402 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:29:40","YLKG08-553517":{"Dimmer":2,"RSSI":-52,"MAC":"DC9758553517"}}
20:29:40.710 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:29:40","YLKG08-553517":{"Dimmer":2,"RSSI":-51,"MAC":"DC9758553517"}}

Downgraded to 14.1 and it triggers. Is there something changed in 14.2 that causes this. I'm using also esp32c3.

20:34:35.021 RUL: TELE-YLKG08-553517#DIMMER=3 performs 'dimmer +'
20:34:35.026 MQT: stat/keuken/RESULT = {"POWER":"ON","Dimmer":69}
20:34:35.330 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:34:35","MHZ19B":{"Model":"B","CarbonDioxide":1102,"Temperature":27.0},"YLKG08-553517":{"Dimmer":2,"RSSI":-51,"MAC":"DC9758553517"},"TempUnit":"C"}
20:34:35.351 RUL: TELE-YLKG08-553517#DIMMER=2 performs 'dimmer +'
20:34:35.356 MQT: stat/keuken/RESULT = {"POWER":"ON","Dimmer":74}
20:34:39.015 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:34:39","MHZ19B":{"Model":"B","CarbonDioxide":1103,"Temperature":27.0},"PVVX-f371e7":{"Temperature":24.7,"Humidity":67.5,"DewPoint":18.3,"Battery":100,"RSSI":-91,"MAC":"A4C138F371E7"},"YLKG08-553517":{"Button0":1,"RSSI":-53,"MAC":"DC9758553517"},"TempUnit":"C"}
20:34:39.046 RUL: TELE-YLKG08-553517#BUTTON0=1 performs 'POWER TOGGLE'
20:34:39.053 MQT: stat/keuken/RESULT = {"POWER":"OFF"}
20:34:39.056 MQT: stat/keuken/POWER = OFF
20:34:41.222 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:34:41","MHZ19B":{"Model":"B","CarbonDioxide":1103,"Temperature":27.0},"PVVX-09da59":{"Temperature":22.9,"Humidity":61.9,"DewPoint":15.2,"Battery":100,"RSSI":-85,"MAC":"A4C13809DA59"},"YLKG08-553517":{"Button0":1,"RSSI":-51,"MAC":"DC9758553517"},"TempUnit":"C"}
20:34:41.255 RUL: TELE-YLKG08-553517#BUTTON0=1 performs 'POWER TOGGLE'
20:34:41.262 MQT: stat/keuken/RESULT = {"POWER":"ON"}
20:34:41.266 MQT: stat/keuken/POWER = ON
20:34:41.348 MQT: stat/keuken/RESULT = {"POWER":"ON","Dimmer":69}
20:34:42.423 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:34:42","MHZ19B":{"Model":"B","CarbonDioxide":1103,"Temperature":27.0},"YLKG08-553517":{"Dimmer":-1,"RSSI":-60,"MAC":"DC9758553517"},"PVVX-6a0097":{"Temperature":24.8,"Humidity":60.3,"DewPoint":16.6,"Battery":100,"RSSI":-95,"MAC":"A4C1386A0097"},"TempUnit":"C"}
20:34:42.463 RUL: TELE-YLKG08-553517#DIMMER=-1 performs 'dimmer -'
20:34:42.468 MQT: stat/keuken/RESULT = {"POWER":"ON","Dimmer":64}
20:34:42.699 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:34:42","MHZ19B":{"Model":"B","CarbonDioxide":1103,"Temperature":27.0},"YLKG08-553517":{"Dimmer":-2,"RSSI":-60,"MAC":"DC9758553517"},"TempUnit":"C"}
20:34:42.728 RUL: TELE-YLKG08-553517#DIMMER=-2 performs 'dimmer -'
20:34:42.733 MQT: stat/keuken/RESULT = {"POWER":"ON","Dimmer":59}
20:34:43.157 MQT: tele/keuken/SENSOR = {"Time":"2024-09-01T20:34:43","MHZ19B":{"Model":"B","CarbonDioxide":1103,"Temperature":27.0},"YLKG08-553517":{"Dimmer":-5,"RSSI":-51,"MAC":"DC9758553517"},"TempUnit":"C"}

[thanhbigface]

How to control the dimmer value when rotating up and down 5 values? Mine when I turn it the numbers are out of order

[kroon040]

dimmerstep, you mean? dimmerstep 5

and than make the rules like I did.

[Staars]

@kroon040 @thanhbigface

I pushed an update to my bind key generator, that shall handle the key modification according to the firmware version of the dimmer.
Update here: https://github.com/Staars/berry-examples/blob/main/bleKeyLegacy.be
The internal log looks like that now:

Will read FW version
Got FW version, will read key
1.0.1_1
Got key with length: 12
Bind Key: B6D99E1703D61567213A0A62
Old firmware type ... will convert key to:
B6D99E1703D68D3D3C971567213A0A62
Success!! Will disconnect sensor.

I assume that firmware major version of 1 is old and 2 is new, so the behavior should change accordingly.
This would always provide a full 16-byte-key and is supposed to work with the current MI32 driver without any further changes.

It would be nice, if you can test this with a newer dimmer (that I do not own).

[sfromis]

I dusted off an YLKG08YL, and was able to have a key generated using the current bleKeyLegacy.be, with workable payload fields like Button0, Hold, Dimmer and Dimmer_P, with the latter two seemingly providing numbers for rotation speed, not position.

However, not a "newer dimmer" - FW 1.0.1_1, "Old firmware type ... will convert key"

[Staars]

Thanks.
Yes, the dimmer works with relative steps (which is more or less the same as the current directional speed). The Tasmota driver only publishes, what the BLE sensor really reports and does not try to make assumptions, how a user might want to convert this afterwards (and other users do not).
RULES are already very powerful and capable to do it most of the time whereas Berry is basically limitless.

[kroon040]

I did it like this in rules, worked in 14.1 and now in 14.2 it doesn't work. Is there another option? It doesn't trigger the rule anymore

on tele-YLKG08-553517#Button0=1 do POWER TOGGLE endon on tele-YLKG08-553517#Button0=2 do publish cmnd/keuken2/POWER toggle ENDON

on tele-YLKG08-553517#Dimmer=1 do dimmer + endon on tele-YLKG08-553517#Dimmer=2 do dimmer + endon on tele-YLKG08-553517#Dimmer=3 do dimmer + endon on tele-YLKG08-553517#Dimmer=4 do dimmer + endon

on tele-YLKG08-553517#Dimmer=-1 do dimmer - endon on tele-YLKG08-553517#Dimmer=-2 do dimmer - endon on tele-YLKG08-553517#Dimmer=-3 do dimmer - endon on tele-YLKG08-553517#Dimmer=-4 do dimmer - endon

[Staars]

Regarding RULES there was a commit:
8f75684

Maybe it is related to a change in behavior?

[sfromis]

Whatever happened with that tele- prefix or not, I'd consider it as "more logical" for it to be working without that weirdness in the triggers. Unfortunately, the tele prefix in the MQTT topic can be confusing, as it is used for more than the telemetry period, which is where the tele- prefix for triggers is supposed to be used.

[kroon040]

What should I use in rules to trigger , any ideas are welcome

[sfromis]

It is the usual, you have to match the payloads you seen in the console, but not adding that tele- prefix to the triggers. If what you posted already is valid (do check), it could be triggers like YLKG08-553517#Dimmer

[kroon040]

Ok thnx that works removing the tele- prefix , and also works with 14.2

[sfromis]

Something is screwed up around the JSON handling. Every time I'm using the dimmer, with Berry rules active (even for unrelated payloads), I'm seeing messages like this:
23:44:40.272 BRY: ERROR, bad json:
And no JSON is shown where it tries to do that.

This is where Berry is issuing that message

      var ev = json.load(ev_json)         # returns nil if invalid JSON
      if ev == nil
        self.log('BRY: ERROR, bad json: '+ev_json, 3)
        ev = ev_json                # revert to string
      end

Thus, the string ev_json where it expects to get the JSON to be processed seems to be empty, implying that something unusual happens when those payloads are generated.

However, I'm still getting the expected JSON, allowing me to see values for Dimmer etc. Hence it seems to be something happening in addition to generating the expected payloads.