Swiid / CBC switch dead after a while #6430
-
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?NO, my problem is NOT within Home Assistant or the ZWave JS integration Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?NO, my problem is NOT within Z-Wave JS UI Checklist
Describe the bugWhat causes the bug? What do you observe? What did you expect to happen? I have had this devices for many years, one at my place and one at my parents. Device informationManufacturer: Swiid But zwave-js identifies it as this device: https://devices.zwave-js.io/?jumpTo=0x0166:0x0100:0x0100:0.0 Node ID in your network: 13 How are you using
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
This is the stick telling us that it didn't get an acknowledgement from the device that it got the command, after several attempts. Sending commands in Z-Wave roughly works like this:
This is an oversimplification, but as you can see, Z-Wave JS has no influence on what happens after telling the stick to send something. That part of communication depends entirely on the stick's hardware, software and location, the device's hardware, software and location, as well as the physical environment (sources of RF noise and interferences, etc...) Not sure what you changed when switching to Z-Wave JS, but there might be a few factors that could cause this:
Being dead/unreachable is often just a temporary state. If you really need to reset the device and include it again, and things pushing a button on the device does not bring it back, this does hint at a problem with the device itself. |
Beta Was this translation helpful? Give feedback.
-
|
Well I guess I did not even consider it could be an issue with the stick in relation to the device. So I suppose you can close this, it's probably indeed a hardware issue, unless there is anything I can do about it? |
Beta Was this translation helpful? Give feedback.
-
It probably won't give us any additional information. You can try following these steps/instructions to try and improve the situation: |
Beta Was this translation helpful? Give feedback.
This is the stick telling us that it didn't get an acknowledgement from the device that it got the command, after several attempts.
Sending commands in Z-Wave roughly works like this:
This is an oversimplification, but as you can see, Z-Wave JS has no influence on what happens after telling the stick to send something. That part of communication depends entirely on the stick's hardware, software and location, the device's hardware, software and location, as well as the physical environment (sources of RF noise and interferences, etc...)
I get similar arguments …