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

[TMV (Taco Vree)]

Yes, installing an HASS update did it for me. I guess this cleared the cash of the browser I guess. Other advice I got was to clear the cash.

[scr]

That totally makes sense, thanks for idea! I’ve added a ticket for this to the backlog.

[scr]

The report should contain exact file name and line number where missing entry was found. These lovelace files are not intended for manual change, they’re basically json files used by the dashboard (ex-Lovelace) editor. Nevertheless, review of them may help to figure out which part of dashboard the missing entity belongs to.

[scr]

The only idea I have is that report was created at the point in time when initialisation of some services/entities was not yet finished (e.g. after HA restart). This is especially true for integrations which are loaded asynchronously by HA, that is, the entities/services they provide become available after some delay. To validate this you can run the report once again and check the result.

[scr]

@carltonb

Can this be exported as a cvs file so I can open it in a spread sheet.

Not yet.

@carltonb

is there a way to expand the columns so most lines are as long as possible, like in the developer tools states.

Yes, check “Report’s columns witdth” settings.

@carltonb

Now my biggest wish for another time and place would be if there was some way that the error was linked to a file on how to fix the problems or more details on what might be wrong.

I was thinking about hyperlinks to a file in the report. It seems that it should be somehow supported by the tool (file editor) used by the user. So far I see no portable solution.

[portigui]

@scr That would make total sense however re-running the report just now had the same results and HA has been running for a couple of hours since my last restart.

[Hellis81]

Any plans to check the Node red flows.json file?
Since it’s JSON it should be easy to work with.

[scr]

Can you please check what’s the state of media_player and scene entities in HA Developer tools? it always a good idea to copy/paste entity name from the report to “Filter entities” field to avoid encoding/typing mismatch.

State unknown means that HA returned “unknown” for this entity to watchman and this is a correct state. It can be that Fully Kiosk makes this entity unknown when corresponding tablet is offline or the application is not active, but the Developer tools should show the actual state anyway.

The same check can be made for the service, try to type “floor” in the Service tab from the Developer tools to check if this service is shown as a suggestion.

[scr]

I am not using NR addon, is this flows.json file stored somewhere under /config directory?

[Hellis81]

Yes.

/config/node-red/flows.json

Do you need a sample file?

[Cafun]

Oh checking Node-Red Flows also would be amazing! +1 for that

[scr]

@Hellis81

Do you need a sample file?

Yes, please create a ticket on the github with a sample file attached. Thank you!

[poudenes]

I love this service. Can you tell us what interval will be for the 2 sensors?
I add both markdown examples and wondering if those sensors will renew every x minutes.

[poudenes]

And what is the benefit to check check_lovelace?
Because the stored Lovelace have many old entities that are not there anymore.
And the stored one is not accurate on the one that is used.

[tom_l]

@poudenes

Because the stored Lovelace have many old entities that are not there anymore.
And the stored one is not accurate on the one that is used.

Not sure what you mean by this.

If you edit a Dashboard or card (HA is moving away from the name “Lovelace”, rightly or wrongly) via the UI as soon as you save it the json in the .storage register is updated.

If you use yaml mode the register is update as soon as you do a reload.

[poudenes]

I edit the dashboard and then save it. When I check it I see lot.of old entities that are not used anymore in the running dashboard.

HA is not updating the file then…?

[tom_l]

I just used the check Lovelace option (I’ve never used it before) and all it found were entities that really don’t exist any more (thanks scr!).

EDIT: ok, after removing or editing the offending entities from my Lovelace raw config, saving and then running another Watchman report I still got the same entities being reported. I had to re-parse the configuration to get them out of the report. It’s this option:

I’m guessing this is only done automatically after a restart.

[scr]

@tom_l

I had to re-parse the configuration to get them out of the report. It’s this option:

Good point, current version cannot automatically detect changes made to Dashboard UI (ex-Lovelace UI), only changes to yaml files are tracked and will trigger re-parsing. I’ll check if there is a relevant event which can be catched by watchman.

[scr]

@poudenes

I add both markdown examples and wondering if those sensors will renew every x minutes.

Watchman sensors are automatically updated when any entity from the monitoring list changes its state either from or to missing, unavailable or unknown. Monitoring list contains all entities from all configuration files except:

• entities, which have a state from ignored_states list
• entities, which name is a part of ignored_items list
• entities, which referenced by a file from the ignored_files list

Update: missing is an artificial state, which doesn’t exist in HA. It simply means that this entity was not found in HA registry.

[Mattie (Mattias)]

I installed watchman using HACS but I can’t find the watchman.report service in the services list. Everything is up to date here. What am I missing?