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

Initial volume not always being set correctly #16

Open
kiwi64ajs opened this issue Mar 1, 2022 · 1 comment
Open

Initial volume not always being set correctly #16

kiwi64ajs opened this issue Mar 1, 2022 · 1 comment

Comments

@kiwi64ajs
Copy link

Hmmm... I've been having some issues with the initial Zone turn-on as the Zone can end up showing 70% (my setting) on the Home app icon but the zone is still silent (or maybe very quiet as its in the next room to my desk).
There must be a race condition here as what I've ended up doing for now is to use NodeRed to send a { "Brightness": 69 } and then half a second later send { "Brightness": 70 } and it seems to work more reliably although its not gotten much of a workout yet.

On the "Homebridge Settings" page I can see a "Homebridge Debug Mode -D" switch to enable logging but is there a way to selectively enable DEBUG for just your plug-in? Perhaps put some magic string into the Environment Variable fields "DEBUG" or "NODE_OPTIONS" fields below the Debug Mode switch.

@Willmac16
Copy link
Owner

As far as I know, the official logging setup for homebridge only has bridge wide debug mode. You may be able to run homebridge in a child bridge or something to focus on the nuvo debug, but I've generally just ignored/disabled other plugins that are filling the log when I need to focus on nuvo.

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

No branches or pull requests

2 participants