-
Notifications
You must be signed in to change notification settings - Fork 6
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
[FIX] refactor dingz.updateAccessory #103
Comments
Issues #116, #118, #120 and #123 are all related to the fact that this part of the code is still quite a mess. I will therefore do two things:
I hope this will eventually solve these issues and cure the sick patient that |
Also of importance to all this: |
Things to be fixed in
Question: must we call this method really regularly or would it be sufficient to update on start? |
- Add new event types - Emit a `DingzEvent.REQUEST_STATE_UPDATE` - Accessories subscribe to this instead of having their own timers - Works towards [FIX] refactor dingz.updateAccessory #103
- will eventually integrate all `_config` functions into one method - work towards [FIX] refactor dingz.updateAccessory #103
- Put device discovery back into the `dingz` - Move to static discovery functions (`dingz`, `platform`) - myStrom still need migration - work [FIX] refactor dingz.updateAccessory #103
- fetching of config updates is much more robust and centralized - updated firmware versions are now picked up reliably - dingz accessory constructor is simplified - Work towards implementing [FIX] refactor dingz.updateAccessory #103
- don't attempt any longer to catch all configuration changes - should throw an unrecoverable error though - update dimmer name changes - fixes #103
Describe the enhancement
The
updateAccessory()
method of the dingz accessory needs refactoring:DingzEvent.UPDATE_INFO
to initiate an accessory UpdategetDingzDeviceInfo()
andplatform.getDingzDeviceInfo
Examples and context
homebridge-dingz/src/dingzAccessory.ts
Lines 1126 to 1156 in f33d1de
The text was updated successfully, but these errors were encountered: