Peter Murray

You are the first to have reported this, hence I don't think it is that common in practice (or there are a lot of quiet people out there facing it,...

Hi @benbucksch 👋 , I have just built up a branch with passing tests and the `node-fetch` library as the `main` branch (along with some improvements to the Type definitions...

Thanks, I will be cutting a new 5.x release soon with this fix in it

What version are you trying this with? The package is supposedly compatible with ESM and CommonJS, I have done some testing on this from the `typescript` branch, but it is...

Looking into this example you provided, adding `--experimental-specifier-resolution=node` to the `start` script allowed the library to load correctly using the esm module variant. The code then has errors as there...

The library has supported the SSDP discovery along with the newer remote API discovery endpoint once it became available. I suspect that they will be removing this functionality from the...

Just an update, I have added mDNS locally to the library, but really not getting reliable of fast results inside my network when using it in practice. I will continue...

I have just released version `5.0.0-beta.14` to npm registry, it includes a new `discovery.mdnsSearch()`, which at long last appears to be reliable on my network, please check it out and...

It is primarily a limitation of the hub, as it will transform that type of request from REST into Zigbee messages to each light, resulting in this behaviour. The concurrency...

There was an issue with the rate limits being swapped between groups and lights, which I have just resolved meaning the limit is now correctly set to once per 60ms...