From: Stuart Henderson <stu@spacehopper.org>
Subject: Re: NEW: comms/zigpy
To: ports <ports@openbsd.org>
Date: Fri, 29 Nov 2024 16:26:32 +0000

Updated tar attached, I made a mistake with PKGNAME in py-asynctest.

On 2024/11/26 23:31, Stuart Henderson wrote:
> Since I got the zigbee2mqtt port working, I thought I'd dust off a
> few related things that have been in mystuff for a while
> 
> zigpy is a zigbee library for Python, it gets used by a few projects
> doing zigbee interfacing (for example homeassistant via zha[*], plugins
> for domoticz and jeedom), can be used to write your own software to
> talk to zigbee devices, and (the bit I wanted this time), the radio
> interface module comes with some tools for connecting to zigbee
> interfaces, dump network config and nvram, do scans, etc.
> 
> In the attached tar, there are:
> 
> comms/py-serial-asyncio - RDEP, async extension for py-serial
> devel/py-asynctest - TDEP, makes it simpler to test asyncio libraries
> devel/py-setuptools-git-versioning - BDEP
> comms/cc2538-bsl - other tool, not directly related, but used to
>   flash firmware on many of these devices
> 
> comms/zigpy/py-zigpy - main zigpy module
> comms/zigpy/py-zigpy-znp - module for common TI devices
> 
> The zigpy ones are laid out like that to keep things together if
> someone wants to add support for other radios etc (zigpy-xbee,
> zigpy-zigate, zigpy-deconz, bellows).
> 
> The tools from py-zigpy-pnp are working fine on my zzh USB stick
> (based on TI CC2652R) with whatever old firmware I have on it.
> 
> cc2538-bsl looks like it should work but I think when I flashed
> my zzh some years ago I accidentally used a firmware which uses the
> wrong pin to trigger BSL mode - either that or the timing is even
> more fussy than I remember - anyway maybe useful to some and it's
> simple so I thought I'd include it here too.
> 
> any OKs to import?
> 
> 
> [*] don't get excited about mentioning homeassistant/hass, I have no
> intention at all to port it, it is extremely fussy about dependency
> versions (even on the linux VM I'm running it on I'm stuck at an old
> version until I figure out how to get things updated...) however: if
> you want to use zigbee devices with hass, you can run zigbee2mqtt on
> another machine and point that and hass at the same mqtt broker.
>