What probably happens is the widget needs you to define an item for its widget property, but you haven’t specified / defined one. So when the widget looks up the property, e.g.
prop[temperature_item_or_something] this resulted in (evaluated to) undefined, and this gets requested to openhab, thus triggering the warning message.
@florian-h05 is there something we can do on the webui to detect this situation and somehow warn the user to make it easier to pinpoint the source of the problem, ie the problematic widget?
With reasonable effort not really … I had a look into the expression parsing some time ago and hoped that I could change its behaviour, so that for undefined Item names no state tracking is tried, however I only managed to get this working for the aliases @ and @@.
When using @ and @@ aliases instead of the items.itemname.state syntax, no request will be send to the server if the item name is undefined.