-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT statestream errors - Object of type ServiceEventData is not JSON serializable #639
Comments
The MQTT integration is a prerequisite for MQTT Statestream to work. We dont use the mqtt integration, we use MQTT as a method to receive our own push messages from MySkoda, but we do not use the HA MQTT integration. Unless I offcourse misunderstand the problem |
Yes this has nothing to do with myskoda using MQTT. Statestream is a core HA integration that mirrors changes to entities and attributes over MQTT. One of the entities that myskoda creates breaks this integration because the data it stores is not serializable. I first raised this issue with statestream but was then asked to raise it here as this problem has not been seen with any other entity across many integrations. |
Right, so this would be because the Options:
|
We will treats this as an enhancement request, not as a bug, since we aim to be compliant with HA, not all it's components, we're simply too young for that. Thanks for the additional information👍 |
With MQTT statestream (https://www.home-assistant.io/integrations/mqtt_statestream/) configured in Home Assistant with all entities and attributes included, the following error gets logged many times with the myskoda integration installed, causing missed MQTT messages:
I've narrowed the issue down to the data and history attributes on the last_service_event entity, which I assume makes use of this ServiceEventData type. I've excluded that item from statestream for now, but is it possible to make it JSON serializable to prevent this from happening?
The text was updated successfully, but these errors were encountered: