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.

Sign up for GitHub

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

Jump to bottom

ReGaHss: Allow to maintain >65k objects #220

Closed
jens-maus opened this issue Dec 20, 2017 · 3 comments
Closed

ReGaHss: Allow to maintain >65k objects #220

jens-maus opened this issue Dec 20, 2017 · 3 comments
Labels
💡 enhancement-ideas New feature or change request 🏷️ ReGaHss This refs the ReGaHss component
Milestone
3.41.11.20181124

Comments

@jens-maus
Copy link
Owner

ReGaHss has an internal limit of 65k objects. That means, there can't be more than 65k objects within ReGa including devices, data points, system variables, etc. etc. This limit is easily hit in large installations, especially if HmIP components are used.
@jens-maus jens-maus added 💡 enhancement-ideas New feature or change request 🏷️ ReGaHss This refs the ReGaHss component labels Dec 20, 2017
@cyber-age
Copy link

Why especially when hmIP is used?

@jens-maus
Copy link
Owner Author

Because HmIP devices have substantially more channels compared to traditional BidCos-RF devices and each channel requires one object within the object-space of ReGaHss.

@jens-maus jens-maus added this to the next release milestone Nov 13, 2018
@jens-maus
Copy link
Owner Author

Coming with next upcoming 3.41.x Update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💡 enhancement-ideas New feature or change request 🏷️ ReGaHss This refs the ReGaHss component
Projects
ReGaHss improvements/fixes
Status: Done
Milestone
3.41.11.20181124
Development

No branches or pull requests
2 participants
@jens-maus @cyber-age