# Coprocessor Not Connected - Homey Bridge **URL:** \ **Category:** Questions & Help\ **Tags:** homey-bridge\ **Created:** [December 31, 2021, 7:02am UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525 "2021-12-31T07:02:57Z")\ **Posts on this page:** 11\ **Page:** 4
**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\ **Post date:** [January 6, 2022, 4:14pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/62 "2022-01-06T16:14:18Z")
> [@wimvandorst](#): > > What actually IS the coprocessor? A Coprocessor is a second processor in the Bridge (and Homey Pro) that is responsible for some RadioCommunication. Zigbee and Z-Wave have their own Chips. ---
**Author:** ![G.P.Velberg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/g.p.velberg/32/47798_2.png) [@G.P.Velberg](https://community.homey.app/u/G.P.Velberg)\ **Post date:** [January 6, 2022, 6:27pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/63 "2022-01-06T18:27:11Z")
I have the same problems with both homey bridge Beta’s , at the moment no problems with coprocessor, problems with KAKU began when i trie to make time schedule’s or day and night schedule’s. All this time modules works over theCLOUD, now i do it old way with ATMT-502 or with Homewizard app ---
**Author:** ![Stefanvh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stefanvh/32/47838_2.png) [@Stefanvh](https://community.homey.app/u/Stefanvh)\ **Post date:** [January 6, 2022, 10:32pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/64 "2022-01-06T22:32:46Z")
I have the homey bridge, all my web based lights work ok. but when homey uses it’s own kaku and zwave antenna’s then the issues start. (fibaro - klikaanklikuit) 🙃 ---
**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:** [January 9, 2022, 6:43pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/65 "2022-01-09T18:43:38Z")
I think atom fixed all the problems today , i don’t have any problems anymore. Fibaro ,zigbee, kaku (rf) is working great. ---
**Author:** ![wimvandorst](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wimvandorst/32/45201_2.png) [@wimvandorst](https://community.homey.app/u/wimvandorst)\ **Post date:** [January 9, 2022, 7:39pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/66 "2022-01-09T19:39:49Z")
Yes, functionality seems to have been restored here too. Interestingly, the Fibaro reaction is some five seconds after all the other devices handle triggering my All-LIghts-Out flow. That’s five lights (RTS, Wiz) within one second after the trigger, and two lights (Fibaro) some five seconds later. But they work again. I’ll give it a few days to really conclude that the problems have been solved. And I would certainly appreciate to learn what was the actual root cause: the technical aspect of the Bridge and home automation is the reason for having a Homey. ---
**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:** [January 9, 2022, 9:02pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/67 "2022-01-09T21:02:04Z")
What does your measured latency say? Here it’s around 50ms atm > ![Screenshot_20220109-220301_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/c/7ce755f268646e6c5ade328af114c1e588ea6725.jpeg) Find it here: > **[The new Homey — Beta Status](https://homey.app/en-us/wiki/homey-beta-status/)** ---
**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\ **Post date:** [January 9, 2022, 11:09pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/68 "2022-01-09T23:09:06Z")
![SmartSelect_20220110-000157_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/8/d89b2474d8ac8dbfe30f52b43662d213c1031fd7.jpeg) 29 seconds, but then again, Iive in Athom’s hometown… 🙂 (which is no guarantee, I know) ---
**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:** [January 9, 2022, 11:29pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/69 "2022-01-09T23:29:01Z")
Milliseconds I think😬 Hehe, the servers are in Frankfurt afaik, but you’re closer anyhow then. I’m on a 100Mbit ADSL so I think a latency around 50ms is pretty realistic 😃 ---
**Author:** ![wimvandorst](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wimvandorst/32/45201_2.png) [@wimvandorst](https://community.homey.app/u/wimvandorst)\ **Post date:** [February 22, 2022, 11:49pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/70 "2022-02-22T23:49:24Z")
Latency: 22 ms (eu-central-1). Middle of Netherlands, 500 Mb/s glasfibre. THIS bit of the Homey Bridge works excellently already for five months, since I have it. But the Fibaro not working, and just now the Coprocessor Not Connected message is not excellent. ---
**Author:** ![fisherman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fisherman/32/123049_2.png) [@fisherman](https://community.homey.app/u/fisherman)\ **Post date:** [April 9, 2026, 7:06pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/71 "2026-04-09T19:06:50Z")
I am getting this error message “coprocessor not connected" when using my Homey Bridge with Fibaro devices. All other web based devices work just fine. When I unplug the Homey Bridge for a minute, afterwards it works again. A few days later, same error returns. Is there a fix for this? ---
**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:** [April 9, 2026, 8:19pm UTC](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525/72 "2026-04-09T20:19:49Z")
It’s probably a local wifi issue, the bridge disconnects (coprocessor == bridge) The bridge needs to connect to an very old style fashioned wifi, like if it’s 2001. - Create a separate 2.4GHz SSID - In case you use access points: \ ***no hopping!** Fix it to one access point (you can use mac filtering / band steering / transmit power tuning) - Move the bridge 50 to 100cm away from a wifi antenna ( too close = bad signal) [Previous page](https://community.homey.app/t/coprocessor-not-connected-homey-bridge/57525.md?page=3)