I’m starting to see these errors in the log for most Items during startup. While they are on Items that are linked to channels in a binding that I’m working on, I don’t believe that bindings bundle has even been started at this stage.
Tried to set invalid state 0.0 (DecimalType) on item <my_item> of type StringItem, ignoring it
My best guess is that something it trying to restore some persisted channel states, and getting it very wrong.
The binding is generally using ASCII values to represent states [A-Za-z0-9], so the actual value in the string is the ASCII character code; i.e. 0 (0x30). For some reason it looks like it’s trying to restore the previous value, which was {(byte)0x30}, but it’s somehow parsed the string into a decimal, then it complains the decimal it converted it to is not appropriate for the String Item type, OR, whatever did the persistence incorrectly stored it as a decimal and then it fails to restore.
Plus, it’s wrong, {(byte)0x30,(byte)0x2E,(byte)0x30} is perfectly valid in a string, even if it is a corrupted non-sense value, it’s not a type violation.
Is this a known bug?