There was a known parser bug, which caused this warning, should be fixed in 0.8.4-rc2.
Thanks for the feedback. Please check the latest version, 0.8.4-rc2.
If the issue persists (and you believe it shouldnât), please submit a bug report. Important: To fix this, I will need a snippet from your Lovelace configuration file (.storage/lovelace) where the parser triggered the false positive.
Funny thing⌠with latest rc2 my error above indeed dissapears, but i get a different âproblemâ: 11 missing actions, although they should be entities⌠? These are not shown on old version, and also it can happen that they are not shown in this one after HA restart, but not always. 2 days ago when i first installer rc2 errors showed, but dissapeared after HA restart. But today HACS update rebooted went through and errors stays, even after a couple of HA rebootsâŚ
Funny thing is that there are random entities on random dashboards. Note that all reported entities are in fact here and alive.
Note info on the left of the picture, when it says 11 missing actions (akcije):
and proof that entities are not unavailable:
works perfectly, thank you! i re-enabled the addon.
Not here. Same 22 âunknownâ entities. Going back to 0.8.3 and all is ok. Updating to 0.8.4 again and errors are back.
Going back to 0.8.4.rc2 unknown entities warning dissapears, but services are back.
So it must be something from rc2 to rc3 which is broken�
Version 0.8.5 rc1 works perfectly here. Thanks A LOT !!!
A quick note regarding scenes: In Home Assistant, scenes (similar to buttons) are stateless entities, meaning they will always display an âunknownâ state. The next release will handle scenes correctly, as discussed in new update 0.8.4 sees Philips Hue lighting scenes as unknown ¡ Issue #286 ¡ dummylabs/thewatchman ¡ GitHub.
Not anymore. Their state is now the last time it was applied. Same for buttons and presses.
just updated to release 0.8.5 after having awaited for some time to let the developments settle.
seems the new config does not excluded the settings for unavailable at all? anyone else seeing the report show all of those?
Thanks for the report! I can confirm this is a bug, not covered by automatic tests. Iâll get it fixed and release an update shortly.
Please try the v0.8.6 pre-release â the bug should be fixed now.
finding broken automations
I just changed some ids of devices
watchman tells me of dashboards which are now using the wrong IDS but it does not seem to help me with any automations or scripts
is there any way to help me find what I need to fix?
and also when there are errors it just shows me the file like this, is there any way to be a bit more specific in where I can find the item to be fixed
When it says lovelace_lovelace_home
home, will be the name of the dashboard where you have the incorrect/missing entity
for example in the Home dash I have all these tabs and I don't know where this
sensor.watchman_missing_services [unavail]
is in those
it would be great if it could actually show me which tab it's in or which block
eg
I don't see this anywhere and I tried to do a search for plug_freezer
Sometimes watchman needs to be restarted in order to correctly recognize all stuff. Did you restart it already?
Exact was not showing this. I found it eventually it was in the scheduler.
It was the list of selected entities in the scheduler but it was not in an actual schedule so there's nothing to see on the UI
Good find, glad you got it. It's certainly not helping that "Find" seems to be broken and no longer scrolls the page to the place in the document where the word exists (in chrome at least).
This started in a recent release (2026.6 I think) when the code completion was changed in the raw dashboard YAML editor.