-
Notifications
You must be signed in to change notification settings - Fork 11
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
Deprecation warnings with 2024.1.0 #42
Comments
I'm not sure if this is related to @sweharris's comment above, but after the last update to Core 2024.1, my dehumidifier entity no longer shows up: Status reads: "This entity is no longer being provided by the frigidaire integration. If the entity is no longer in use, delete it in settings." Oddly enough, my automations that turn the dehumidifier on and off still run, even if I can't control the unit through the UI or see status. Presumably calls to the Frigidaire cloud server are still being passed through correctly. |
Sooo....it's working again for me, after HA Core 2024.1.1 updated this morning :) |
Sharing this as well, in case it's helpful: WARNING (MainThread) [homeassistant.helpers.entity] Entity None (<class 'custom_components.frigidaire.humidifier.FrigidaireDehumidifier'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <HumidifierEntityFeature.MODES: 1>, please create a bug report at https://github.com/bm1549/home-assistant-frigidaire/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation |
Hi @bm1549 - can you clarify why this is not planned? Are you no longer supporting the dehumidifier through this integration? Just wanted to confirm one way or another since the warnings are still present and 2025.1 is coming up soon. Thanks! |
I must have mistaken this. Re-opened the issue Unfortunately, I do not own a dehumidifier to test so someone else would need to make the necessary changes here |
I suspect you're aware of this, but I thought I'd raise the issue just so it's documented.
After an update to 2024.1.0
The text was updated successfully, but these errors were encountered: