Theengs Gateway - BLE to MQTT on a Raspberry Pi, Windows PC or Apple Mac

Dom_KS · January 23, 2023, 5:45pm

There is something wrong with my Rpi

openhabian@openhabian:~ $ sudo sudo python3 -m pip install bluetooth-clocks
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting bluetooth-clocks
  Downloading https://files.pythonhosted.org/packages/1b/56/c33b5aac4fd85626a6b31c888bf4bde777324ab52eca0b0d837f65d7e887/bluetooth_clocks-0.1.0-py3-none-any.whl
Collecting bleak>=0.19.0 (from bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/44/be/da0de00c7c66c14c0ccaa5927abd048927f93d9c7ed2598d99549d7f9109/bleak-0.19.5-py3-none-any.whl (132kB)
    100% |████████████████████████████████| 133kB 896kB/s
Collecting importlib-metadata; python_version < "3.8" (from bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/26/a7/9da7d5b23fc98ab3d424ac2c65613d63c1f401efb84ad50f2fa27b2caab4/importlib_metadata-6.0.0-py3-none-any.whl
Collecting async-timeout<5,>=3.0.0 (from bleak>=0.19.0->bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/d6/c1/8991e7c5385b897b8c020cdaad718c5b087a6626d1d11a23e1ea87e325a7/async_timeout-4.0.2-py3-none-any.whl
Collecting typing-extensions<5.0.0,>=4.2.0; python_version < "3.8" (from bleak>=0.19.0->bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/0b/8e/f1a0a5a76cfef77e1eb6004cb49e5f8d72634da638420b9ea492ce8305e8/typing_extensions-4.4.0-py3-none-any.whl
Collecting dbus-fast<2.0.0,>=1.22.0; platform_system == "Linux" (from bleak>=0.19.0->bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/81/67/a83522d6692a72911c3586e2fcd2363ce22d1522a7e17e1012f255a6083b/dbus_fast-1.84.0.tar.gz (65kB)
    100% |████████████████████████████████| 71kB 2.2MB/s
  Installing build dependencies ... done
Collecting zipp>=0.5 (from importlib-metadata; python_version < "3.8"->bluetooth-clocks)
  Using cached https://files.pythonhosted.org/packages/d8/20/256eb3f3f437c575fb1a2efdce5e801a5ce3162ea8117da96c43e6ee97d8/zipp-3.11.0-py3-none-any.whl
Building wheels for collected packages: dbus-fast
  Running setup.py bdist_wheel for dbus-fast ... \                                                 done
  Stored in directory: /root/.cache/pip/wheels/8f/56/85/2d82b076cf6e733315e4cc4f922055f3f9a47c952b55264659
Successfully built dbus-fast
Installing collected packages: typing-extensions, async-timeout, dbus-fast, bleak, zipp, importlib-metadata, bluetooth-clocks
Successfully installed async-timeout-4.0.2 bleak-0.19.5 bluetooth-clocks-0.1.0 dbus-fast-1.84.0 importlib-metadata-6.0.0 typing-extensions-4.4.0 zipp-3.11.0
openhabian@openhabian:~ $
openhabian@openhabian:~ $ bluetooth-clocks discover
Traceback (most recent call last):
  File "/usr/local/bin/bluetooth-clocks", line 6, in <module>
    from bluetooth_clocks.__main__ import run
  File "/usr/local/lib/python3.7/dist-packages/bluetooth_clocks/__main__.py", line 12, in <module>
    from bluetooth_clocks.scanners import discover_clocks, find_clock
  File "/usr/local/lib/python3.7/dist-packages/bluetooth_clocks/scanners.py", line 16, in <module>
    async def find_clock(address: str, scan_duration: float = 5.0) -> BluetoothClock | None:
TypeError: unsupported operand type(s) for |: 'ABCMeta' and 'NoneType'
openhabian@openhabian:~ $ sudo bluetooth-clocks discover
Traceback (most recent call last):
  File "/usr/local/bin/bluetooth-clocks", line 6, in <module>
    from bluetooth_clocks.__main__ import run
  File "/usr/local/lib/python3.7/dist-packages/bluetooth_clocks/__main__.py", line 12, in <module>
    from bluetooth_clocks.scanners import discover_clocks, find_clock
  File "/usr/local/lib/python3.7/dist-packages/bluetooth_clocks/scanners.py", line 16, in <module>
    async def find_clock(address: str, scan_duration: float = 5.0) -> BluetoothClock | None:
TypeError: unsupported operand type(s) for |: 'ABCMeta' and 'NoneType'
openhabian@openhabian:~ $

koenvervloesem · January 23, 2023, 6:48pm

No, there’s nothing wrong with your Raspberry Pi, the error was all mine. I published a bugfix release. Can you try again with the updated version?

python3 -m pip install -U bluetooth-clocks

maxin · January 27, 2023, 8:42am

Thank you, for answer!

Thanks I got it. As I understand it, the gateway can only process received states, but cannot send (manage)? For example, a Xiaomi scooter requires sending a request for data, and only then sends the required data.
Wrapped python into a service (with virtual environment) using WinSW

<service>
  <id>openhabblemqttbridge.exe</id>
  <name>OpenHAB BLE MQTT Bridge</name>
  <description>Python TheengsGateway BLE MQTT Bridge</description>  
  <executable>r:\servers\python\ble2mqtt\Scripts\python.exe</executable>
  <argument>-m</argument>
  <argument>TheengsGateway</argument>
  <argument>-ll</argument>
  <argument>ERROR</argument>
  <argument>-s</argument>
  <argument>passive</argument>
  <argument>-sd</argument>
  <argument>5</argument>
  <argument>-tb</argument>
  <argument>55</argument>
  <argument>-H</argument>
  <argument>127.0.0.1</argument>
  <argument>-P</argument>
  <argument>1883</argument>
  <argument>-u</argument>
  <argument>MYLOGIN</argument>
  <argument>-p</argument>
  <argument>MYPASSWORD</argument>
  <argument>-pt</argument>
  <argument>ble2mqtt/device</argument>
  <argument>-st</argument>
  <argument>ble2mqtt/device/set</argument>
  <argument>-pa</argument>
  <argument>1</argument>
  <argument>-D</argument>
  <argument>1</argument>
  <argument>-Dh</argument>
  <argument>0</argument>
  <argument>-Dt</argument>
  <argument>ble2mqtt/discovery</argument>
  <argument>-Dn</argument>
  <argument>bledev</argument>
  <logmode>rotate</logmode>
  <stoptimeout>30sec</stoptimeout>
  <serviceaccount>
    <domain>MYSERVER</domain>
    <user>LocalSystem</user>
    <password></password>
  </serviceaccount>
  <workingdirectory>r:\servers\python\ble2mqtt</workingdirectory>
  <env name="VIRTUAL_ENV" value="r:\servers\python\ble2mqtt"/>
  <env name="PROMPT" value="(ble2mqtt) $P$G"/>
  <env name="PATH" value="r:\servers\python\ble2mqtt\Scripts;%PATH%"/>  
</service>

4-5.It would be convenient if we could specify any id, not just those for which the author’s parsers were written. In general, it seems to me that it would be cool to use not only Deny Filter, but also Allow Filter (id/vendor).
6. I didn’t put it that way, of course “brand”. I would like that “brand” was published for any device, and not just for those that the gateway can work with. Of course, if it is specified in manufactordata or servicedata (most devices have this data).
7. I implemented lastseen and availability via OpenHab rules. But a built-in feature would be much more convenient.

For MQTT channel

  - id: lastseen
    channelTypeUID: mqtt:datetime
    label: Last seen
    configuration:
      stateTopic: ble2mqtt/device/FF0727A00CAF
      transformationPattern: JS:device\device_lastseen.js
  - id: availability
    channelTypeUID: mqtt:contact
    label: Availability
    configuration:
      stateTopic: ble2mqtt/device/FF0727A00CAF
      transformationPattern: JS:device\device_availability.js
      off: offline
      on: online

// device_availability.js

(function(i) {
	return "online";
})(input)

// device_lastseen.js
(function(i) {
	function pad(num){
		var norm = Math.floor(Math.abs(num));
		return (norm < 10 ? '0' : '') + norm;
	};

	var date =  new Date();
	var tzOffset = -date.getTimezoneOffset();
	var plusOrMinus = tzOffset >= 0 ? '+' : '-';	
	
	return date.getFullYear() + '-' + pad(date.getMonth() + 1) +'-' + pad(date.getDate()) + 'T' + pad(date.getHours()) + ':' + pad(date.getMinutes()) + ':' + pad(date.getSeconds()) + plusOrMinus + pad(tzOffset / 60) + ':' + pad(tzOffset % 60);	
})(input)

And a rule that runs once a minute and changes states for devices that are more than 10 minutes offline

// include
import java.time.format.DateTimeFormatter
import org.openhab.core.model.script.ScriptServiceUtil

// ble2mqtt device availability
val String[]    bluetooth_ble_device_availability_list = newArrayList("sperl_sp620e_dev01", "sperl_sp611e_dev01", "qhtek_triones_dev01")
val String      bluetooth_ble_device_availability_source = "bluetooth_ble_device_availability"
val Long        bluetooth_ble_device_availability_timeout = 10L

rule "Bluetooth: BLE device availability"
when
    Time cron "0 * * * * ? *"
then
    val _now = ZonedDateTime.now();
    
    bluetooth_ble_device_availability_list.forEach[_item | 
        val _lastseen = ScriptServiceUtil.getItemRegistry.getItem(_item + "_lastseen").state; 
        if(NULL !== _lastseen){            
            val ZonedDateTime _previous = ZonedDateTime.parse(_lastseen.toString() /* 2023-01-26T01:35:09.000+0300 */, DateTimeFormatter.ofPattern("yyyy-MM-dd'T'HH:mm:ss.SSSZ"));
            val Duration _diff = Duration.between(_previous, _now); 
            //logInfo(bluetooth_ble_device_availability_source, _item + " last seen " +  _lastseen.toString() + " [" + _previous.toString() + "] -> " +  _diff.toString());
            if (_diff.compareTo(Duration.of(bluetooth_ble_device_availability_timeout, MINUTES)) > 0)
                ScriptServiceUtil.getItemRegistry.getItem(_item + "_availability").sendCommand(CLOSED);
        }
    ];
end

Hans_Lree · January 27, 2023, 1:19pm

Might not an Expiration Timer for your devices’ items be a shorter and easier way to achieve this?

maxin · January 27, 2023, 1:33pm

I completely forgot about him!!! Thank you!

Dom_KS · January 31, 2023, 6:15pm

Sorry but I didn’t have free time. Today I take my test rpi 3 b+ and now I can test what you need.

There is something wrong

openhabian@openhabian:~ $ python3 -m pip install -U bluetooth-clocks
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting bluetooth-clocks
  Downloading https://files.pythonhosted.org/packages/3e/d5/0262beb7bfa2847c938861ece41bac44378735b4c2165be74560e616e60f/bluetooth_clocks-0.1.1-py3-none-any.whl
Collecting importlib-metadata; python_version < "3.8" (from bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/26/a7/9da7d5b23fc98ab3d424ac2c65613d63c1f401efb84ad50f2fa27b2caab4/importlib_metadata-6.0.0-py3-none-any.whl
Collecting bleak>=0.19.0 (from bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/44/be/da0de00c7c66c14c0ccaa5927abd048927f93d9c7ed2598d99549d7f9109/bleak-0.19.5-py3-none-any.whl (132kB)
    100% |████████████████████████████████| 133kB 871kB/s
Collecting zipp>=0.5 (from importlib-metadata; python_version < "3.8"->bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/01/3c/9d84fc1dbac1c5103bf3cd994e4895642001f75eb2139bddbc02aa1906e5/zipp-3.12.0-py3-none-any.whl
Collecting typing-extensions>=3.6.4; python_version < "3.8" (from importlib-metadata; python_version < "3.8"->bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/0b/8e/f1a0a5a76cfef77e1eb6004cb49e5f8d72634da638420b9ea492ce8305e8/typing_extensions-4.4.0-py3-none-any.whl
Collecting dbus-fast<2.0.0,>=1.22.0; platform_system == "Linux" (from bleak>=0.19.0->bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/81/67/a83522d6692a72911c3586e2fcd2363ce22d1522a7e17e1012f255a6083b/dbus_fast-1.84.0.tar.gz (65kB)
    100% |████████████████████████████████| 71kB 987kB/s
  Installing build dependencies ... done

Collecting async-timeout<5,>=3.0.0 (from bleak>=0.19.0->bluetooth-clocks)
  Downloading https://files.pythonhosted.org/packages/d6/c1/8991e7c5385b897b8c020cdaad718c5b087a6626d1d11a23e1ea87e325a7/async_timeout-4.0.2-py3-none-any.whl
Building wheels for collected packages: dbus-fast
  Running setup.py bdist_wheel for dbus-fast ... |                                                 done
  Stored in directory: /home/openhabian/.cache/pip/wheels/8f/56/85/2d82b076cf6e733315e4cc4f922055f3f9a47c952b55264659
Successfully built dbus-fast
Installing collected packages: zipp, typing-extensions, importlib-metadata, async-timeout, dbus-fast, bleak, bluetooth-clocks
  The script bluetooth-clocks is installed in '/home/openhabian/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed async-timeout-4.0.2 bleak-0.19.5 bluetooth-clocks-0.1.1 dbus-fast-1.84.0 importlib-metadata-6.0.0 typing-extensions-4.4.0 zipp-3.12.0
openhabian@openhabian:~ $
openhabian@openhabian:~ $
openhabian@openhabian:~ $ bluetooth-clocks discover
-bash: bluetooth-clocks: command not found
openhabian@openhabian:~ $ sudo bluetooth-clocks discover
[sudo] password for openhabian:
sudo: bluetooth-clocks: command not found

Dom_KS · January 31, 2023, 6:49pm

I restarted rpi and now it works. There is probably problem with time zone. There is always 1h mistake (I live in +1h zone). My rpi has set good time&date. I took screens from Telink Flasher.
First one is before any changes, second after bluetooth-clocks set -a A4:C1:38:34:A4:EC and the last one is taken after bluetooth-clocks set -a A4:C1:38:34:A4:EC -t 2023-01-10T16:20

openhabian@openhabian:~ $ bluetooth-clocks discover -s 10
Scanning for supported clocks...
Found a PVVX: address A4:C1:38:34:A4:EC, name ATC_34A4EC
Found a PVVX: address A4:C1:38:20:C2:AB, name ATC_20C2AB
Found a PVVX: address A4:C1:38:DD:13:4E, name ATC_DD134E
Found a PVVX: address A4:C1:38:C6:AF:20, name ATC_C6AF20
Found a PVVX: address A4:C1:38:9A:E4:40, name ATC_9AE440
Found a PVVX: address A4:C1:38:D6:5E:0B, name ATC_D65E0B
openhabian@openhabian:~ $ bluetooth-clocks discover
Scanning for supported clocks...
Found a PVVX: address A4:C1:38:34:A4:EC, name ATC_34A4EC
Found a PVVX: address A4:C1:38:DD:13:4E, name ATC_DD134E
Found a PVVX: address A4:C1:38:C6:AF:20, name ATC_C6AF20
Found a PVVX: address A4:C1:38:9A:E4:40, name ATC_9AE440
Found a PVVX: address A4:C1:38:20:C2:AB, name ATC_20C2AB
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Writing time to device...
Synchronized time
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC -t 2023-01-10T16:20
Scanning for device A4:C1:38:34:A4:EC...
Writing time to device...
Synchronized time
openhabian@openhabian:~ $ date
Tue 31 Jan 19:38:43 CET 2023
openhabian@openhabian:~ $

First one is before any changes,

bluetooth-clocks set -a A4:C1:38:34:A4:EC

bluetooth-clocks set -a A4:C1:38:34:A4:EC -t 2023-01-10T16:20

koenvervloesem · February 1, 2023, 8:42am

And is the clock also showing the time one hour off on its display?

Dom_KS · February 1, 2023, 9:45am

Yes it is. Screens shows exactly what is displayed on display.

BTW.
This 10s scannig discovered 6 thermometers but I have 7 .

BTW 2.
Now I’ve got runing second Rpi 3 b+ (test one) so I can do more test if you need.

koenvervloesem · February 1, 2023, 10:13am

I found the error, this will be fixed in the next release. But I’m glad setting the time works, as I don’t have such a device myself, so I had to resort to reverse engineering the original code. Thanks for trying this out! I’ll let you know when you can try the new release.

koenvervloesem · February 2, 2023, 8:25am

@Dom_KS Try upgrading to the new 0.1.2 release:

python3 -m pip install -U bluetooth-clocks

Let me know whether the time is synchronized correctly now.

If it’s always the same thermometer that isn’t discovered, maybe it’s too far from your Raspberry Pi. You could always try with an even longer scan duration.

Dom_KS · February 3, 2023, 10:26am

first try and errors:

openhabian@openhabian:~ $ python3 -m pip install -U bluetooth-clocks
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting bluetooth-clocks
  Downloading https://files.pythonhosted.org/packages/65/a5/432269d8d7d8c0143711ce4f197a327b1285e03342e92a0ddbe3f7129d0a/bluetooth_clocks-0.1.2-py3-none-any.whl
Requirement already satisfied, skipping upgrade: bleak>=0.19.0 in ./.local/lib/python3.7/site-packages (from bluetooth-clocks) (0.19.5)
Requirement already satisfied, skipping upgrade: importlib-metadata; python_version < "3.8" in ./.local/lib/python3.7/site-packages (from bluetooth-clocks) (6.0.0)
Requirement already satisfied, skipping upgrade: async-timeout<5,>=3.0.0 in ./.local/lib/python3.7/site-packages (from bleak>=0.19.0->bluetooth-clocks) (4.0.2)
Requirement already satisfied, skipping upgrade: dbus-fast<2.0.0,>=1.22.0; platform_system == "Linux" in ./.local/lib/python3.7/site-packages (from bleak>=0.19.0->bluetooth-clocks) (1.84.0)
Requirement already satisfied, skipping upgrade: typing-extensions<5.0.0,>=4.2.0; python_version < "3.8" in ./.local/lib/python3.7/site-packages (from bleak>=0.19.0->bluetooth-clocks) (4.4.0)
Requirement already satisfied, skipping upgrade: zipp>=0.5 in ./.local/lib/python3.7/site-packages (from importlib-metadata; python_version < "3.8"->bluetooth-clocks) (3.12.0)
Installing collected packages: bluetooth-clocks
  Found existing installation: bluetooth-clocks 0.1.1
    Uninstalling bluetooth-clocks-0.1.1:
      Successfully uninstalled bluetooth-clocks-0.1.1
Successfully installed bluetooth-clocks-0.1.2
openhabian@openhabian:~ $ bluetooth-clocks discover -s 30
Scanning for supported clocks...
Found a PVVX: address A4:C1:38:9A:E4:40, name ATC_9AE440
Found a PVVX: address A4:C1:38:DD:13:4E, name ATC_DD134E
Found a PVVX: address A4:C1:38:20:C2:AB, name ATC_20C2AB
Found a PVVX: address A4:C1:38:34:A4:EC, name ATC_34A4EC
Found a PVVX: address A4:C1:38:C6:AF:20, name ATC_C6AF20
Found a PVVX: address A4:C1:38:66:DC:AD, name ATC_66DCAD
Found a PVVX: address A4:C1:38:D6:5E:0B, name ATC_D65E0B
Found a PVVX: address A4:C1:38:5A:D0:87, name ATC_5AD087
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Writing time to device...
Traceback (most recent call last):
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/backends/bluezdbus/client.py", line 177, in connect
    member="Connect",
  File "/home/openhabian/.local/lib/python3.7/site-packages/dbus_fast/aio/message_bus.py", line 371, in call
    await future
concurrent.futures._base.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 210, in set_clock_time
    await clock.set_time(timestamp, args.am_pm)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__init__.py", line 335, in set_time
    async with BleakClient(self.address) as client:
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/__init__.py", line 433, in __aenter__
    await self.connect()
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/__init__.py", line 471, in connect
    return await self._backend.connect(**kwargs)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/backends/bluezdbus/client.py", line 177, in connect
    member="Connect",
  File "/home/openhabian/.local/lib/python3.7/site-packages/async_timeout/__init__.py", line 129, in __aexit__
    self._do_exit(exc_type)
  File "/home/openhabian/.local/lib/python3.7/site-packages/async_timeout/__init__.py", line 212, in _do_exit
    raise asyncio.TimeoutError
concurrent.futures._base.TimeoutError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/openhabian/.local/bin/bluetooth-clocks", line 10, in <module>
    sys.exit(run())
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 28, in run
    asyncio.run(main(sys.argv[1:]))
  File "/usr/lib/python3.7/asyncio/runners.py", line 43, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
    return future.result()
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 41, in main
    await cli_args.func(cli_args)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 216, in set_clock_time
    except asyncio.exceptions.TimeoutError as exc:
AttributeError: module 'asyncio' has no attribute 'exceptions'
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Didn't find device A4:C1:38:34:A4:EC.
openhabian@openhabian:~ $ bluetooth-clocks discover -s
usage: bluetooth-clocks discover [-h] [-s SCAN_DURATION]
bluetooth-clocks discover: error: argument -s/--scan-duration: expected one argument
openhabian@openhabian:~ $

after rpi reboot

openhabian@openhabian:~ $ bluetooth-clocks discover
Scanning for supported clocks...
Found a PVVX: address A4:C1:38:DD:13:4E, name ATC_DD134E
Found a PVVX: address A4:C1:38:66:DC:AD, name ATC_66DCAD
Found a PVVX: address A4:C1:38:9A:E4:40, name ATC_9AE440
Found a PVVX: address A4:C1:38:20:C2:AB, name ATC_20C2AB
Found a PVVX: address A4:C1:38:34:A4:EC, name ATC_34A4EC
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Didn't find device A4:C1:38:34:A4:EC.
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Didn't find device A4:C1:38:34:A4:EC.
openhabian@openhabian:~ $ bluetooth-clocks discover 30
usage: bluetooth-clocks [-h] [--version] [-v] [-vv] {discover,get,set} ...
bluetooth-clocks: error: unrecognized arguments: 30
openhabian@openhabian:~ $ bluetooth-clocks discover -s 30
Scanning for supported clocks...
Found a PVVX: address A4:C1:38:34:A4:EC, name ATC_34A4EC
Found a PVVX: address A4:C1:38:9A:E4:40, name ATC_9AE440
Found a PVVX: address A4:C1:38:20:C2:AB, name ATC_20C2AB
Found a PVVX: address A4:C1:38:66:DC:AD, name ATC_66DCAD
Found a PVVX: address A4:C1:38:D6:5E:0B, name ATC_D65E0B
Found a PVVX: address A4:C1:38:5A:D0:87, name ATC_5AD087
Found a PVVX: address A4:C1:38:DD:13:4E, name ATC_DD134E
openhabian@openhabian:~ $ bluetooth-clocks discover -s 60
Scanning for supported clocks...
Found a PVVX: address A4:C1:38:9A:E4:40, name ATC_9AE440
Found a PVVX: address A4:C1:38:66:DC:AD, name ATC_66DCAD
Found a PVVX: address A4:C1:38:C6:AF:20, name ATC_C6AF20
Found a PVVX: address A4:C1:38:5A:D0:87, name ATC_5AD087
Found a PVVX: address A4:C1:38:34:A4:EC, name ATC_34A4EC
Found a PVVX: address A4:C1:38:DD:13:4E, name ATC_DD134E
Found a PVVX: address A4:C1:38:D6:5E:0B, name ATC_D65E0B
Found a PVVX: address A4:C1:38:20:C2:AB, name ATC_20C2AB
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Writing time to device...
Synchronized time
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC -t 2023-01-10T16:20
Scanning for device A4:C1:38:34:A4:EC...
Didn't find device A4:C1:38:34:A4:EC.
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC -t 2023-01-10T16:20
Scanning for device A4:C1:38:34:A4:EC...
Didn't find device A4:C1:38:34:A4:EC.
openhabian@openhabian:~ $ bluetooth-clocks discover -s 30
Scanning for supported clocks...
Found a PVVX: address A4:C1:38:DD:13:4E, name ATC_DD134E
Found a PVVX: address A4:C1:38:C6:AF:20, name ATC_C6AF20
Found a PVVX: address A4:C1:38:9A:E4:40, name ATC_9AE440
Found a PVVX: address A4:C1:38:34:A4:EC, name ATC_34A4EC
Found a PVVX: address A4:C1:38:66:DC:AD, name ATC_66DCAD
Found a PVVX: address A4:C1:38:20:C2:AB, name ATC_20C2AB
^[[B^[[Aopenhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC -t 2023-01-10T16:20
Scanning for device A4:C1:38:34:A4:EC...
Didn't find device A4:C1:38:34:A4:EC.
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC -t 2023-01-10T16:20
Scanning for device A4:C1:38:34:A4:EC...
Writing time to device...
Synchronized time
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Didn't find device A4:C1:38:34:A4:EC.
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Writing time to device...
Traceback (most recent call last):
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 210, in set_clock_time
    await clock.set_time(timestamp, args.am_pm)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__init__.py", line 335, in set_time
    async with BleakClient(self.address) as client:
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/__init__.py", line 433, in __aenter__
    await self.connect()
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/__init__.py", line 471, in connect
    return await self._backend.connect(**kwargs)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/backends/bluezdbus/client.py", line 207, in connect
    dangerous_use_bleak_cache=dangerous_use_bleak_cache
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/backends/bluezdbus/client.py", line 591, in get_services
    self._device_path, dangerous_use_bleak_cache
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/backends/bluezdbus/manager.py", line 573, in get_services
    await self._wait_for_services_discovery(device_path)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/backends/bluezdbus/manager.py", line 672, in _wait_for_services_discovery
    raise BleakError("failed to discover services, device disconnected")
bleak.exc.BleakError: failed to discover services, device disconnected

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/openhabian/.local/bin/bluetooth-clocks", line 10, in <module>
    sys.exit(run())
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 28, in run
    asyncio.run(main(sys.argv[1:]))
  File "/usr/lib/python3.7/asyncio/runners.py", line 43, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
    return future.result()
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 41, in main
    await cli_args.func(cli_args)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 216, in set_clock_time
    except asyncio.exceptions.TimeoutError as exc:
AttributeError: module 'asyncio' has no attribute 'exceptions'
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Writing time to device...
Traceback (most recent call last):
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/backends/bluezdbus/client.py", line 177, in connect
    member="Connect",
  File "/home/openhabian/.local/lib/python3.7/site-packages/dbus_fast/aio/message_bus.py", line 371, in call
    await future
concurrent.futures._base.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 210, in set_clock_time
    await clock.set_time(timestamp, args.am_pm)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__init__.py", line 335, in set_time
    async with BleakClient(self.address) as client:
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/__init__.py", line 433, in __aenter__
    await self.connect()
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/__init__.py", line 471, in connect
    return await self._backend.connect(**kwargs)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/backends/bluezdbus/client.py", line 177, in connect
    member="Connect",
  File "/home/openhabian/.local/lib/python3.7/site-packages/async_timeout/__init__.py", line 129, in __aexit__
    self._do_exit(exc_type)
  File "/home/openhabian/.local/lib/python3.7/site-packages/async_timeout/__init__.py", line 212, in _do_exit
    raise asyncio.TimeoutError
concurrent.futures._base.TimeoutError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/openhabian/.local/bin/bluetooth-clocks", line 10, in <module>
    sys.exit(run())
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 28, in run
    asyncio.run(main(sys.argv[1:]))
  File "/usr/lib/python3.7/asyncio/runners.py", line 43, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
    return future.result()
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 41, in main
    await cli_args.func(cli_args)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 216, in set_clock_time
    except asyncio.exceptions.TimeoutError as exc:
AttributeError: module 'asyncio' has no attribute 'exceptions'
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Didn't find device A4:C1:38:34:A4:EC.
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Didn't find device A4:C1:38:34:A4:EC.
openhabian@openhabian:~ $ bluetooth-clocks set -a A4:C1:38:34:A4:EC
Scanning for device A4:C1:38:34:A4:EC...
Writing time to device...
Traceback (most recent call last):
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 210, in set_clock_time
    await clock.set_time(timestamp, args.am_pm)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__init__.py", line 335, in set_time
    async with BleakClient(self.address) as client:
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/__init__.py", line 433, in __aenter__
    await self.connect()
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/__init__.py", line 471, in connect
    return await self._backend.connect(**kwargs)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/backends/bluezdbus/client.py", line 190, in connect
    assert_reply(reply)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bleak/backends/bluezdbus/utils.py", line 20, in assert_reply
    raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.Failed] Operation already in progress

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/openhabian/.local/bin/bluetooth-clocks", line 10, in <module>
    sys.exit(run())
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 28, in run
    asyncio.run(main(sys.argv[1:]))
  File "/usr/lib/python3.7/asyncio/runners.py", line 43, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
    return future.result()
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 41, in main
    await cli_args.func(cli_args)
  File "/home/openhabian/.local/lib/python3.7/site-packages/bluetooth_clocks/__main__.py", line 216, in set_clock_time
    except asyncio.exceptions.TimeoutError as exc:
AttributeError: module 'asyncio' has no attribute 'exceptions'
openhabian@openhabian:~ $

So conclusion:

I’ve got 8 ATC thermometers - sorry forget about one . It is discovered when I set longer discovery time 60s.
Don’t know why but there is a problem with connecting to thermometer ( it was less than a 1m from rpi ) . It dosen’t connect everytime or there is error when writing settings . Only solution is removing battery from thermometer. I use new battery for sure.
The best one - if it connect properly it set good time !
The almost last one - as previously I can do more test if you need.
The last one - I use OMG with RF on ESP and TheengsGateway in container but is there a chance to add RF support to TheengsGateway ? I know that we need RF parts but Rpi has a lot GPIOs and that will be nice to reduce number of devices needed to run . Second thing is reducing energy consumption.

koenvervloesem · February 3, 2023, 11:01am

Ok, nice, thanks for the confirmation! So now you can set up automatic daily time synchronization with Theengs Gateway 0.8.0. Setting the options for the Docker container is still being tested.

I don’t think we can do much about the unreliability of discovery or connections.

Although adding RF support would definitely be interesting, there are currently no plans to extend Theengs Gateway’s protocol support beyond BLE.

Piatho · February 3, 2023, 4:54pm

Hi there
i have been using the docker container for a while now pushing data to my mqtt server. I am using a here a skill/instance of iobroker.

I must say i am a complete newbee o mqtt and may not fully understand the concepts.Proberly for that reason, i haven’t noticed that my server has generated millons of entries (topics) and thus slowed down performance.

I am actually only using the Theengs gateway for some LE bluetooth devices and was wondering if there is an option to only send topics for a selected list of MAC adresses (hence the sensors i would like to use.

Is there such a feature and i simply haven’t understood the concept or is there any other way to limit the bluetooth scanning to known devices?

Thanks
Thorben

1technophile · February 4, 2023, 2:18am

Hello,

Your server should not store the topics and payload unless they are retained.

You will find more infos below:

In particular the PUBLISH_ALL and DISCOVERY could be set to 0

Dom_KS · February 9, 2023, 7:51pm

Is there any chance to add support for YKYK01YL remote control ? It is a BT RC, it’s cheap and looks good.

Here is a something from Theengs-gateway:

DEBUG:BLEGateway:F8:24:41:EA:AC:B5 RSSI:-54 AdvertisementData(local_name='yee-rc', service_data={'0000fe95-0000-1000-8000-00805f9b34fb': b'P0S\x014\xb5\xac\xeaA$\xf8\x01\x10\x03\x00\x00\x02'}, rssi=-54)
INFO:BLEGateway:Sent `{"servicedatauuid": "fe95", "servicedata": "5030530134b5acea4124f8011003000002", "name": "yee-rc", "id": "F8:24:41:EA:AC:B5", "rssi": -54}` to topic `home/TheengsGateway/BTtoMQTT/F82441EAACB5`
DEBUG:BLEGateway:F8:24:41:EA:AC:B5 RSSI:-49 AdvertisementData(local_name='yee-rc', manufacturer_data={356: b'd\x01\x00\x00\x00\x004\x12\x01\xb5\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'}, service_data={'0000fe95-0000-1000-8000-00805f9b34fb': b'P0S\x01\r\xb5\xac\xeaA$\xf8\x01\x10\x03\x02\x00\x00'}, rssi=-60)

Here is info that it works with HA

Hans_Lree · February 9, 2023, 9:28pm

Hi @Dom_KS,

would you mind opening a discussion in Theengs Decoder Discussions at

for a more detailed communication and space for possible follow-up questions?

While I can see some similarly named Yeelight remotes in the HA ble-monitor compatibility section, your mentioned YKYK01YL doesn’t seem to be included, or was it a typo above? Which model do you have?

Also the fact that the entries mention that parts of the data is encrypted, which is out of the scope of Decoder at this stage, it might only be possible to get partial data, if any at all.

Best to be investigated together in the discussion thread.

Piatho · February 9, 2023, 11:13pm

Thanks for the reply.

To my understanding, the mqtt server in IOBROKER is storing every topic in an object to make them availble for scripts. The documentation indicates that it thereby not follows 100% the mqtt guidelines. To my understanding i could configure the Server to become a client and installing another “real” MQTT broker somewhere else. However in order to reduce complexity, i would prefer not to do.

I have checked the documentation, also set the two parameter to 0 but that does not stop the gateway to send all topics to the broker

1technophile · February 10, 2023, 1:16am

With PUBLISH_ALL at 0 you should only see decoded sensors. Do you see other devices ?

koenvervloesem · February 10, 2023, 9:08am

Thanks for pointing this out, there’s an error in the way the gateway processes the publish_all parameter, so it ignores this when you set it to 0 on the command line. The fix will be in the next release of Theengs Gateway.

For now you can always set the value of the "publish_all" key in your theengsgw.conf file to 0, this works.