# ZymKey not working on latest Buster (8Apr20)

**URL:** <https://community.zymbit.com/t/zymkey-not-working-on-latest-buster-8apr20/749>\
**Category:** ZYMKEY4\
**Created:** [April 8, 2020, 2:27pm UTC](https://community.zymbit.com/t/zymkey-not-working-on-latest-buster-8apr20/749 "2020-04-08T14:27:35Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![Bob\_of\_Zymbit](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@Bob\_of\_Zymbit](https://community.zymbit.com/u/Bob_of_Zymbit)\
**Post date:** [May 19, 2020, 2:41pm UTC](https://community.zymbit.com/t/zymkey-not-working-on-latest-buster-8apr20/749/21 "2020-05-19T14:41:38Z")

</div>

There are general discussions of GPIO pin conflicts in the documentation but your suggestion is good to include checking the 1-wire interface in the troubleshooting section.

We’ll fix the access problem with that link too.

You can use an alternative GPIO pin for the Zymkey. The steps are outline here:  
[https://community.zymbit.com/t/using-an-alternative-gpio-pin/589](https://community.zymbit.com/t/using-an-alternative-gpio-pin/589)

The other way would be to remap your 1-Wire interface (may be easier with your wiring?) To change the default GPIO pin used for 1-wire communication edit `/boot/config.txt` and add gpiopin=x to the end of this line (x is your new GPIO pin, no spaces), then reboot:

```auto
dtoverlay=w1-gpio,gpiopin=x

```

[Previous page](https://community.zymbit.com/t/zymkey-not-working-on-latest-buster-8apr20/749.md?page=1)