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.

Sign up for GitHub

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

Jump to bottom

Z-wave climate configuration not properly save #103254

Closed
liollury opened this issue Nov 2, 2023 · 5 comments · May be fixed by zwave-js/node-zwave-js#6583
Closed

Z-wave climate configuration not properly save #103254

liollury opened this issue Nov 2, 2023 · 5 comments · May be fixed by zwave-js/node-zwave-js#6583
Labels
integration: zwave_js stale

Comments

@liollury
Copy link
Contributor

liollury commented Nov 2, 2023 •
edited

The problem

I include brand new Eurotronic Comet zwave into my zwave network and I try to set parameter 6 (valve opening percent report). But when I requery device, this configuration field return to its default settings. Otherwise, this is the only parameter name that doesn't seem to be translated:
image

Logs seems to be goods at all.

What version of Home Assistant Core has the issue?

core-2023.11.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

zwave

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Niveau de journalisation modifié en : Debug
2023-11-02T15:47:20.344Z DRIVER   all queues busy
2023-11-02T15:47:20.358Z SERIAL » 0x011c001334159f03630056e662f4c9d9a091bc28dc2cc12153f5c72513fa      (30 bytes)
2023-11-02T15:47:20.371Z DRIVER » [Node 052] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      19
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 99
                                    │ security class:  S2_Unauthenticated
                                    └─[SupervisionCCGet]
                                      │ session id:      53
                                      │ request updates: true
                                      └─[ConfigurationCCSet]
                                          parameter #:      6
                                          reset to default: false
                                          value size:       1
                                          value format:     Enumerated
                                          value:            2
2023-11-02T15:47:20.381Z SERIAL « [ACK]                                                                   (0x06)
2023-11-02T15:47:20.386Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2023-11-02T15:47:20.389Z SERIAL » [ACK]                                                                   (0x06)
2023-11-02T15:47:20.394Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-11-02T15:47:21.875Z SERIAL « 0x01070013130000976f                                                 (9 bytes)
2023-11-02T15:47:21.879Z SERIAL » [ACK]                                                                   (0x06)
2023-11-02T15:47:21.885Z DRIVER « [REQ] [SendData]
                                    callback id:     19
                                    transmit status: OK
2023-11-02T15:47:21.966Z SERIAL « 0x011700040034119f03a2006e60065c32b79fa850ecb0a98430                (25 bytes)
2023-11-02T15:47:21.976Z SERIAL » [ACK]                                                                   (0x06)
2023-11-02T15:47:21.985Z DRIVER « [Node 052] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 162
                                    │ security class:  S2_Unauthenticated
                                    └─[SupervisionCCReport]
                                        session id:          53
                                        more updates follow: false
                                        status:              Success
                                        duration:            0s
2023-11-02T15:47:21.998Z DRIVER   all queues idle

Additional information

I don't know if it's an issue from HA, zwaveJS or the device.
I use Razberry V2 controller
@liollury
Copy link
Contributor Author

liollury commented Nov 3, 2023

The problem seems to be the same with some other parameters (not all). If I set parameter 4 to 1. Controller get success response :

2023-11-03T08:16:18.983Z DRIVER » [Node 054] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      152
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 217
                                    │ security class:  S2_Unauthenticated
                                    └─[SupervisionCCGet]
                                      │ session id:      49
                                      │ request updates: true
                                      └─[ConfigurationCCSet]
                                          parameter #:      4
                                          reset to default: false
                                          value size:       1
                                          value format:     SignedInteger
                                          value:            1
2023-11-03T08:16:18.989Z SERIAL « [ACK]                                                                   (0x06)
2023-11-03T08:16:18.994Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2023-11-03T08:16:18.996Z SERIAL » [ACK]                                                                   (0x06)
2023-11-03T08:16:18.999Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-11-03T08:16:20.476Z SERIAL « 0x0107001398000095e6                                                 (9 bytes)
2023-11-03T08:16:20.479Z SERIAL » [ACK]                                                                   (0x06)
2023-11-03T08:16:20.483Z DRIVER « [REQ] [SendData]
                                    callback id:     152
                                    transmit status: OK
2023-11-03T08:16:20.566Z SERIAL « 0x011700040036119f03df0095044f536b0da6789aab2a5815eb                (25 bytes)
2023-11-03T08:16:20.572Z SERIAL » [ACK]                                                                   (0x06)
2023-11-03T08:16:20.577Z DRIVER « [Node 054] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 223
                                    │ security class:  S2_Unauthenticated
                                    └─[SupervisionCCReport]
                                        session id:          49
                                        more updates follow: false
                                        status:              Success
                                        duration:            0s

But when I get this data back, device response default value :

2023-11-03T08:16:42.211Z DRIVER   all queues busy
2023-11-03T08:16:42.222Z SERIAL » 0x01160013360f9f03da00241998f4618a62b3bd0d73259991                  (24 bytes)
2023-11-03T08:16:42.227Z DRIVER » [Node 054] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      153
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 218
                                    │ security class:  S2_Unauthenticated
                                    └─[ConfigurationCCGet]
                                        parameter #: 4
2023-11-03T08:16:42.236Z SERIAL « [ACK]                                                                   (0x06)
2023-11-03T08:16:42.239Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2023-11-03T08:16:42.241Z SERIAL » [ACK]                                                                   (0x06)
2023-11-03T08:16:42.244Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-11-03T08:16:43.765Z SERIAL « 0x010700139900009ae8                                                 (9 bytes)
2023-11-03T08:16:43.770Z SERIAL » [ACK]                                                                   (0x06)
2023-11-03T08:16:43.774Z DRIVER « [REQ] [SendData]
                                    callback id:     153
                                    transmit status: OK
2023-11-03T08:16:43.854Z SERIAL « 0x011700040036119f03e00001d20b9bdff47b2aad3047dfa229                (25 bytes)
2023-11-03T08:16:43.861Z SERIAL » [ACK]                                                                   (0x06)
2023-11-03T08:16:43.867Z CNTRLR   [Node 054] [~] [Configuration] 4: 1 => 0                          [Endpoint 0]
2023-11-03T08:16:43.871Z DRIVER « [Node 054] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 224
                                    │ security class:  S2_Unauthenticated
                                    └─[ConfigurationCCReport]
                                        parameter #: 4
                                        value size:  1
                                        value:       0
2023-11-03T08:16:43.876Z DRIVER   all queues idle

@liollury liollury changed the title Zwave climate configuration not properly save Z-wave climate configuration not properly save Nov 3, 2023
@Mart124
Copy link

Mart124 commented Jan 2, 2024 •
edited

Hi,
I also have issues with my Eurotronic Comet Z-Wave device, I can't change its parameters.
Comet reports like this :
https://pastebin.com/raw/zbF6cpfY

Trying to set for example parameter 1 to 1 clearly returns a Fail status :
https://pastebin.com/raw/ePFWWBUP

Exactly same status: Fail result for every parameter change...

Running HAOS 2023.12.4.
Same issue with 2024.1.0.

Thx 👍

@home-assistant
Copy link

home-assistant bot commented Jan 2, 2024

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

zwave_js documentation
zwave_js source
(message by IssueLinks)

This was referenced Jan 4, 2024
Closed
Open
@Mart124
Copy link

Mart124 commented Jan 5, 2024

Fixed by zwave-js/node-zwave-js#6583 👍

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 11, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
integration: zwave_js stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(config): support Comet parameters properly Mart124/node-zwave-js
3 participants
@joostlek @liollury @Mart124