Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HomeSeer HS-WX300R1 in switch mode ignores on or off commands from HA #732

Open
vikingsource opened this issue Nov 23, 2024 · 0 comments
Open

Comments

@vikingsource
Copy link

Problem/Motivation

After including a HomeSeer HS-WX300R1 in switch mode it cannot be turned on or off by Home Assistant. The HS-WX300R2 with the same command set (different chip set) works as expected.

Expected behavior

Turning on the debug in JS UI, the R2 version produce the following output and works as expected when using a control to turn on:

2024-11-22 20:39:47.331 INFO STORE: [Node 213] Value updated: 37-0-targetValue false => true
2024-11-22 20:39:47.333 INFO STORE: [Node 213] Value updated: 37-0-currentValue false => true
2024-11-22 20:39:47.594 INFO STORE: [Node 213] Value updated: 37-0-currentValue true => true
2024-11-22 20:39:47.595 INFO STORE: [Node 213] Value updated: 37-0-targetValue true => true
2024-11-22 20:39:47.596 INFO STORE: [Node 213] Value updated: 37-0-duration 0s => 0s

Actual behavior

The same action for the R1 device results in the following output and the device does not change state:

2024-11-23T04:25:24.715Z CNTRLR « [Node 217] TODO: no handler for application command
2024-11-22 20:25:25.208 INFO STORE: [Node 217] Value updated: 37-0-targetValue false => true
2024-11-22 20:25:25.209 INFO STORE: [Node 217] Value updated: 37-0-currentValue false => true
2024-11-23T04:25:26.243Z CNTRLR « [Node 217] TODO: no handler for application command
2024-11-23T04:25:27.258Z CNTRLR   [Node 217] Timed out while waiting for a response from the node (ZW0201)

Steps to reproduce

  1. Factory reset the device (observe all LEDs blink several times)
  2. Press the on-device button to place the device in switch mode (observe bottom LED blink blue)
  3. Scan the QR code on the device and include it in the lists of smart start devices
  4. Get a verification that the device has been included
  5. Send an on or command to the device and nothing happens
  6. Manually press the device rocker and observe that the status in HA changes
  7. Use the JS UI to change other configuration parameters and the device accept these

Proposed changes

Since the R2 version works without any problems and they share the same command set, it appears that there might be something wrong with the device definition. However, I'm new to both HA and Z-wave, so the problem may be somewhere else. Pls let me know if this issue needs to be filed against some other component in HA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant