Add support for Smart Radiator Thermostat - comet-blue-eurotronic

[matteopedani]

I'm testing the binding of https://community.openhab.org/t/comet-blue-eurotronic/36590
Now I can bind.

How can I create the XML files?
Where to put?
How to add an extra coefficent to each radiator (to calculate the calories)
How to elaborate data. (to calculate calories and for billing purpose)

[vkolotov]

Hi @matteopedani , it looks similar to eQ-3 radiator thermostat, is it the same device?

[matteopedani]

I don't think so. May be. I don't have eQ-3
They use the similar hardware but they program in a different way.
They have different ID manufactor
I can expose my raspberry and the 7 thermostat to internet if you like to play send me your ssh pubblic id

[bademux]

@matteopedani
It can be same device https://translate.google.com/translate?sl=auto&tl=en&js=y&prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2Ftorsten-traenkner.de%2Fwissen%2Fsmarthome%2Fheizung.php&edit-text=

[vkolotov]

Looks like it is not the same device. Here is a python project with some good details about its characteristics:
https://github.com/im-0/cometblue/blob/master/cometblue/device.py

What you will need to do is:

1. Create GATT xml files similar to this (please do not think it is easy to accomplish):

   • https://github.com/sputnikdev/bluetooth-gatt-parser/blob/396bdee4c6ec4c0656a31b7f12b9952b7bb928de/src/main/resources/gatt/service/com.eq-3.service.radiator_thermostat.xml
   • https://github.com/sputnikdev/bluetooth-gatt-parser/blob/396bdee4c6ec4c0656a31b7f12b9952b7bb928de/src/main/resources/gatt/characteristic/com.eq-3.characteristic.state_and_control.xml

2. Install a new build of the Bluetooth binding from here (you will need to uninstall the binding from MarketPlace first): https://oss.sonatype.org/content/repositories/snapshots/org/sputnikdev/org.eclipse.smarthome.binding.bluetooth/1.1-SNAPSHOT/org.eclipse.smarthome.binding.bluetooth-1.1-20180114.100602-6.jar

It will give you a new experimental feature that can discover all characteristics (including "unknown" characteristics). To enable this feature:

3. Create a folder on your file system that is accessible by "openhab" user, something like that:
   /home/pi/.bluetooth_smart
   That folder should contain two subfolders:
   • characteristic
   • service

These two folders should contain your xml files from the point n1, e.g. "characteristic" folder contains XML file for characteristics and "service" contains XML files for your services.
Make sure that file permissions are set correctly so that "openhab" user can read them.

Specify that folder here:

I just want to warn you that this process is not easy, you should have some background in bluetooth technology (GATT) and in software engineering. So please do not expect any magic.

[matteopedani]

@bademux
Yes, Is this device In this page I linked for reference https://community.openhab.org/t/comet-blue-eurotronic/36590

@vkolotov
I will try to follow your instructions to create GATT xml files.

[matteopedani]

To find the right ID
Can I use ?
sudo bluetoothctl

##############
follow the full output of bluetoothctl

[termosifone cucina piano terra]# devices
Device D0:B5:C2:FB:BE:B3 termosifone bagno blu primo piano
Device D0:B5:C2:FB:BE:C3 termosifone 5
Device D0:B5:C2:FB:B9:40 termosifone 1
Device D0:B5:C2:FB:AF:64 termosifone 2
Device D0:B5:C2:F1:73:2E termosifone 3 primo piano
Device D0:B5:C2:FB:B9:3A termosifone 4
Device D0:B5:C2:F1:72:4D termosifone cucina piano terra
[termosifone cucina piano terra]# connect D0:B5:C2:F1:72:4D
Attempting to connect to D0:B5:C2:F1:72:4D
Connection successful
[termosifone cucina piano terra]# info
Device D0:B5:C2:F1:72:4D
Name: Comet Blue
Alias: termosifone cucina piano terra
Paired: yes
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (47e9ee00-47e9-11e4-8939-164230d1df67)
ManufacturerData Key: 0xffff
ManufacturerData Value:
ff 00 01 ff ff ff ......
ManufacturerData Key: 0x2229
ManufacturerData Value:
20 00 00 ff 69 88 ...i.
ManufacturerData Key: 0x2f26
ManufacturerData Value:
23 01 00 ff af 69 #....i
RSSI: -82
TxPower: 0
[termosifone cucina piano terra]# list-attributes
Primary Service
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b
47e9ee00-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0046
47e9ee30-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0044
47e9ee2e-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0042
47e9ee2d-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0040
47e9ee2c-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char003e
47e9ee2b-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char003c
47e9ee2a-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char003a
47e9ee27-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0038
47e9ee26-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0036
47e9ee25-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0034
47e9ee24-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0032
47e9ee23-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0030
47e9ee22-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char002e
47e9ee21-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char002c
47e9ee20-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char002a
47e9ee16-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0028
47e9ee15-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0026
47e9ee14-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0024
47e9ee13-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0022
47e9ee12-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char0020
47e9ee11-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char001e
47e9ee10-47e9-11e4-8939-164230d1df67
Vendor specific
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service001b/char001c
47e9ee01-47e9-11e4-8939-164230d1df67
Vendor specific
Primary Service
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service0010
0000180a-0000-1000-8000-00805f9b34fb
Device Information
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service0010/char0019
00002a29-0000-1000-8000-00805f9b34fb
Manufacturer Name String
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service0010/char0017
00002a28-0000-1000-8000-00805f9b34fb
Software Revision String
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service0010/char0015
00002a26-0000-1000-8000-00805f9b34fb
Firmware Revision String
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service0010/char0013
00002a24-0000-1000-8000-00805f9b34fb
Model Number String
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service0010/char0011
00002a23-0000-1000-8000-00805f9b34fb
System ID
Primary Service
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service000c
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
Characteristic
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service000c/char000d
00002a05-0000-1000-8000-00805f9b34fb
Service Changed
Descriptor
/org/bluez/hci0/dev_D0_B5_C2_F1_72_4D/service000c/char000d/desc000f
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration

[vkolotov]

hi @matteopedani, yes those "manufacturer specific" services and characteristics are those that you will need to create mapping for. Look at this project, if you can read python code, you will find what each characteristic can do: https://github.com/im-0/cometblue/blob/master/cometblue/device.py

[vkolotov]

@matteopedani, looks like these ones are the most interesting:

'datetime': {
            'description': 'time and date',
            'uuid': '47e9ee01-47e9-11e4-8939-164230d1df67',
            'read_requires_pin': True,
            'decode': _decode_datetime,
            'encode': _encode_datetime,
        },

        'flags': {
            'description': 'flags',
            'uuid': '47e9ee2a-47e9-11e4-8939-164230d1df67',
            'read_requires_pin': True,
            'decode': _decode_flags,
        },

        'temperatures': {
            'description': 'temperatures',
            'uuid': '47e9ee2b-47e9-11e4-8939-164230d1df67',
            'read_requires_pin': True,
            'decode': _decode_temperatures,
            'encode': _encode_temperatures,
        },

        'battery': {
            'description': 'battery charge',
            'uuid': '47e9ee2c-47e9-11e4-8939-164230d1df67',
            'read_requires_pin': True,
            'decode': _decode_battery,
        },

        'firmware_revision2': {
            'description': 'firmware revision #2',
            'uuid': '47e9ee2d-47e9-11e4-8939-164230d1df67',
            'read_requires_pin': True,
            'decode': str,
        },

        'lcd_timer': {
            'description': 'LCD timer',
            'uuid': '47e9ee2e-47e9-11e4-8939-164230d1df67',
            'read_requires_pin': True,
            'decode': _decode_lcd_timer,
            'encode': _encode_lcd_timer,
        },

        'pin': {
            'description': 'PIN',
            'uuid': '47e9ee30-47e9-11e4-8939-164230d1df67',
            'encode': _encode_pin,
        },

[matteopedani]

Thank's I will work on these. Matteo 2018-01-16 11:42 GMT+01:00 Vlad Kolotov <notifications@github.com>:

…

@matteopedani <https://github.com/matteopedani>, looks like these ones are the most interesting: 'datetime': { 'description': 'time and date', 'uuid': '47e9ee01-47e9-11e4-8939-164230d1df67', 'read_requires_pin': True, 'decode': _decode_datetime, 'encode': _encode_datetime, }, 'flags': { 'description': 'flags', 'uuid': '47e9ee2a-47e9-11e4-8939-164230d1df67', 'read_requires_pin': True, 'decode': _decode_flags, }, 'temperatures': { 'description': 'temperatures', 'uuid': '47e9ee2b-47e9-11e4-8939-164230d1df67', 'read_requires_pin': True, 'decode': _decode_temperatures, 'encode': _encode_temperatures, }, 'battery': { 'description': 'battery charge', 'uuid': '47e9ee2c-47e9-11e4-8939-164230d1df67', 'read_requires_pin': True, 'decode': _decode_battery, }, 'firmware_revision2': { 'description': 'firmware revision #2', 'uuid': '47e9ee2d-47e9-11e4-8939-164230d1df67', 'read_requires_pin': True, 'decode': str, }, 'lcd_timer': { 'description': 'LCD timer', 'uuid': '47e9ee2e-47e9-11e4-8939-164230d1df67', 'read_requires_pin': True, 'decode': _decode_lcd_timer, 'encode': _encode_lcd_timer, }, 'pin': { 'description': 'PIN', 'uuid': '47e9ee30-47e9-11e4-8939-164230d1df67', 'encode': _encode_pin, }, — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASiPBT7Z1oeB9jsVIDCt2L-Es3-O9Aztks5tLH0WgaJpZM4RfePM> .

-- *Matteo Pedani* www.pedani.it mobile +39 3343637690 phone +39 0699341466 phone +39 069415152

[xrucka]

Hi, thanks @vkolotov for pointing me in this dirrection, I have only skimmed through the original discussion and completely missed the roadmap. I suggest using my fork of cometblue control utility, as I had further developed the encoding of status triplet. You can find my fork at https://github.com/xrucka/cometblue . @matteopedani - is there any way I can contribute on developing the specs?

[vkolotov]

Hi @xrucka, any contribution is greatly appreciated. Looks like you have some knowledge of GATT stuff, If so you could try to come up with GATT files as I mentioned above:
#14 (comment)

I'll be supporting you in this answering any questions you have.

Please note that this might not be possible to add support for this device through GATT XML files. Please see here: #13

In short, the eQ-3 device has API that does not follow GATT specification, to be more precise the data structures for its main characteristic are different for read, write and notify operations. That's why for the eQ-3 device we will have to develop a custom bluetooth binding.

[xrucka]

Ok, thanks for the headsup; I should be able to look into it either on tomorrow or thursday evening. I'll get back to you guys once I manage to do something about it. As for odd data structures, I've not noticed anything special, except perhaps the status triplet, but I believe that it should be manageable with correct read/write order.