-
Notifications
You must be signed in to change notification settings - Fork 31
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
2 keys: 1 can be updated, the other not #102
Comments
Look at the first number. 20:20200101.0 20 > 2 |
But the key were given to me at the same time and the current firmware is 2... How can the 2nd key be higher than the current firmware ? The key doesn t blink or lights except once blue. Can I override ? |
It means solo20 ! Instead of solo2... |
I wonder if that is either a custom firmware, or else one of the keys you have is a 'hacker' edition. |
It should be the hacker edition. It was from the kickstarter. Lukas from Sensor.Community who is always up to date (or state of the art?) give us 2 keys each. Unfortunately I have jsut one now... |
I will have to wait 18 years... |
Yeah, the hacker edition cannot be updated using the normal updates from my understanding. I have one of each as well. I use the standard one all the time. The hacker edition is sitting here because I haven't learned it / figured it out yet. |
The both keys are the same. The Update perfectly worked for the first. Maybe I will succeed to get a new key ... |
Does anyone have the same issue? |
Hacker edition is not the same as regular edition. Look at your screenshots again - the Solo2 also shows "locked" after it. The Solo20 does not. I suspect that while they look the same they actually are not. |
I can't Tell more... |
I have an issue I can't understand:
I was given 2 solokeys and I was told I have to update them before use.
I followed the instructions and it works perfectly on the first key.
For the second key, I can see 1 blue bink only and then:
20:20200101.0 is under 2:20220822.0, isn't it ?
Can you explain me the issue.
When I plug the both keys:
The first line is the key which was updated succesfully. Why is there this locked ?
The text was updated successfully, but these errors were encountered: