Already reported, please try:
Yes that fixed it.
With my new installation, I tested the new sitemap chart interpolation option.
This was a feature I was really looking forward to. Sorry to say that it does not seem to work in my case - or I did not really understand the concept. I thought
interpolation="step"
would really create steps until the next data point. But this does not look like it:

I am ready to test or debug - could you give me some instructions?
In the log no complains about the new option. There was one when I put interpolation=step without quotes. Corresponding sitemap entry is:
Chart item=Multisplit4_Power period=h service="influxdb" legend=true refresh=60000 interpolation="step" visibility=[Periode==0]
Another point: I understood that frontail is not wanted anymore because of security reasons.
Honestly, however, I am not at all satisified with the built-in log viewer. Accuse me of stating a xy problem, but in my fresh installation, it does not work very well:
I donât get continuously log entries, but maybe for half an hour or so, it either
- stops by itself and I have to press the play button again or
- stops by itself while still showing the play status, then I have to refresh the browser tab
- after refreshing, I sometimes see:
11:44:15.991[INFO] [org.openhab.core.io.websocket.log.LogWebSocket] - WebSocket error: java.util.concurrent.TimeoutException: Idle timeout expired: 10000/10000 ms
In frontail, I could without a problem let it run for hours.
Is this new behaviour a desired one?
It would probably make sense to discuss the frontail questions here? Frontail is dead - long live the UI but
Isnât this strictly about the UI log viewer, not Frontail?
Unless the upgrade scripts in the runtime/bin folders are updated new folders from the distro will not be created during an upgrade.
the console
app.3d2cd33c5fa657413c0e.js:2 TypeError: Cannot read properties of null (reading 'split')
at i.semanticTag (app.46bcc4058b7eec26fc09.js:2:136266)
at app.46bcc4058b7eec26fc09.js:2:135147
at Array.filter (<anonymous>)
at i.nonSemanticTags (app.46bcc4058b7eec26fc09.js:2:135078)
at e.get (app.3d2cd33c5fa657413c0e.js:2:1539340)
at e.evaluate (app.3d2cd33c5fa657413c0e.js:2:1540336)
at i.nonSemanticTags (app.3d2cd33c5fa657413c0e.js:2:1542531)
at i.<anonymous> (app.46bcc4058b7eec26fc09.js:2:137834)
at e._render (app.3d2cd33c5fa657413c0e.js:2:1556919)
at i.r (app.3d2cd33c5fa657413c0e.js:2:1590872)
and the network tab (sorry, donât know how to share better than screenshot)

Are those the right ones?
Pick the request that contains the name of the Item you attempted to open (Balboa_Target_Temperature2 ??) and send me its response.
Is it JSScripting?
@florian-h05 : does this âstringifyâ talks to you ?
Yes Java script
JSON.stringify is part of the language itself.
Did you try restarting openHAB? I cannot really explain that issue.
@Larsen
The fix should now be available, please do the following again:
I updated the bundle and it seems to working now.
I will wait and see what happens if there is another milestone update.
Did that also fix your out of memory errors? Iâm seeing an increased memory consumption in the latest milestone but havenât had time to do the testing on whatâs causing it yet.
As far as I know it did fix those errors as well.
I havenât really given it a long test as it is just a test system on my laptop.
I just looked to see what errors were showing in the log.
@florian-h05
I can confirm that with the latest patch from Florian all items I tested now open correctly. ![]()
But (sorry), I found another issue:
When creating a rule in the UI and selecting âitem eventâ + âshow non-semanticâ (some?) items without semantic tags are not displayed. The item I tested had
"tags": [],
Hmm, thatâs not enough to reproduce that issue for me.
I try better: The triggering item is e.g.:
trigger item
{
"link": "http://rapi2:8080/rest/items/Balboa_Target_Temp_high",
"state": "38 °C",
"stateDescription": {
"pattern": "%.1f %unit%",
"readOnly": false,
"options": []
},
"lastState": "38.5 °C",
"lastStateUpdate": 1752671224000,
"lastStateChange": 1752671224000,
"unitSymbol": "°C",
"metadata": {
"unit": {
"value": "°C",
"editable": true
},
"widget": {
"value": "oh-stepper-card",
"config": {
"raised": true,
"step": 0.5,
"large": true,
"fill": true
},
"editable": true
},
"stateDescription": {
"value": " ",
"config": {
"pattern": "%.1f %unit%"
},
"editable": true
}
},
"editable": true,
"type": "Number:Temperature",
"name": "Balboa_Target_Temp_high",
"label": "Pool_Target_Temp_high",
"category": "",
"tags": [],
"groupNames": [
"Balboa",
"TempPersG"
]
}
In the UI:
- create Rule
- add trigger
- Item event
- select âShow non-semanticâ
=> The above item is missing. (It seems items without semantic tags are completely missing)
This feature was not implemented in any sitemap UI at my knowledge.
An implementation in Basic UI has just been proposed but not tested.