It might be a nice feature to be able to store an override of pepper1db that can be managed by the user if needed. In my case, my HEM v1 supports association, but the device omits this class when queried by HG. I can manually add the association class by modifying the param in HG, but it will be reset any time I click the query node info button.