# Could not reach device - message **URL:** \ **Category:** Questions & Help\ **Created:** [February 26, 2019, 9:44pm UTC](https://community.homey.app/t/could-not-reach-device-message/9768 "2019-02-26T21:44:23Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Ikon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ikon/32/11729_2.png) [@Ikon](https://community.homey.app/u/Ikon)\ **Post date:** [February 26, 2019, 9:44pm UTC](https://community.homey.app/t/could-not-reach-device-message/9768/1 "2019-02-26T21:44:23Z")
![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/4/41ed1dbb5681cd0b1b394ca1cd6ca0f9b2ff760c.jpeg) i get this message now for one of my Ikea lights. Is there anyway to fix it? I really really don’t wanna reset it since i have the light in a lot of flows ---
**Author:** ![bvdbos](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bvdbos/32/2352_2.png) [@bvdbos](https://community.homey.app/u/bvdbos)\ **Post date:** [February 27, 2019, 5:55am UTC](https://community.homey.app/t/could-not-reach-device-message/9768/2 "2019-02-27T05:55:34Z")
Can you reach your device through [https://developer.athom.com/tools/zigbee](https://developer.athom.com/tools/zigbee) ? ---
**Author:** ![Ikon](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ikon/32/11729_2.png) [@Ikon](https://community.homey.app/u/Ikon)\ **Post date:** [February 27, 2019, 6:37am UTC](https://community.homey.app/t/could-not-reach-device-message/9768/3 "2019-02-27T06:37:12Z")
well, yeah, I can SEE it in the list. but I can’t DO anything to it, or? ---
**Author:** ![cloun](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cloun/32/14219_2.png) [@cloun](https://community.homey.app/u/cloun)\ **Post date:** [August 5, 2019, 7:29pm UTC](https://community.homey.app/t/could-not-reach-device-message/9768/4 "2019-08-05T19:29:45Z")
I have the same issue with a lot of IKEA devices (early tunable GU10 lights). Sometimes (after a Homey reboot or power outage) a device answers to dimming, but not to on/off. But usually they are “unreachable” to all types of commands when in this state. Sometimes a reboot of Homey does the trick, sometimes several reboots, but I have no real solution to this. My IKEA lights are located 7 meters up so I’m not so keen on trying to re-pair them with Homey… Any progress with your issues or anyone else have any advice? ---
**Author:** ![Lars\_Faber](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lars_faber/32/8118_2.png) [@Lars\_Faber](https://community.homey.app/u/Lars_Faber)\ **Post date:** [August 5, 2019, 7:39pm UTC](https://community.homey.app/t/could-not-reach-device-message/9768/5 "2019-08-05T19:39:34Z")
I have the same issue. I think this is the problem Homey has with Zigbee. If you search on the forums you find more posts about it. I hope it will be fixed when the Zigbee rewrite is done. ---
**Author:** ![cloun](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cloun/32/14219_2.png) [@cloun](https://community.homey.app/u/cloun)\ **Post date:** [August 5, 2019, 7:54pm UTC](https://community.homey.app/t/could-not-reach-device-message/9768/6 "2019-08-05T19:54:14Z")
Thanks for your answer! I’ll do some more reading. I’m starting to get frustrated with Athom’s poor software now… The consequence of their incompetence is a way too high impact on my everyday life. Guess I shouldn’t have trusted their solution to automate my whole home. I’ll update my Homey to 2.5.1 and hope for a miracle while waiting for the ZigBee rewrite… ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [August 6, 2019, 4:27pm UTC](https://community.homey.app/t/could-not-reach-device-message/9768/7 "2019-08-06T16:27:43Z")
> [@cloun](#): > > Sometimes a reboot of Homey does the trick, sometimes several reboots, but I have no real solution to this. Maybe next time first try to restart only the Ikea app instead of the complete Homey. That has less impact on the rest of your apps & devices. ---
**Author:** ![cloun](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cloun/32/14219_2.png) [@cloun](https://community.homey.app/u/cloun)\ **Post date:** [August 6, 2019, 10:06pm UTC](https://community.homey.app/t/could-not-reach-device-message/9768/8 "2019-08-06T22:06:53Z")
Thanks Peter! That will speed things up and might resolve some of the situations. My current unreachable devices show up as “offline” without a “joinTime” in devtools. That makes me guess that the major problem probably is located in the Homey ZigBee stack. Is that a hasty conclusion? Strangely they do have the Homey nodeID 0 listed as route, in contrast to my truly disconnected devices that only shows its own nodeID. ---
**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\ **Post date:** [August 7, 2019, 4:56am UTC](https://community.homey.app/t/could-not-reach-device-message/9768/9 "2019-08-07T04:56:41Z")
Hmm, sorry , i wouldn’t know that and have never seen that with my Zigbee mesh. All my devices have Homey directly as a route. But that it is a possibility indeed.