That happens because when we parse the logs a lot of times fields have null values and the description of the field in the HA documentation says it contains a string value so we assume it will always be a string. BUT, sometimes the field represents a list of possible values and then it shows up in the json as an array of strings. e.g. {state: "on"} vs. {state: ["on", "off", "unknown"]}. When the driver gets a non-null value that it thinks should be a string but it really is an array then we get that error.
To fix we need the verbose HA log so we can see what device and value needs to be parsed differently.
