This will require some improvements to localization support, I will add it to the backlog.
When you call the service, you implicitly ask Watchman to send the report via notification channel (even when zero problems are detected). Nevertheless, using simple automation, one can send a report (notification) only when Watchman sensors have non-zero values.
I like the idea, let me check if this can be implemented without significant changes to Watchman architecture. AFAIK, knowledge about âvalidâ states for a sensor is encapsulated within its domain and canât be easily retrieved by an integration. Probably we can introduce some heuristics which will mark some states as âsuspiciousâ without 100% reliability.
That would be a great improvement. Maybe you can also catch this: a numeric_state on covers not having set the attribute to current_position (e.g. field was left blank) or using âonâ âoffâ instead of âopenâ and âclosedâ for states.
Which is probably the number one reason why my automations fail
Is there an integrated way to ignore changes that are only there for e.g. less than 5 minutes?
For example some devices fail intermittently to send variables, but they work fine. Only if the error persists for more than 5 minutes I would consider this an issue that needs action. For now I use a time helper to check after 5 minutes if the issue is still present (missing entities > 0 or missing services > 0) and only then I send a notification.
Like this I will never get a âall okâ though. The reason for that is, otherwise I would get a message after five minutes each time I save an automation (because they are all reloaded, which triggers my time helper twice).
I found a few notes when running the report. Not sure if any of this is known (could not find references) or working as intended. Just passing along some info.
This integration has a Rules section in its config. Two things are messing with the report.
The integration adds some services that are not identified by the report. Even though this is valid the report has it marked as missing.
action: call-service
service: floorplan.class_set
A feature of this integration is mapping SVG elements to HA entities. It is common to name the SVG elements in the same convention as the HA entities. I have some that are not 1-to-1 mappings but rather several SVG elements map to a single HA element. However those are in the elements section and not the entities section and should not be reported.
This integration allows for controlling a tablet used as a control panel from HA. One of the things it does is creates a media player entity for the tablet. This media player shows up in the configuration entities section and works as intended however the following shows as unknown.
Hi I learned about this tool today, but Iâve an issue activating it. I installed vs 0.5 via HACS and rebooted HASS (a few times as a matter of fact). It does show in HACS as installed. No entries in any error log.
But, I cannot add the tool to my integrations.
I did remove the tool and reinstalled, but no difference (as I would not ask for help then).
I have been using this for a few days and I appoligize for my naivety in the use of this.
A few questions.
Can this be exported as a cvs file so I can open it in a spread sheet.
I am using VSC to read the file it seems very âsquishedâ is there a way to expand the columns so most lines are as long as possible, like in the developer tools states.
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.
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.
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.
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.
@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.