openhab-core icon indicating copy to clipboard operation
openhab-core copied to clipboard

Deleted items still available in WebUI, changed items use old state/config

Open skupfer opened this issue 4 years ago • 5 comments
trafficstars

I successfully upgraded to OH3 from OH2. Today I added / changed / removed some items and especially the removed items from an ITEM.items file won't get removed from the WebUI. No error in log.

EDIT: Further information

I changed the item Switch Shelly_483fda91aba0_Light "Light [%d]" { channel="shelly:shelly1:483fda91aba0:relay#output" } to Switch Shelly_483fda91aba0_Light "Light" { channel="shelly:shelly1:483fda91aba0:relay#output" } and I still receive the following warning when using it: 2021-03-20 18:34:26.939 [WARN ] [e.internal.SseItemStatesEventBuilder] - Exception while formatting value 'OFF' of item Shelly_483fda91aba0_Light with format '%d': d != java.lang.String

skupfer avatar Mar 20 '21 17:03 skupfer

I suspect you would need to put [] in your Item file definition to erase the old 'state presentation pattern [%d] already in held in JSONDB, simply omitting any [presentation] may not be enough.

Rossko57 avatar Apr 16 '21 10:04 Rossko57

Items defined in a config file are read-only and they cannot be removed from MainUI.

Regarding the changed item, I imagine a simple restart of OH would have solved the problem.

I would suggest to close this issue.

lolodomo avatar Jul 03 '21 08:07 lolodomo

Items defined in a config file are read-only and they cannot be removed from MainUI.

Yep. That's why I deleted them from the config file just as usual. Should have made this more clear.

Regarding the changed item, I imagine a simple restart of OH would have solved the problem.

Best case scenario is that this shouldn't be necessary. Never had to restart before for simply deleting an item. That's why I guessed it's a bug or something and reported it here.

I would suggest to close this issue.

Up to you. Since it got a label I am not sure whether I should close it now.

skupfer avatar Jul 05 '21 19:07 skupfer

I can't reproduce this issue. Is this still present for you on 3.2 release or 3.3 milestone?

J-N-K avatar Apr 30 '22 17:04 J-N-K

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Jun 29 '22 18:06 stale[bot]