Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not send data/control end device after connect to a router #1090

Closed
dzungpv opened this issue Feb 14, 2019 · 16 comments
Closed

Could not send data/control end device after connect to a router #1090

dzungpv opened this issue Feb 14, 2019 · 16 comments
Labels
stale Stale issues

Comments

@dzungpv
Copy link
Contributor

dzungpv commented Feb 14, 2019

I am running the latest release version 1.1.1 and the edge version.
Coordinator is CC2530+CC2591 firmware version: '20190109'.

Step to produce bug:

First connect a zigbee end device (ZED) (custom hardware running on cc2630 chip using TI sample switch , send report state each 1 minute) to coordinator (ZC) directly. Now it could be control normally with on/ off. turn on/off the ZED or ZC not affect.

Now connect 1 CC2530 router running SampleLight project or ptvoinfo firmware to the network.
two of them work normally. Now turn off the ZC for 5 minute, ZED will find the router and connect to it.
And then turn on the ZC. From that moment the ZED switch could not control any more, it show:

Zigbee publish to device '0x00xxxx000d801379', genOnOff - off - {} - {"manufSpec":0,"disDefaultRsp":0} - 1 failed with error Error: AF data request fails, status code: 240. MAC transaction expired.

Please note that from an CC2531 sniffer the network still running normally, ZED could send report each minute and zigbee2mqtt show it:

2019-2-14 17:45:47 - debug: Received zigbee message of type 'attReport' with data '{"cid":"genOnOff","data":{"onOff":1}}' of device 'DNCKAT_S004' (0x00xxxx000d801379)

But turn off the router, ZED can be control normally
Logs: https://pastebin.com/iZKBimxX

This bug prevent me to use any router to extend the network. Also cause the Livolo switch could not use any router and may be issue with control it as mention here #592

@dzungpv dzungpv changed the title Could not send data to End device after connect to a router Could not send data/control end device after connect to a router Feb 14, 2019
@Koenkk
Copy link
Owner

Koenkk commented Feb 14, 2019

@ptvoinfo could this be a bug in the router firmware?

@dzungpv
Copy link
Contributor Author

dzungpv commented Feb 14, 2019

@Koenkk I also build my own router firmware base on TI samplelight and sampleswitch project. Any device could be a router too.

@dzungpv
Copy link
Contributor Author

dzungpv commented Feb 14, 2019

This also occur with xiaomi wall switch and plug.

@dzungpv
Copy link
Contributor Author

dzungpv commented Feb 23, 2019

@Koenkk I guest that zigbee2mqtt or zigbee-sepherd send the packet (on/off command) not work when end device reconnect to the router or when the router reconnect to the coordinator.
The problem occur when the coordinator off line for 5 minutes and online after that (router and end device still online ), the command only receive but not send to end device, it only could send to router.
In zigbee it call hop, it may not handle fine.

We may use broad cast send with end device. I will check zigbee-sepherd api.

@kirovilya Do you have any idea?

@kirovilya
Copy link
Contributor

kirovilya commented Feb 25, 2019

@dzungpv Hmm, strange. I saw this with xiaomi plug. It was treated by turning off and turning on the plug.
Now in iobroker.zigbee we send a reset when the adapter starts, and we also send ping to all routers every minute.
Maybe this approach will help in this case.

@dzungpv
Copy link
Contributor Author

dzungpv commented Feb 25, 2019

@kirovilya  I don't know what you mean send a reset when adapter start.

You reset the coordinator or the router? How you do that?

@kirovilya
Copy link
Contributor

@dzungpv I mean this signal https://github.com/Koenkk/zigbee2mqtt/blob/master/lib/zigbee.js#L81 at coordinator. Some routers at this time re-pairing with the coordinator

@dzungpv
Copy link
Contributor Author

dzungpv commented Feb 25, 2019

@kirovilya But we must allow_to_joint with soft reset?

@kirovilya
Copy link
Contributor

@dzungpv no

@dzungpv
Copy link
Contributor Author

dzungpv commented Feb 25, 2019

@Koenkk can you check this?
Is z2m now send soft reset when coordinator start?

@Koenkk
Copy link
Owner

Koenkk commented Feb 25, 2019

@dzungpv no, I will add this.

@kirovilya
Copy link
Contributor

check first :)

@Koenkk
Copy link
Owner

Koenkk commented Feb 25, 2019

@dzungpv
Copy link
Contributor Author

dzungpv commented Feb 28, 2019

@Koenkk I will try, but this is an Zigbee 1.2 issue, we must migrate to 3.0 to solve the problem:
https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/p/766240/2834664#2834664

@Koenkk
Copy link
Owner

Koenkk commented Mar 22, 2019

did this change have any effect, or is 3.0 the only solution?

@stale
Copy link

stale bot commented May 21, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale issues
Projects
None yet
Development

No branches or pull requests

3 participants