Skip to content
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

Define / change BidCos-Address in RM #3006

Open
teichtaucher opened this issue Jan 28, 2025 · 0 comments
Open

Define / change BidCos-Address in RM #3006

teichtaucher opened this issue Jan 28, 2025 · 0 comments
Labels
💡 enhancement-ideas New feature or change request 🔅 low priority This issue/ticket has low priority (not urgent)

Comments

@teichtaucher
Copy link

Describe the solution you'd like

Many people want to migrate from other Homematic implementations. For example I'm using HomeMatic in FHEM. In FHEM it's one of the first steps to define the HM-ID (or so called BidCos-Address of the central).
When I setup RM from scratch the HM ID of the corresponding interface is used intially. It would be nice if this ID could be changed afterwards in the web interface of RM. It can be changed via some workarounds (adapt the id in file /etc/config/ids). But the work is quite high and not possible for unexperianced users.
Once the HM ID is changed, it is quite easy to pair the devices with RM using pair by serial and to use thm (temporarily) in parallel to FHEM or other implementations.
So I'd appreaciate to make the HM ID or BidCos Address configurable in RaspberryMatic.

Describe alternatives you've considered

Change the HM ID via SSH in RaspberryMatic.

Is your feature request related to a problem?

No. It's working also without this feature. But with higher effort for migration.

Additional information

No response

@teichtaucher teichtaucher added the 💡 enhancement-ideas New feature or change request label Jan 28, 2025
@jens-maus jens-maus added the 🔅 low priority This issue/ticket has low priority (not urgent) label Jan 28, 2025
@jens-maus jens-maus added this to the future release milestone Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 enhancement-ideas New feature or change request 🔅 low priority This issue/ticket has low priority (not urgent)
Projects
Status: No status
Development

No branches or pull requests

2 participants