ioBroker.zigbee2mqtt
ioBroker.zigbee2mqtt copied to clipboard
arteck
Adapter for Zigbee2MQTT integration
## Notification from ioBroker Check and Service Bot Dear adapter developer, I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I...
Bumps [chai-as-promised](https://github.com/chaijs/chai-as-promised) and [@types/chai-as-promised](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/chai-as-promised). These dependencies needed to be updated together. Updates `chai-as-promised` from 7.1.2 to 8.0.0 Release notes Sourced from chai-as-promised's releases. v8.0.0 What's Changed Migrate CI to GitHub...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [@iobroker/adapter-core](https://github.com/ioBroker/adapter-core) from 3.1.6 to 3.2.1. Release notes Sourced from @iobroker/adapter-core's releases. Release v3.2.1 (@foxriver76) updated types (@GermanBluefox) Added i18n module (@GermanBluefox) Migrated eslint to iobroker.eslint-config Release v3.2.0 (@foxriver76) updated...
# Think about update stable version to 2.13.10 **Version**: stable=**2.13.6** (193 days old) => latest=**2.13.10** (15 days old) **Installs**: stable=**1548** (63.7%), latest=**174** (7.16%), total=**2430** Click to use [developer portal](https://www.iobroker.dev/adapter/zigbee2mqtt/releases) Click...
### What happend? I notice this type of warnings in the log: zigbee2mqtt.0 | 2024-09-28 17:51:53.687 | warn | State value to set for "zigbee2mqtt.0.group_9.colortemp" has value "1818" less than...
### What happened? Hello, my iobroker installation is running under macOS so there are several differences to the linux installation (iobroker path /usr/local/iobroker not /opt/iobroker etc etc.). My main problem...
### Notification from ioBroker Check and Service Bot Dear Adapter developer, Node.js 22 will become the official node.js LTS release October 2024 - see [node-releases](https://github.com/nodejs/release#nodejs-release-working-group) **So please check your adapter...