Skip to content
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

Error messages #6

Closed
maxverstappen opened this issue Jun 17, 2021 · 4 comments
Closed

Error messages #6

maxverstappen opened this issue Jun 17, 2021 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@maxverstappen
Copy link

I get the following errors
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/climatisationWithoutExternalPower: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/climatizationAtUnlock: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/windowHeatingEnabled: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/zoneFrontLeftEnabled: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/zoneFrontRightEnabled: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/zoneRearLeftEnabled: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/zoneRearRightEnabled: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: id /vehicles/XXXXXX/controls/charging cannot be set. You need to provide it in the correct format select one of [start, stop]
INFO:weconnect-mqtt:Error setting value: id /vehicles/XXXXXX/controls/climatization cannot be set. You need to provide it in the correct format select one of [start, stop]
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/climatisationWithoutExternalPower: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/climatizationAtUnlock: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/windowHeatingEnabled: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/zoneFrontLeftEnabled: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/zoneFrontRightEnabled: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXXstatus/climatisationSettings/zoneRearLeftEnabled: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: /vehicles/XXXXXX/status/climatisationSettings/zoneRearRightEnabled: new value must be of type <class 'bool'> but is of type <class 'str'>
INFO:weconnect-mqtt:Error setting value: id /vehicles/XXXXXX/controls/charging cannot be set. You need to provide it in the correct format select one of [start, stop]
INFO:weconnect-mqtt:Error setting value: id /vehicles/XXXXXX/controls/climatization cannot be set. You need to provide it in the correct format select one of [start, stop]

Most data is received in MQTT server.

@tillsteinbach
Copy link
Owner

I'll have a look. My first idea is that the client receives the old messages it had previously published itself when subscribing. My idea was that this won't happen if I publish an empty message with retain flag. I have to check the standard there. For now I'll see if I can just ignore empty messages.
So I guess all you can see is correct, but I have to get rid of the ugly error messages.

@tillsteinbach tillsteinbach self-assigned this Jun 17, 2021
@tillsteinbach tillsteinbach added the bug Something isn't working label Jun 17, 2021
@tillsteinbach
Copy link
Owner

@maxverstappen can you check if Version 0.6.2 fixes your problem? Thanks!

@maxverstappen
Copy link
Author

10 points. Works like a charm.

@tillsteinbach
Copy link
Owner

Nice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants