Your comments

Hello, 

I removed the node and re-add the device, and it solved the issue. 

Thank you for your advice, 

François 

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,

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

Thanks,

François 

Thank you for your answers. 

I'm not on site anymore. I'll try your suggestions in a couple of months when I'm back. 

Hello, 

Sorry for my late answer, I didn't see your message. 

Yes, Refresh Configuration fixed the issue. Thank you very much for your help. 

François 

Hello,

The GC is connected and working. It's an iTach IP2IR, connected via a network cable. Fixed IP address. It's from early 2019.  It disconnects 5-7 times / day. Half of it at random ; and the other half when bOS attempts to send an IR command. It reconnects almost immediately, but there are still a couple of IR commands that are not sent.

And I'm still getting the error on the Z-Wave. Very rare now, once every two days. But I'm still getting them :-(

Best regards, 

François 

Hello,

I use the external z-wave interface as it's more convenient to set-up (can be moved easily close to the Z-Wave device) and in case I have to change the server I don't have to re-include all devices. 

I have set "ping enabled" to True, and the Connection Type to "External" : I'm pretty sure that I already chose "external" when doing the initial set-up, maybe it was reset by the bOS upgrade ? 

I also disabled the internal Z-Wave device. 

Since I did all that I haven't had one single disconnection on the Z-Wave device. So, looks good to me :-)

I'm still getting disconnects on Global Caché with the message : "error connecting to device. No Ack"

I never got this message before the upgrade (although I was getting some random disconnect, but not with the "No Ack" message) Any ideas how to fix that ? 

Thanks,

François 

Hello,

Thank you for your quick answer. 

I cannot update Linux OS : I don't have any Linux Upgrade Menu under the building node. Is that because I'm on the old Z-Wave Jigsaw server, and not Colibri ? How can I get this menu ? 

GC disconnects are at random. 

Z-Wave disconnects might be more often for scenes than at random. I'll have to monitor more closely to confirm. 

Is there anything that can be done on the Z-Wave settings to fix the issue : Read Delay and Ping enabled ? 

Note that I'm using an external Z-Wave key plugged to a Jigsaw USB port ; I'm not using the built-in Z-Wave controller. 

Same Z-Wave external controller that I'm using on my other KNX and Grinder servers, and I have no issues on those other servers. 

Best regards,

François 

Thank you for your quick answer. 

However, I don't have the update Linux OS menu on the building node :-(

Note that I don't have the KNX Jigsaw ; I have the Z-Wave Jigsaw, that has now been replaced by Colibri Z-Wave.

Is that the reason why I don't have that menu ? What can I do then ? 

Thanks,

François 

Hello,

Do you know when you will release the fix ? 

I can't use workarounds based on Chrome Browser on my tablets as for security reasons they can only access the bOS Android client. And I can't downgrade to a previous server version as I'm on Jigsaw. So, I'm stuck :-(

Thank you,

François