Global Caché disconnection

Francois Lesueur 5 years ago in Devices / Global Caché updated 5 years ago 4


I've got several Global Caché iTach devices. 

I'm getting the following error messages a couple of time every day, at random : 

"Error connecting to device"

"Device is connected"

This is just a 1 minute disconnection, but when this is happening when I want to trigger an IR command, that's a disaster : it's not working, and users get very irritated. 

Any ways to fix this ? 

Please note that I was using before another smart home box, and I didn't have any issues at all with the Global Caché. 



Hey there François, how's it going?

I've noticed that this problem is also related to your other post, where you're getting random devices disconnected and reconnected.

I had a similar problem a few months ago, and to be honest I don't remember how it was fixed. But can you try to do a "Repair Server" option on the Configurator, to see if it fixes the problem?

Best regards

Hi Ricardo, I'm fine, and you ? Any plans to come to Paris soon ? 

Thank you very much for your advice. I did "Repaired" the server this morning. And so far, so good. But let's wait a couple of days to confirm. 

Kind regards,


Hello Ricardo,

It did the trick on the Grinder : I haven't had a single Globl Caché error since I repaired the server. 

Thank you very much for your suggestion ; it's been very helpful. 

It's not so convincing on the Jigsaw. I did a server repair, and I'm getting much fewer errors, but I'm still getting a few. Actually, got only two, and they might have happened at the same time than  a connection issue between bOS iOS client and the server. (Another bug I can't seem to fix ; have to do the uninstall / reinstall each time). It doesn't seem to be making any sense as there shouldn't be anylinks, but who knows... I have to monitor a bit longer to be sure. 

Kind regards,


After two weeks looking at the logs, I confirm this is fixed for Grinder, but unfortunately this is not fixed for Jigsaw. The number of errors was smaller, but now it's back to the usual 2-3 errors every day. 

Guys from ComfortClick, any ways to fix this ? This is clearly something wrong with bOS server...