-
Notifications
You must be signed in to change notification settings - Fork 645
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
Increase routing table sizes #375
Comments
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 |
Did the new SDK fix this issue? |
It seems it is, thanks for pinging, increased the MAX_RTG_SRC_ENTRIES to 500 @ Devon1984 can you check this fw on your network? |
So, this should support larger networks more efficiently, without recurring route discoveries? |
@tteck yes, it can cache more source routes |
I am getting these errors on our new device. I am really far away from the coordinator with no routers when this happens. I'll flash and report back to see if this changes things over the next week. |
@Koenkk sorry when you tagged me it didnt send me a ping. I think its because of the space between the @ and my name :-) |
@Koenkk Its been running now for about an hour and no NWK_TABLE_FULL errors! :-) normally i would have some by now. |
@Koenkk Im letting the FW run for a bit longer to get some more data points but comparing the logs i can see a huge improvement. Previously i would get around at least 22 NWK_TABLE_FULL errors per day and now im getitng only 1 or 2 of those errors on the new FW. Would you like me to send any logs for you to look over? |
@Koenkk I have been running this FW for the last 2 days and I have only had 8 instances of NWK_TABLE_FULL errors. Out of curiosity, is 500 source routes the maximum number or can we go higher? whats the disadvantage of going higher? Im wondering what it would take to completely eliminate the NWK_TABLE_FULL errors. |
Great to hear. I've recently improved the firmware further for larger networks. Can you check if this firmware gives more improvements? https://github.com/Koenkk/Z-Stack-firmware/tree/develop/coordinator/Z-Stack_3.x.0/bin |
Thats excellent news!! Thanks for working on this and helping us users with large networks @Koenkk :-) |
@Koenkk This FW is most definetly better than the last one! In short, i have had this running now for over 28 hours and i have had NO occurances of the NWK_TABLE_FULL errors which is a GREAT result! I havent noticed any device drop off's either which is amazing. I have attached my log for information, please start reading from the following time "2022-09-29 15:48:01" before this time i was turning on all my lights and getting the network to settle after the FW upgrade so these errors can be ignored. You will see a lot of the following errors "(Data request failed with error: 'MAC no ack' (233))" but i believe this is normal because we do use the wall switches in the house to turn off the lights from time to time and of course then the coordinator cant ping the light and hence the error but the most important thing is once i do turn on the light switch there are NO "NWK_TABLE_FULL errors" at all, where before i would be getting them regularly when i turn the lights on. The only other new error is the following "(Data request failed with error: 'MAC channel access failure' (225))" I have never seen this error before so not sure what this one is but they dont happen very often and i suspect it has something to do with the light switch being off. Do you know what the difference between these two MAC errors are? Ill let this FW run now for the rest of the weekend and give it a good workout :-) and give you an update on Monday. If you have any more FW versions that you would like me to test please pass them on to me and ill load it up and test it for you! especially if you have further improvements for the larger networks :-) |
|
Thanks Koen. My coordinator is on zigbee channel 11 and all my local wifi network is on channell 11, 12 and 13. I will check the neighbours wifi, although none of my neighbours are really close to me at all and with brick house walls it should be fine. Im not too concerned as this error doesn't happen very often at all. I was just curious what it actually meant. :-) |
@Koenkk I have been running the new FW for the last 3 days and the only day that had any NWK_TABLE_FULL errors in the logs was today. It was only 14 events and it all happened this morning around the same time, but im putting it down to my server as it was busy with a Parity check. I have been very impressed with the modifications that you have made, they are making a HUGE difference on my side, especially with all the lights in the kids rooms etc. as sometimes the kids turn the switch off when they go to bed. Before this FW i used to get lots of NWK_TABLE_FULL errors and delayed responses when lights were turned off and on at the wall but now im not seeing any of this behaviour. Also, i havent seen any of my other passive devices disconnecting and/or staying disconnected which is awesome!! Definetly one of the best FW releases i have had! Thanks so much!! |
@Devon1984 great to hear! |
Follow up: #439 |
Thanks for the tag @Koenkk ill get this installed ASAP today and report back. |
To decrease the chances of a
NWK_TABLE_FULL
error (e.g. Koenkk/zigbee2mqtt#12439) the routing table size should be increased (MAX_RTG_SRC_ENTRIES
andMAX_RTG_ENTRIES
). Due to a bug in the SDK these tables cannot be increased beyond 255 currently: https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1103762/simplelink-cc13x2-26x2-sdk-cannot-set-max_rtg_src_entries-higher-than-255The text was updated successfully, but these errors were encountered: