Bonjour,
En cherchant j’ai trouvé ce post : désactiver Soft Reset dans le plugin ZWave
Merci grace à toi et avec la désactivation du « Soft Reset » ça à totalement fonctionné pour ma part.
Aeotec ZW090 - Z‐Stick Gen5 USB Controller.
Ce que j’ai fait
Je ne sais pas pourquoi
merci
Bonjour,
Ce n’est pas lié à la clé, mais à l’utilisation d’une machine virtuelle.
Cette situation n’est pas présente sur un Raspberry Pi, ou la clé est en direct sur la machine.
Bonjour,
Un peu de lecture :
ouvert 09:39AM - 29 Sep 23 UTC
Restarting (aka. soft-resetting) a Z-Wave controller is automatically done at st… artup of Z-Wave JS to start from a clean state where the controller isn't doing anything weird. This is also necessary in certain situations, e.g. to apply configuration changes, or to work around firmware bugs.
Simply put, for **700 and 800 series** controllers, restarting is **required** from time to time.
For **500 series** and older, it is strongly **recommended**. Unfortunately, 500 series controllers may reconnect to USB when restarted, which can cause issues in certain setups. This is especially true in VMs, where the USB passthrough stops working unless the VM is configured correctly.
Until the update to v12, Z-Wave JS would detect these situations where the controller stayed unavailable after restarting and would disable soft-reset going forward. However this feature caused false negatives that could be nearly impossible to recover from, aside from manually editing a file that can be hard to get to. As a result, it was removed and the burden is now on the user to ensure their environment is set up correctly.
#### There are a few known solutions to this:
1. Prefer `/dev/serial/by-id/...` paths over `/dev/tty...` in case the path changes after reconnecting
1. When using the Aeotec Gen5 or Gen5+, [updating the firmware to 1.2](https://aeotec.freshdesk.com/support/solutions/articles/6000252294-z-stick-gen5-v1-02-firmware-update) can help, plus you get SmartStart support for free. **Warning:** A failed update can brick the controller, proceed at your own risk or look at other options first.
1. If you're using ESXi, [updating to 7.0u1](https://community.home-assistant.io/t/vmware-esxi-7-0-usb-compatibility/185939) can help.
1. For some other VMs, [this document](https://github.com/AlCalzone/ioBroker.zwave2/blob/master/docs/en/vm-usb.md) contains instructions for properly setting up USB passthrough.
1. [Expose the serial port via TCP](https://zwave-js.github.io/node-zwave-js/#/usage/tcp-connection), either from the host or a different device.
1. As a last measure, [soft-reset can be disabled](https://zwave-js.github.io/zwave-js-ui/#/usage/setup?id=z-wave) in the Z-Wave JS UI settings. The stick may need to be re-plugged, or the VM may need a restart before it starts working again. It is preferable to try the other solutions first, since being able to restart the stick has the aforementioned upsides.
Le problème ne concerne que la série 500.
ok merci beaucoup pour les infos
Je vais essayer de passer sur la ZOOZ que vous me conseillez
la migration sans tout réinclure manuellement mes 13 périphériques : est elle possible ?
MA clé est en Version ZwaveJS UI 9.20.0
Merci encore
Il y a déjà tout un post sur cette question.
Antoine
system
Mars 10, 2025, 2:44
7
Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.