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

Add support for BHI-US Bosch Universal Switch II #6651

Merged
merged 1 commit into from
Dec 7, 2023

Conversation

slugzero
Copy link
Contributor

@slugzero slugzero commented Dec 7, 2023

Adds support for the Bosch BHI-US Universal Switch II.

This converter requires a new manufacturer specific cluster:
Koenkk/zigbee-herdsman#820

@Koenkk Koenkk merged commit 7adcbfc into Koenkk:master Dec 7, 2023
2 checks passed
@Koenkk
Copy link
Owner

Koenkk commented Dec 7, 2023

Thanks!

@slugzero slugzero deleted the BHI-US branch December 7, 2023 20:59
@mldytech
Copy link
Contributor

Hi @slugzero, first of all thanks for adding support for this device. I noticed that the actual button presses are not exposed in the zigbee2mqtt webinterface and are also not available (at least not out of the box) in e. g. homeassistant.

Nevertheless, when pressing a button, it seems working and the MQTT messages are correct (e. g. for short press upper left):
zigbee2mqtt/friendly-name/action: button_top_left_release

Since I'm not very familiar with this project, is there anything I could do to get this device working as intended? I would be grateful for any suggestions and am also willing to do some work / get into the project.

@slugzero
Copy link
Contributor Author

Hi @mldytech, you are right, the action expose is missing from the device definition. Note that it should work in Home Assistant nonetheless: Make sure you have sent all actions at least once (i.e. press and long press all four buttons) while HA is running. After that, the entries should show up in the list of device triggers.

It will take me a little while to change this, because the device is in my "productive" network rn. But if you'd like to give it a try yourself: Adding

e.action(['button_top_left_release',
	'button_top_right_release',
	'button_bottom_left_release',,
	'button_bottom_right_release',
	'button_top_left_longpress',
	'button_top_right_longpress',
	'button_bottom_left_longpress',
	'button_bottom_right_longpress',
	'button_top_left_longpress_release',
	'button_top_right_longpress_release',
	'button_bottom_left_longpress_release',
	'button_bottom_right_longpress_release']),

to the list of exposes in

should fix it.

The simplest way to do and test this is probably to copy over the device definition to a custom converter file as described here: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

@mldytech
Copy link
Contributor

@slugzero Thank you very much for your answer. You're right, the entries were already visible in HA.

I appreciate your tips / guide and will definitely give it a try on the weekend!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants