-
Notifications
You must be signed in to change notification settings - Fork 2
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
TypeError: 'WMClient' object is not callable #14
Comments
@dcmeglio should we consider this abandoned and possibly looking for adoption ? |
Yes. I no longer have waste management for my trash service so I can’t really provide any support for this. |
I would be happy to at least try and adopt the repo / project but I would need you to grant me appropriate access to do things like accept MR's and manage actions for the both repo's for release tasks. I could also fork it and you could deprecate and link to mine if that is better for you.. |
@johntdyer there might be a bug in your version of HomeAssistant that doesn't allow the python module to be loaded during startup. Depending on your sys.path, HomeAssistant will try to load the module during runtime when the sensor is added or updated, which is considered a blocking operation. As a workaround, I copied the waste_management python module from /config/deps/ to /config/custom_components/waste_management/ I then updated config_flow.py & sensor.py files to load the classes from component's location instead of relying on the larger python environment. Change line 14 of sensor.py & line 17 of config_flow.py from: to: Restart HomeAssistant. I don't know how long this will work nor what versions are all affected but it's something. |
@ParagonDefect - ok, but I am running HassOS, so arent those libraries immutable docker layers and just going to reset on restart? |
Core - 2024.12.1
Supervisor 2024.11.4
OS - 14.0
The text was updated successfully, but these errors were encountered: