Closed Cereal2nd closed 1 year ago
@DannyDeGaspari this is something i see since the merge of #66
I'll try to reproduce it, did not get this error while testing. Maybe because I cleared the cache first?
nevermind indeed it was the cache ....
I'm afraid HA users will bump into the same issue. Is there something foreseen on the HA side that with breaking cache releases of velbus-aio, the cache needs to be cleared ?
no, we will have to implement this
and befor this is implemented we can not upgrade, so i have a lot of work on the hass side:
Let me know if I can be of any help with testing.
I've run into the same problem when developing. This is something that's on my "I'll need to fix this"-list, but haven't gotten around to. I think the best way to solve this is to move from pickle to our own (de)serializer (e.g. JSON?), where the deserializer takes care of the upgrade path.
@Cereal2nd Should this be a separate Issue specifically for "Make deserializer from cache backward compatible"? Or can we re-purpose this issue for that?
We can do whatever we want reuse this one or create a new one.
But we either fix this asap, or we continue to handle this on the Hass side. On the Hass side this change is minimal and I have this almost implemented
If we fix this on the velbusaio side we need to have a solution before we can upgrade Hass to this newer version.
I'll open a new issue, for the 'long term solution'; when and if we get around to that. Go ahead with the Hass-side fix.