Add dependencies to the ConfigValue sensor.

As a first step, yes.

Additionally, it would be good to add a dependency on the actual config in case it is a config entity. So if we check for a specific view, we should also directly depend on that config.

I thought about doing that in a follow-up, but that's actually quite easy to identify. Load the config, if it exists and has a dependency key on the first level, we can assume it is a config entity, then add that to the dependencies too.

We should also have some test coverage for this, we can probably just extend our existing tests.

Tested locally seems to work.

+++ b/src/Tests/MonitoringUITest.php
@@ -266,6 +266,17 @@ class MonitoringUITest extends MonitoringTestBase {
+    $this->assertTrue($dependencies['config']);

I think that should be some string that refers to the specific config object... Not just plain TRUE... We should specifically test this.

Much nice! Thx, committed.