You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow up of #81535 In my long run to have my Bticino system working with Home Assistant.
After upgrading to 2022.11.2 i get this new issue. Couldn’t find any reference online of what Z3L is :-(
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/pyatmo/home.py", line 72, in get_module
return getattr(modules, module["type"])(
AttributeError: module 'pyatmo.modules' has no attribute 'Z3L'
What version of Home Assistant Core has the issue?
core-2022.11.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Core
Integration causing the issue
Netatmo
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: homeassistant.config_entries
Source: components/netatmo/data_handler.py:199
First occurred: 10 novembre 2022, 18:28:22 (1 occurrences)
Last logged: 10 novembre 2022, 18:28:22
Error setting up entry Home Assistant Cloud for netatmo
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/pyatmo/home.py", line 72, in get_module
return getattr(modules, module["type"])(
AttributeError: module 'pyatmo.modules' has no attribute 'Z3L'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 365, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/netatmo/__init__.py", line 164, in async_setup_entry
await data_handler.async_setup()
File "/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py", line 151, in async_setup
await self.subscribe(ACCOUNT, ACCOUNT, None)
File "/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py", line 243, in subscribe
await self.async_fetch_data(signal_name)
File "/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py", line 199, in async_fetch_data
await getattr(self.account, self.publisher[signal_name].method)(
File "/usr/local/lib/python3.10/site-packages/pyatmo/account.py", line 69, in async_update_topology
self.process_topology()
File "/usr/local/lib/python3.10/site-packages/pyatmo/account.py", line 58, in process_topology
self.homes[home_id] = Home(self.auth, raw_data=home)
File "/usr/local/lib/python3.10/site-packages/pyatmo/home.py", line 49, in __init__
self.modules = {
File "/usr/local/lib/python3.10/site-packages/pyatmo/home.py", line 50, in <dictcomp>
module["id"]: self.get_module(module)
File "/usr/local/lib/python3.10/site-packages/pyatmo/home.py", line 78, in get_module
return getattr(modules, "NLunknown")(
File "/usr/local/lib/python3.10/site-packages/pyatmo/modules/module.py", line 508, in __init__
self.device_type = DeviceType(module["type"])
File "/usr/local/lib/python3.10/enum.py", line 385, in __call__
return cls.__new__(cls, value)
File "/usr/local/lib/python3.10/enum.py", line 710, in __new__
raise ve_exc
ValueError: 'Z3L' is not a valid DeviceType
Additional information
No response
The text was updated successfully, but these errors were encountered:
The problem
Follow up of #81535 In my long run to have my Bticino system working with Home Assistant.
After upgrading to 2022.11.2 i get this new issue. Couldn’t find any reference online of what Z3L is :-(
What version of Home Assistant Core has the issue?
core-2022.11.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Core
Integration causing the issue
Netatmo
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: