-
Notifications
You must be signed in to change notification settings - Fork 579
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
Home Assistant 2022.7: LocaltuyaNumber is overriding deprecated methods on an instance of NumberEntity #929
Comments
I updated to HA core 2022.7 today and I see the same warning.
|
Relates to issues [929](rospogrigio#929), [939](rospogrigio#939) & [941](rospogrigio#941) I do not have any suitable tuya devices in use to test against this number entity however the warning in logs "LocaltuyaNumber is overriding deprecated methods on an instance of NumberEntity] is now gone https://developers.home-assistant.io/blog/2022/06/14/number_entity_refactoring/
Will follow here for updates 👍🏻 |
Using the changes in this commit/pull request worked for me. Thanks! |
same problem I am facing Logger: homeassistant.components.number custom_components.localtuya.number::LocaltuyaNumber is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author. suddenly my Local Tuya devices go offline and I need to restart HA to fix it |
hey how do we do this? pls help |
You will need to make the changes manually to the custom_components/localtuya/number.py file using file editor. |
yes did that and it worked, thanks :) |
Relates to issues [929](rospogrigio#929), [939](rospogrigio#939) & [941](rospogrigio#941) I do not have any suitable tuya devices in use to test against this number entity however the warning in logs "LocaltuyaNumber is overriding deprecated methods on an instance of NumberEntity] is now gone https://developers.home-assistant.io/blog/2022/06/14/number_entity_refactoring/
obviously newbie here. thats my "number.py" code:
|
@sebaschn See https://github.com/rospogrigio/localtuya/pull/944/files for the changes you have to make (red lines are old, green lines are new, blue and white ones unchanged) Ran into this problem just today |
@ElStupid |
Relates to issues [929](rospogrigio#929), [939](rospogrigio#939) & [941](rospogrigio#941) I do not have any suitable tuya devices in use to test against this number entity however the warning in logs "LocaltuyaNumber is overriding deprecated methods on an instance of NumberEntity] is now gone https://developers.home-assistant.io/blog/2022/06/14/number_entity_refactoring/
I still have local tuya down even after updating number.py manually. 2022.8.7 `Logger: homeassistant Error doing job: Exception in callback _SelectorDatagramTransport._read_ready() |
Relates to issues [929](#929), [939](#939) & [941](#941) I do not have any suitable tuya devices in use to test against this number entity however the warning in logs "LocaltuyaNumber is overriding deprecated methods on an instance of NumberEntity] is now gone https://developers.home-assistant.io/blog/2022/06/14/number_entity_refactoring/
Now closable |
#944 fixed the isssue. Thanks for all the help! |
The problem
Per Home Assistant 2022.7, i receive the following warning. There is no functional impact yet (which makes sense, it will sart breaking in version 2022.10). Local Tuya is making use of a to-be-deprecated mtehod.
Environment
Steps to reproduce
Configuration
configuration.yaml
orconfig_flow
DP dump
Provide Home Assistant taceback/logs
Additional information
The text was updated successfully, but these errors were encountered: