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

Homekit Dimmer/Fan Switch always turns on to 100% #10

Open
c0d3r22 opened this issue Feb 2, 2024 · 4 comments
Open

Homekit Dimmer/Fan Switch always turns on to 100% #10

c0d3r22 opened this issue Feb 2, 2024 · 4 comments

Comments

@c0d3r22
Copy link

c0d3r22 commented Feb 2, 2024

Issue: When turning on a dimmer switch from Apple Home there are two commands being sent out: one to turn it on and one to set the level=100 which overwrites any previously set dimmer levels.
Update: This issue seems to also happen with Fans where it sends on and level=100 ignoring the last setting

I know this probably is an Apple issue but I would hope there is a way to capture the commands from the bridged z-way device and filter out level=99 or level=100 so that if the dimmer value is anything other than 99-100 (some z-wave dimmers only go to 99) then it would simply send the 'on' command and it will turn on to the last know brightness set by the user or through an automation.

@c0d3r22
Copy link
Author

c0d3r22 commented Feb 2, 2024

I would assume something could be added here? https://github.com/jmichas/homebridge-zway-plugin/blob/master/index.js#L815-L838

@c0d3r22 c0d3r22 changed the title Homekit Dimmer Switch always turns on to 100% Homekit Dimmer/Fan Switch always turns on to 100% Feb 2, 2024
@c0d3r22
Copy link
Author

c0d3r22 commented Feb 12, 2024

After doing some digging the call to ZAutomation/api/v1/devices in the poll update is where this 'bug' lies. It's not really a bug, it's how the zwave devices are setup and which association reports are being sent to the controller. In my case, this poll update would always receive 100 as the brightness/rotationSpeed level as that value wasn't being relayed properly to the controller. This could be handled by adding something that keeps track of those values locally and then replacing the polled value if they don't match. Food for thought I guess

@jmichas
Copy link
Owner

jmichas commented Feb 12, 2024

Yeah, sorry, I have to look at this, I haven't had much time.
I have maybe 30 dimmers and some fan controllers in my house and I don't notice the behavior that you describe.
What brand of dimmers are they?

Just so I am clear, you are saying when homebridge polls for device updates it is then receiving the wrong dimmer value from the controller?
Then the new polled dimmer value is cached in homebridge or the device is actually set to newly polled value?

Or is the zway controller receiving the wrong value from the device?

@c0d3r22
Copy link
Author

c0d3r22 commented Feb 16, 2024

So I'm using a razberry 7 running zway and I have a bunch of Zooz zen72 dimmer switches. From what I could debug the zway call to get device states was reporting 100% whenever I turned one on regardless of the previous state. It could be that the switches aren't reporting the right value back to the controller so that it can report to the zway api?

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