The first issue is the choice of base component type here. An oh-list-card is expecting specific items as it’s children: list items. So while you can render other thing such as the oh-label-card within the list, the results are not necessarily going to be what you expect. In this case, you probably just want a more basic starting component such as an f7-card or f7-block.
Most of the other issues are with this line here:
The yaml definitions interpret all inputs as strings unless you explicitly define them as expressions using the = at the front. So, in this case you are not setting the input array to your JSON text you are setting it to the literal string "items[14_Entry_Users]".
To access the keys in the items object using the bracket notation, your item name must be a string. It can either be a variable that holds a string value or if its a literal string then it needs " around it.
Here in the widgets, the items object has both .state. and .displayState properties, so you have to specify which you want at all times. In this case I assume you want the raw .state.
Whenever you retrieve an item state in the widget yaml it is simply a string (that’s how it gets delivered by the API). So this won’t be an actual array of JSON objects until you parse that state string. The widgets can use the parse method of the javascript JSON object.
Taken together then, this line should probably be: