Yes you did!
Thx you so much (again) for all these clarifications 
Hi,
previously the Zymkey module was working fine in raspbian stretch (raspberry 3), but when I upgraded to raspberry pi 3+ and raspbian buster, the zymkey is not binding (its blinking 5 times/sec), but not once in 3 sec.
Also, irrespective of that when I tried to run the test code, they were giving the attribute error (which I believe is secondary, primary is binding issue.)
is it the stretch/ buster issue, or am I missing something?
@Phil_S_Zymbit_1
Hi, could you please help me out with my question?
@siddhartha,I’m also experiencing same thing…Need reply for the same.
Critical members of our staff are on travel at the moment, but we will have an answer early next week.
Did you upgrade from an existing installation of Stretch to Buster or was this a fresh install? If the answer is no, then I assume you have done a fresh installation of Buster. Check to insure that you have enabled i2c support with sudo raspi-config.
We have tested things out and, in spite of an issue reported with Buster involving the Suite status to have changed from ‘testing’ to ‘stable’, we have no problem with Zymkey binding under Buster if the instructions in “Getting Started” are followed.
I wrote my own test code that do only encryption and decryption of data using public key
that is working fine but when I integrate with my project code its giving error in lock bad return code -110 after that zymkey is blinking 5 times per second.If I reboot raspberrypi then only it will
bind properly and one blink per second if I run my project code means it will blink fastly.binding ll go off.
Now I’m able to run both test codes without errors .I just converted strings of data into byte array
and encoded (utf8).
Yes, I did that, and in past it was working just fine.
Is there a possibility of that somehow, I accidentally broke the zymkey? Its taking power that for sure, but not binding after multiple reboots and installations. I switched back to ‘stretch’ but still its not binding.
Are there any other devices on the i2c bus or on GPIO4?
Battery problems -
My zymkey is in notify mode and tab not cut with the coin battery inserted.
I was expecting to keep flashing (every 3 seconds) once I power off the pi because the coin battery is still in there.
However, once I remove the pi, there are no flashing LEDs. Why would that be? How do I verify that the battery inserted in the zymkey works properly?
I’ve just moved a ZymKey still in developer mode from one Pi to another (both running Buster). It did go into slow blinking mode on the old Pi about 6 weeks ago. The new Pi has the latest Buster fully updated. On installing the software no errors are reported and it gets through to ‘Rebooting now…’.
However the ZymKey remains in its rapidly blinking mode?
I’ve tried this on 2 fresh installs with the same result. Please advise, thanks.
@rpiMike, have you enabled i2c on the fresh installs with raspi-config?
The flashing does not occur when power is removed, even if a battery is plugged in. This is to conserve power as the LED will consume some power.
Yes, i2c was enabled before installing software.
Hello, the zymkey number that we have at the back of every zymkey, is it unique? If not, is there a way to uniquely identify each zymkey?
@pragya015 - Yes, each datamatrix label is unique to a specific unit of zymkey.