0
Under review

GC disconnection

Francois Lesueur 10 months ago in Devices / Global Caché updated by ComfortClick Support 1 month ago 12

Hello,

I've got several GC modules on several bOS systems. 

On all of these systems (Grinder, Jigsaw KNX, Jigsaw Z-Wave) the GC gets sometimes disconnected, at random. Sometimes it reconnects in a matter of seconds ; sometimes it doesn't reconnect and the only solution is to disable and then re-enable the device, or to restart bOS. 


1st question : is there any ways to fix that ? 


2nd question : I can make a test before using GC to check if it is connected or not. But then what can I do ? It seems that it is not possible by program to disable a device, or to restart bOS. Is that correct ? Any other solutions ? 


Thanks,

François 

Hi Francois,

Had similar behavior in the past. It came from IP address interferences... no disconnection ever since I've set all my GC device on fix IPs. Hope this can help...

Hi Fabien,

Thank you for the tip. I will move to fix IP and cross my fingers :-)

Hello,

Unfortunately, no luck : the GC still gets disconnected, even with fixed IP address. 

Even more strange : I'm using both the GC IR and input : so, I have two devices : one for the input, the other one for sending the IR signals. 

The device for the input never gets disconnected ; the one for the IR output gets disconnected. After a power cut, it is disconnected, and does not reconnect, unless I disable the device and re-enable it. 

bOS team, any solutions to fix the issue, or at least to re-connect the GC through some tasks ? I'm on Jigsaw KNX CCJigsaw 0.0.1 server version 4.7.0

Under review

Hello,

we'll do some internal testing regarding these GC disconnects and try to resolve this issue.

We'll also try and add this function that will allow us to disconnect/connect our drivers using our tasks as in some cases this resolves the problem.

Best regards.

Hello, 

Thank you for your answer. 

Can you let me know when the new function to disconnect/connect drivers with tasks is available in Beta ? 

Thank you very much, 

François 

Hello,

each time the power is cut, you have to manually enable and disable it to make it work again?

Which GC do you have?

We have tested in the office this situation with the iTachFlexEthernet, so it has a built in ethernet connector. 

We set the static IP, added our AC device, learned a couple of commands, then the power was cut multiple time, but after plugged back in, IR commands are still working normally.

Can't say which beta or version will we implement the option on automated restart or restart with a button, but it will be added.

Since one device works normally all the time and only another is causing issues, could the issue also be on the device's side?

Best regards.

Hello, 

I have several iTach IP2IR. 

It doesn't re-connect after a general power cut - but this means the the entire network of the house is powering up. 

When I'm disconnecting the iTach power supply only, and then plug it back, it does re-connect. 

I can explain to my customer that after a power cut we need to do something. The problem is more the random disconnections - and they are not due to power cut. I don't know the cause, it's random. 

I suspect the cause might be with the Internet provider : on one house, I moved to another Internet provider, and the issue has almost disappeared : it has become very rare. 

No ways to tell why as it's random, it's difficult to diagnose. 

So, the reconnect feature (even with a button or from a task) would indeed be very useful. 

Thank you very much,

François 

Hello,

indeed all random disconnects and random malfunctions of devices/lost connections are really difficult to recreate and diagnose, automated reconnects of our drivers would be a nice workaround for these random disconnects and connection issues with the drivers.

There's no ETA on the release of this task but we'll try and push it a bit closer to our releases so it will be available sooner.

Best regards.

Hello,

Do you now have an ETA for the availability of the above feature, automated reconnects ? 

Thanks,

François 

Hello,

we did some re-testing on the driver and all of our drivers already have this type of feature, if a response doesn't occur in a time period, the device will try and automatically reconnect, so additional function for manual restart will unfortunately not occur.

We will however, take a closer look at the GC driver and check if there are any other tweaks that can be done to improve the connectivity.

Also, if possible, next time the device stops working to contact us directly and we can immediately check the connection and see what the problem might be.

Also, if you have any logs (bOS logs) that you can provide regarding the device's response when sending commands will be helpful.

best regards,

Hello,

Indeed the drivers automatically reconnect most of the time. But not always. In some cases, I don't know why, they don't reconnect, and then the only solution is to disable the driver from bOS configurator, and to enable it again. This is the feature that I'm requesting : being able to disable and enable a driver from bOS script. 

I'll send you bOS logs when I'm on site in July. What kind of logs do you need ? Devices ? Monitor ? Debug ? 

Do you need the log when the GC is disconnected, or when it's working correctly ?  

Best regards, 

François 

Hello,

we have some other minor tweaks to do on our GC driver so we'll take a closer look at the reconnect pattern and maybe improve the connection by tweaking some settings. In most cases, responses are stored in the debug log, but other ones can come in handy as well.

Best regards.