[RESOLVED] Problem with a zigbee2mqtt device

Hello everyone,

I’m creating a thread because although I searched directly in the zigbee2mqtt docs it seems my understanding of English / the thing isn’t sufficient… so I’m asking for help here!

I noticed in the zigbee2mqtt logs that I have a device that talks a lot: an Aqara bulb. This bulb keeps reporting messages like this:

Error 2022-10-06 16:20:20Publish 'set' 'brightness' to 'Ampoule Arrière Cuisine' failed: 'Error: Command 0x00158d0004243037/1 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))'
Error 2022-10-06 16:21:13Publish 'set' 'color_temp' to 'Ampoule Arrière Cuisine' failed: 'Error: Command 0x00158d0004243037/1 lightingColorCtrl.moveToColorTemp({"colortemp":244,"transtime":0}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))'
Info 2022-10-06 16:23:10MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'color_temp' to 'Ampoule Arrière Cuisine' failed: 'Error: Command 0x00158d0004243037/1 lightingColorCtrl.moveToColorTemp({\"colortemp\":244,\"transtime\":0}, {\"sendWhen\":\"immediate\",\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (Data request failed with error: 'MAC channel access failure' (225))'","meta":{"friendly_name":"Ampoule Arrière Cuisine"},"type":"zigbee_publish_error"}'
Error 2022-10-06 16:23:19Publish 'set' 'brightness' to 'Ampoule Arrière Cuisine' failed: 'Error: Command 0x00158d0004243037/1 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))'
Info 2022-10-06 16:23:19MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'brightness' to 'Ampoule Arrière Cuisine' failed: 'Error: Command 0x00158d0004243037/1 genLevelCtrl.moveToLevelWithOnOff({\"level\":254,\"transtime\":0}, {\"sendWhen\":\"immediate\",\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (Data request failed with error: 'MAC no ack' (233))'","meta":{"friendly_name":"Ampoule Arrière Cuisine"},"type":"zigbee_publish_error"}'

Always these color_temp and brightness that report these errors. Incidentally I noticed this because I was having trouble controlling its operation.

So I had the brilliant idea to remove it using a button in the zigbee2mqtt interface:

In case I force the removal… I delete my bulb… and surprise: errors continue to appear concerning my device (now labeled with a friendly_name like 0x0034XXXXX)

I read HERE that to remove a device from z2m, you have to do it with an MQTT command, with a topic and a payload. I don’t understand much of it but I’ve already seen these things in Node-RED… so I tried — in vain — to do this:

Does anyone know where I’m going wrong? I have the impression that this device also has the annoying tendency to slow down my setup a bit. I’d like to get rid of it properly, and possibly then re-pair it to see if it behaves the same way.

I’m all ears…!! :wink:

In Zigbee2MQTT you have an option « force device removal » and especially « prevent reconnecting ».
:warning: I don’t know what this command actually does, but it may then prevent you from reconnecting the bulb to your Zigbee network.

But all the logs you see are those of Zigbee2MQTT, not Gladys if you haven’t added the bulb in the Gladys interface. So they don’t use your database, for example.

Why are you trying to remove the bulb from the network?

You have an interference problem. Try changing the Wi-Fi channel on your internet router.

I confirm! Actually, last night I read on a forum that the Wi‑Fi could mess things up… So I changed my channel but I hadn’t had time to check.

This evening I looked: the latest log is from over an hour ago, nothing more related to that bulb :light_bulb:!

That’s perfect! Thanks @VonOx

1 Like

I wanted to remove the bulb from the network because it would create errors all over the place.