Unfortunately after upgrading hassio to 0.61.1, fritzhome is starting with an eroor and no devices are available
I already copied the latest versions from your Github…, but it’s not working. These are the errors I’m receiving:
Timer got out of sync. Resetting
09:50 core.py (ERROR)
Error during setup of component fritzhome
09:50 deps/lib/python3.6/site-packages/pyfritzhome/fritzhome.py (ERROR)
Unable to load /config/known_devices.yaml: while scanning a simple key in "/config/known_devices.yaml", line 322, column 3 could not find expected ':' in "/config/known_devices.yaml", line 323, column 3
09:50 components/device_tracker/__init__.py (ERROR)
while scanning a simple key in "/config/known_devices.yaml", line 322, column 3 could not find expected ':' in "/config/known_devices.yaml", line 323, column 3
09:50 util/yaml.py (ERROR)`Preformatted text`
Any ideas? Or is it a dependency from the known_devices error? But I can’T see any misfunctiondue to this error message
even with the latest version of Fritzhome climate runs still into errors:
Error while setting up platform fritzhome
23:35 custom_components/climate/fritzhome.py (ERROR)
Error while setting up platform fritzhome
23:35 custom_components/switch/fritzhome.py (ERROR)
here the details:
Tue Jan 23 2018 23:35:53 GMT+0100 (W. Europe Standard Time)
Error while setting up platform fritzhome
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 171, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
return fut.result()
File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result
raise self._exception
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/switch/fritzhome.py", line 24, in setup_platform
for device in device_list:
TypeError: 'Fritzhome' object is not iterable
and:
Tue Jan 23 2018 23:35:53 GMT+0100 (W. Europe Standard Time)
Error while setting up platform fritzhome
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 171, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
return fut.result()
File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result
raise self._exception
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/climate/fritzhome.py", line 38, in setup_platform
for device in device_list:
TypeError: 'Fritzhome' object is not iterable
@hthiery: would be great if you could help me out on that…
@hthiery I really don’t wanna bother you…
But I’m currently trying to get forward with some other things, and all of a sudden I receive again some errors…(even after moving back all changes…)
Could you have again a look?
Log Details (ERROR)
Fri Jan 26 2018 01:23:56 GMT+0100 (Mitteleuropäische Zeit)
Error while setting up platform fritzhome
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 171, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
return fut.result()
File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result
raise self._exception
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/climate/fritzhome.py", line 40, in setup_platform
device_list = fritz.get_devices()
File "/config/deps/lib/python3.6/site-packages/pyfritzhome/fritzhome.py", line 127, in get_devices
device = FritzhomeDevice(self, node=element)
File "/config/deps/lib/python3.6/site-packages/pyfritzhome/fritzhome.py", line 231, in __init__
self._update_from_node(node)
File "/config/deps/lib/python3.6/site-packages/pyfritzhome/fritzhome.py", line 250, in _update_from_node
self.actual_temperature = int(get_node_value(n, 'tist')) / 2
ValueError: invalid literal for int() with base 10: ''
OK after upgrade to 0.62.0 works again…
Probabyl it was related to the double entries in the known devices? I remeber there were some entries in the log with double devices…
anyway: works fine again.
A big thank you for your work in general. Do you know when it will be integrated in homeassistant?
Hi @hthiery, will you be planning support for more than 1 FritzBox in future? Built-in AVM module does support that, but no Comet Dect and your module supports Comet Dect, but only 1 Box . Would be really nice to find a solution for that one day…
As I understood, your development is a custom on not (yet) included in official repository. This one supports DECT 300 / Comet DECT, too, but only for one box. I wanted to know, if multi-box support is planned by you in future.
I’m working on Integration to upstream and plan to support multiple fritzboxes.
First I will release a custom component in my GitHub repo. Just to note that the platform is renamed from fritzhone to fritzbox. This was done after a discussion with the Home-Assistent maintainers.
Hi, a new version with multi fritzbox support is now available on my github account. Please try it out and give feedback if this will work wiht multiple fritzboxes on your site. This would be great because I use only one fritzbox.
having the problem with failed login for my second box. See more details here:
Could you help? Only difference with regard to my 1st box is that 2nd box is not really local, but permanently connected via VPN. It is detected by device tracker of platform fritz, but login fails nonetheless. Credentials are correct.
Yes, fritzbox component and access of dect smarthome devices connected to fritzboxes.
As described in the thread linked to you (see all my fritzbox-related config there), I access my second fritzbox the same way like my first one - by IP address. HASS can then login to the first - like before - but for the second one, login fails. I suppose that the reason may be that this box is not connected really locally, but by a permanent VPN connection. But maybe, I am wrong and there seems to be another kind of bug.
. Would be really nice to find a solution for that one day…