Support for HEM-6161T-D (RS3 IntelliIT)

[cyroxx]

Hi,

I have a HEM-6161T-D and would be willing to test a few things.

So far I have tried to connect it with the following device profiles both under Linux Mint (so Debian-based) and Win 11, but it always failed during the pairing phase (as far as I can tell):

• HEM-7361T
• HEM-7322T
• HEM-7600T

I will add the terminal output after I redacted it.

[cyroxx]

Win11 results

It always gives bleak.exc.BleakError: Could not pair with device: FAILED:

(.venv) PS omblepy> python ./omblepy.py -p -d HEM-7361T
2025-10-17 05:42:14,988 - omblepy - INFO - Attempt to import module for device hem-7361t
To improve your chance of a successful connection please do the following:
 -remove previous device pairings in your OS's bluetooth dialog
 -enable bluetooth on you omron device and use the specified mode (pairing or normal)
 -do not accept any pairing dialog until you selected your device in the following list

Select your Omron device from the list below...

+----+-------------------+-------------------------------+------+
| ID | MAC               | NAME                          | RSSI |
+----+-------------------+-------------------------------+------+
| .  | ...               | ...                           | ...  |
+----+-------------------+-------------------------------+------+

Enter ID or just press Enter to rescan.
1
2025-10-17 05:42:23,471 - omblepy - INFO - Attempt connecting to XX:XX:XX:XX:XX:XX.
2025-10-17 05:42:28,988 - omblepy - INFO - unpair and disconnect
Traceback (most recent call last):
  File "omblepy\omblepy.py", line 395, in <module>
    asyncio.run(main())
    ~~~~~~~~~~~^^^^^^^^
  File "C:\Program Files\Python313\Lib\asyncio\runners.py", line 194, in run
    return runner.run(main)
           ~~~~~~~~~~^^^^^^
  File "C:\Program Files\Python313\Lib\asyncio\runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
  File "C:\Program Files\Python313\Lib\asyncio\base_events.py", line 720, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "omblepy\omblepy.py", line 364, in main
    await bleClient.pair(protection_level = 2)
  File "omblepy\.venv\Lib\site-packages\bleak\__init__.py", line 602, in pair     
    await self._backend.pair(*args, **kwargs)
  File "omblepy\.venv\Lib\site-packages\bleak\backends\winrt\client.py", line 624, in pair
    raise BleakError(
        f"Could not pair with device: {pairing_result.status.name}"
    )
bleak.exc.BleakError: Could not pair with device: FAILED

(.venv) PS omblepy> python ./omblepy.py -p -d HEM-7322T
2025-10-17 05:42:54,781 - omblepy - INFO - Attempt to import module for device hem-7322t
To improve your chance of a successful connection please do the following:
 -remove previous device pairings in your OS's bluetooth dialog
 -enable bluetooth on you omron device and use the specified mode (pairing or normal)
 -do not accept any pairing dialog until you selected your device in the following list

Select your Omron device from the list below...
+----+-------------------+-------------------------------+------+
| ID | MAC               | NAME                          | RSSI |
+----+-------------------+-------------------------------+------+
| .  | ...               | ...                           | ...  |
+----+-------------------+-------------------------------+------+
Enter ID or just press Enter to rescan.
2
2025-10-17 05:43:02,482 - omblepy - INFO - Attempt connecting to XX:XX:XX:XX:XX:XX.
2025-10-17 05:43:11,714 - omblepy - INFO - unpair and disconnect
Traceback (most recent call last):
  File "omblepy\omblepy.py", line 395, in <module>
    asyncio.run(main())
    ~~~~~~~~~~~^^^^^^^^
  File "C:\Program Files\Python313\Lib\asyncio\runners.py", line 194, in run
    return runner.run(main)
           ~~~~~~~~~~^^^^^^
  File "C:\Program Files\Python313\Lib\asyncio\runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
  File "C:\Program Files\Python313\Lib\asyncio\base_events.py", line 720, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "omblepy\omblepy.py", line 364, in main
    await bleClient.pair(protection_level = 2)
  File "omblepy\.venv\Lib\site-packages\bleak\__init__.py", line 602, in pair     
    await self._backend.pair(*args, **kwargs)
  File "omblepy\.venv\Lib\site-packages\bleak\backends\winrt\client.py", line 624, in pair
    raise BleakError(
        f"Could not pair with device: {pairing_result.status.name}"
    )
bleak.exc.BleakError: Could not pair with device: FAILED
(.venv) PS omblepy> python ./omblepy.py -p -d HEM-7600T
2025-10-17 05:43:37,618 - omblepy - INFO - Attempt to import module for device hem-7600t
To improve your chance of a successful connection please do the following:
 -remove previous device pairings in your OS's bluetooth dialog
 -enable bluetooth on you omron device and use the specified mode (pairing or normal)
 -do not accept any pairing dialog until you selected your device in the following list

Select your Omron device from the list below...
+----+-------------------+-------------------------------+------+
| ID | MAC               | NAME                          | RSSI |
+----+-------------------+-------------------------------+------+
| .  | ...               | ...                           | ...  |
+----+-------------------+-------------------------------+------+
Enter ID or just press Enter to rescan.
1
2025-10-17 05:43:45,421 - omblepy - INFO - Attempt connecting to XX:XX:XX:XX:XX:XX.
2025-10-17 05:43:52,268 - omblepy - INFO - unpair and disconnect
Traceback (most recent call last):
  File "omblepy\omblepy.py", line 395, in <module>
    asyncio.run(main())
    ~~~~~~~~~~~^^^^^^^^
  File "C:\Program Files\Python313\Lib\asyncio\runners.py", line 194, in run
    return runner.run(main)
           ~~~~~~~~~~^^^^^^
  File "C:\Program Files\Python313\Lib\asyncio\runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
  File "C:\Program Files\Python313\Lib\asyncio\base_events.py", line 720, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "omblepy\omblepy.py", line 364, in main
    await bleClient.pair(protection_level = 2)
  File "omblepy\.venv\Lib\site-packages\bleak\__init__.py", line 602, in pair     
    await self._backend.pair(*args, **kwargs)
  File "omblepy\.venv\Lib\site-packages\bleak\backends\winrt\client.py", line 624, in pair
    raise BleakError(
        f"Could not pair with device: {pairing_result.status.name}"
    )
bleak.exc.BleakError: Could not pair with device: FAILED

[userx14]

The pairing process is independent of the device driver that is in use.

For win 11 the problem is that the pairing dialog timeout is so short, that there is no reliable way to accept it fast enough. If one very quickly accepts it, one can get it to work <10% of the time. I have reported this issue for the bluetooth library that the project is based on, but it seems that they also have no way to influence this timeout behavior. I have considered testing the simplepyble library instead, but did not get to it.

For linux mind I do not have any experience, but observed problems with ble with other debian based distributions.
Here the issue was that bluetooth attributes and services of the omron device were not showing up, even in in other tools like bluetoothctl or gatttool.

So possible ideas would be:

• test if the pairing process works with https://codeberg.org/LazyT/ubpm on win11
• if you have an esp32 microcontroller you can try the https://github.com/userx14/omblepy/tree/esp32bridge version, that bypasses the os blueotooth stack.
• testing with a different linux distro (maybe in live boot environment), I had success with nixos 25 in the past

[cyroxx]

Thank you for the explanation.
I will probably try the win11 and esp32 ideas soon.

For the sake of completeness, here are the results from my tests under Mint:

(.venv) ~/Entwicklung/omblepy$ python ./omblepy.py -p -d HEM-7361T
2025-10-16 20:22:08,652 - omblepy - INFO - Attempt to import module for device hem-7361t
To improve your chance of a successful connection please do the following:
 -remove previous device pairings in your OS's bluetooth dialog
 -enable bluetooth on you omron device and use the specified mode (pairing or normal)
 -do not accept any pairing dialog until you selected your device in the following list

Select your Omron device from the list below...
+----+-------------------+-------------------------------+------+
| ID | MAC               | NAME                          | RSSI |
+----+-------------------+-------------------------------+------+
| .  | ...               | ...                           | ...  |
+----+-------------------+-------------------------------+------+

2025-10-16 20:23:48,979 - omblepy - INFO - Attempt connecting to XX:XX:XX:XX:XX:XX.
2025-10-16 20:23:56,209 - omblepy - INFO - unpair and disconnect
2025-10-16 20:23:56,252 - omblepy - ERROR - Bleak AssertionError during disconnect. This usually happens when using the bluezdbus adapter.
2025-10-16 20:23:56,252 - omblepy - ERROR - You can find the upstream issue at: https://github.com/hbldh/bleak/issues/641
2025-10-16 20:23:56,252 - omblepy - ERROR - AssertionError details: 
Traceback (most recent call last):
  File "/home/cyroxx/Entwicklung/omblepy/./omblepy.py", line 395, in <module>
    asyncio.run(main())
  File "/usr/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/cyroxx/Entwicklung/omblepy/./omblepy.py", line 364, in main
    await bleClient.pair(protection_level = 2)
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/__init__.py", line 602, in pair
    await self._backend.pair(*args, **kwargs)
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/backends/bluezdbus/client.py", line 521, in pair
    assert_reply(reply)
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/backends/bluezdbus/utils.py", line 27, in assert_reply
    raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.AuthenticationFailed] Authentication Failed
(.venv) ~/Entwicklung/omblepy$ python ./omblepy.py -p -d HEM-7322T
2025-10-16 20:28:49,706 - omblepy - INFO - Attempt to import module for device hem-7322t
To improve your chance of a successful connection please do the following:
 -remove previous device pairings in your OS's bluetooth dialog
 -enable bluetooth on you omron device and use the specified mode (pairing or normal)
 -do not accept any pairing dialog until you selected your device in the following list

Select your Omron device from the list below...
+----+-------------------+-------------------------------+------+
| ID | MAC               | NAME                          | RSSI |
+----+-------------------+-------------------------------+------+
| .  | ...               | ...                           | ...  |
+----+-------------------+-------------------------------+------+
Enter ID or just press Enter to rescan.
2
2025-10-16 20:28:58,507 - omblepy - INFO - Attempt connecting to XX:XX:XX:XX:XX:XX.
2025-10-16 20:29:08,654 - omblepy - INFO - unpair and disconnect
Traceback (most recent call last):
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/backends/bluezdbus/client.py", line 299, in connect
    reply = await self._bus.call(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/dbus_fast/aio/message_bus.py", line 398, in call
    await future
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/cyroxx/Entwicklung/omblepy/./omblepy.py", line 395, in <module>
    asyncio.run(main())
  File "/usr/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/cyroxx/Entwicklung/omblepy/./omblepy.py", line 362, in main
    await bleClient.connect()
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/__init__.py", line 580, in connect
    await self._backend.connect(self._pair_before_connect, **kwargs)
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/backends/bluezdbus/client.py", line 156, in connect
    async with async_timeout(timeout):
  File "/usr/lib/python3.12/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
(.venv) ~/Entwicklung/omblepy$ python ./omblepy.py -p -d HEM-7322T
2025-10-16 20:29:27,324 - omblepy - INFO - Attempt to import module for device hem-7322t
To improve your chance of a successful connection please do the following:
 -remove previous device pairings in your OS's bluetooth dialog
 -enable bluetooth on you omron device and use the specified mode (pairing or normal)
 -do not accept any pairing dialog until you selected your device in the following list

Select your Omron device from the list below...
+----+-------------------+-------------------------------+------+
| ID | MAC               | NAME                          | RSSI |
+----+-------------------+-------------------------------+------+
| .  | ...               | ...                           | ...  |
+----+-------------------+-------------------------------+------+
Enter ID or just press Enter to rescan.
3
2025-10-16 20:29:36,296 - omblepy - INFO - Attempt connecting to XX:XX:XX:XX:XX:XX.
2025-10-16 20:29:46,455 - omblepy - INFO - unpair and disconnect
Traceback (most recent call last):
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/backends/bluezdbus/client.py", line 299, in connect
    reply = await self._bus.call(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/dbus_fast/aio/message_bus.py", line 398, in call
    await future
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/cyroxx/Entwicklung/omblepy/./omblepy.py", line 395, in <module>
    asyncio.run(main())
  File "/usr/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/cyroxx/Entwicklung/omblepy/./omblepy.py", line 362, in main
    await bleClient.connect()
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/__init__.py", line 580, in connect
    await self._backend.connect(self._pair_before_connect, **kwargs)
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/backends/bluezdbus/client.py", line 156, in connect
    async with async_timeout(timeout):
  File "/usr/lib/python3.12/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
(.venv) ~/Entwicklung/omblepy$ python ./omblepy.py -p -d HEM-7600T
2025-10-16 20:30:25,656 - omblepy - INFO - Attempt to import module for device hem-7600t
To improve your chance of a successful connection please do the following:
 -remove previous device pairings in your OS's bluetooth dialog
 -enable bluetooth on you omron device and use the specified mode (pairing or normal)
 -do not accept any pairing dialog until you selected your device in the following list

Select your Omron device from the list below...
+----+-------------------+-------------------------------+------+
| ID | MAC               | NAME                          | RSSI |
+----+-------------------+-------------------------------+------+
| .  | ...               | ...                           | ...  |
+----+-------------------+-------------------------------+------+
Enter ID or just press Enter to rescan.
3
2025-10-16 20:30:33,327 - omblepy - INFO - Attempt connecting to XX:XX:XX:XX:XX:XX.
2025-10-16 20:30:38,957 - omblepy - INFO - unpair and disconnect
2025-10-16 20:30:39,002 - omblepy - ERROR - Bleak AssertionError during disconnect. This usually happens when using the bluezdbus adapter.
2025-10-16 20:30:39,002 - omblepy - ERROR - You can find the upstream issue at: https://github.com/hbldh/bleak/issues/641
2025-10-16 20:30:39,002 - omblepy - ERROR - AssertionError details: 
Traceback (most recent call last):
  File "/home/cyroxx/Entwicklung/omblepy/./omblepy.py", line 395, in <module>
    asyncio.run(main())
  File "/usr/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/cyroxx/Entwicklung/omblepy/./omblepy.py", line 364, in main
    await bleClient.pair(protection_level = 2)
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/__init__.py", line 602, in pair
    await self._backend.pair(*args, **kwargs)
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/backends/bluezdbus/client.py", line 521, in pair
    assert_reply(reply)
  File "/home/cyroxx/Entwicklung/omblepy/.venv/lib/python3.12/site-packages/bleak/backends/bluezdbus/utils.py", line 27, in assert_reply
    raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.AuthenticationFailed] Authentication Failed

[cyroxx]

WIth the help of ubpm wiki I just figured out how to do it correctly - doing a long press on the bluetooth button until the P appears.

So I got this to work on win11 on first try, without any special interaction:

Select your Omron device from the list below...
+----+-------------------+-------------------------------+------+
| ID | MAC               | NAME                          | RSSI |
+----+-------------------+-------------------------------+------+
| .  | ...               | ...                           | ...  |
+----+-------------------+-------------------------------+------+
Enter ID or just press Enter to rescan.
2
2025-10-18 05:30:17,708 - omblepy - INFO - Attempt connecting to ....
2025-10-18 05:30:34,123 - omblepy - INFO - Paired device successfully with new key bytearray(b'...').
2025-10-18 05:30:34,124 - omblepy - INFO - From now on you can connect omit the -p flag, even on other PCs with different bluetooth-mac-addresses.
2025-10-18 05:30:34,862 - omblepy - INFO - unpair and disconnect

[userx14]

Very nice. Now you can connect without the -p commandline option and with a short press of the bluetooth button.
I have to admit, I did not test with win11 in the last year, maybe things have improved.
For the device driver, I have some prototype file prepared in this branch: https://github.com/userx14/omblepy/tree/hem6161
Maybe the record format is identical to hem6232t. If not, the only way is to compare the readout records with what the device displays and compare.

[userx14]

Win 11 behavior seems to have changed from the last time I tested. Now the pairing dialog already shows up when calling .connect(). With an added delay one has enough time to accept the pairing dialog, I updated the main branch with the required change.

[cyroxx]

Very nice. Now you can connect without the -p commandline option and with a short press of the bluetooth button. I have to admit, I did not test with win11 in the last year, maybe things have improved. For the device driver, I have some prototype file prepared in this branch: https://github.com/userx14/omblepy/tree/hem6161 Maybe the record format is identical to hem6232t. If not, the only way is to compare the readout records with what the device displays and compare.

It actually works!
I was able to perform a measurement and then extract it (and the previous measurements), using the hem-6232t logic.

There were a few records where the parsing failed.
I leave them here for the sake of documentation/debugging, in case it might be helpful for further debugging/reverse engineering.

2025-10-21 13:41:12,213 - omblepy - WARNING - Error parsing record for user1 at offset 420 data 00640b6b02750d95f2b3ffffffff, ignoring this record.
2025-10-21 13:41:16,581 - omblepy - WARNING - Error parsing record for user2 at offset 308 data ffffffffffffffffffffffff0161, ignoring this record.
2025-10-21 13:41:16,581 - omblepy - WARNING - Error parsing record for user2 at offset 322 data 0040000000000000000000000000, ignoring this record.
2025-10-21 13:41:16,581 - omblepy - WARNING - Error parsing record for user2 at offset 336 data 0000000000000000000000000000, ignoring this record.
2025-10-21 13:41:16,581 - omblepy - WARNING - Error parsing record for user2 at offset 350 data 0000011800060095000900060000, ignoring this record.
2025-10-21 13:41:16,581 - omblepy - WARNING - Error parsing record for user2 at offset 364 data 00000000000d0005000100300001, ignoring this record.
2025-10-21 13:41:16,581 - omblepy - WARNING - Error parsing record for user2 at offset 378 data 0008000000020000001200b10000, ignoring this record.

Detailed parsing info for these records:

{'dia': 0, 'sys': 125, 'bpm': 107, 'ihb': 0, 'mov': 0}
(2011, 0, 19, 21, 54, 21)
Error parsing record 00640b6b02750d95f2b3ffffffff: month must be in 1..12

{'dia': 255, 'sys': 280, 'bpm': 255, 'ihb': 1, 'mov': 1}
(2063, 15, 31, 31, 63, 59)
Error parsing record ffffffffffffffffffffff0161: month must be in 1..12

{'dia': 0, 'sys': 89, 'bpm': 0, 'ihb': 0, 'mov': 0}
(2000, 0, 0, 0, 0, 0)
Error parsing record 0040000000000000000000000000: month must be in 1..12

{'dia': 0, 'sys': 25, 'bpm': 0, 'ihb': 0, 'mov': 0}
(2000, 0, 0, 0, 0, 0)
Error parsing record 0000000000000000000000000000: month must be in 1..12

{'dia': 0, 'sys': 25, 'bpm': 24, 'ihb': 0, 'mov': 0}
(2001, 0, 0, 6, 2, 21)
Error parsing record 0000011800060095000900060000: month must be in 1..12

{'dia': 0, 'sys': 25, 'bpm': 0, 'ihb': 0, 'mov': 0}
(2000, 0, 0, 13, 0, 5)
Error parsing record 00000000000d0005000100300001: month must be in 1..12

{'dia': 0, 'sys': 33, 'bpm': 0, 'ihb': 0, 'mov': 0}
(2000, 0, 0, 2, 0, 0)
Error parsing record 0008000000020000001200b10000: month must be in 1..12

PS: I just realized that you use file names with dashes for the device-specific drivers, which makes importing them unnecessary complicated. Is there any particular reason for that? Since you normalize the device name anyway, you might use underscores instead.

[userx14]

Thanks for the update, so I can copy the record logic from hem-6232t and merge the testing branch.
The good records look the same as the data displayed by the device I assume?

if you have fewer than 30 records, there might be "trash data" in the remaining data slots. One way to avoid reading these is analyzing the "settings region" that stores the currently valid records, and which one of them were not transfered yet. I have this implemented for some other devices.

For the driver name the dash is a choice without much thought. I did not even notice any problem, as the importing logic based on the commandline arg here does not seem to care:

omblepy/omblepy.py

Line 339 in 51394f4

deviceSpecific = __import__(deviceName.lower())

If you have some usecase where you manually import them in other code, I can see the problem with the dash in the name. Is that what you mean? Would be willing to change them to _ in this case.