-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
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
Uncaught thread exception #43388
Comments
Edit: I removed below customization, the issue persists. |
This is a reopen of: #41479 that seem to have been incorrectly closed. |
This is a guess, but our signature for the on disconnect callback does not match v5 semantics here: https://github.com/eclipse/paho.mqtt.python/blob/5a9ca61a6c3071972caddf554490bf9ee5316491/src/paho/mqtt/client.py#L2027 We don't expect a properties parameter in our mqtt integrations here: core/homeassistant/components/mqtt/__init__.py Line 1013 in 7f640c4
|
Ps. Still does not explain how the exception is logged. I wonder if /usr/local is really where hassos installs deps. |
Hey there @home-assistant/core, @emontnemery, mind taking a look at this issue as its been labeled with an integration ( |
Opening #41479 was my fault, we should not have rolled back PAHO MQTT to 1.5.0 and it was re-bumped back to 1.5.1 shortly after. The link to paho code is not correct, Home Asssistant core pins v1.5.1, so this is the right version to link to: https://github.com/eclipse/paho.mqtt.python/blob/v1.5.1/src/paho/mqtt/client.py#L3360 The line numbers in the stack trace matches v.1.5.1precisely, so the issue shouldn't be Home Assistant picking up the wrong version of PAHO MQTT. Our core/homeassistant/components/mqtt/__init__.py Line 1013 in aec17d2
It's however not named @gdiciancia have you added some other customization or modification which is interfacing with MQTT? |
@emontnemery, Not that we can think of. I use the standard mqtt add-on. If you can be more specific, I can look more in detail. I had either wemos connected via mqtt or 1 Shelly 3EM with auto discovery. No customization on Home assistant |
Try searching for any python file including |
The signature is not really incorrect per say. It's just not compatible with v5 of mqtt: https://github.com/eclipse/paho.mqtt.python/blob/42f0b13001cb39aee97c2b60a3b4807314dfcb4d/src/paho/mqtt/client.py#L467 It can send an additional properties field. That said, i agree the error would seem to be from another version of paho. @gdiciancia do you think you can uninstall (pip uninstall paho-mqtt) inside the home assistant core container. Then let restart home assistant so it reinstalls it as a dependency. |
@elupus, I’ll give that a try a soon as possible |
@elupus Home Assistant is not using MQTT version 5, and as I mentioned before the callback is named Hence, try to find a python package interfacing PAHO, with a function named |
Found it. I'm using the Roomba integration (added via discovery). This is what the search found: |
I opened a PR on roombapy to fix this. |
roomba documentation |
This should be fixed by #43594 which bumps roombapy to 1.6.2 which includes pschmitt/roombapy#45 |
The problem
Recurring error multiple times a minute showing up in the logs.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
For MQTT I use:
This are the only custom things I have (I don't use HACS):
The text was updated successfully, but these errors were encountered: