search

mduran80 / daikin_madoka

Home Assistant custom component integration for the BRC1H thermostat (madoka)
MIT License
42 stars 10 forks source link

Can't connect to BRC1H #3

Closed denisov-vlad closed 3 years ago

denisov-vlad commented 3 years ago

Hi!

Thank you for the integration!

I can't connect from my Pi 4 (HassOS): 1) all steps up to pair looks ok 2) after pair I see that bluetoothctl switches to BRC1H: from [bluetooth] to BRC1H xx:yy:zz 3) i see nothing on thermostat nor in prompt 4) the Failed to pair: org.bluez.Error.AuthenticationCanceled appeared

Could you help please?

mduran80 commented 3 years ago

It seems to me that your thermostat is still connected to another master. Once you try to pair and the thermostat is unbound, the authorization prompt should be displayed in your CLI and in the thermostat screen.

Please make sure of that:

Let me know if you are able to connect.

denisov-vlad commented 3 years ago

@mduran80 I've tried to repeat all steps. The logs is below:

➜  ~ bluetoothctl
Agent registered
[CHG] Controller DC:A6:32:E3:EC:B8 Pairable: yes
[DEL] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[DEL] Device 00:CC:3F:63:14:1D BRC1H 63:14:1D
[DEL] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[DEL] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[DEL] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[DEL] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[DEL] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[DEL] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[DEL] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[DEL] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[NEW] Device 00:CC:3F:63:14:1D BRC1H 63:14:1D
[NEW] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[NEW] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[NEW] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[NEW] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[NEW] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[NEW] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[NEW] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[NEW] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[NEW] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[bluetooth]# agent off
Agent unregistered
[CHG] Controller DC:A6:32:E3:EC:B8 Pairable: no
[bluetooth]# agent KeyboardDisplay
Agent registered
[CHG] Controller DC:A6:32:E3:EC:B8 Pairable: yes
[bluetooth]# remove 00:CC:3F:63:14:1D
[DEL] Device 00:CC:3F:63:14:1D BRC1H 63:14:1D
Device has been removed
[DEL] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[DEL] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[DEL] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[DEL] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[DEL] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[DEL] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[DEL] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[DEL] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[DEL] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[bluetooth]# scan on
Discovery started
[CHG] Controller DC:A6:32:E3:EC:B8 Discovering: yes
[NEW] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[NEW] Device 00:CC:3F:63:14:1D BRC1H 63:14:1D
[NEW] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[NEW] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[NEW] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[NEW] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[NEW] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[NEW] Device 28:D1:27:3C:7B:84 MJYD2S
[NEW] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[NEW] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[NEW] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[bluetooth]# scan off
Discovery stopped
[CHG] Device 5C:E5:0C:23:5A:E5 RSSI is nil
[CHG] Device 6E:72:84:03:62:FC TxPower is nil
[CHG] Device 6E:72:84:03:62:FC RSSI is nil
[CHG] Device 50:EC:50:81:F2:57 RSSI is nil
[CHG] Device 28:D1:27:3C:7B:84 RSSI is nil
[CHG] Device D0:D0:03:FF:9F:6F RSSI is nil
[CHG] Device 7A:8C:9F:A5:EE:8E TxPower is nil
[CHG] Device 7A:8C:9F:A5:EE:8E RSSI is nil
[CHG] Device 50:EC:50:83:4D:6B RSSI is nil
[CHG] Device 5C:E5:0C:25:03:7A RSSI is nil
[CHG] Device 6E:47:67:29:2F:91 RSSI is nil
[CHG] Device 00:CC:3F:63:14:1D RSSI is nil
[CHG] Device 79:A1:0F:C2:5C:54 RSSI is nil
[CHG] Controller DC:A6:32:E3:EC:B8 Discovering: no
[bluetooth]# pair 00:CC:3F:63:14:1D
Attempting to pair with 00:CC:3F:63:14:1D
[CHG] Device 00:CC:3F:63:14:1D Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device 00:CC:3F:63:14:1D Connected: no
[DEL] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[DEL] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[DEL] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[DEL] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[DEL] Device 28:D1:27:3C:7B:84 MJYD2S
[DEL] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[DEL] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[DEL] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[DEL] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[bluetooth]# pair 00:CC:3F:63:14:1D
Attempting to pair with 00:CC:3F:63:14:1D
[CHG] Device 00:CC:3F:63:14:1D Connected: yes
[DEL] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[NEW] Primary Service (Handle 0xf170)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0010
    00001801-0000-1000-8000-00805f9b34fb
    Generic Attribute Profile
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0010/char0011
    00002a05-0000-1000-8000-00805f9b34fb
    Service Changed
[NEW] Descriptor (Handle 0x8e90)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0010/char0011/desc0013
    00002902-0000-1000-8000-00805f9b34fb
    Client Characteristic Configuration
[NEW] Primary Service (Handle 0xf170)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030
    0000180a-0000-1000-8000-00805f9b34fb
    Device Information
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0031
    00002a29-0000-1000-8000-00805f9b34fb
    Manufacturer Name String
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0033
    00002a23-0000-1000-8000-00805f9b34fb
    System ID
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0035
    00002a24-0000-1000-8000-00805f9b34fb
    Model Number String
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0037
    00002a25-0000-1000-8000-00805f9b34fb
    Serial Number String
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0039
    00002a26-0000-1000-8000-00805f9b34fb
    Firmware Revision String
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char003b
    00002a27-0000-1000-8000-00805f9b34fb
    Hardware Revision String
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char003d
    00002a28-0000-1000-8000-00805f9b34fb
    Software Revision String
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char003f
    00002a2a-0000-1000-8000-00805f9b34fb
    IEEE 11073-20601 Regulatory Cert. Data List
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0041
    00002a50-0000-1000-8000-00805f9b34fb
    PnP ID
[NEW] Primary Service (Handle 0xf170)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100
    2141e100-213a-11e6-b67b-9e71128cae77
    Vendor specific
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100/char0101
    2141e101-213a-11e6-b67b-9e71128cae77
    Vendor specific
[NEW] Descriptor (Handle 0x9e20)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100/char0101/desc0103
    00002902-0000-1000-8000-00805f9b34fb
    Client Characteristic Configuration
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100/char0104
    2141e102-213a-11e6-b67b-9e71128cae77
    Vendor specific
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100/char0106
    2141e103-213a-11e6-b67b-9e71128cae77
    Vendor specific
[NEW] Descriptor (Handle 0x1cd0)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100/char0106/desc0108
    00002902-0000-1000-8000-00805f9b34fb
    Client Characteristic Configuration
[NEW] Primary Service (Handle 0xf170)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0200
    2141e110-213a-11e6-b67b-9e71128cae77
    Vendor specific
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0200/char0201
    2141e111-213a-11e6-b67b-9e71128cae77
    Vendor specific
[NEW] Descriptor (Handle 0x1f00)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0200/char0201/desc0203
    00002902-0000-1000-8000-00805f9b34fb
    Client Characteristic Configuration
[NEW] Characteristic (Handle 0x0430)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0200/char0204
    2141e112-213a-11e6-b67b-9e71128cae77
    Vendor specific
[CHG] Device 00:CC:3F:63:14:1D UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 00:CC:3F:63:14:1D UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 00:CC:3F:63:14:1D UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device 00:CC:3F:63:14:1D UUIDs: 2141e100-213a-11e6-b67b-9e71128cae77
[CHG] Device 00:CC:3F:63:14:1D UUIDs: 2141e110-213a-11e6-b67b-9e71128cae77
[CHG] Device 00:CC:3F:63:14:1D ServicesResolved: yes
[CHG] Device 00:CC:3F:63:14:1D Name: UE878 RF MODULE
[CHG] Device 00:CC:3F:63:14:1D Alias: UE878 RF MODULE
[CHG] Device 00:CC:3F:63:14:1D Modalias: usb:v06E7p7031d0110
[NEW] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[NEW] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[NEW] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[NEW] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[NEW] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[NEW] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[NEW] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[NEW] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[NEW] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[NEW] Device 28:D1:27:37:B5:40 MJYD2S
[DEL] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[DEL] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[DEL] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[DEL] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[DEL] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[DEL] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[DEL] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[DEL] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[DEL] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[DEL] Device 28:D1:27:37:B5:40 MJYD2S
[NEW] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[NEW] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[NEW] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[NEW] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[NEW] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[NEW] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[NEW] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[NEW] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[NEW] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[BRC1H 63:14:1D]# yes
Invalid command in menu main: yes

Use "help" for a list of available commands in a menu.
Use "menu <submenu>" if you want to enter any submenu.
Use "back" if you want to return to menu main.
[DEL] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[DEL] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[DEL] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[DEL] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[DEL] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[DEL] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[DEL] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[DEL] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[DEL] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[NEW] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[NEW] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[NEW] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[NEW] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[NEW] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[NEW] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[NEW] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[NEW] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[NEW] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[DEL] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[DEL] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[DEL] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[DEL] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[DEL] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[DEL] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[DEL] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[DEL] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[DEL] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[NEW] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[NEW] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[NEW] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[NEW] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[NEW] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[NEW] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[NEW] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[NEW] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[NEW] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
Failed to pair: org.bluez.Error.AuthenticationCanceled
[DEL] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[DEL] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[DEL] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[DEL] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[DEL] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[DEL] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[DEL] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[DEL] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[DEL] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[NEW] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
[NEW] Device 6E:72:84:03:62:FC 6E-72-84-03-62-FC
[NEW] Device 50:EC:50:81:F2:57 50-EC-50-81-F2-57
[NEW] Device 50:EC:50:83:4D:6B 50-EC-50-83-4D-6B
[NEW] Device 5C:E5:0C:23:5A:E5 5C-E5-0C-23-5A-E5
[NEW] Device 6E:47:67:29:2F:91 6E-47-67-29-2F-91
[NEW] Device 7A:8C:9F:A5:EE:8E 7A-8C-9F-A5-EE-8E
[NEW] Device 79:A1:0F:C2:5C:54 79-A1-0F-C2-5C-54
[NEW] Device 5C:E5:0C:25:03:7A 5C-E5-0C-25-03-7A
[NEW] Device 28:D1:27:37:A6:C6 MJYD2S
[DEL] Descriptor (Handle 0xb760)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0010/char0011/desc0013
    00002902-0000-1000-8000-00805f9b34fb
    Client Characteristic Configuration
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0010/char0011
    00002a05-0000-1000-8000-00805f9b34fb
    Service Changed
[DEL] Primary Service (Handle 0x6fd8)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0010
    00001801-0000-1000-8000-00805f9b34fb
    Generic Attribute Profile
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0031
    00002a29-0000-1000-8000-00805f9b34fb
    Manufacturer Name String
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0033
    00002a23-0000-1000-8000-00805f9b34fb
    System ID
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0035
    00002a24-0000-1000-8000-00805f9b34fb
    Model Number String
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0037
    00002a25-0000-1000-8000-00805f9b34fb
    Serial Number String
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0039
    00002a26-0000-1000-8000-00805f9b34fb
    Firmware Revision String
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char003b
    00002a27-0000-1000-8000-00805f9b34fb
    Hardware Revision String
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char003d
    00002a28-0000-1000-8000-00805f9b34fb
    Software Revision String
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char003f
    00002a2a-0000-1000-8000-00805f9b34fb
    IEEE 11073-20601 Regulatory Cert. Data List
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030/char0041
    00002a50-0000-1000-8000-00805f9b34fb
    PnP ID
[DEL] Primary Service (Handle 0x6fd8)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0030
    0000180a-0000-1000-8000-00805f9b34fb
    Device Information
[DEL] Descriptor (Handle 0xe860)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100/char0101/desc0103
    00002902-0000-1000-8000-00805f9b34fb
    Client Characteristic Configuration
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100/char0101
    2141e101-213a-11e6-b67b-9e71128cae77
    Vendor specific
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100/char0104
    2141e102-213a-11e6-b67b-9e71128cae77
    Vendor specific
[DEL] Descriptor (Handle 0xe920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100/char0106/desc0108
    00002902-0000-1000-8000-00805f9b34fb
    Client Characteristic Configuration
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100/char0106
    2141e103-213a-11e6-b67b-9e71128cae77
    Vendor specific
[DEL] Primary Service (Handle 0x6fd8)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0100
    2141e100-213a-11e6-b67b-9e71128cae77
    Vendor specific
[DEL] Descriptor (Handle 0x0000)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0200/char0201/desc0203
    00002902-0000-1000-8000-00805f9b34fb
    Client Characteristic Configuration
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0200/char0201
    2141e111-213a-11e6-b67b-9e71128cae77
    Vendor specific
[DEL] Characteristic (Handle 0xa920)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0200/char0204
    2141e112-213a-11e6-b67b-9e71128cae77
    Vendor specific
[DEL] Primary Service (Handle 0x6fd8)
    /org/bluez/hci0/dev_00_CC_3F_63_14_1D/service0200
    2141e110-213a-11e6-b67b-9e71128cae77
    Vendor specific
[DEL] Device 00:CC:3F:63:14:1D UE878 RF MODULE
[DEL] Device D0:D0:03:FF:9F:6F [TV] Samsung Q80 Series (55)
mduran80 commented 3 years ago

After all the services are discovered lines beginning with [NEW]) a question should appear asking you if the authorization code is correct. However, that question does not appear in your logs.

are you able to pair with the mobile app? Sometimes the thermostat has to be fully resetted by disconnecting all the wires when some connection has been unsuccessful. Try to connect it to your phone, then unbind the bluetooth device on the thermostat and repeat the procedure.

If not successful, you may have to do the hard reset.

denisov-vlad commented 3 years ago

I successfully connected from the mobile app and was able to turn the air conditioner on/off.

Then clicked disconnect in the bluetooth menu both on the thermostat and phone.

Later, I repeated all the steps you described in the pull-request, but nothing changed - the prompt to confirm the connection did not appear.

Device: Raspberry Pi 4 OS Version: Home Assistant OS 5.12 Madoka Version: 3.4.0

mduran80 commented 3 years ago

I see you are using a Raspberry Pi 4. In the Raspberry Pi 3b+ I have to enable bluetooth connections by removing it from the rfkill list (not sure if needed in Rpi 4). Please try the following commands and check if the bluetooth connections are blocked:

sudo rfkill list sudo rfkill unblock bluetooth

Is the Raspberry far from the thermostat?

Next thing you can try is to start a btmon and log all the bluetooth output to see why it is refusing to connect.

denisov-vlad commented 3 years ago

Raspberry is about 5m from thermostat.

Hass OS (Terminal & SSH addon), connected via ssh:

➜  ~ rfkill list
rfkill: /dev/rfkill: Operation not permitted
➜  ~ sudo rfkill list
rfkill: /dev/rfkill: Operation not permitted
mduran80 commented 3 years ago

Try with the SSH & Web Terminal addon and disable the protection mode in the addon config.

denisov-vlad commented 3 years ago

@mduran80 the same thing with SSH & Web Terminal in disabled protection mode. I think the main problem is HassOS, because I can connect to thermostat from another Pi 4 on Raspbian.

capcorpha commented 3 years ago

same problem here, no thermostat screen ask for permission. i tryed all steps as denisov

denisov-vlad commented 3 years ago

@mduran80 Hi! Can I help you to make it work in HassOS?

mduran80 commented 3 years ago

@denisov-vlad The problem is that I am using HassOS myself and haven't found any issue trying to connect (on Raspberry Pi 3b+ and Intel Nuc). Not sure about the cause, I don't have many clues about it and I don't own a Raspi 4 so I can't test. Have you tried a clean HassOS reinstall? Is it updated?

denisov-vlad commented 3 years ago

Similar issue: https://community.home-assistant.io/t/can-i-install-bluez-bluetoothctl-on-a-rpi-that-has-hassio-as-os/160508/5

denisov-vlad commented 3 years ago

@mduran80 i will try to repeat all steps on fresh HassOS later.

wishmaster1984 commented 3 years ago

Hi, I'm having the exact same issue on Pi4 with latest HASSIO. Did you ever manage to solve this issue? Would be great to have this integration working.

mduran80 commented 3 years ago

Hi, I'm having the exact same issue on Pi4 with latest HASSIO. Did you ever manage to solve this issue? Would be great to have this integration working.

Have you tried with an external BT adapter? The problem seems to be related to the BT support in the Rpi.

wishmaster1984 commented 3 years ago

No I have not. Thanks for the quick reply, I'll try to find one and will update. (Could be a few days).

wishmaster1984 commented 3 years ago

I now have a external BT adapter and this seems to be working as expected. "[CHG] Device ServicesResolved: yes"

I was also able to enable the integration and it says succesfull. However I'm not seeing any entities. Any idea's on why this is?

mduran80 commented 3 years ago

No idea about the entities, they should be listed if no error happened during the setup (basically, the mac address and activate the checkbox to force disconnection).

A bit of very basic troubleshooting.. did you reboot the HA instance (not required)? Any message in the logs?

Anyway, I also recommend using the code of the HA core fork in my repo. I expect it to be merged someday and become an official integration. You can install it as a custom component too, but the source has been cleaned up.

I am glad to know the issue is related to the Rpi internal BT, I will let other people with similar problems know about it.

wishmaster1984 commented 3 years ago

I now have a external BT adapter and this seems to be working as expected. "[CHG] Device ServicesResolved: yes"

I was also able to enable the integration and it says succesfull. However I'm not seeing any entities. Any idea's on why this is?

I've found my issue. The steps to add where a bit different for me. The way I got it working was:

Hope this helps anyone also having issues.

wishmaster1984 commented 3 years ago

How can I add multiple BRC's? When trying to start the integration again, it states "aborted". Should I add all MAC's at the same time? if so what is the split character?

mduran80 commented 3 years ago

You should add all at once. I think it is all mentioned in the integration steps. IIRC it is a comma separated list.

wishmaster1984 commented 3 years ago

Still having issues connecting multiple units. I can't seem to get the other 3 units paired, I'm getting the code through the bluetoothtcl and approving it but then still authentication fails. These units have a master (the one I have successfully paired) could this be the issue? The one that I managed to pair and add to the integration is working like a charm by the way. Great work!!

mduran80 commented 3 years ago

The issue is probably related to the master setup, I have just one thermostat and I don't know how it behaves with that configuration.

The secondary thermostats don't authenticate because once a thermostat is bound with a device (phone or dongle) it does not respond to pairing requests.

Other users have setup several thermostats at once but I guess none of them had any as master.

denisov-vlad commented 3 years ago

It works after update to Home Assistant OS 6.0 RC.

denisov-vlad commented 3 years ago

@mduran80 I've used to switch to mobile app connection for a while.

Then I've tried to connect and had the same problems on RPi4 + HassOS. This flow helped me to reconnect again:

  1. ssh to host (or via addon)
  2. docker exec -ti homeassistant /bin/bash
  3. rfkill unblock bluetooth
  4. bleak-lescan -i hci0
  5. bluetoothctl
  6. next steps from guide