DateTime Item with LastUpdate Profile doesn't take state descriptions and I get some interesting log messages

I’m having a weird issue here, not sure what I could be doing wrong.

I have this door contact

And for the open/state channel I added two items. One without a profile - it represents the open/closed state. It doesn’t have any state description (but probably gets something from the binding/thing).

The second item that I created for the same channel, is a timestamp item with the link profile to update it when the channel state changes.

Works fine so far, I get the desired timestamp for every change.

Now I want to use this in the main ui and set up a state description for the item and set this pattern:

 %1$td. %1$tm. %1$tR

I use this pattern on other timestamp items, so I know it works fine.

However, it isn’t applied to this item here, I still see the raw timestamp in the ui, no state description metadata applied.

When I look up the item in the expression tester, I don’t get a displayState at all:
image

{ "state": "2021-05-07T09:10:18.724+0200" }

Now, when I fetch the item in the api explorer, I get the pattern BUT I additionally get a state description for open/close …

I guess this is inherited from the channel somehow?

{
  "link": "http://192.168.0.199:8080/rest/items/Haustur_LastOpenState",
  "state": "2021-05-07T09:10:18.724+0200",
  "stateDescription": {
    "pattern": " %1$td. %1$tm. %1$tR",
    "readOnly": true,
    "options": [
      {
        "value": "CLOSED",
        "label": "geschlossen"
      },
      {
        "value": "OPEN",
        "label": "offen"
      }
    ]
  },
  "commandDescription": {
    "commandOptions": [
      {
        "command": "CLOSED",
        "label": "geschlossen"
      },
      {
        "command": "OPEN",
        "label": "offen"
      }
    ]
  },
  "editable": true,
  "type": "DateTime",
  "name": "Haustur_LastOpenState",
  "label": "Letztes Mal geöffnet",
  "category": "time",
  "tags": [
    "Point"
  ],
  "groupNames": [
    "Haustur"
  ]
}

I assume this is the cause of the problem, yet the raw timestamp still shows up.

And to make things worse/weirder:

At some point I got this in the log, but I can’t reproduce it .

2021-05-07 10:19:47.702 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: H
2021-05-07 10:19:47.705 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Ha
2021-05-07 10:19:47.707 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Hau
2021-05-07 10:19:47.710 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haus
2021-05-07 10:19:47.713 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haust
2021-05-07 10:19:47.716 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustu
2021-05-07 10:19:47.718 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_
2021-05-07 10:19:47.721 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_L
2021-05-07 10:19:47.724 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_La
2021-05-07 10:19:47.727 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_Lat
2021-05-07 10:19:47.730 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_Las
2021-05-07 10:19:47.732 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_Last
2021-05-07 10:19:47.735 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_LastO
2021-05-07 10:19:47.738 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_LastOp
2021-05-07 10:19:47.740 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_LastOpe
2021-05-07 10:19:47.743 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_LastOpen
2021-05-07 10:19:47.746 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_LastOpenS
2021-05-07 10:19:47.748 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_LastOpenSt
2021-05-07 10:19:47.751 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_LastOpenSta
2021-05-07 10:19:47.753 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: Haustur_LastOpenStat
2021-05-07 10:19:47.757 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: anycubic_Timestampoflastprogressmessag
2021-05-07 10:19:47.760 [WARN ] [e.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: anycubic_Timestampoflastprogressmessa

For the moment my solution is to use a rule to update an “independent” item that isn’t linked to the thing at all. But I wonder what the problem is with the much more elegant solution of using a profile.

In case that it’s a known bug, I’m still on the 3.0.0 release build at the moment

It is, but you have uncovered another interesting facet of it here with the state options

Thank you. Guess it’s time to update, I’ll try to do it over the weekend and check whether this issue persists.

It will, there’s no fix yet. (apart from manually editing ‘pattern’ as you have done, and I guess manually delete the options)