search

dummylabs / thewatchman

Home Assistant custom integration to keep track of missing entities and actions in your config files
MIT License
475 stars 20 forks source link

Entity in Tuya-Local file erroneously included in report #151

Closed reef-actor closed 1 day ago

reef-actor commented 2 months ago

I have the tuya-local integration installed. In the Watchman report I see the following notification:

climate.current_humidity [missing]
electriq_desd9lw_dehumidifier.yaml

I don't have an entity called climate.current_humidity or a dehumidifier. The entity name exists on line 92 of the file in tuya-local.

reef-actor commented 1 month ago

I have avoided this issue by adding **/config/custom_components/** to Ignored files. Would it make sense to ignore this path by default? Perhaps the description by the Ignored files field could be modified to mention that it supports globs and it supports ignoring folders?

felipecrs commented 2 days ago

I believe it would make a lot of sense to ignore such path by default.

dummylabs commented 2 days ago

Right, this will also help with #130

dummylabs commented 1 day ago

Following items will be set as default ignored files for new installations of Watchman 0.6.4 */blueprints/*, */custom_components/*, */esphome/*

felipecrs commented 1 day ago

@dummylabs, to be honest, it makes sense to scan the *.yaml files in ESPHome.

That's because we can call Home Assistant actions within ESPHome devices. I use this a lot, for example I have a wall socket in which the button will toggle my Home Assistant fan entity if I long press.

It would be great to have feedback for missing Home Assistant entities within my ESPHome yaml files.

dummylabs commented 1 day ago

Okay, I've added esphome to the default in ignored items to prevent new users from getting confused by the report output. Advanced users can configure their own settings.