Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[shelly] BLU HT - sensor channels missing #16736

Closed
ijasan opened this issue May 10, 2024 · 3 comments · Fixed by #16746
Closed

[shelly] BLU HT - sensor channels missing #16736

ijasan opened this issue May 10, 2024 · 3 comments · Fixed by #16746
Assignees
Labels
bug An unexpected problem or unintended behavior of an add-on PR pending There is a pull request for resolving the issue

Comments

@ijasan
Copy link

ijasan commented May 10, 2024

Binding version: SNAPSHOT 4.2.0.202404071245

The BLU HT device only shows the standard channels after discovery. The temperature and humidity sensor channels are not generated.

grafik

The log file from adding the device:
openhab_BLU_SBHT.log

The script console output on the gateway device shows when BT button is pressed:
BTH: unknown type

@ijasan ijasan added the bug An unexpected problem or unintended behavior of an add-on label May 10, 2024
@ijasan
Copy link
Author

ijasan commented May 10, 2024

I found out that some sensor id definitions were incorrect and some were missing.

Based on the documentation at:
https://shelly-api-docs.shelly.cloud/docs-ble/Devices/ht
and
https://bthome.io/format

the definitions should be adjusted:

Typo in line "BTH[0x43] = { n: "UVIndex", t: uint8 };" --> wrong ID, should be 0x46.

According to Shelly documentation above, BLU HT uses the following ID's for the temperature and humidity sensor:

BTH[0x2e] = { n: "Humidity", t: uint8 };
BTH[0x45] = { n: "Temperature", t: int16, f: 0.1 };

These two must be added to the script. The sensors are then recognized and the two missing channels are generated by the binding.

In addition, the other definitions should also be checked. For example, the factor for sensor 0x51 "Acceleration" is 0.01, which differs from the documentation. Here 0.001 is specified.

@markus7017 markus7017 self-assigned this May 11, 2024
@markus7017
Copy link
Contributor

markus7017 added a commit to markus7017/openhab-addons that referenced this issue May 11, 2024
…enhab#16735

Signed-off-by: Markus Michels <markus7017@gmail.com>
@markus7017 markus7017 added PR pending There is a pull request for resolving the issue and removed awaiting feedback labels May 27, 2024
@markus7017
Copy link
Contributor

verified @ijasan

lsiepel pushed a commit that referenced this issue May 28, 2024
…V set temp (#16746)

* fixes ##16736, #16734, #16542, #16709, #16735

Signed-off-by: Markus Michels <markus7017@gmail.com>
psmedley pushed a commit to psmedley/openhab-addons that referenced this issue Jun 15, 2024
…V set temp (openhab#16746)

* fixes #openhab#16736, openhab#16734, openhab#16542, openhab#16709, openhab#16735

Signed-off-by: Markus Michels <markus7017@gmail.com>
Signed-off-by: Paul Smedley <paul@smedley.id.au>
markus7017 added a commit to markus7017/openhab-addons that referenced this issue Jun 21, 2024
…enhab#16735

Signed-off-by: Markus Michels <markus7017@gmail.com>
pgfeller pushed a commit to pgfeller/openhab-addons that referenced this issue Sep 29, 2024
…V set temp (openhab#16746)

* fixes #openhab#16736, openhab#16734, openhab#16542, openhab#16709, openhab#16735

Signed-off-by: Markus Michels <markus7017@gmail.com>
Signed-off-by: Patrik Gfeller <patrik.gfeller@proton.me>
joni1993 pushed a commit to joni1993/openhab-addons that referenced this issue Oct 15, 2024
matchews pushed a commit to matchews/openhab-addons that referenced this issue Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior of an add-on PR pending There is a pull request for resolving the issue
Projects
None yet
2 participants