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

Mapping root reports to an endpoint via compat flags still exposes the value on the root #6555

Closed
7 tasks done
AlCalzone opened this issue Dec 11, 2023 Discussed in #6554 · 1 comment · Fixed by #6760
Closed
7 tasks done

Mapping root reports to an endpoint via compat flags still exposes the value on the root #6555

AlCalzone opened this issue Dec 11, 2023 Discussed in #6554 · 1 comment · Fixed by #6760
Labels
bug Something isn't working

Comments

@AlCalzone
Copy link
Member

Discussed in #6554

Originally posted by @kvaster December 11, 2023

Checklist

  • I have read and followed the above instructions

  • I have checked the troubleshooting section and my problem is not described there.

  • I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

Fibaro thermostat fgt001 have special section for reportion endpoint 0 as endpoint 1 for battery level. This is cause endpoint 0 and endpoint 1 are duplicated and endpoint 2 reports battery level for external sensor. With recent version endpoint 1 and endpoint 2 are shown during introduce and are working OK. Manual refresh also shows values OK. But when battery level is reported due to changes (withour request) - it is reported on endpoint 0 and is not remapped.

Also battery values found during introduce are shown as 'Battery v1'. And battery values reported on endpoint 0 are shown as 'Battert v0' in zwavejs-ui.

Software versions

Latest git as of this issue, but the problem was introduced since of September (approx).

Device information

Fibaro fgt001

zwave-1.tar.gz
zwave-2.tar.gz

Checklist

  • I made sure to provide a driver log on level debug.

  • The log includes a re-interview of the problematic device (if applicable).

  • The log includes the problematic interaction with the device (if applicable).

  • I provided the node ID of the problematic device (if applicable).

Upload Logfile

No response

@AlCalzone
Copy link
Member Author

Relevant log:

2023-12-11T09:42:02.627Z CNTRLR   [Node 008] [~] [Battery] level: 98 => 100                         [Endpoint 0]
2023-12-11T09:42:02.633Z CNTRLR   [Node 008] [~] [Battery] isLow: false => false                    [Endpoint 0]
2023-12-11T09:42:02.642Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
                                  └─[BatteryCCReport]
                                      level:  100
                                      is low: false
2023-12-11T09:42:02.643Z CNTRLR   [Node 008] Mapping unsolicited report from root device to endpoint #1
2023-12-11T09:42:02.644Z CNTRLR   [Node 008] [~] [Battery] level: 98 => 100                         [Endpoint 1]
2023-12-11T09:42:02.656Z CNTRLR   [Node 008] [~] [Battery] isLow: false => false                    [Endpoint 1]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant