-
Notifications
You must be signed in to change notification settings - Fork 170
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
Server limited to 25 characteristics #199
Comments
What chip are you using? Devices like the esp8266 have limited memory, each service & characteristic consumes some memory, you may be hitting the limit of what the chip can handle. |
I'm running the ESP-wroom-32. I've attached the details from the chip below To be absolutely sure, I now also print the free heap when the characteristics are requested.
|
I found the "issue". For my use case, I simply increased this to 100. (Causing 300 bytes of extra memory consumption) To ensure a low memory profile for the esp8266, maybe this should be made dynamic? |
So, yes, I agree, that it can be made configurable with ESP32 devices getting larger values by default plus allowing overriding defaults if really needed. Will think about automating it (e.g. automatically configuring it to the number of characteristics present). |
I'm trying to run a bridge with 14 blinds (as different accessories as I want to put them in different rooms).
These each have 3 services.
My setup can handle 9 blinds, from 10 blinds and above, the accessories have the red "not responsive" text.
Output from the terminal tells me that when all target and position characteristics are being requested not all of them "make it".
For only 12/14 blinds, both target and current position is being asked. For the unlucky 13th, only one is asked, and the 14th blind is ignored.
Fun shenanigans:
My Setup:
Part of the main.c code:
Part of the blinds.c code:
Output log:
(Note that for only 12/14 blinds, both target and current position is being asked. For the unlucky 13th, only one is asked, and the 14th blind is ignored.)
The text was updated successfully, but these errors were encountered: