🛡 Watchman - keeps track of missing entities and actions in your config files

[scr]

Make sure you went through all 3 steps mentioned in quick start.

[Mattie (Mattias)]

Ah, sorry I missed this!

[tom_l]

Hi scr, has the Lovelace check been removed from the latest version?

[tom_l]

I’m being asked to downgrade?

[sparkydave (🇦🇺 Dave)]

I have the same thing so ignored it for now…

[micque]

Me too. Looks like an extra dot got added in the version number last update.

[wormvortex]

I’ve downloaded via HACS. Rebooted HA but when I try to add watchman as an integration it does not appear on the list. Not sure what’s wrong.

[CentralCommand (Mike)]

Something strange seems to be happening with this integration. I’m now being asked to massively downgrade to v0.2.5. And the release I’m on seems to have disappeared (along with everything above 0.2.5). Anyone know what is going on here?

EDIT: Ok it looks like the tags still exist. I guess I wasn’t actively checking this repo, were there previously releases to go along with those tags or was it being managed entirely as tags? Still the issue of why I’m being presented with a massive downgrade by HACS.

[scr]

@tom_l

I’m being asked to downgrade?

@CentralCommand

Still the issue of why I’m being presented with a massive downgrade by HACS.

It’s on the GitHub side, I’ve fixed it for now without any guarantee it won’t happen again.

[Leighball]

So please help an old man out here :)…once I have this report, how do i actually go in and repair the error which the report has shown me?
I’m sorry for the stupid question.
Are there any video tutorials on this?

[stevemann (Stephen Mann (YAML-challenged))]

@Leighball

how do i actually go in and repair the error which the report has shown me?

It depends…
First, I doubt that anyone who has been tinkering with Home Assistant for a while doesn’t have missing entities.
If you aren’t experiencing problems, then this is just a matter of house cleaning.

Here’s an example:

The missing service is from an automation that I was writing a long time ago. I meant to say “switch_turn_on” but forgot the “on”. If you use the UI to make automations, it will be difficult to make this mistake.

For the missing entities,
State: unavail - In my case, either the device is offline or it’s an old entry in a YAML file. “wemos_blinkr_led” is simply offline.

State: missing- “sensor.freezer” was changed in the device yaml file to “sensor.freezer_temperature_c”, I need to change the entry in configuration.yaml (the Location column shows where sensor.freezer was specified, but not found.

State: unknown- This one took some research. The entity is good and I can turn the dining room light on and off from HA, so why is it “unknown” in the report? In my case, this switch has recently decided to not send a status unless I turn it on or off:

I toggled the light and ran another Watchman report, and the “unknown” disappeared. The problem is in my switch, not my automation.

Hope this helps.
As was said above, Watchman is only a snapshot of things to investigate or clean up. Most of us using Watchman for the first time were surprised at the remnants from older experiments or tinkering or deleted devices that have no effect on Home Assistant.

[scr]

Thanks @stevemann for the great and detailed explanation!

@Leighball

Are there any video tutorials on this?

There’s a short review on youtube: https://www.youtube.com/watch?v=XKD5vBZLKgE&t=3s

[Leighball]

Right!!..this makes total sense. Thanks for the explanation…and patience

[Leighball]

Thank you very much

[duittenb (Dirk)]

Nice add-on!

Question: Can I control how often Watchman checks files?

Right now it runs quite often but I only need it to run once a day.

[davinci]

The plugin is not working anymore in 2022.6.6

There are always zero errors, even though I have missing devices. It worked before the update and I didn’t change anything else.

Anyone else having this issue?

I updated to 0.6.0 and to 2022.6.6 at the same time. Not sure what is to blame.

[stevemann (Stephen Mann (YAML-challenged))]

@davinci

Anyone else having this issue?

No problems here.

[scr]

@duittenb

Can I control how often Watchman checks files?
Right now it runs quite often but I only need it to run once a day.

From the watchman perspective this is a two-stage process:

1. Re-parse configuration files when they’re changed. This is a resource-intensive operation and it should not happen very often as it only triggers at HA reboot or when you reload a part of you configuration files via Developer tools->YAML-> YAML configuration reloading
2. Update watchman sensors when any entity from previously parsed config (step 1) changes its state either to or from: “missing”, “unavailable”, “unknown”. This can happen quite often if an entity from your configuration file changes its state, e.g. from unknown to 25 and back every minute or less.

The next version of Watchman will get the ability to disable sensors for those users who don’t need them. For the moment, a workaround is to identify the entity which triggers watchman sensors update and add it to the ignore list.
Hope this helps.

[scr]

@davinci

Anyone else having this issue?

Does watchman.report work? The easiest way to test it is to add a yaml file to your /config folder with something like sensor.fake_sensor and run the report with “parse_config=true”. This sensor should then appear in the report.

[davinci]

Yes, it reports.

The problem was that the path was set to /config. Changed it to the full path and now it works again. But I think this behavior was different before.