Closed tido- closed 1 year ago
I have created the virtual environment, according to the instruction.
Just run the command directly, you don't need to install anything. zigpy-znp is already installed within Home Assistant OS.
Also, you don't actually need to drop into the CLI to perform an energy scan, or to reset anything. Forming a new network with ZHA does both and securely picks a randomly-generated network key, in addition to scanning for a new channel automatically (in 2023.5.0 or above).
@puddly thank you very much indeed and I mean it. I spent at least 6 hours before I wrote this message.
To save others time, I have some suggestions, after understanding it. Don't get mad at me I just try to help. In a situation where I don't know what am I doing I follow your guidance, and this is how it came across for me.
https://github.com/zigpy/zigpy-znp on this README.md it is written:
Stable releases of zigpy-znp are automatically installed when you install the ZHA component. (To keep the terminology within HA, it is in the menu called integration) so I suggest a change like: Stable releases of zigpy-znp are automatically installed when you install the Zigbee Home Automation (ZHA) integration. At first use of ZHA, I would write it out.
Could you add another line like: So, you can test it right away no further install is needed. In HA you can skip the "installation section" and go to the section: Tools
This is also true for: zigpy-cli README.md On zigpy-cli, a reference that it is already installed is missing here.
I stumbled over "no install is needed", mainly on this site TOOLS.md. https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md zigpy-znp is already installed by Home Assistant's ZHA component (To keep the terminology within HA, it is in the menu called integration).
CC2531 if I look straight for this, I am asked one more time to: "Once you are inside of the virtualenv (if you created one)" https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#network-migration-for-coordinator-upgrades
As you have recommended in your post, I unistalled and re-installed ZHA. The third option upon install was to create a new network and a new key :+1:
Thank you for the software, I will now test the "Flash write" on CC2531 :)
I have no knowledge about Python, but it looks to me like a dependency hell. I guess it is really tough for a developer to finally (and each change on python modules) take a fresh copy of a distro and check if dependencies still fit or is it easier to offer a binary? In his write down it sounded like a walk in the park: https://www.reddit.com/r/homeassistant/comments/qzwya8/configuring_zigbee_usb_adapter/
Anyway, my story. I have Home Assistant Supervised (It leverages Docker /alpine/v3.16/, which is managed by the Home Assistant Supervisor) that is running on a Raspbian (Debian Bullseye). docker exec -it homeassistant bash -> so I work directly inside Docker, not via Webinterface of HoAss. I have created the virtual environment, according to the instruction.
You need to install into the alpine OS:
apk add gcc-arm-none-eabi gcc musl-dev python3-dev libffi-dev openssl-dev libressl-dev cargo
And then inside the virtual environment:
It stopps now here:
After all, hours of searching and retry, to only reset the NVRAM to issue a new security-key for my CC2531 Zigbee-Stick.
Do you have some guidance to escape this try and error?