# TKB Home - Firmware 3.0.0 Problem

**URL:** <https://community.homey.app/t/tkb-home-firmware-3-0-0-problem/80151>\
**Category:** Apps\
**Created:** [May 6, 2023, 5:48pm UTC](https://community.homey.app/t/tkb-home-firmware-3-0-0-problem/80151 "2023-05-06T17:48:31Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![woto](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/woto/32/33967_2.png) [@woto](https://community.homey.app/u/woto)\
**Post date:** [May 6, 2023, 5:48pm UTC](https://community.homey.app/t/tkb-home-firmware-3-0-0-problem/80151/1 "2023-05-06T17:48:31Z")

</div>

Hey Guys

Wondering if anyone has had a problem with the new TKB Home firmware 3.0.0 that was pushed the other day ?

New firmware has been pushed today 3.0.1 but still having this problem when clicking on the switch to turn it on or off comes up with this error - Could not get device by id

This only happens with the TZ88E switches

![IMG_0732](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/f/0f9f6eaa03270282752fd0d1764e458652a8253e.jpeg)

---

<div class="post-metadata">

**Author:** ![Phil\_Shotton](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phil_shotton/32/12622_2.png) [@Phil\_Shotton](https://community.homey.app/u/Phil_Shotton)\
**Post date:** [May 7, 2023, 9:43pm UTC](https://community.homey.app/t/tkb-home-firmware-3-0-0-problem/80151/2 "2023-05-07T21:43:17Z")

</div>

So this was working fine pre 3.0.0? Can you create a diagnostic report (apps…TKB Home, select the cogwheel top right and ‘Create diagnostics report’).

---

<div class="post-metadata">

**Author:** ![woto](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/woto/32/33967_2.png) [@woto](https://community.homey.app/u/woto)\
**Post date:** [May 8, 2023, 5:32am UTC](https://community.homey.app/t/tkb-home-firmware-3-0-0-problem/80151/3 "2023-05-08T05:32:57Z")

</div>

Hey Phil

Yes the switches have been working fine pre 3.0.0 - here is the diagnostic report “75189F”

---

<div class="post-metadata">

**Author:** ![Phil\_Shotton](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phil_shotton/32/12622_2.png) [@Phil\_Shotton](https://community.homey.app/u/Phil_Shotton)\
**Post date:** [May 8, 2023, 9:31am UTC](https://community.homey.app/t/tkb-home-firmware-3-0-0-problem/80151/4 "2023-05-08T09:31:45Z")

</div>

Hi, that number doesn’t come up in my crash reports. What I need is a log id like the following:  
Log ID: 4a138536-b731-4fc9-991f-a00b74d53677

Can you provoke the error, create a diagnostic report and send me the log id.  
Thanks

---

<div class="post-metadata">

**Author:** ![woto](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/woto/32/33967_2.png) [@woto](https://community.homey.app/u/woto)\
**Post date:** [May 8, 2023, 10:19am UTC](https://community.homey.app/t/tkb-home-firmware-3-0-0-problem/80151/5 "2023-05-08T10:19:41Z")

</div>

Hi - not sure where to find that - I use this tab to create the id number

 ![IMG_3326](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/3/432c1c56c539ed13beeee7c729f6a99c44d45606.jpeg)

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [May 8, 2023, 10:40am UTC](https://community.homey.app/t/tkb-home-firmware-3-0-0-problem/80151/6 "2023-05-08T10:40:03Z")

</div>

You need to send a report on app level:  
Mobile app → more… → apps → TKB Home → cogwheel (top right) → create diagnostic report

---

<div class="post-metadata">

**Author:** ![woto](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/woto/32/33967_2.png) [@woto](https://community.homey.app/u/woto)\
**Post date:** [May 9, 2023, 6:37pm UTC](https://community.homey.app/t/tkb-home-firmware-3-0-0-problem/80151/7 "2023-05-09T18:37:44Z")

</div>

Hi - thanks for the info - never had to do the diagnostic report like that - here is the log file a0e4543f-9f82-4326-97d6-72e0729fb39f
