Felipe Cavalcanti

Take a look https://github.com/ffenix113/zigbee_home/pull/73

Tried on WSL/Linux and on it I get this other error: `go run ../../cmd/zigbee/main.go --config zigbee.yaml firmware build 2024/06/18 12:55:01 generator.go:106: Device: "xiao_ble", selected bootloader: "adafruit_nrf52_sd140_v7", forced bootloader: true 2024/06/18...

Hey @ffenix113, even though there's an Image from Nordic (I used it as a base), it doesn't contain zb home binary, so to build with docker we either generate a...

This broken my _TZ3210_mja6r5ix that I fixed in the PR https://github.com/Koenkk/zigbee-herdsman-converters/pull/6266 Maybe they're utilizing same product id for different bulbs? I wonder what we can do to make it behave...

You're right, ctx is currently not propagated. However, there's default integration with Opentelemetry already in master branch. See the docs. [Here](https://pitaya.readthedocs.io/en/latest/tracing.html) If you want to propagate more values between calls...

Can you be more specific about which kind of key/values you will be propagating? Also, does this manual propagation method fits your needs? I'm thinking about a more transparent way...

once #8412 is merged and development gets easier by being able to build in the dev web interface, I will continue development

did it! now possible to build from the dev device builder. next I will take a look into OTA so that its easier to iterate and afterwards, fixing API encryption...

made good progress with ota. managed to get it working with mcumgr using udp transport over thread. rebased the work in #6075 ota works already by calling mcumgr manually but...

ota works (needs to run esphome dashboard from this pr/branch) e.g. ``` external_components: - source: github://pr#8410 components: [ logger, nrf52, time, zephyr, zephyr_openthread, mdns, network, socket, api, openthread_info, ota, zephyr_mcumgr...