【ESPHome】ESP32 DIY通用蓝牙网关，接入米家系门锁等各种设备

XCray

breakjia 发表于 2022-11-24 00:14
楼主你好，我用你的mible_0.4编译之后 为什么打印出这样的日志。可以指点一下吗    bindkey是破解版app ...

玩这个思路，需要起码的编程基础。

[xiaomi_blez:114]: parse_xiaomi_header(): service data has no DATA flag. 这句提示其实说的很清楚，数据标志不符。具体你看看源代码105~119行就明白了。然后根据你的锁修改。

对了，你是用的什么锁？也许早就有人改好了呢

chenquanhao

netwolf 发表于 2023-5-10 11:45
是的，最近安装的新的锁也是这个问题

好像论坛里没人提到过40位字符的问题，我一直以为我操作的问题，按理说我的鹿客class 2x也是2019年那会儿的锁了，也不是新设备，你的是什么锁

netwolf

chenquanhao 发表于 2023-5-11 22:15
好像论坛里没人提到过40位字符的问题，我一直以为我操作的问题，按理说我的鹿客class 2x也是2019年那会儿 ...

也是老锁,MJZNMS02LM，米家霸王锁那款。
另一个房子MJZNMS03LM,这个反而是先装的，可能取bindkey早，没问题。

breakjia

XCray 发表于 2023-5-10 15:33
玩这个思路，需要起码的编程基础。

[xiaomi_blez:114]: parse_xiaomi_header(): service data has no DA ...

小米全自动智能门锁，好像这个不是蓝牙协议的

白云纷飞

果然不能盲目抄作业，读了3遍帖子后终于成功了，但是出现新的问题了，多个不同指纹解锁后返回的keyid都是同一个，经查看日志发现log输出的keyid和最终sending的值不一致，操作的时间戳也不一致

白云纷飞

白云纷飞 发表于 2023-6-18 16:49
果然不能盲目抄作业，读了3遍帖子后终于成功了，但是出现新的问题了，多个不同指纹解锁后返回的keyid都是同 ...

多个不同指纹解锁后返回的keyid都是同一个，经查看日志发现log输出的keyid和最终sending的值不一致，操作的时间戳也不一致


附上日志

[00:50:11][D][xiaomi_blez:128]: Packet : 48.44.1A.03.91.9B.ED.95.21.F2.62.20.F6.96.6A.D8.C1.5A.D9.03.B0.C5.E1.AA (24)
[00:50:11][D][xiaomi_blez:237]: decrypt_xiaomi_payload(): authenticated decryption passed.
[00:50:11][D][xiaomi_blez:239]:   Plaintext : 0B.00.09.A4.FF.FF.FF.FF.C2.7B.94.64 (12), Packet : 145
[00:50:11][D][xiaomi_blez:093]: value_length:9;payload_length:12
[00:50:11][D][xiaomi_blez:251]: Got Xiaomi MijiaLock (CC:9C:CE:63:F2:E3):
[00:50:11][D][xiaomi_blez:254]:   OpMethod:10
[00:50:11][D][xiaomi_blez:257]:   action:4
[00:50:11][D][xiaomi_blez:269]:   OpTS:1687452610
[00:50:11][D][xiaomi_blez:272]:   KeyID:-1
[00:50:11][D][sensor:094]: 'action': Sending state 4.00000  with 0 decimals of accuracy
[00:50:11][D][sensor:094]: 'opmethod': Sending state 10.00000  with 0 decimals of accuracy
[00:50:11][D][sensor:094]: 'KeyID': Sending state 4294967296.00000  with 0 decimals of accuracy
[00:50:11][D][sensor:094]: 'opts': Sending state 1687452672.00000  with 0 decimals of accuracy
[00:50:11][D][xiaomi_blez:128]: Packet : 48.44.1A.03.91.9B.ED.95.21.F2.62.20.F6.96.6A.D8.C1.5A.D9.03.B0.C5.E1.AA (24)
[00:50:11][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (145).
[00:50:11][D][xiaomi_blez:128]: Packet : 48.44.1A.03.91.9B.ED.95.21.F2.62.20.F6.96.6A.D8.C1.5A.D9.03.B0.C5.E1.AA (24)
[00:50:11][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (145).
[00:50:11][D][xiaomi_blez:128]: Packet : 48.44.1A.03.91.9B.ED.95.21.F2.62.20.F6.96.6A.D8.C1.5A.D9.03.B0.C5.E1.AA (24)
[00:50:11][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (145).
[00:50:11][D][xiaomi_blez:128]: Packet : 48.44.1A.03.91.9B.ED.95.21.F2.62.20.F6.96.6A.D8.C1.5A.D9.03.B0.C5.E1.AA (24)
[00:50:11][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (145).
[00:50:11][D][xiaomi_blez:128]: Packet : 48.44.1A.03.91.9B.ED.95.21.F2.62.20.F6.96.6A.D8.C1.5A.D9.03.B0.C5.E1.AA (24)
[00:50:11][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (145).
[00:50:14][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:14][D][xiaomi_blez:237]: decrypt_xiaomi_payload(): authenticated decryption passed.
[00:50:14][D][xiaomi_blez:239]:   Plaintext : 07.00.05.02.C5.7B.94.64 (8), Packet : 147
[00:50:14][D][xiaomi_blez:093]: value_length:5;payload_length:8
[00:50:14][D][xiaomi_blez:251]: Got Xiaomi MijiaLock (CC:9C:CE:63:F2:E3):
[00:50:14][D][xiaomi_blez:266]:   DoorEvt: 2
[00:50:14][D][xiaomi_blez:278]:   DoorEvtTS: 1687452613
[00:50:14][D][sensor:094]: 'doorevt': Sending state 2.00000  with 0 decimals of accuracy
[00:50:14][D][sensor:094]: 'doorevtts': Sending state 1687452672.00000  with 0 decimals of accuracy
[00:50:15][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:15][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:15][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:15][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:15][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:15][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:15][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:15][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:15][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:15][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:15][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:15][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:15][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:15][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:15][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:15][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:16][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:16][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:16][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:16][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:16][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:16][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:16][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:16][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:16][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:16][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:16][D][xiaomi_blez:128]: Packet : 48.44.1A.03.93.D3.D5.89.BF.42.FF.AF.04.02.14.A3.E7.AB.F2.7E (20)
[00:50:16][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (147).
[00:50:18][D][xiaomi_blez:128]: Packet : 48.44.1A.03.95.88.6A.FF.48.1A.97.69.DA.EE.04.0A.3B.EA.62.FA (20)
[00:50:18][D][xiaomi_blez:237]: decrypt_xiaomi_payload(): authenticated decryption passed.
[00:50:18][D][xiaomi_blez:239]:   Plaintext : 07.00.05.01.C8.7B.94.64 (8), Packet : 149
[00:50:18][D][xiaomi_blez:093]: value_length:5;payload_length:8
[00:50:18][D][xiaomi_blez:251]: Got Xiaomi MijiaLock (CC:9C:CE:63:F2:E3):
[00:50:18][D][xiaomi_blez:266]:   DoorEvt: 1
[00:50:18][D][xiaomi_blez:278]:   DoorEvtTS: 1687452616
[00:50:18][D][sensor:094]: 'doorevt': Sending state 1.00000  with 0 decimals of accuracy
[00:50:18][D][sensor:094]: 'doorevtts': Sending state 1687452672.00000  with 0 decimals of accuracy
[00:50:18][D][xiaomi_blez:128]: Packet : 48.44.1A.03.95.88.6A.FF.48.1A.97.69.DA.EE.04.0A.3B.EA.62.FA (20)
[00:50:18][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (149).
[00:50:18][D][xiaomi_blez:128]: Packet : 48.44.1A.03.95.88.6A.FF.48.1A.97.69.DA.EE.04.0A.3B.EA.62.FA (20)
[00:50:18][D][xiaomi_blez:132]: parse_xiaomi_header(): duplicate data packet received (149).
[00:50:18][D][xiaomi_blez:128]: Packet : 48.44.1A.03.95.88.6A.FF.48.1A.97.69.DA.EE.04.0A.3B.EA.62.FA (20)

jy940006145

chenquanhao 发表于 2023-5-11 22:15
好像论坛里没人提到过40位字符的问题，我一直以为我操作的问题，按理说我的鹿客class 2x也是2019年那会儿 ...

你好，请教一下，40位字符的问题解决了么？可以使用么？

chenquanhao

jy940006145 发表于 2023-9-1 18:55
你好，请教一下，40位字符的问题解决了么？可以使用么？

没，好像没人关注了，继续用XiaomiGateway3，其实也没有很大问题，只是想能彻底离线最好

jy940006145

chenquanhao 发表于 2023-9-4 18:38
没，好像没人关注了，继续用XiaomiGateway3，其实也没有很大问题，只是想能彻底离线最好 ...

我也是这个问题，试了几个版本的多模了，都是40位，看来是没啥希望本地获取了。

silang521

XCray 发表于 2023-5-10 15:33
玩这个思路，需要起码的编程基础。

[xiaomi_blez:114]: parse_xiaomi_header(): service data has no DA ...

X大 我的门锁型号是MJZNMS03LM   开门关门传感器也有数据 但是esphome log里面还是会显示  parse_xiaomi_header(): service data has no DATA flag.

以下是我的log


我的105-119行数据是下面的内容
optional<XiaomiParseResult> parse_xiaomi_header(const esp32_ble_tracker::ServiceData &service_data) {
  XiaomiParseResult result;
  if (!service_data.uuid.contains(0x8F, 0x03) and !service_data.uuid.contains(0x95, 0xFE)) {
    ESP_LOGD(TAG, "parse_xiaomi_header(): no service data UUID magic bytes.");
    return {};
  }
  auto raw = service_data.data;
  result.has_data = (raw[0] & 0x40) ? true : false;
  result.has_capability = (raw[0] & 0x20) ? true : false;
  result.has_encryption = (raw[0] & 0x08) ? true : false;
  ESP_LOGD(TAG, "Packet : %s", hexencode(raw.data(), raw.size()).c_str());

请教X大 我这种情况需要怎么修改？