Data request failed with error mac no ack 233

After switch to CC1352P-2: Error: Data request failed with error: ‘MAC no ack’ (233) #2789

As I don’t want the discussion in #2761 to loose focus I am opening a separate issue.

After resetting the tradfri bulb using touchlink I was able to pair it again. But after unplugging it and moving it back to its location I get errors again. I had this same behavior after I switched the coordinator to CC1352P-2. It first paired and worked but after a short period of time it refused to respond. Another identical bulb works fine.

I changed all three when migrating to CC1352: channel (now 15), pan id and extended pan id. Might that be the issue? I wanted to pick something unique not to interfere with possible other networks nearby.

Debug Info

zigbee2mqtt version: 1.8.0
CC1352p-2 firmware version: 20191106

The text was updated successfully, but these errors were encountered:

After migrating to the CC1352p-2 did you repair all your devices?

Yes of course. I also changed the network key.

I just did a quick check this morning without observing the logs:
When I get switch the other bulb that used to work after pairing off physically (or unplug it) it also stops working.

I assume that the network parameters are not correctly stored for the tradfris. I will try to reproduce this with log observation and provide an update on this.

So the second bulb works fine and reconnects to the network after a few seconds. It is only this device that keeps failing.

I’m getting this same message maybe every 10th time, the reason might also be that the antenna is bit far from the IKEA bulb.

MQTT is supposed to be reliable protocol, how about a configurable amount of retries before giving up with error message (and in user perspective failure to function)?

@Koenkk resetting through touchlink did not change anything. But today I moved the bulb to another location in the house and boom itt is functional again even without repairing. There must be an issue with the message routing. Maybe one of the routers are not working correctly.

Since today I also have an issue with a PIR sensor that is nearby the disfunctional location and now reporting movements only in rare cases.

I will check if the other sensors are all working and reset the routers to see if that helps.

It seems this is the only device not working so far. This issue reappears again and again.

When I reset the device near to the coordinator it works until I move if away.

@odx try pairing the bulb at the place you want to keep it.

The log was taken at That location.

I think there is something messed up with the routing tables, if it doesn’t work we can try rediscovering the route.

Here is what I did:

• The device was currently not in the Database (Probably because I recently force removed it)
• The device did not have the network key (Because it has been reset recently)

• Enable join
• Reset the device next to the Coordinator
• Wait until paring completed
• Remove (not force remove) the device
• Move to distant location
• Switch on the device

Here is the log:

How can the route be checked? I have a CC2531 sniffer available.

As you have a sniffer, can you sniff when trying to control the bulb at the distant location after pairing it successfully close to the coordinator?

This is what I see in the packet log when I try to control the device. 0xa34f is the affected bulb according to the «nwkAddr» of the database.db.

in the IEE 802.15.4 Data.

What exactly should I look for in the network frames?

There are a few things that I noticed when grubbing through the packages:

• I found that on my channel there seem to be other 802.15.4 traffic. As there are network frames referencing network addresses not in my database and another PAN.
• I discovered network frames from 0x0000 to 0xa34f referencing a different PAN than what I have configured. (also being reported as Bad FCS).
• Lastly I saw a few network frames from network addresses not in my database but using my PAN.

This means that the packets are corrupted, I think there is too much interference on the current channel.

Ok. Weird is that ist seems only this device is affected.

I will scan other channels and see if they are more quiet. Occasionally I will go back to default channel 11 which worked better earlier.

@Koenkk any idea why this tends to happen mostly just to that single device and when its at its place far from the coordinator whereas another bulb in the same room works fine? I’d assume that the complete network is unstable when there is noise on the band.

@Koenkk i swapped the bulbs (I left the lamps in place and only exchanged the bulbs themselves):
The other bulb works
The problematic bulb initially did not respond but throughout the next few minutes it started to react to more and more commands until it emerged to function well.

I will observe if it this state remains. As sometimes after pairing it worked for several hours.

Now that the bulb is responsive, I see less bad control sequences but they have not completely gone away and are definitely also within my network.

Nevertheless I believe that moving the network to a different channel seems to be a wise idea. I also moved my 2.4 Ghz Wifi from Channel 6 to 11 in Order to free up the lower Zigbee channel bands so I might get good results on Zigbee channel 11.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Источник

Nue 3A Single/Double Gang Switch Not receiving Data request failed with error: ‘MAC no ack’ (233) #12062

What happened?

Recently my Nue/3A Single and Double gang switches are failing.
When the switch is manually activated the state and LQI are updated in Z2M however when trying to send a command I am receiving the error Data request failed with error: ‘MAC no ack’ (233)

All my other Nue/3A switches work as expected and havent had any issues.

its only the
3x LXN-2S27LX1.0
1x LXN-1S27LX1.0 with the issue

I have completely deleted the db and started with a fresh config, still occurring.

What did you expect to happen?

Up until last week the switches were operating correctly all commands were sent and received, no new devices added to the network, ZZH is on an USB extension, have tried additional ports and extension cables.

Expectation is that a command is sent and that it is received.
The switch can report all states and LQI to the coordinator no issues

How to reproduce it (minimal and precise)

Attempt any send command to the device and they fail with Data request failed with error: ‘MAC no ack’ (233)

Zigbee2MQTT version

Adapter firmware version

Adapter

Debug log

2022-04-03T22:31:34.614Z zigbee-herdsman:adapter:zStack:unpi:writer —> frame [254,14,36,1,149,242,1,1,25,0,60,0,30,4,25,21,2,152,229]
2022-04-03T22:31:34.614Z zigbee-herdsman:adapter:zStack:unpi:parser — parseNext []
2022-04-03T22:31:34.626Z zigbee-herdsman:adapter:zStack:unpi:parser parsed 1 — 3 — 4 — 1 — [0] — 100
2022-04-03T22:31:34.626Z zigbee-herdsman:adapter:zStack:znp:SRSP parsed 3 — 2 — 4 — 128 — [0,1,60] — 250
2022-04-03T22:31:34.636Z zigbee-herdsman:adapter:zStack:znp:AREQ AF — dataRequest — <«dstaddr»:1107,»destendpoint»:1,»srcendpoint»:1,»clusterid»:6,»transid»:61,»options»:0,»radius»:30,»len»:5,»data»:<«type»:»Buffer»,»data»:[24,81,11,10,0]>>
2022-04-03T22:31:35.609Z zigbee-herdsman:adapter:zStack:unpi:writer —> frame [254,15,36,1,83,4,1,1,6,0,61,0,30,5,24,81,11,10,0,21]
2022-04-03T22:31:35.621Z zigbee-herdsman:adapter:zStack:unpi:parser parsed 1 — 3 — 4 — 1 — [0] — 100
2022-04-03T22:31:35.621Z zigbee-herdsman:adapter:zStack:znp:SRSP parsed 3 — 2 — 4 — 128 — [233,1,61] — 18
2022-04-03T22:31:35.687Z zigbee-herdsman:adapter:zStack:znp:AREQ

The text was updated successfully, but these errors were encountered:

Источник

Ikea Float Panel MAC no ack’ (233) #2599

I have a strange behaviour with my Ikea Float Panel. I paired the device successfully and everything seems fine. But when i publish a Message to the device i get an error (See log below).

I already removed the device from the database file manually and readd the Float Panel but get the same error.

I had my coordinator for pairing only a few centimeters away from the Float Panel. So for now i have no Idea what i could do next. all other devices workes fine

Here is the log:

zigbee2mqtt:info 2019-12-24 10:23:53: Device ‘0x000b57fffe9e4f52’ joined
stdout
10:23:53
zigbee2mqtt:info 2019-12-24 10:23:53: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘<«type»:»device_connected»,»message»:<«friendly_name»:»0x000b57fffe9e4f52″>>’
stdout
10:23:53
zigbee2mqtt:info 2019-12-24 10:23:53: Starting interview of ‘0x000b57fffe9e4f52’
stdout
10:23:53
zigbee2mqtt:info 2019-12-24 10:23:53: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘<«type»:»pairing»,»message»:»interview_started»,»meta»:<«friendly_name»:»0x000b57fffe9e4f52″>>’
stdout
10:24:03
zigbee2mqtt:info 2019-12-24 10:24:03: Successfully interviewed ‘0x000b57fffe9e4f52’, device has successfully been paired
stdout
10:24:03
zigbee2mqtt:info 2019-12-24 10:24:03: Device ‘0x000b57fffe9e4f52’ is supported, identified as: IKEA FLOALT LED light panel, dimmable, white spectrum (30×90 cm) (L1528)
stdout
10:24:03
zigbee2mqtt:info 2019-12-24 10:24:03: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘<«type»:»pairing»,»message»:»interview_successful»,»meta»:<«friendly_name»:»0x000b57fffe9e4f52″,»model»:»L1528″,»vendor»:»IKEA»,»description»:»FLOALT LED light panel, dimmable, white spectrum (30×90 cm)»,»supported»:true>>’
stdout

zigbee2mqtt:error 2019-12-24 10:25:27: Publish ‘set’ ‘state’ to ‘0x000b57fffe9e4f52’ failed: ‘Error: Data request failed with error: ‘MAC no ack’ (233)’
stdout
10:25:27
zigbee2mqtt:info 2019-12-24 10:25:27: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘<«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x000b57fffe9e4f52’ failed: ‘Error: Data request failed with error: ‘MAC no ack’ (233)'»,»meta»:<«friendly_name»:»0x000b57fffe9e4f52″>>’

And here the entry in the database:

The text was updated successfully, but these errors were encountered:

Источник

CC2652, Eurotronic SPZB0001 ‘MAC no ack’ (233))’ or MAC transaction expired’ (240))’ #5272

What happened

Paired Thermostat
Vendor
Eurotronic
Model
SPZB0001
2 works 2 get Mac error while changing Temperatur via hassio

What did you expect to happen

The thermostat sets the given temperature

How to reproduce it (minimal and precise)

Via Hassio Webfrontend set the Temperatur in Lovelace or via zigbee2mqtt webui change the occupied_heating_setpoint
The following error shows up in logs:

The issue describes my problem with different coordinator Hardware
#2500
The given solution isn’t working so I opened a new ticket.

Debug Info

The text was updated successfully, but these errors were encountered:

Interesting, I am experiencing what seems to be the same issue: I have 2 Eurotronic SPZB0001, both worked for some time, then one stopped working and when I want to adjust the temperature, I see this error in the log:

Also, if I adjust the temperature at the device, it is not reported back to HomeAssistant (it remains unchanged).
I am running Home Assistant 2020.12.0 on a Pi4, Zigbee2mqtt version 1.16.2.2, adapter hardware CC2652 (from slaesh).

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

CC2652, Eurotronic SPZB0001 ‘MAC no ack’ (233))’ or MAC transaction expired’ (240))’ #5272

What happened

Paired Thermostat
Vendor
Eurotronic
Model
SPZB0001
2 works 2 get Mac error while changing Temperatur via hassio

What did you expect to happen

The thermostat sets the given temperature

How to reproduce it (minimal and precise)

Via Hassio Webfrontend set the Temperatur in Lovelace or via zigbee2mqtt webui change the occupied_heating_setpoint
The following error shows up in logs:

The issue describes my problem with different coordinator Hardware
#2500
The given solution isn’t working so I opened a new ticket.

Debug Info

The text was updated successfully, but these errors were encountered:

Interesting, I am experiencing what seems to be the same issue: I have 2 Eurotronic SPZB0001, both worked for some time, then one stopped working and when I want to adjust the temperature, I see this error in the log:

Also, if I adjust the temperature at the device, it is not reported back to HomeAssistant (it remains unchanged).
I am running Home Assistant 2020.12.0 on a Pi4, Zigbee2mqtt version 1.16.2.2, adapter hardware CC2652 (from slaesh).

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

What happened?

Recently my Nue/3A Single and Double gang switches are failing.
When the switch is manually activated the state and LQI are updated in Z2M however when trying to send a command I am receiving the error Data request failed with error: 'MAC no ack' (233)

All my other Nue/3A switches work as expected and havent had any issues.

its only the
3x LXN-2S27LX1.0
1x LXN-1S27LX1.0 with the issue

I have completely deleted the db and started with a fresh config, still occurring.

What did you expect to happen?

Up until last week the switches were operating correctly all commands were sent and received, no new devices added to the network, ZZH is on an USB extension, have tried additional ports and extension cables.

Expectation is that a command is sent and that it is received.
The switch can report all states and LQI to the coordinator no issues

How to reproduce it (minimal and precise)

Attempt any send command to the device and they fail with Data request failed with error: 'MAC no ack' (233)

Zigbee2MQTT version

1.25.0

Adapter firmware version

20220219

Adapter

zzh

Debug log

2022-04-03T22:31:34.614Z zigbee-herdsman:adapter:zStack:unpi:writer —> frame [254,14,36,1,149,242,1,1,25,0,60,0,30,4,25,21,2,152,229]
2022-04-03T22:31:34.614Z zigbee-herdsman:adapter:zStack:unpi:parser — parseNext []
2022-04-03T22:31:34.626Z zigbee-herdsman:adapter:zStack:unpi:parser <— [254,1,100,1,0,100]
2022-04-03T22:31:34.626Z zigbee-herdsman:adapter:zStack:unpi:parser — parseNext [254,1,100,1,0,100]
2022-04-03T22:31:34.626Z zigbee-herdsman:adapter:zStack:unpi:parser —> parsed 1 — 3 — 4 — 1 — [0] — 100
2022-04-03T22:31:34.626Z zigbee-herdsman:adapter:zStack:znp:SRSP <— AF — dataRequest — {«status»:0}
2022-04-03T22:31:34.626Z zigbee-herdsman:adapter:zStack:unpi:parser — parseNext []
2022-04-03T22:31:34.635Z zigbee-herdsman:adapter:zStack:unpi:parser <— [254,3,68,128,0,1,60,250]
2022-04-03T22:31:34.636Z zigbee-herdsman:adapter:zStack:unpi:parser — parseNext [254,3,68,128,0,1,60,250]
2022-04-03T22:31:34.636Z zigbee-herdsman:adapter:zStack:unpi:parser —> parsed 3 — 2 — 4 — 128 — [0,1,60] — 250
2022-04-03T22:31:34.636Z zigbee-herdsman:adapter:zStack:znp:AREQ <— AF — dataConfirm — {«status»:0,»endpoint»:1,»transid»:60}
2022-04-03T22:31:34.636Z zigbee-herdsman:adapter:zStack:unpi:parser — parseNext []
2022-04-03T22:31:35.608Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0x149f0111e00bfdb0:1107/1 (0,4,1)
2022-04-03T22:31:35.608Z zigbee-herdsman:adapter:zStack:znp:SREQ —> AF — dataRequest — {«dstaddr»:1107,»destendpoint»:1,»srcendpoint»:1,»clusterid»:6,»transid»:61,»options»:0,»radius»:30,»len»:5,»data»:{«type»:»Buffer»,»data»:[24,81,11,10,0]}}
2022-04-03T22:31:35.609Z zigbee-herdsman:adapter:zStack:unpi:writer —> frame [254,15,36,1,83,4,1,1,6,0,61,0,30,5,24,81,11,10,0,21]
2022-04-03T22:31:35.621Z zigbee-herdsman:adapter:zStack:unpi:parser <— [254,1,100,1,0,100]
2022-04-03T22:31:35.621Z zigbee-herdsman:adapter:zStack:unpi:parser — parseNext [254,1,100,1,0,100]
2022-04-03T22:31:35.621Z zigbee-herdsman:adapter:zStack:unpi:parser —> parsed 1 — 3 — 4 — 1 — [0] — 100
2022-04-03T22:31:35.621Z zigbee-herdsman:adapter:zStack:znp:SRSP <— AF — dataRequest — {«status»:0}
2022-04-03T22:31:35.621Z zigbee-herdsman:adapter:zStack:unpi:parser — parseNext []
2022-04-03T22:31:35.687Z zigbee-herdsman:adapter:zStack:unpi:parser <— [254,3,68,128,233,1,61,18]
2022-04-03T22:31:35.687Z zigbee-herdsman:adapter:zStack:unpi:parser — parseNext [254,3,68,128,233,1,61,18]
2022-04-03T22:31:35.687Z zigbee-herdsman:adapter:zStack:unpi:parser —> parsed 3 — 2 — 4 — 128 — [233,1,61] — 18
2022-04-03T22:31:35.687Z zigbee-herdsman:adapter:zStack:znp:AREQ <— AF — dataConfirm — {«status»:233,»endpoint»:1,»transid»:61}
2022-04-03T22:31:35.687Z zigbee-herdsman:adapter:zStack:unpi:parser — parseNext []
2022-04-03T22:31:35.687Z zigbee-herdsman:adapter:zStack:adapter Data confirm error (0x149f0111e00bfdb0:1107,233,4)
2022-04-03T22:31:35.688Z zigbee-herdsman:controller:endpoint DefaultResponse 0x149f0111e00bfdb0/1 6(10, {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:1,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘MAC no ack’ (233))
2022-04-03T22:31:35.688Z zigbee-herdsman:controller:device:error Default response to 0x149f0111e00bfdb0 failed

What happened?

Recently I replaced two accent lights with ones using IKEA LED1935C5’s (which are listed as supported). The previous bulbs connected to Zigbee2MQTT without issue (IKEA LED1836G9’s). When first connected the new bulbs work as expected however, after a few hours they stop responding and report the following error in the logs:

2022-07-06 08:06:42Publish ‘set’ ‘state’ to ‘Light — Right Nightstand ‘ failed: ‘Error: Command 0x804b50fffe79b8e1/1 genOnOff.on({}, {«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))’

The fix seems to be to re-pair them and they work again for a few hours. I’ve tried pairing them next to the coordinator and forcing them to pair to another router located closer to the location they’re in with the same result. The old lights still work in this location so I don’t believe it’s an issue of low signal strength.

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.26.0

Adapter firmware version

20220219

Adapter

SONOFF Zigbee 3.0 USB Dongle Plus

Debug log

log.txt

Zigbee Adapter: V1.1.1
Zigbee Stick: CC2538+CC2592
Endgerät:

• model:GL-C-007
• vendor:Gledopto
• description:Zigbee LED controller RGBW
• supports:on/off, brightness, color, white

Hallo,
ich habe Problem mit dem o.g. Endgerät. Solange das Teil neben dem Raspi lag, lief alles rund. Nun ist der RGB-Controller im Zielraum installiert und es kommt beim Zugriff zu Fehlern «Error: Data request failed with error: ‘MAC no ack’ (233)». Die Steuerbefehle werden dann zum Teil nur mit Verzögerungen von mehreren Sekunden umgesetzt. Hier ein Auszug aus dem Log:

2020-07-26 23:21:11.198 - error: zigbee.0 (20068) Error on send command to 0x00124b001fb4d78d. Error: Error: Command 0x00124b001fb4d78d/11 genLevelCtrl.moveToLevelWithOnOff({"level":51,"transtime":0}, {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":false}) failed (Error: Data request failed with error: 'MAC no ack' (233))
at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:349:23)
at Generator.throw ()
at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65)
2020-07-26 23:21:14.271 - error: zigbee.0 (20068) Error on send command to 0x00124b001fb4d78d. Error: Error: Command 0x00124b001fb4d78d/11 lightingColorCtrl.moveToColorTemp({"colortemp":500,"transtime":0}, {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":false}) failed (Error: Data request failed with error: 'MAC no ack' (233))
at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:349:23)
at Generator.throw ()
at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65)
2020-07-26 23:21:17.345 - error: zigbee.0 (20068) Error on send command to 0x00124b001fb4d78d. Error: Error: Command 0x00124b001fb4d78d/11 genOnOff.on({}, {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":false}) failed (Error: Data request failed with error: 'MAC no ack' (233))
at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:349:23)
at Generator.throw ()
at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65)

Das Endgerät ist ca. 8 Meter vom Zigbee-Stick entfernt, wobei 2 Wände (mind. eine davon Stahlbeton) dazwischen liegen. Als Verbindungsqualität wird 68 angezeigt.

Was bedeutet der Fehler ‘MAC no ack’ und was kann man tun?

I am receiving the error/info messages below every 90 seconds in my zigbee2mqtt log, when office_lamp (GE 22670bulb) is off:

Zigbee2MQTT:error 2021-09-17 17:58:29: Publish ‘set’ ‘brightness’ to ‘office_lamp’ failed: ‘Error: Command 0x7ce5240000023969/1 genLevelCtrl.moveToLevelWithOnOff({«level»:254,»transtime»:450}, {«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))’ Zigbee2MQTT:info 2021-09-17 17:58:29: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«message»:»Publish ‘set’ ‘brightness’ to ‘office_lamp’ failed: ‘Error: Command 0x7ce5240000023969/1 genLevelCtrl.moveToLevelWithOnOff({«level»:254,»transtime»:450}, {«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»:»office_lamp»},»type»:»zigbee_publish_error»}’

How can I find out what triggers the set brightness command? I have looked high and low through my Node-RED flows, and disabled everything remotely connected to setting parameters for office_lamp, but the error still shows up.