Nerivec

Did you do a full HA reboot (red-icon button)? Some setups had trouble adjusting after the 2.7.1 update apparently. > I'm not sure where such errors come from. Zigbee net...

You can try to configure reporting, but this is Tuya stuff, so, I wouldn't get my hopes up... https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html#spammy-devices

Do note that [this stuff](https://www.zigbee2mqtt.io/guide/configuration/devices-groups.html#generic-device-options) is only on Z2M side, the device is still sending as many messages on the network as it was before, Z2M just skips some when...

Did you follow the docs (especially the part about confirming the channel)? https://www.zigbee2mqtt.io/devices/PTM_215Z.html#pairing

_Err, misread, first reply deleted._ I don't think so, this would count as cross-over, add-on security won't allow that. Might be able to work around it, but would have to...

@offsetkeyz try updating your adapter's firmware to 8.0.2: https://github.com/Nerivec/silabs-firmware-builder/releases/tag/v2024.6.2-update7 It should eliminate the base of the timeout issues (contains several fixes on that point). The issue linked above is about...

The Dongle-E was particularly affected by these timeout issues that the newer firmware fix. In case you still see issues, updating will be the only way to fix it completely...

Did you try the hotfix release? 2.7.1 is out now.

`adapter` must be indented under serial. This is the proper behavior: ```yaml serial: port: /dev/ttyUSB0 adapter: ember baudrate: 115200 rtscts: true ``` https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html --- From your error message, the configured...

Can you solve the MQTT issue first (`Not connected to MQTT server!`), then provide a `debug` log?