Known issues

As with any design approach, there are also some downsides to the one I've taken with this library. The most notable being size. This library takes up more RAM space than I would like it to. This is in large part due to the overhead necessary to support the local knowledge approach.

Here is an overview of other known limits and issues related to this library. I hope to address some of these in the coming months as I roll out this library to a bunch of my own devices.

• Embedded resources are not yet supported (though planned for future updates)
• Only numerical values can be used for resource states

Please let me know about any issues that you encounter with this library. Thanks. Julio