Closed DenisTimofijuk closed 4 days ago
The only think I can suggest is try creating one of each from the webui. Then go to the filesystem and see they are created on the expected path.
Then add your own. See if that works.
You might also have to include the directory of automations/scenes/scripts in the configuration.yaml
I’m not sure I fully understand your suggested solutions. Let me clarify a few points:
I haven't encountered any errors during the creation process, neither in the Pod Shell console nor in the web UI console.
This issue has been present from the very beginning since I started using Home Assistant on TrueNAS Scale. Until now, I wasn’t actively using automations, but I would like to resolve this so I can use the feature as intended.
What could be causing this behavior? Are there any specific steps I can take to debug further?
I’m attaching some screenshots to better illustrate the issue. Please let me know if additional information is needed or if there’s anything else I should check.
Check the difference in the configuration.yaml between working and not working setup. It will probably have a some extra includes there
Description: I'm experiencing an issue where automations, scripts, and scenes saved in Home Assistant are not appearing on their respective dashboards. After creating and saving these items, the dashboard resets to its initial "Start automating" view, as if nothing was saved. However, I can access each created item directly using URLs, confirming that the items are saved but not displayed in the dashboard.
Steps to Reproduce:
/config/automation/dashboard
/config/scene/dashboard
/config/script/dashboard
Expected Behavior: Saved automations, scripts, and scenes should appear on their respective dashboards after saving, without the dashboard resetting to the initial view.
Observed Behavior: After saving, the dashboard displays the following initial view text:
However, I can still access the saved items directly via URL, e.g.,
/config/automation/edit/1731534753959
.System Information:
Additional Notes:
Any insights or guidance would be appreciated, as the issue impacts the usability of automation and scene management.