I’m a developer myself, so I’m not afraid of “not customer friendly”… Would you like to share your solution? Depending on the used technologies, I might be able to put some effort in as well.
Regarding your question: I was trying to get a feeling about the chance of success when I’m going to buy that stick. Since you’re saying that most ember based sticks are roughly the same, I think I’m going to buy one.
I’ve got everything working with this stick. I’ve not yet reached 20 devices, but I don’t see a reason why that shouldn’t work. I don’t have any Zigbee 3.0 devices yet, so I can’t confirm if that works.
While zigbee networks can support a lot of devices (in theory there’s no limitation) devices hold a bunch of tables and the size of these tables depends on memory. You can nearly always get more than 20 devices to join a network, but performance may not be good if the devices have limited memory.
These older devices do have limited memory - that said, newer devices have more, but likely don’t use it unless the code is modified to support larger tables which I suspect most aren’t. I worked with a company in Germany last year to look at this issue to support large networks so there are a few tricks to work through to get the system to perform.
Yes, both of my Bitronvideo 2010/10 are marked as “Bitronvideo 2010/10”.
I do not remember if they where bought as “Bitronvideo 2010/10”. Purchased some months apart.
It do look like “Telkom” is the same stick, as pictures on Amazon show “Bitronvideo” stamped on them.
After just a quick look at the binding docs, I could not find any link to newer firmware.
But it can be my eyes
As written by @Ap15e, Silabs stopped supporting certain devices quite recently. Any device with less than 512k of memory is not supported by newer stacks. The EM35x series are now quite old and are no longer supported by Silabs.
Yes, I know it is not longer supported by silabs.
the version published looks like 6.7.8.
One will be better off with a newer chip and newer firmware,
no doubt if looking at it in a longer perspective.
Sorry - it looked like you were disputing what was said earlier when you said there was a newer firmware “updated yesterday” - my bad. I think 6.8 is the last version that will be supported on these older Ember chips before Silabs added more code to the codebase that meant it doesn’t compile on the smaller chips.
I also missed to answer your question -:
You need to select the “Latest” documentation as I posted above - or to be sure you really have the latest (since I don’t know how often the OH docs is updated from GitHub), then it’s always safest to just look on GitHub.
Scrolling down to the Ember NCP Coordinator section has the relevant links -:
This bug was only in snapshots for a week or so - it was introduced in some changes shortly before you noticed, so most people won’t have had any issue using 115k2 (I’ve personally always used this on all my systems going back to the first version of the binding).