Safeguard default not working in all cases#14
Closed
While merging my last pull request containing the "safeguard", you made a few changes to my proposal. Instead of having a config option to switch the safeguard on or off, you made it the default (which I fully support) and removed the config option. However, you only changed it for the case when homebridge is not able to receive devices/homeegrams due to a time-out (lines 63/64). The other case where no devices/homeegrams can be retrieved due to an incorrect group name (lines 139-141) still requires the safeGuard config parameter, defaulted to false in line 38 and not documented anymore. Is this behaviour intended or did you just miss that second case?
AI Analysis
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by FlyingLemming and has received 1 comments.
Add a comment
Comment form would go here