-
Notifications
You must be signed in to change notification settings - Fork 423
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
XNumber/XPulseWidth is overriding deprecated methods on an instance of NumberEntity #897
Comments
Thanks for reporting. Was about to report this |
Same problem here |
Same here… |
Using the changes in this commit/pull request worked for me. Thanks! |
Greetings, |
You have a different issue - this issue will not cause that behavior - it is just a warning. |
Any news regarding this issue ? |
I still get errors for some devices, even after the new v3.2.0 update
|
Are you sure you using v3.2.0? |
Yes. v3.2.0 Edit: only 1-2 devices from more than 50 :-D Edit2: I think I found out why these two are getting me this error. I have enabled 3 of the entities, which I use in automation. |
|
Check it, maybe you done what I done as well :-D Disabling those entities, will remove the error |
Currently I still see this error message in Logger.
|
I disabled it. |
Hi everyone, I still get the error for one device. I am on v3.2.0 of the integration (that is what HACS says). My version of HA is 2022.7.2. The entity 'number.sonoff_10002c57c2_pulseWidth' is already disabled. However the log mentions the entity 'sonoff.sonoff_10002c57c2_pulseWidth', which is nonexistent. This are the warnings in the log: Thanks. |
I also am having this issue as soon as I enable number.sonoff_switch_pulsewidth entities. |
Will be fixed again |
No need to fix anything in my case. After I upgraded to HA 2022.09.1 the warnings in the log stopped. Sorry for not mentioning it before. Thanks for all your work. |
Newest release 3.1.0 gives the following warnings in HA logs:
All works fine at the moment.
edit: TO OTHER USERS: no need to report 'same here' or alike messages. Your component is still working fine, this is a dev warning. IF you want to report that you are seeing the same, just hit the thumbs-up button in this post.
The text was updated successfully, but these errors were encountered: