Closed sweetpants closed 1 year ago
Same here. A fix is appreciated!!
same here.
When installing from HACS, same issue with an extra error in the log
2022-07-07 10:31:45 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nefiteasy which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-07-07 10:31:59 WARNING (MainThread) [homeassistant.components.number] custom_components.nefiteasy.models is setting deprecated attributes on an instance of NumberEntityDescription, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author. 2022-07-07 10:31:59 DEBUG (MainThread) [custom_components.nefiteasy] Initialize Nefit class 2022-07-07 10:31:59 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 518910035 for nefiteasy File "/config/custom_components/nefiteasy/init.py", line 44, in async_setup_entry client = NefitEasy(hass, credentials) File "/config/custom_components/nefiteasy/init.py", line 107, in init
Same here
Stopped indeed, after update. We will wait for the fix ;)
See #152
This is an issue in the slixmpp library version used by aionefit. It should be fixed in aionefit, but as aionefit is not maintained anymore, it essentially becomes an issue here. Won't be easy to fix, a new supporting library is needed.
same here
The same issue on my server and hope you will/can update it. I love the Custom Component.
This is the upgrade to Python 3.10.5 that will be the problem.
This error originated from a custom integration.
Logger: homeassistant.config_entries
Source: custom_components/nefiteasy/__init__.py:107
Integration: Nefit Easy Bosch Thermostat (documentation, issues)
Error setting up entry... Removed Some numbers.... for nefiteasy
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 353, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/nefiteasy/__init__.py", line 44, in async_setup_entry
client = NefitEasy(hass, credentials)
File "/config/custom_components/nefiteasy/__init__.py", line 107, in __init__
self.nefit = NefitCore(
File "/usr/local/lib/python3.10/site-packages/aionefit/__init__.py", line 45, in __init__
self.xmppclient = NefitXmppClient(jid=self.jid,
File "/usr/local/lib/python3.10/site-packages/aionefit/provider/slixmpp_impl.py", line 32, in __init__
self.register_plugin('xep_0280') #carbons
File "/usr/local/lib/python3.10/site-packages/slixmpp/basexmpp.py", line 241, in register_plugin
self.plugin.enable(plugin, pconfig)
File "/usr/local/lib/python3.10/site-packages/slixmpp/plugins/base.py", line 165, in enable
self.enable(dep, enabled=enabled)
File "/usr/local/lib/python3.10/site-packages/slixmpp/plugins/base.py", line 165, in enable
self.enable(dep, enabled=enabled)
File "/usr/local/lib/python3.10/site-packages/slixmpp/plugins/base.py", line 153, in enable
load_plugin(name)
File "/usr/local/lib/python3.10/site-packages/slixmpp/plugins/base.py", line 82, in load_plugin
__import__(module)
File "/usr/local/lib/python3.10/site-packages/slixmpp/plugins/xep_0203/__init__.py", line 11, in <module>
from slixmpp.plugins.xep_0203 import stanza
File "/usr/local/lib/python3.10/site-packages/slixmpp/plugins/xep_0203/stanza.py", line 13, in <module>
from slixmpp.plugins import xep_0082
File "/usr/local/lib/python3.10/site-packages/slixmpp/plugins/xep_0082.py", line 12, in <module>
from slixmpp.thirdparty import tzutc, tzoffset, parse_iso
File "/usr/local/lib/python3.10/site-packages/slixmpp/thirdparty/__init__.py", line 7, in <module>
from slixmpp.thirdparty.orderedset import OrderedSet
File "/usr/local/lib/python3.10/site-packages/slixmpp/thirdparty/orderedset.py", line 25, in <module>
class OrderedSet(collections.MutableSet):
AttributeError: module 'collections' has no attribute 'MutableSet'
` collections module has changed I guess.
And also a deprecation change, that should have been fixed earlier, but I guess not noticed.
Logger: homeassistant.components.number
Source: components/number/__init__.py:152
Integration: Number (documentation, issues)
custom_components.nefiteasy.models is setting deprecated attributes on an instance of NumberEntityDescription, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author.
The deprecation message is also new to 2022.07 release. Every week this integration is built against the newest HA. Last week it built against a 2022.06 release still, no deprecation messages, so no way to have that fixed earlier.
Same problem here:
Error setting up entry 756920963 for nefiteasy July 7, 2022, 12:21:26 PM – (ERROR) Nefit Easy Bosch Thermostat (custom integration)
custom_components.nefiteasy.models is setting deprecated attributes on an instance of NumberEntityDescription, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author. July 7, 2022, 12:21:26 PM – (WARNING) number
Same here
+1 for this issue for me.
Please use the thumbs up on the original post instead of posting things like same here. It’s not adding anything. Everybody who uses this with 2022.07 will have this issue.
Use the thread if you have something useful to add.
still the same here. ;-) any progress in plan? this device here is running in a lot of automations, although it's summertime, I need to know when it will be fixed otherwise i have to replace it asap.
Nobody is getting paid here. I'm sure Rob already feels pressured. You cannot demand that you need to know when it's fixed. Fix it yourself.
Nobody is getting paid here. I'm sure Rob already feels pressured. You cannot demand that you need to know when it's fixed. Fix it yourself.
Thanks for stating the obvious
it's good you feel the pressure. I think you need to feel very responsible for any bug, if you can't handle the presure then stop offering the module to end users. if i could fix it i fix it, but it's not my baby, so please shed some light in the dark, that is the least you can do. The other option I have is roll back to a working version, but when I am not nformed it's hard to decide how to proceed from here.
it's good you feel the pressure. I think you need to feel very responsible for any bug, if you can't handle the presure then stop offering the module to end users. if i could fix it i fix it, but it's not my baby, so please shed some light in the dark, that is the least you can do.
Are you serious???? How much did you pay for using this component? How much did you contribute to the open source community? Are you really this thick!? It is thanks to people like Rob that we can run absolute great software for free. If you keep it up like this that will soon be a thing from the past. So, stuff it and buy something sh*t of the shelf and start complaining to a paid and ignorant 'client rep'...
I love this Component and don't mind the pressure. Be 'Zen' and we will be patiently waiting.
it's good you feel the pressure. I think you need to feel very responsible for any bug, if you can't handle the presure then stop offering the module to end users. if i could fix it i fix it, but it's not my baby, so please shed some light in the dark, that is the least you can do.
Are you serious???? How much did you pay for using this component? How much did you contribute to the open source community? Are you really this thick!? It is thanks to people like Rob that we can run absolute great software for free. If you keep it up like this that will soon be a thing from the past. So, stuff it and by something shot of the shelf and start complaining to a paid and ignorant 'client rep'...
i have spent many many expensive hours on this module
it's good you feel the pressure. I think you need to feel very responsible for any bug, if you can't handle the presure then stop offering the module to end users. if i could fix it i fix it, but it's not my baby, so please shed some light in the dark, that is the least you can do. The other option I have is roll back to a working version, but when I am not nformed it's hard to decide how to preceed from here.
For someone who wants a quick fix you may want to overthink your communication skills.
Luckily there are nice people here as well who understand :)
I don't need to do anything,what kind of people are you?
it's good you feel the pressure. I think you need to feel very responsible for any bug, if you can't handle the presure then stop offering the module to end users. if i could fix it i fix it, but it's not my baby, so please shed some light in the dark, that is the least you can do. The other option I have is roll back to a working version, but when I am not nformed it's hard to decide how to preceed from here.
For someone who wants a quick fix you may want to overthink your communication skills.
Luckily there are nice people here as well who understand :)
the moment you moaned about only thumps up, i knew you where not taking reponsibility on your product. it's really sad how you are communicating this.
All. Let us give the developer/owner some time to see how to fix this! As long as it is summer we do not really need the thermostat, do we??? And a walk to the wall mounted easy-device does not hurt anyone....
Jeetje wat een berichten allemaal hiero.....
Jeez what a discussion here, and for what?
Take your time, drink a beer and all will be ok....no pressure.....
Carpe Diem ...... Enjoy your life...there are more other thinks to worried about...
Love and respect all.....happy days
Op vr 8 jul. 2022 20:00 schreef Rob Bierbooms @.***>:
it's good you feel the pressure. I think you need to feel very responsible for any bug, if you can't handle the presure then stop offering the module to end users. if i could fix it i fix it, but it's not my baby, so please shed some light in the dark, that is the least you can do. The other option I have is roll back to a working version, but when I am not nformed it's hard to decide how to preceed from here.
For someone who wants a quick fix you may want to overthink your communication skills.
Luckily there are nice people here as well who understand :)
— Reply to this email directly, view it on GitHub https://github.com/ksya/ha-nefiteasy/issues/153#issuecomment-1179239213, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALEFS6REEKAGE3K64T3RSKLVTBUE5ANCNFSM524MIG2Q . You are receiving this because you commented.Message ID: @.***>
@KYHS-BOX I suggest you remove the integration. This was not meant for people like you. You totally misunderstand the concept of free open source software.
Workaround implemented, thanks to @spoetnik
Since the latest upgrade of HA to 2022.7.0, this integration stopped working. Logviewer says:
2022-07-07 09:33:05 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration nefiteasy which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-07-07 09:33:23 DEBUG (MainThread) [custom_components.nefiteasy] Initialize Nefit class 2022-07-07 09:33:23 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 518910035 for nefiteasy File "/config/custom_components/nefiteasy/init.py", line 106, in async_setup_entry client = NefitEasy(hass, credentials) File "/config/custom_components/nefiteasy/init.py", line 169, in init
Re-install of this integration did not help
Regards, Harry