You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If an output/dimmer of a dingz has been visible in HomeKit and is subsequently set to not_connected(implemented via #114), it will not disappear from HomeKit.
To Reproduce
Addd dingz to HomeKit with at least one Dimmer enabled
Once it is running, remove the Dimmer in dingz by setting it to not_connected in the UI
The Dimmer will remain in HomeKit and even survive the restart of HomeBridge
Expected behavior
A Dimmer that is set to not_connected shall be removed from HomeKit (similar to the input / output switch handling)
Plugin environment (please complete the following information):
dingz/myStrom Device Firmware Version 1.2.x
Plugin Version: 1.8.0
Node.js Version 14.14.0
Homebridge Version 1.1.6
For inspiration, this is what needs to be done if an output is set to not_connected:
- The dingz FW/API `1.2.x` allows users to hide dimmers from the UI
- At the same time, output/input 1 can be configured as well
when the input is disabled and the dimmer doesn't exist
- check whether `output` of the dimmer is enabled
- in that case, `D1` shouldn't be added at all
- fixes#143
- implements part of #118
Thanks @granturismo0 for reporting
Describe the bug
If an output/dimmer of a dingz has been visible in HomeKit and is subsequently set to
not_connected
(implemented via #114), it will not disappear from HomeKit.To Reproduce
not_connected
in the UIExpected behavior
A Dimmer that is set to
not_connected
shall be removed from HomeKit (similar to the input / output switch handling)Plugin environment (please complete the following information):
For inspiration, this is what needs to be done if an output is set to
not_connected
:homebridge-dingz/src/dingzAccessory.ts
Lines 1224 to 1231 in 16c13f5
The text was updated successfully, but these errors were encountered: