If you set homeassistant.loader: error, it will filter those out
@Marius in this specific case automation is triggered by change in album name attribute of media_player entity. In my later post you can find whole automation, so you can see triggers too. So nothing fancy. I’m just trying to recreate sort of roon web display finctionality; every time album is changed I ask ChatGPT for information about this album (interesting to read, as responces are varying over time and sometimes something interesting can be found. I’m not trying to use here any type of music service (something like IMDB for music) as I’d expect length of response to vary, but asking the right question to ChatGPT I can limit lenght of response to something I can fully fit onto screen (I’m actually planning to put Samsung The Frame next to my audio gear to display this). So might be not very functional automation per se, more designed to enrich listening experience and yet showing what H A can be used for 
Here is how it looks now:
Regarding other use cases; I just wanted to highlight that it is easy to retrieve long infomration string from internet (parsing json, scrapping web page etc), but storing of such data is not easy and requires some trickery, as in example we just went through. That’s why having possibility to use sort of input_text.set_attribute service and put very long text there would be huge simplification.
5 Likes
Thx, and yes this might actually be very nice and enriching indeed. I have to reconsider my initial perspective on that. Cool
And thx for your elaboration.
Might even have to install ChatGpt now…
Regarding the new “image” entity:
I am 100% sure that it should work with this:
template:
- image:
- name: test_image
url: '/local/images/test/pink.jpg'
w/o specifying http, https, ports etc - in case of locally stored images.
“Should” - means “from a noob user’s PoV”.
In all other places of HA we use either “/local/…” path or “http(s)://…” path when needed.
See no reason why the “image” entity is an exception.
input_boolean:
test_xxxxxxx:
test_xxxxxxx_2:
homeassistant:
customize:
input_boolean.test_xxxxxxx:
entity_picture: '/local/images/test/pink.jpg'
input_boolean.test_xxxxxxx_2:
entity_picture: 'https://design.home-assistant.io/images/logo.png'
Here is no difference, both paths are accepted.
It could be not a bug but a poor functionality.
that would have been a different approach indeed, not trying to filter logged messages, but set loglevel to a lower level (than my default warn) in the first place.
Doesn’t work though, all warnings are still logged. I fear it’s like I mentioned above, Loader is not the regular component, and can not be filtered/altered. I have that on authority of one of the core dev’s…
Not sure why it’s being characterized as “trickery”.
What petro suggested leverages the strengths of a Trigger-based Template Sensor, namely the ability to set its state, and/or attributes, to whatever you want via any kind of trigger. In other words, the example is using a Trigger-based Template Sensor the way it’s meant to be used.
The example ‘publishes’ the data via a custom event:
- event: chatgpt_response
event_data:
entity_id: "{{ trigger.entity_id }}"
response: "{{ chatgpt.response.speech.plain.speech }}"
The Trigger -based Template Sensor ‘subscribes’ to the custom event and receives the data (via trigger.event.data.response):
- platform: event
event_type: chatgpt_response
event_data:
entity_id: media_player.volumio_2
The Trigger-based Template Sensor uses the received data to set the value of one of its attributes. Easy-peasy (and that value survives a restart).
FWIW, what petro suggested is something I first discovered from these examples by CentralCommand and TheFes:
It’s a pattern I have also employed to fulfill other applications that require storing a value in a sensor’s attribute (with and without the use of custom events). Examples:
Message Queue
Last Ten Motion Detectors
Bad Shutdown Sensor
Song History
It’s a useful design pattern and far from being ‘trickery’.
Your proposed new service call, input_text.set_attribute, would probably need to be called multiple times, once for each attribute you wanted to set … unless it supported setting multiple attributes at once. Here’s a mockup of what the service call could look like:
service: input_text.set_attribute
target:
entity_id: "input_text.{{ trigger.to_state.object_id }}"
data:
attribute: album_description
state: "{{ chatgpt.response.speech.plain.speech }}"
The main difference is that creating an Input Text is admittedly easier than a Trigger-based Template Sensor. Unless there’s an existing Feature Request, feel free to post a request for this new service call.
5 Likes
It does filter them from the log gui, not homeassistant.log
Hmm, this is not mentioned in Docs.
Reolink Cameras, using picture-entity lovelace pages is no longer working correctly.
The picture entities take 4-10 seconds if not timeout completely to display the camera. 2023.6.3. the images loaded immediately. Upgraded to 2023.7.1 and this problem started. On the one page I have with 5 cameras on it, it takes a good 20 seconds for most of them to come up and 1 or 2 have a broken image - sometimes 30 seconds later the broken ones will fill in. It then will often miss refresh updates or timeout while you watch it.
Back down to 2023.6.3 and it works perfectly again.
Live versions of the cameras using WebRTC gets the cameras in live real-time instantly.
It’s only the 10 second refresh picture-entity card that is causing this only seemingly on reolink cameras. (I use picture entity for weather radar and other refreshing images, and they still work and refresh perfectly) …
Hmm.
Dave
No you’re right but that’s what happens for me. The loader messages appear in the log file but not in the gui
I believed the whole Logger integration is about managing the way the Log file is processed.
Not about “which part of Log is to be displayed in UI”.
@Holdestmade would you mind to continue this discussion here?
They never were in the log Ui…
And ofc we were talking homeassistant.log in the first place ( or at least that’s what I took for being the issue at hand in Ildars post)
On the particular initial loader, let me quote
quote
There are only a few at the very top. Is that much of a concern?
in any case, if you review the logs, you’ll see that the logger finishes setup after the initial homeassistant.loader messages:
2022-07-01 11:54:49 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration pyscript which has not been t
2022-07-01 11:54:49 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds
so I suspect that you cannot filter those messages
end quote
then this explains the issue with “loader”.
Yes. For some more background on how to filter using those regex expressions see Regular expression: What is correct syntax for the new logger filter on Google TTS where Petro helps out a lot
Also mark Ludeeus’ words on Loader 
Can anyone do a small test for me?
Starting from 2023.7 I see some really strange behaviour - but I wonder is it only me or anyone else.
Please add this card and see what happens:
type: grid
cards:
- type: history-graph
hours_to_show: 12
entities:
- entity: zone.home
Hey I’m also seeing this error that HA cannot connect or determine the Envoy model. I was using the integrated Envoy method. I cannot find any HACS custom integration though (I probably don’t know how to). But I would like to know which one you are using, I found in another thread that there seem to be multiple different custom integrations.
Thanks a lot
I am seeing my browser and the Android app become essentially unresponsive on my dashboard that contains history cards. I think the 2023.7 release broke history cards somehow.
My guess is this is because of grid.
Have you tested with my card?
Because mainly history-graphs work OK in my setup.
Hmm, there are also some new issues related to “history-graph + custom card with canvas” on a same view (one, two, three).
1 Like
I put your card in a blank dashboard, same behavior - “Loading state data…” forever, and unresponsive. Same thing I’m seeing on my main dashboard that has those cards.
1 Like
Thank you one more time for testing!
So far I got 3 observations for 2023.7:
- Demo integration became inconsistent.
- “Image” entity does not accept “/local/…” path.
- A simple card may hang a page.
1 Like