Jigsaw Z-Wave and latest version
Francois Lesueur 2 years ago in bOS Server • updated 2 years ago • 6
I'm getting very very frequent errors (several times / day) on :
- Z-Wave external device (not the built-in device which I do not use) : Error connecting to device. Failed to re-send
- Global Caché IP devices : Error connecting to device. No Ack
This starts happening since I updated my Jigsaw Z-Wave to 4.5. Continued in 4.8.8
They reconnect almost immediately ; but of course a few Z-Wave or GC orders are not executed while they are disconnected. So that's a big issue.
I'm also using Grinder and Jigsaw KNX : I don't have any issues on these servers which have similar configs (but V 4.7.0)
I was wondering if there were any support issues with the Jigsaw Z-Wave that you are not selling anymore ?
Can you help me fixing these issues ?
Customer support service by UserEcho
when do these disconnects occur? Randomly or are you controlling any bigger scenes or larger number of devices?
You could also try and update Linux OS on the device and check if you notice any improvements.
Please follow the instructions on the update and try to be patient as the update can take 1-2 hours to finish and the device shouldn't lose power/internet connection while updating.
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.
if the update isn't available via config, it could be updated via SSH manually by us.
Can't say for sure what's causing the disconnects, but it could be the use of external z-wave on the same server with the internal Z-wave interface. Why aren't you using the internal z-wave interface?
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 ?
oh yes, if both internal and external were enabled, that may caused the interference in the connection.
Regarding the GC connection, is the device connected and working? Seems the bOS is losing connection to the interface, how old is the device? How often do these disconnects occur?
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 :-(