8 Likes
The home-assistant.log changes
For those of you that want the log file back on supervised installations (HAOS, HA Supervised), try out this custom integration.
New yaml template entity repair
For anyone running into template trigger repairs, please see this explanation:
10 Likes
Awesome additions to the energy chart and this release shows that some changes from the last releases (automation editor, entity naming in dashboards, …) that received some negative feedback are just baby steps in a bigger picture to a hopefully better future. 
I was very exited for the new FireFly integration… But it’s not what I expected. Its create more then 1029 entities for transactions…
I had a custom integration where you able to select what you want.
All the piggy banks, all the accounts, all subscriptions etc…
Hope this new integration will grow and become something great!
1 Like
Quick question: does this update mean that only HA OS now logs? Supervised and docker are then blind?
Thank you @petro for acting so quickly to work around the bad decision (in my opinion) to remove the logs for the config folder.
I’m also unsure why a change like this is buried at the bottom of the release notes.
2 Likes
Why are the logs not written anymore by default. In case your system doesn’t start , and you want to troubleshoot, this will be impossible anymore since you can’t access the page to download them?
Core and container still write to home-assistant.log. The change only affects HAOS and HA supervised.
3 Likes
You can access them from the console or ssh
I have been using HA since 2016, so all my automations are on NodeRed, but all those updates to the Automations section are looking great! I don’t know if I should take the time to migrate…
Yeah, but it was so easy before, strange that they removed this feature, or at least make it an user option… Now we have to install another custom to get that feature back (thanx for that anyway!!)
1 Like
What about the previous log file, that was sometimes usefull too, if you forgot to check the logs for example, how can we obtain that file now? Is that also removed?
2 Likes
There’s a command to see more, I’ll have to dig it out.
For me this update completely destroyed how card mod works with markdown card inside grid card (not sure yet on which side the problem is). Seems like additional vertical space is added to markdown, so instead of nicely showing in defined grid window it is vertically shifted and scroll bars are added. Here is the sample of my person card (how it looks now):
vs what is should look like; more-less, there should be no scroll bars and positioning was very precise, here you can spot some ugly misalignments and scroll bars, that should not be there:
1 Like
With the new target picker in automations, does that mean we should rename our light entities without the room name, or keep as is still?
Are using the new card-mod v4 beta? If not, it should fix the issue.
1 Like
Thx, still, bad decision to remove the log files, this was so usefull to debug , now we need commands to see the log, when you want to debug , strange decision. At least make it an user option to enable it… 
Or you could just use the custom integration I created above
4 Likes
Hello,
thanks, you did a good job with this release!
I love to write automations on yaml directly, but I am sure, I will love the new form of editing automations and the target picker too!
- It’s a easy way of selecting targets.
Additional the changes on energy dashboard are very well, IMHO!
With best regards
Helmut
I don’t understand if this change to the LG webOS TV integration affects me.
The release note says
The state of LG webOS TV media player entities that do not have an automation trigger to turn on the device will be set to unavailable instead of off.
What is meant by an “automation trigger”. Reading the PR it seems to indicate that we should no longer use WakeOnLAN. But the integration documention still recommends this. I don’t understand what the alternative is. Can someone explain?