Home assistant error Received unhandled response 0x8012 tradfri IKEA #104

baimard · 2021-11-07T13:25:03Z

``

Line 22 in 818c3a1

RESPONSES = {

My IKEA light send me a 0x8012 answer.

Is it possible to had this response ?

home_assistant.1.mn6u4y319qpd@ocre    | 2021-11-07 14:18:38 DEBUG (MainThread) [zigpy_zigate.uart] Frame received: 80000009be00b7053001b7000300
home_assistant.1.mn6u4y319qpd@ocre    | 2021-11-07 14:18:38 DEBUG (MainThread) [zigpy_zigate.api] data received 0x8000 b'00b7053001b70003' LQI:0
home_assistant.1.mn6u4y319qpd@ocre    | 2021-11-07 14:18:38 DEBUG (MainThread) [zigpy_zigate.zigbee.application] zigate_callback_handler [0, 183, 1328, b'\x01\xb7\x00\x03']
home_assistant.1.mn6u4y319qpd@ocre    | 2021-11-07 14:18:38 DEBUG (MainThread) [zigpy_zigate.uart] Frame received: 8012000a47000101025231b700030a
home_assistant.1.mn6u4y319qpd@ocre    | 2021-11-07 14:18:38 DEBUG (MainThread) [zigpy_zigate.api] data received 0x8012 b'000101025231b70003' LQI:10
home_assistant.1.mn6u4y319qpd@ocre    | 2021-11-07 14:18:38 ERROR (MainThread) [zigpy_zigate.api] Received unhandled response 0x8012

The text was updated successfully, but these errors were encountered:

baimard · 2021-11-16T10:17:05Z

RESPONSES = {
    0x004D: (t.NWK, t.EUI64, t.uint8_t, t.uint8_t),
    0x8000: (t.uint8_t, t.uint8_t, t.uint16_t, t.Bytes),
    0x8002: (t.uint8_t, t.uint16_t, t.uint16_t, t.uint8_t, t.uint8_t,
             t.Address, t.Address, t.Bytes),
    0x8009: (t.NWK, t.EUI64, t.uint16_t, t.uint64_t, t.uint8_t),
    0x8010: (t.uint16_t, t.uint16_t),
    0x8011: (t.uint8_t, t.NWK, t.uint8_t, t.uint16_t, t.uint8_t),
    0x8012: (t.uint32_t,),
    0x8017: (t.uint32_t,),
    0x8024: (t.uint8_t, t.NWK, t.EUI64, t.uint8_t),
    0x8035: (t.uint8_t, t.uint32_t),
    0x8048: (t.EUI64, t.uint8_t),
    0x8701: (t.uint8_t, t.uint8_t),
    0x8702: (t.uint8_t, t.uint8_t, t.uint8_t, t.Address, t.uint8_t),
    0x8806: (t.uint8_t,),
}

I just add this line : 0x8012: (t.uint32_t,),

nlhomme · 2021-11-28T11:08:06Z

I'm having the same issue on Home Assistant with the ZHA integration:

Logger: zigpy_zigate.api
Source: /usr/local/lib/python3.9/site-packages/zigpy_zigate/api.py:115
First occurred: 12:03:31 (2 occurrences)
Last logged: 12:03:33
Received unhandled response 0x8012

My Zigbee controller is a Zigate v1 with firmware 3.1e

See issues 104 for more details

nlhomme · 2021-12-16T10:54:46Z

It seems that this issue has been treated in #107

Hedda · 2022-01-03T08:29:55Z

@baimard You might want to consider reopening issue and @nlhomme might want to create a new pull request based on #107

See the last comment by pipiche38 in #107

we are currently working on zigpy-zigate library under a fork dedicated to our project, we don't have the possibility to test it under the ZHA environment but if you are ready to do, you can eventually use it https://github.com/zigbeefordomoticz/zigpy-zigate

When ready we will be providing PRs against the main stream

Forking a project/library means that the library has been copied and some or any code patches (like new fixes or features) to forks might or might not be actively contributed back to the original upstream project by the developers that are working on that forked version.

In this case, it means that there is at least one patch in the fork https://github.com/zigbeefordomoticz/zigpy-zigate that is not available in upstream https://github.com/zigpy/zigpy-zigate but those patches in that fork are not currently being actively tested to check for any breakage in the ZHA integration component in Home Assistant by the developers working on that fork of zigpy-zigate as they are testing the library with another software application and do not have time or interest in regression testing with other applications using the same library, like ZHA.

As in, if you want those patches to be in upstream now rather than hoping that they might be added later then regression testing of that fork (or just specific patches) is needed by other volunteers and then once confirmed not broken anything, someone, either the tester or some other volunteer will need to backport that and any other acceptable fixes from that fork back here to the upstream zigpy-zigate.

Terminology for reference:

If you have the ability to test that fork with your setup then please do so and report your result here and also to #107 and #106

There is some more information about testing here that would need to be adapted when working with a forked library version:

PS: As I understand it, the main reason why they choose to fork to https://github.com/zigbeefordomoticz/zigpy-zigate rather than just keep submitting pull requests to upstream https://github.com/zigpy/zigpy-zigate is that no zigpy developers who own any ZiGate hardware and have a personal interest in maintaining support for are currently actively working on maintaining upstream https://github.com/zigpy/zigpy-zigate thus new volunteering developers with a personal interest in maintaining support is needed.

baimard · 2022-01-03T08:43:31Z

done

pipiche38 · 2022-01-03T11:07:44Z

@baimard You might want to consider reopening issue and @nlhomme might want to create a new pull request based on #107

See the last comment by pipiche38 in #107

we are currently working on zigpy-zigate library under a fork dedicated to our project, we don't have the possibility to test it under the ZHA environment but if you are ready to do, you can eventually use it https://github.com/zigbeefordomoticz/zigpy-zigate
When ready we will be providing PRs against the main stream

Forking a project/library means that the library has been copied and some or any code patches (like new fixes or features) to forks might or might not be actively contributed back to the original upstream project by the developers that are working on that forked version.

In this case, it means that there is at least one patch in the fork https://github.com/zigbeefordomoticz/zigpy-zigate that is not available in upstream https://github.com/zigpy/zigpy-zigate but those patches in that fork are not currently being actively tested to check for any breakage in the ZHA integration component in Home Assistant by the developers working on that fork of zigpy-zigate as they are testing the library with another software application and do not have time or interest in regression testing with other applications using the same library, like ZHA.

As in, if you want those patches to be in upstream now rather than hoping that they might be added later then regression testing of that fork (or just specific patches) is needed by other volunteers and then once confirmed not broken anything, someone, either the tester or some other volunteer will need to backport that and any other acceptable fixes from that fork back here to the upstream zigpy-zigate.

Terminology for reference:
* https://en.wikipedia.org/wiki/Fork_(software_development)

* https://en.wikipedia.org/wiki/Regression_testing

* https://en.wikipedia.org/wiki/Backporting
If you have the ability to test that fork with your setup then please do so and report your result here and also to #107 and #106

There is some more information about testing here that would need to be adapted when working with a forked library version:
* https://github.com/zigpy/zigpy-zigate#testing-new-releases

* https://github.com/zigpy/zigpy/blob/dev/CONTRIBUTING.md

* https://github.com/zigpy/zha-device-handlers/#testing-quirks-in-development-in-docker-based-install
PS: As I understand it, the main reason why they choose to fork to https://github.com/zigbeefordomoticz/zigpy-zigate rather than just keep submitting pull requests to upstream https://github.com/zigpy/zigpy-zigate is that no zigpy developers who own any ZiGate hardware and have a personal interest in maintaining support for are currently actively working on maintaining upstream https://github.com/zigpy/zigpy-zigate thus new volunteering developers with a personal interest in maintaining support is needed.

I don't understand all of this communication from @Hedda, if you are against what we are currently doing, tell us frankly , but so far the zigpy-zigate library is stuck and not maintained. So it is unbelievable to read such messages !

MattWestb · 2022-01-03T11:24:23Z

I agree with @pipiche38 but if hi and some more like forking some part (or all) of the Zigpy libs and patching it like more devs have doing in other system its more than OK.
The best is they can making the patches upstream for easter maintaining there system but its not primary one Zigpy problem but its best for all if its possible doing it.

In the end if more support for different hardware /system then better for all parts and our community.

Also having more devs working with different parts is also one win win situation then getting more devices supported in the upstream (pipiche38 have helping getting more device added and some other system have doing the same).

I hope all is working well and getting all part in place and the system working with Zigpy libs as underlying radio lib.

Witch one great 2022 to all that is helping all working well in our system and many hours or nice "dream coeding" for getting more function in place !!

pipiche38 · 2022-01-03T12:55:28Z

@MattWestb this is exactly my point, we are currently trying to enhance the zigpy-zigate layer, because we benefits from all good work done on zigpy and especially zigpy-znp.
At the end we are not interested to use zigpy-zigate as we have our own native way to communicate with zigate and for now there is no plan. Our approach was to get zigpy-zigate to a point where it is usable , now if the zigpy community @Hedda feels this is not interested for them, fine.

Hedda · 2022-01-07T09:44:47Z

I don't understand all of this communication from @Hedda, if you are against what we are currently doing, tell us frankly , but so far the zigpy-zigate library is stuck and not maintained. So it is unbelievable to read such messages !

@pipiche38 I am not against what you are doing at all. I am not against it in any way. I am very much a fan of what you are trying to achieve and think all that you guys are doing is a good thing. I think that it is great that more projects are trying to use zigpy.

I was just trying to inform others what it means by a fork as do not think that was made clear when the pull requests were closed.

Personally, I understand why you forked and understand that it will hopefully not be your long term goal but something that has to be done in order to speed up the development process and part of the normal everyday development process.

So, me being frank; I really LOVE what you have been doing with your project and I do wish that you will continue using zigpy in it.

I also do hope that you at some point get to having a stable version of zigpy-zigate in it too, no matter if it is a fork of it or not.

@pipiche38 Again I am sorry for the misunderstanding. I am not a native English speaker and I believe that neither are you(?)..

PS: I think if you would re-read my posts and remember they were not posted as something bad then they read very differently. As again, my posts was not aimed towards or against you but instead aimed towards other people reporting about zigpy-zigate issues.

In the end if more support for different hardware /system then better for all parts and our community.

+1 The more projects using zigpy and the more developers/users using hardware with different Zigbee stack the better for us all.

pipiche38 · 2022-01-10T15:27:13Z

@Hedda I have been contacted by several HA users willing to test the current fork that we have. Is there any one from HA whom can give a short procedure on how to shift from the current zigpy-zigate package to the one available here https://github.com/zigbeefordomoticz/zigpy-zigate

Currently we have made changes to:

Support Zigbee group and broadcast
Support Zigate firmware 321 (which is the minimum)
Support and handle the message flow ( 8011/8012/8702 )

baimard · 2022-01-10T16:42:30Z

Maybe a quick procedure can be to replace the package by this one in : /usr/local/lib/python3.9/site-packages/zigpy_zigate Cordialement, Benjamin AIMARD Le 10/01/2022 à 16:27, Pipiche a écrit :

…

@Hedda <https://github.com/Hedda> I have been contacted by several HA users willing to test the current fork that we have. Is there any one from HA whom can give a short procedure on how to shift from the current zigpy-zigate package to the one available here https://github.com/zigbeefordomoticz/zigpy-zigate Currently we have made changes to: * Support Zigbee group and broadcast * Support Zigate firmware 321 (which is the minimum) * Support and handle the message flow ( 8011/8012/8702 ) — Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABZ5OENPOLGA4T2RZ3ZZHITUVL3F3ANCNFSM5HQ2GH7Q>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

pipiche38 · 2022-01-10T16:55:42Z

Don't know if that will be enought to overwrite the standard package

pip3 install git+https://github.com/zigbeefordomoticz/zigpy-zigate.git

baimard · 2022-01-10T17:06:26Z

It maybe better to directly replace the package, because of docker user. With this command I don't know if you replace existing package ... Cordialement, Benjamin AIMARD Le 10/01/2022 à 17:55, Pipiche a écrit :

…

Don't know if that will be enought to overwrite the standard package pip3 install git+https://github.com/zigbeefordomoticz/zigpy-zigate.git — Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABZ5OEKQTHD7DPH7TFPB2RDUVMFRRANCNFSM5HQ2GH7Q>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

pipiche38 · 2022-01-10T17:54:06Z

So this is out of my knowledge

baimard · 2022-01-10T17:57:28Z

git clone https://github.com/zigbeefordomoticz/zigpy-zigate.git mv /usr/local/lib/python3.9/site-packages/zigpy_zigate /usr/local/lib/python3.9/site-packages/zigpy_zigate.back cp -r ./zigpy-zigate /usr/local/lib/python3.9/site-packages C'est tout :) Cordialement, Benjamin AIMARD Le 10/01/2022 à 18:54, Pipiche a écrit :

…

So this is out of my knowledge — Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABZ5OEKBVSK65PD5HTIPD2LUVMMMRANCNFSM5HQ2GH7Q>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

Gemies · 2022-01-10T19:10:47Z

Benjamin,

Thanks a lot for you're small tutorial on how to update the zigpy-zigate library.
Now I have to find a way to acces usr/local/lib/python3.9........... file. From the command line I don't get acces to the file location.
Any ideas?

Thanks alot?
Gr, Gemies

Hedda · 2022-01-11T08:40:33Z

@Hedda I have been contacted by several HA users willing to test the current fork that we have. Is there any one from HA whom can give a short procedure on how to shift from the current zigpy-zigate package to the one available here https://github.com/zigbeefordomoticz/zigpy-zigate

Sorry I'm not good with either Linux or Python packages myself, and especially not when the use of Docker containers is involved.

I believe you need to make sure you are in the Docker virtual environment.

Home Assistant has this official documentation on adding new dependencies inside a test environment for Home Assistant:

https://developers.home-assistant.io/docs/development_testing/#adding-new-dependencies-to-test-environment

I'm not sure how it works if want to test alternative Python packages from alternative sources when a users is using "Home Assistant Container" "Home Assistant Operating System" (a.k.a. "HAOS" Home Assistant OS embedded Linux distribution) installations which both uses/depends on Docker containers? That is, installing a new Python module from the PyPI within your virtual environment to overwrite the existing package.

https://github.com/zigpy/zigpy-zigate/blob/dev/README.md#testing-new-releases

Probably easy for testers using Home Assistant without Docker, as is when have only installed "Home Assistant Core" directly under any other Linux distribution. The differences between the different installation methods of Home Assistant are described here:

https://www.home-assistant.io/installation/

Don't know if that will be enought to overwrite the standard package

pip3 install git+https://github.com/zigbeefordomoticz/zigpy-zigate.git

Again, I believe you need to make sure you are within your virtualenv (Docker virtual environment).

Then probably first want to start by uninstalling whichever existing zigpy-zigate package before installing the new package or?

(venv) $ python -m pip uninstall zigpy-zigate

If you do not first do pip uninstall then I believe pip install will not overwrite the existing package when you install from Git.

Think it should then be to just install the new Python module via git using pip install from PyPI Git within your virtualenv:

pip install git+https://github.com/zigbeefordomoticz/zigpy-zigate/

Alternativly pip install of "branch" (where replace "branch.zip" with branch) that want ZHA users with ZiGate to test, with either:

pip install https://github.com/zigbeefordomoticz/zigpy-zigate/archive/branch.zip

Example:

(venv) $ pip install https://github.com/zigbeefordomoticz/zigpy-zigate/archive/dev.zip

or to download each file individually via git as you wrote which takes longer but might be simpler (again replace "branch"):

pip install git+https://github.com/zigbeefordomoticz/zigpy-zigate.git@branch

Example:

pip install git+https://github.com/zigbeefordomoticz/zigpy-zigate.git@dev

PS: Many used to use a this "zha-custom-radios" custom component to test zigpy-znp and other custom radio modules in Home Assistant via HACS (Home Assistant Community Store) before zigpy-znp was merged into the mainline which made testing simple:

https://github.com/zha-ng/zha-custom-radios

Today that is not maintained and guess would have to be updated and maybe even rebased on this to make updating tests easier:

https://github.com/MatthewFlamm/pytest-homeassistant-custom-component

Think then updating hassio-addons-development is the generally prefered way when using a "Home Assistant Supervised" install:

https://github.com/home-assistant/addons-development

PPS: Maybe start new issue or discussion with the subject topic "Testing fork of zigpy-zigate"? -> https://github.com/zigpy/zigpy-zigate/issues/ or https://github.com/zigpy/zigpy/discussions

Hedda · 2022-01-11T08:44:51Z

When got a working guide for easy way to test specific branches from other forks it might be good idea to add it to README.md?

https://github.com/zigpy/zigpy-zigate/blob/dev/README.md#testing-new-releases

pipiche38 · 2022-01-11T08:52:12Z

@Gemies I think the best is for you to use this Issue to report any problem/issue. I'm sure you'll find some help

Hedda · 2022-01-11T09:11:35Z

FYI, also now posted a general plea for help with testing with ZHA in Home Assistant community forum here:

https://community.home-assistant.io/t/zigate-users-help-wanted-to-test-zha-with-fork-of-zigpy-zigate-with-new-patches/378362

PPS: Maybe start new issue with the subject topic "Testing fork of zigpy-zigate"? -> https://github.com/zigpy/zigpy-zigate/issues/

Update: Also posted a copy of that for generic zigpy development discussion here -> zigpy/zigpy#880

baimard · 2022-01-11T09:40:46Z

@Gemies are you on Linux Windows Docker ?

Hedda · 2022-01-11T10:03:47Z

are you on Linux Windows Docker ?

It should also be noted that Home Assistant is not officially supported directly under Microsoft Windows OS or Mac OS, only Linux.

Nor is it supported to install Home Assistant core directly under MS Windows or Mac OS via Python releases for Windows/macOS.

Microsoft Windows OS or Mac OS is really only options if installing Home Assistant in Linux running inside a virtual machine (VM).

https://www.home-assistant.io/installation/

If you are running Windows or Mac OS then you need to install HA inside Linux OS running in a VM on a virtualization hypervisor.

So could install in a virtual machine under hypervisor. like; VirtualBox, Proxmox VE, KVM, Hyper-V, or VMware Workstation/Fusion.

baimard · 2022-01-11T10:04:59Z

Even with WSL on windows with a docker container ? ...

Gemies · 2022-01-11T10:09:24Z

@baimard I run HA on Synology Nas with a VM.

baimard · 2022-01-11T10:11:43Z

@baimard I run HA on Synology Nas with a VM.

I'm sorry I don't know where you can find the package ... try with find command

Hedda · 2022-01-11T10:19:42Z

I run HA on Synology Nas with a VM.

Which exact Linux distribution? Running inside that VM? Are you running "Home Assistant Operating System" or .... other distro?

https://www.home-assistant.io/installation/

At least assume by "run HA on Synology Nas with a VM" you mean run HA in Linux under a virtual machine via Synology VMM?

https://www.synology.com/en-global/dsm/feature/virtual_machine_manager

It is really not recommended to run Home Assistant directly within Synology's DSM OS even though can install Docker within DSM.

The same would go if have a QNAP NAS. It is OK to install in a VM under its hypervisor but not OK to install in the NAS's own OS.

https://www.qnap.com/en/software/virtualization-station

Even with WSL on windows with a docker container ? ...

Yes as I understand it, believe Home Assistant is officially not supported under WSL. You might be able to get different results today as later versions of Windows Subsystem for Linux in Microsoft Windows operating systems are getting more compatible with native Linux with each newer version of WSL such as "WSL 2" in Microsoft Windows 11. (And yes I know that you can today install Ubuntu subset for Linux from the Windows Store to get Ubuntu's Docker image for WSL2). The fact remains that Home Assistant core is officially not supported under WSL even if you could practically get it to work for you.

You need to understand and remember that WSL (Windows Subsystem for Linux) is still not a full Linux distribution. WSL only a compatibility layer for running Linux binary executables (in ELF format) natively on Microsoft Windows 10. WSL it only meant to include a subset of the most common Linux command-line tools and applications.

https://docs.microsoft.com/en-us/windows/wsl/about

So I think it would be a very bad idea to use WSL on Windows as a testing environment platform when it is not officially supported.

At least I know that if you would submit a ZHA bug-report to Home Assistant core then they will close it if you are not running it under either Home Assistant OS or any other proper Linux distribution. Thus it is really a moot point to spend time testing in WSL.

Gemies · 2022-01-11T13:29:56Z

I use the vm manager from Synology. Installed the official HA OS image which provided by home assistant on the website.

https://www.home-assistant.io/installation/alternative/#install-home-assistant-operating-system

max5962 · 2022-01-18T11:52:22Z

Hello,

The purpose of zigpy is to be cross plateform ? (domoticz/ha/jeedom/ect ?)
So if it work on domoticz that should work on home assistant. isn't it ?

On HaOS VM, :
"/usr/local/lib/python3.9/site-packages/zigpy_zigate" do not exist
and
"pip3 install git+https://github.com/zigbeefordomoticz/zigpy-zigate.git" failed to build
"Failed to build aiohttp frozenlist multidict yarl
ERROR: Could not build wheels for aiohttp, frozenlist, multidict, yarl which use PEP 517 and cannot be installed directly"

any idea ?

Hedda · 2022-01-18T12:23:21Z

The purpose of zigpy is to be cross plateform ? (domoticz/ha/jeedom/ect ?)
So if it work on domoticz that should work on home assistant. isn't it ?

@max5962 What are you asking? FYI, see back-story on Zigbee for Domoticz in zigpy general discussion here -> zigpy/zigpy#865

Xavier-M · 2022-01-18T15:31:05Z

Thank you all for your work on this.

I think I was able to install this into hassio. I have the plugin "SSH & Web Terminal", I then connect with SSH and enter the following lines (it's an image, i cannot copy paste using this...):

After that I restarted home assistant. But then I don't really know how I can know if it is taken into account, or if I have to do something else for it to work ;-)
In the log I have things like that:

2022-01-18 16:28:02 ERROR (MainThread) [zigpy_zigate.api] data_received : error details received 0x9999 error:0x83 
2022-01-18 16:28:02 ERROR (MainThread) [zigpy_zigate.api] command : error status cmd:0x530 error:163
2022-01-18 16:28:03 ERROR (MainThread) [zigpy_zigate.api] data_received : error details received 0x9999 error:0x83 
2022-01-18 16:28:03 ERROR (MainThread) [zigpy_zigate.api] command : error status cmd:0x530 error:163
2022-01-18 16:28:04 ERROR (MainThread) [zigpy_zigate.api] data_received : error details received 0x9999 error:0x83 
2022-01-18 16:29:53 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback SerialTransport._read_ready()
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/local/lib/python3.9/site-packages/serial_asyncio/__init__.py", line 119, in _read_ready
    self._protocol.data_received(data)
  File "/config/deps/lib/python3.9/site-packages/zigpy_zigate/uart.py", line 90, in data_received
    self._api.data_received(cmd, f_data, lqi)
  File "/config/deps/lib/python3.9/site-packages/zigpy_zigate/api.py", line 213, in data_received
    fut.set_result((data, lqi))
asyncio.exceptions.InvalidStateError: invalid state
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/local/lib/python3.9/site-packages/serial_asyncio/__init__.py", line 119, in _read_ready
    self._protocol.data_received(data)
  File "/config/deps/lib/python3.9/site-packages/zigpy_zigate/uart.py", line 90, in data_received
    self._api.data_received(cmd, f_data, lqi)
  File "/config/deps/lib/python3.9/site-packages/zigpy_zigate/api.py", line 213, in data_received
    fut.set_result((data, lqi))

pipiche38 · 2022-01-18T18:33:58Z

2022-01-18 16:28:02 ERROR (MainThread) [zigpy_zigate.api] data_received : error details received 0x9999 error:0x83
2022-01-18 16:28:02 ERROR (MainThread) [zigpy_zigate.api] command : error status cmd:0x530 error:163
2022-01-18 16:28:03 ERROR (MainThread) [zigpy_zigate.api] data_received : error details received 0x9999 error:0x83
2022-01-18 16:28:03 ERROR (MainThread) [zigpy_zigate.api] command : error status cmd:0x530 error:163
2022-01-18 16:28:04 ERROR (MainThread) [zigpy_zigate.api] data_received : error details received 0x9999 error:0x83
2022-01-18 16:29:53 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback SerialTranspor

These are ZiGate errors reported by the firmware via 0x9999 .
"No free APS acknowledgement handles (resource error) - the number of handles is set in the Maximum Number of Simultaneous Data Requests with Acks field of the APS layer configuration section of the ZPS Configuration Editor"

For the stack trace, it would be important to have more debug to understand what was the context. So better to enable debug for zigpy-zigate

baimard · 2022-07-19T12:15:17Z

everythings work well now !

baimard · 2022-07-19T16:30:28Z

New error

home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:06:44 WARNING (MainThread) [homeassistant.components.camera] Platform netatmo not ready yet: None; Retrying in background in 30 seconds
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:06:44 WARNING (MainThread) [homeassistant.components.climate] Platform netatmo not ready yet: None; Retrying in background in 30 seconds
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:06:44 WARNING (MainThread) [homeassistant.components.light] Platform netatmo not ready yet: None; Retrying in background in 30 seconds
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:06:44 WARNING (MainThread) [homeassistant.components.select] Platform netatmo not ready yet: None; Retrying in background in 30 seconds
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:08:38 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x67B8:1:0x0001]: 'async_configure' stage failed: 'NoneType' object has no attribute 'raw_aps_data_request'
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:08:38 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x67B8:1:0x0405]: 'async_configure' stage failed: 'NoneType' object has no attribute 'raw_aps_data_request'
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:08:38 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x67B8:1:0x0402]: 'async_configure' stage failed: 'NoneType' object has no attribute 'raw_aps_data_request'
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:08:38 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
home_assistant.1.01549c7p5vbr@home2    | Traceback (most recent call last):
home_assistant.1.01549c7p5vbr@home2    |   File "/usr/src/homeassistant/homeassistant/components/zha/core/device.py", line 481, in async_configure
home_assistant.1.01549c7p5vbr@home2    |     await self._channels.identify_ch.trigger_effect(
home_assistant.1.01549c7p5vbr@home2    |   File "/usr/src/homeassistant/homeassistant/components/zha/core/channels/base.py", line 78, in wrapper
home_assistant.1.01549c7p5vbr@home2    |     result = await command(*args, **kwds)
home_assistant.1.01549c7p5vbr@home2    |   File "/usr/local/lib/python3.10/site-packages/zigpy/device.py", line 291, in request
home_assistant.1.01549c7p5vbr@home2    |     radio_result, msg = await self._application.request(
home_assistant.1.01549c7p5vbr@home2    |   File "/usr/local/lib/python3.10/site-packages/zigpy_zigate/zigbee/application.py", line 230, in request
home_assistant.1.01549c7p5vbr@home2    |     return await self._request(device.nwk, profile, cluster, src_ep, dst_ep, sequence, data,
home_assistant.1.01549c7p5vbr@home2    |   File "/usr/local/lib/python3.10/site-packages/zigpy_zigate/zigbee/application.py", line 243, in _request
home_assistant.1.01549c7p5vbr@home2    |     v, lqi = await self._api.raw_aps_data_request(nwk, src_ep, dst_ep, profile, cluster, data, addr_mode)
home_assistant.1.01549c7p5vbr@home2    | AttributeError: 'NoneType' object has no attribute 'raw_aps_data_request'
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:08:39 WARNING (MainThread) [zigpy_zigate.zigbee.application] Unexpected message send failure
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:08:39 WARNING (MainThread) [zigpy_zigate.zigbee.application] Unexpected message send failure
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:17:31 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x67B8:1:0x0001]: async_initialize: all attempts have failed: [TimeoutError(), TimeoutError(), TimeoutError(), TimeoutError()]
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:17:32 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x67B8:1:0x0402]: async_initialize: all attempts have failed: [TimeoutError(), TimeoutError(), TimeoutError(), TimeoutError()]
home_assistant.1.01549c7p5vbr@home2    | 2022-07-19 18:17:32 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0x67B8:1:0x0405]: async_initialize: all attempts have failed: [TimeoutError(), TimeoutError(), TimeoutError(), TimeoutError()]

baimard · 2022-07-19T16:31:41Z

baimard · 2022-07-20T07:02:39Z

When I change this value on this new parameter, everything seems to be ok.

MattWestb · 2022-07-20T15:22:03Z

@baimard I have sniffing all types of IKEA controllers for one year ago and they is needing one "Reconfigure device" from device card for reporting OK in ZHA.
But IKEA have updating all controllers after that but i think its still needed for getting the reporting working OK.

Try it and not forgetting waking the device up by pressing one button then sending things to it (they is sleeper).

nlhomme added a commit to nlhomme/zigpy-zigate that referenced this issue Nov 28, 2021

Resolve issue zigpy#104: unhandled 0x8012 responses

0edef93

See issues 104 for more details

nlhomme mentioned this issue Nov 28, 2021

Resolve issue #104: unhandled 0x8012 responses for Ikea TRADFRI #106

Closed

baimard closed this as completed Dec 16, 2021

baimard reopened this Jan 3, 2022

MichaelBitard mentioned this issue Jan 8, 2022

handle response 0x8012 #113

Merged

This was referenced Jan 25, 2022

zigpy-zigate 0.8.0 or newer 0.8.x release with later fixes already added? #93

Open

Unable to install ZHA - zigate - RPi.GPIO with Python 3.10 #115

Closed

Hedda mentioned this issue Feb 14, 2022

Implement the new zigpy radio API #117

Merged

baimard closed this as completed Jul 19, 2022

baimard reopened this Jul 19, 2022

baimard closed this as completed Jul 20, 2022

Home assistant error Received unhandled response 0x8012 tradfri IKEA #104

Home assistant error Received unhandled response 0x8012 tradfri IKEA #104

Comments

baimard commented Nov 7, 2021

baimard commented Nov 16, 2021

nlhomme commented Nov 28, 2021

nlhomme commented Dec 16, 2021

Hedda commented Jan 3, 2022 • edited Loading

baimard commented Jan 3, 2022

pipiche38 commented Jan 3, 2022

MattWestb commented Jan 3, 2022

pipiche38 commented Jan 3, 2022

Hedda commented Jan 7, 2022 • edited Loading

pipiche38 commented Jan 10, 2022

baimard commented Jan 10, 2022 via email

pipiche38 commented Jan 10, 2022

baimard commented Jan 10, 2022 via email

pipiche38 commented Jan 10, 2022

baimard commented Jan 10, 2022 via email

Gemies commented Jan 10, 2022

Hedda commented Jan 11, 2022 • edited Loading

Hedda commented Jan 11, 2022 • edited Loading

pipiche38 commented Jan 11, 2022

Hedda commented Jan 11, 2022 • edited Loading

baimard commented Jan 11, 2022

Hedda commented Jan 11, 2022 • edited Loading

baimard commented Jan 11, 2022

Gemies commented Jan 11, 2022

baimard commented Jan 11, 2022

Hedda commented Jan 11, 2022 • edited Loading

Gemies commented Jan 11, 2022

max5962 commented Jan 18, 2022

Hedda commented Jan 18, 2022

Xavier-M commented Jan 18, 2022

pipiche38 commented Jan 18, 2022

baimard commented Jul 19, 2022

baimard commented Jul 19, 2022

baimard commented Jul 19, 2022

baimard commented Jul 20, 2022

MattWestb commented Jul 20, 2022

Hedda commented Jan 3, 2022 •

edited

Loading

Hedda commented Jan 7, 2022 •

edited

Loading

Hedda commented Jan 11, 2022 •

edited

Loading

Hedda commented Jan 11, 2022 •

edited

Loading

Hedda commented Jan 11, 2022 •

edited

Loading

Hedda commented Jan 11, 2022 •

edited

Loading

Hedda commented Jan 11, 2022 •

edited

Loading