It took me a few extra steps to get this add-on running because I leverage the "packages: !include_dir_named" feature to organize my configuration and my recorder DB URL is included in one of the yaml files where my packages directory is. The install of the add-in and the startup reported no problem. That said, when I ran the example, I was receiving errors about tables missing.
I didn't see anything in the documentation to explain what could be going on. I dug through the logs and noticed it said something about "!include_dir_named not supported". I then tried moving my recorder config out of a package file and into the main config and voila, it worked.
Expected behavior
Ideally: this add-on supports reading from package files
Practically: the documentation makes it clear that the add-on doesn't support this and that you need to move your recorder config in for the plugin to work.
Actual behavior
No indication of why tables are not found and no documentation to suggest this is a none limitation
Problem/Motivation
It took me a few extra steps to get this add-on running because I leverage the "packages: !include_dir_named" feature to organize my configuration and my recorder DB URL is included in one of the yaml files where my packages directory is. The install of the add-in and the startup reported no problem. That said, when I ran the example, I was receiving errors about tables missing.
I didn't see anything in the documentation to explain what could be going on. I dug through the logs and noticed it said something about "!include_dir_named not supported". I then tried moving my recorder config out of a package file and into the main config and voila, it worked.
Expected behavior
Ideally: this add-on supports reading from package files Practically: the documentation makes it clear that the add-on doesn't support this and that you need to move your recorder config in for the plugin to work.
Actual behavior
No indication of why tables are not found and no documentation to suggest this is a none limitation
Thanks!