csobrinho

Query

I'm planning to do a big refactor to all scales inside the scales/ folder. My plan is to switch the hardcoded and forked logic for each scale implementation to use new C++ mixins. In order to reliably do that I need to know, for each scale, all the details that are common between them and all the smaller details that are very unique. For instance:
- are they all bluetooth
- do they use one uuid descriptor for weight or more than one
- same for command uuid (one or more)
- are they all using notifications (the class subscribes to the weight UUID, receives the payload and decodes the data, notifies the weight callback.
- do they contain warnings/miss used logic, bad patterns, unnecessary heap allocations, potential leaks
- do they need a heartbeat