Attempting to send a state update of an item which doesn't exist: __v_isRef
Closed this issue · 7 comments
With the last snapshot (4064), here is what I can found in my logs:
14:36:06.569 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:36:06.575 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
14:36:17.125 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:36:17.131 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
14:36:25.157 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:36:25.162 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
14:36:32.135 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:36:32.142 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
14:36:37.619 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:36:37.625 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
14:36:53.905 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:36:53.913 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
14:37:53.943 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:37:53.949 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
14:37:59.730 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:37:59.736 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
14:40:40.387 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:40:40.393 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
14:41:19.736 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:41:19.743 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
14:41:30.680 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __ob__
14:41:30.687 [WARN ] [se.internal.SseItemStatesEventBuilder] - Attempting to send a state update of an item which doesn't exist: __v_isRef
```
Looks like an issue in WebUI or JS Scripting.
I let you move it to the right place in that case.
I found exactly the same issue but it was closed:
openhab/openhab-webui#2530
@florian-h05 : apparently, the issue is not yet solved.
When does the issue occur? What do you do in the UI at that time?
When working on fixing the linked issue I was not able to reproduce it after my code changes, so I considered if fixed.
I discovered the warnings after browsing a lot in the UI. But I guess it was during opening every cards in location/equipment.
I can’t reproduce on snapshot 4038 (this is was my production system is currently using).
Can you please go to the about page of Main UI and „reload app and clear caches“?
It can be possible that you still have an old version of Main UI inside your browser …
I can't reproduce the problem today after opening and navigating in all my cards.
I close the issue and I will reopen it if it appears again.