-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
Adjust Zooz ZSE42 battery types #1910
Comments
This device was recently discussed here |
Thanks for the link to the discussion section (the one place I didn't check). Does setting it to manual prevent it from being updated automatically by a new device request issue? The reason I opened this issue is that it used to work in manual mode for me for the past couple of months and then recently I got a new ZSE42 and it was suggesting an incorrect battery again. Maybe my library version was out of date since I see the current main branch has it set correctly. |
It was changed back to Manual only a few days ago, you should get the library updated daily unless there was a problem the last time it tried to update. |
That was my suggestion with this feature request. Thanks for the explanation! |
Checklist
Is your feature request related to a problem? Please describe.
Zooz has multiple versions of the ZSE42. Older models use the CR2032 battery. Newer models use the CR2450 battery. This seems to be getting changed regularly in the device listing as people with different models fill out new device requests.
Most recently this was changed in #1496
Describe the solution you'd like
I'd like there to be a way to either differentiate between the two devices (and store both in the device listing) or to prevent updates to this device from being populated automatically into the device listing. In the current architecture, this device needs to be kept at "MANUAL"
Related discussions have happened in #1266, #1228 (comment)
Describe alternatives you've considered
Alternatively, users can maintain their own device listing, but that seems like a bad idea.
Additional context
N/A
The text was updated successfully, but these errors were encountered: