Skip to content

Automatically detect bticino configuration#13

Draft
s0ullight wants to merge 2 commits intoslyoldfox:mainfrom
s0ullight:feature/auto-detect
Draft

Automatically detect bticino configuration#13
s0ullight wants to merge 2 commits intoslyoldfox:mainfrom
s0ullight:feature/auto-detect

Conversation

@s0ullight
Copy link

This PR aims to automatically detect devices from the BTicino mymodules configuration file.
Currently locks are detected and exposed.
Devices with visible set to 0 are skipped unless configured otherwise.

- Add DeviceDetector class to read and parse BTicino mymodules file
- Auto-detect locks with device IDs, names, visibility, and button IDs
- Generate unique lock names using button IDs to avoid HomeKit conflicts
- Add exposeInvisibleLocks flag to control visibility of hidden locks
- Remove manual doorUnlock and additionalLocks configuration
- Update door-unlock API to work with auto-detected locks
@slyoldfox
Copy link
Owner

Thank you for your PR, I quickly skimmed through it and have a few questions/remarks:

  • C300X doesn't have a /home/bticino/cfg/extra/.bt_eliot/mymodules - what will happen in this case?
  • I think this is a breaking change and breaks configs that have doorUnlock and additionalLocks?

So for the C300X where I haven't found yet where the configs are stored, there needs to be

  1. a default case with the most popular setup which is 8XX*20##
  2. a way to extend the default case with additional locks

If your current code easily supports this, you're free to add it and we'll mark it as breaking, but the default case for C300X must remain and it must be easy to add any additional locks as well in the config.json

Extra ❤️ if you also up the documentation with this breaking change :-)

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

Successfully merging this pull request may close these issues.

2 participants