# Could not reach device , is it powered on? **URL:** \ **Category:** Questions & Help\ **Tags:** homey-bridge\ **Created:** [March 29, 2022, 2:40pm UTC](https://community.homey.app/t/could-not-reach-device-is-it-powered-on/62143 "2022-03-29T14:40:58Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![eric\_nobel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eric_nobel/32/49173_2.png) [@eric\_nobel](https://community.homey.app/u/eric_nobel)\ **Post date:** [March 29, 2022, 2:40pm UTC](https://community.homey.app/t/could-not-reach-device-is-it-powered-on/62143/1 "2022-03-29T14:40:58Z")
I am getting the error in the topic could not reach device …. On almost all my zigbee switches or light bulbs. I restarted my Homey bridge a couple of times or removed the power of the Homey bridge but Nothing helps. ---
**Author:** ![Mannni](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mannni/32/33829_2.png) [@Mannni](https://community.homey.app/u/Mannni)\ **Post date:** [March 29, 2022, 5:01pm UTC](https://community.homey.app/t/could-not-reach-device-is-it-powered-on/62143/2 "2022-03-29T17:01:37Z")
By clicking to much you might have resetted those devices. Pair them again. ---
**Author:** ![Picsou621](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/picsou621/32/15357_2.png) [@Picsou621](https://community.homey.app/u/Picsou621)\ **Post date:** [March 29, 2022, 8:10pm UTC](https://community.homey.app/t/could-not-reach-device-is-it-powered-on/62143/3 "2022-03-29T20:10:40Z")
Zigbee is broken since the last update, I created a topic here: [Since last Homey Pro update, Zigbee is broken](https://community.homey.app/t/since-last-homey-pro-update-zigbee-is-broken/62153) This problem has absolutely nothing to do with “to much clicks” or “to much Zigbee devices”. And “pair them again” doesn’t work. ---
**Author:** ![Mannni](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mannni/32/33829_2.png) [@Mannni](https://community.homey.app/u/Mannni)\ **Post date:** [March 30, 2022, 1:29pm UTC](https://community.homey.app/t/could-not-reach-device-is-it-powered-on/62143/4 "2022-03-30T13:29:06Z")
You may read, bridge != Pro 🙄 ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [March 30, 2022, 2:07pm UTC](https://community.homey.app/t/could-not-reach-device-is-it-powered-on/62143/5 "2022-03-30T14:07:26Z")
> [@eric\_nobel](#): > > Nothing helps Didn’t restart Homey help? (Longshot) [https://tools.developer.homey.app/tools/system](https://tools.developer.homey.app/tools/system) ![Screenshot_20220330-160423_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/b/5bfe5b772572e461f9fbcb5befa704b1667880a4.jpeg) And notify Athom if you didn’t alr: [https://support.homey.app/hc/en-us/requests/new](https://support.homey.app/hc/en-us/requests/new) ---
**Author:** ![eric\_nobel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eric_nobel/32/49173_2.png) [@eric\_nobel](https://community.homey.app/u/eric_nobel)\ **Post date:** [March 30, 2022, 2:53pm UTC](https://community.homey.app/t/could-not-reach-device-is-it-powered-on/62143/6 "2022-03-30T14:53:23Z")
Reboot with developer tool did not help and power Toggle also did not help ---
**Author:** ![eric\_nobel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eric_nobel/32/49173_2.png) [@eric\_nobel](https://community.homey.app/u/eric_nobel)\ **Post date:** [March 30, 2022, 2:55pm UTC](https://community.homey.app/t/could-not-reach-device-is-it-powered-on/62143/7 "2022-03-30T14:55:39Z")
So often things don’t work. Did you already report it to atom ? I don’t get any responce from atom