I am seeing the following warning show up in the logs quite a lot:
QuestDB: Unsupported value type for MY_ITEM: <class 'NoneType'>
This is caused by the quest_microservice.py code not allowing None values through the match-case statement so if falls back to that warning message. The MY_ITEM in this case is a derived item that is put together from other items, but depending on the current configuration it may just remain null which fills up the log output with that warning message.

The following line is in the section of code where this match-case statement is located. I am not sure what the ramifications are or if it is the right approach to even allow None values in a database, but is changing it to case float() | str() | None: sufficient here?