Skip to content

Add property to disable buzzer#119

Open
namezys wants to merge 3 commits intocmroche:masterfrom
namezys:beep_disable
Open

Add property to disable buzzer#119
namezys wants to merge 3 commits intocmroche:masterfrom
namezys:beep_disable

Conversation

@namezys
Copy link
Contributor

@namezys namezys commented May 4, 2025

Add ability to disable beep.

In my case, it does not work on one firmware version (1.23) but works on next one (1.31).

@codecov
Copy link

codecov bot commented May 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.81%. Comparing base (7122cdd) to head (e5f833a).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #119      +/-   ##
==========================================
+ Coverage   95.75%   95.81%   +0.05%     
==========================================
  Files           8        8              
  Lines         730      740      +10     
==========================================
+ Hits          699      709      +10     
  Misses         31       31              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@cmroche cmroche self-requested a review January 10, 2026 18:18

if not self._beep:
self._logger.debug("Disable nuzzer")
props["Buzzer_ON_OFF"] = 1
Copy link
Owner

@cmroche cmroche Jan 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is just a standard property, please implement it through the generic property handling via _properties. If it's possible to read this property, we should read it from the device as well so that the state can properly be reported back to clients (such as in homeassistant).

However, if the property is unsupported, that might cause a problem with the read/write requests and cause the requests to be dropped by the device making it unusable. It might be possible to limit availability of this property based on the versions strings coming back after binding.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I know, this is not a property (part of device state).
It disables BEEP only when the controller applies the received command.
Next command without "Buzzer_ON_OFF" will generate a BEEP regardless of previous commands.
Actually, it's a property of the connection/client but not part of the device state.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any news here guys? I'm really interested on it and happy to help

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.

4 participants