-
Notifications
You must be signed in to change notification settings - Fork 16
Integrate unreleased command classes: multilevel sensor, schedule entry lock #143
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
base: main
Are you sure you want to change the base?
Conversation
…ss update [Philippe Coval] Add exported changes Forwarded: SiliconLabsSoftware#143 Signed-off-by: Philippe Coval <[email protected]>
Apply splited change from uic, [Philippe Coval] This patch was split in two, this version is the change that apply to Unify, please refer to previous commit to undestand the flow, I after the failed cherry-pick, I just used patch -p1 < patch and commited only the changes that applies to z-p-c, the same operation was done in UnifySDK (see log in provious patchset) Origin: ver_1.7.0-unstable-23-g38f24ffb48 Bug-SiliconLabs: UIC-3273 Origin: s.s.com/projects/UIC/repos/uic/pull-requests/2855 Relate-to: SiliconLabsSoftware#44 Forwarded: https://github.com/rzr/UnifySDK/tree/z-wave/core/zpc/main Forwarded: SiliconLabsSoftware#143 Signed-off-by: Philippe Coval <[email protected]>
Origin: ver_1.7.0-unstable-24-geddc303adc Forwarded: SiliconLabsSoftware#143 Signed-off-by: Philippe Coval <[email protected]>
5f0418b
to
9cb0a02
Compare
[Philippe Coval] This change has been applied without any change and will be forwarded to: This change was made from uic repo by exporting patch using: git format-patch -1 943ae4c683f819ae8b6407ee29aa4f7c9bd69ddf And then applied on top of z-wave/core/zpc/main (dangling branch of Unify, currently in rzr fork, that may be pushed to public Unify repo) git apply -i 0001-UIC-3273-Generated-files-for-Unify_MultilevelSensor-.patch Then a patch is generated for z-p-c project using: git format-patch --no-numbered \ -o ~/mnt/z-wave-protocol-controller/patches/UnifySDK/ \ ver_1.7.0 Bug-SiliconLabs: UIC-3273 Origin: ver_1.7.0-unstable-22-g943ae4c683 Origin: s.s.com/projects/UIC/repos/uic/pull-requests/2855 Relate-to: SiliconLabsSoftware/z-wave-protocol-controller#44 Forwarded: https://github.com/rzr/UnifySDK/tree/z-wave/core/zpc/main Forwarded: SiliconLabsSoftware/z-wave-protocol-controller#143 Signed-off-by: Philippe Coval <[email protected]>
[Philippe Coval] This patch was split in two, this version is the change that apply to Unify, please refer to previous commit to undestand the flow, I after the failed cherry-pick, I just used patch -p1 < patch and commited only the changes that applies to Unify, the same operation should be done for z-p-c project (in the opposite way). Origin: ver_1.7.0-unstable-23-g38f24ffb48 Bug-SiliconLabs: UIC-3273 Origin: s.s.com/projects/UIC/repos/uic/pull-requests/2855 Relate-to: SiliconLabsSoftware/z-wave-protocol-controller#44 Forwarded: https://github.com/rzr/UnifySDK/tree/z-wave/core/zpc/main Forwarded: SiliconLabsSoftware/z-wave-protocol-controller#143 Signed-off-by: Philippe Coval <[email protected]>
…ss update [Philippe Coval] Add exported changes Forwarded: SiliconLabsSoftware#143 Signed-off-by: Philippe Coval <[email protected]>
Apply splited change from uic, [Philippe Coval] This patch was split in two, this version is the change that apply to Unify, please refer to previous commit to undestand the flow, I after the failed cherry-pick, I just used patch -p1 < patch and commited only the changes that applies to z-p-c, the same operation was done in UnifySDK (see log in provious patchset) Origin: ver_1.7.0-unstable-23-g38f24ffb48 Bug-SiliconLabs: UIC-3273 Origin: s.s.com/projects/UIC/repos/uic/pull-requests/2855 Relate-to: SiliconLabsSoftware#44 Forwarded: https://github.com/rzr/UnifySDK/tree/z-wave/core/zpc/main Forwarded: SiliconLabsSoftware#143 Signed-off-by: Philippe Coval <[email protected]>
Origin: ver_1.7.0-unstable-24-geddc303adc Forwarded: SiliconLabsSoftware#143 Signed-off-by: Philippe Coval <[email protected]>
9cb0a02
to
6d1f387
Compare
[Philippe Coval] This patch was split in two, this version is the change that apply to Unify, please refer to previous commit to undestand the flow, I after the failed cherry-pick, I just used patch -p1 < patch and commited only the changes that applies to Unify, the same operation should be done for z-p-c project (in the opposite way). Origin: ver_1.7.0-unstable-23-g38f24ffb48 Bug-SiliconLabs: UIC-3273 Origin: s.s.com/projects/UIC/repos/uic/pull-requests/2855 Relate-to: SiliconLabsSoftware/z-wave-protocol-controller#44 Forwarded: https://github.com/rzr/UnifySDK/tree/z-wave/core/zpc/main Forwarded: SiliconLabsSoftware/z-wave-protocol-controller#143 Signed-off-by: Philippe Coval <[email protected]>
[Philippe Coval] This change has been applied without any change and will be forwarded to: This change was made from uic repo by exporting patch using: git format-patch -1 943ae4c683f819ae8b6407ee29aa4f7c9bd69ddf And then applied on top of z-wave/core/zpc/main (dangling branch of Unify, currently in rzr fork, that may be pushed to public Unify repo) git apply -i 0001-UIC-3273-Generated-files-for-Unify_MultilevelSensor-.patch Then a patch is generated for z-p-c project using: git format-patch --no-numbered \ -o ~/mnt/z-wave-protocol-controller/patches/UnifySDK/ \ ver_1.7.0 Bug-SiliconLabs: UIC-3273 Origin: ver_1.7.0-unstable-22-g943ae4c683 Origin: s.s.com/projects/UIC/repos/uic/pull-requests/2855 Relate-to: SiliconLabsSoftware/z-wave-protocol-controller#44 Forwarded: https://github.com/rzr/UnifySDK/tree/z-wave/core/zpc/main Forwarded: SiliconLabsSoftware/z-wave-protocol-controller#143 Signed-off-by: Philippe Coval <[email protected]>
…ss update [Philippe Coval] Add exported changes Forwarded: SiliconLabsSoftware#143 Signed-off-by: Philippe Coval <[email protected]>
Apply splited change from uic, [Philippe Coval] This patch was split in two, this version is the change that apply to Unify, please refer to previous commit to undestand the flow, I after the failed cherry-pick, I just used patch -p1 < patch and commited only the changes that applies to z-p-c, the same operation was done in UnifySDK (see log in provious patchset) Origin: ver_1.7.0-unstable-23-g38f24ffb48 Bug-SiliconLabs: UIC-3273 Origin: s.s.com/projects/UIC/repos/uic/pull-requests/2855 Relate-to: #44 Forwarded: https://github.com/rzr/UnifySDK/tree/z-wave/core/zpc/main Forwarded: #143 Signed-off-by: Philippe Coval <[email protected]>
Origin: ver_1.7.0-unstable-24-geddc303adc Forwarded: #143 Signed-off-by: Philippe Coval <[email protected]>
6d1f387
to
25e4765
Compare
…ltilevelSensor-.patch (phcoval/cc/review/main) Signed-off-by: Philippe Coval <[email protected]>
Apply splited change from uic, [Philippe Coval] This patch was split in two, this version is the change that apply to Unify, please refer to previous commit to undestand the flow, I after the failed cherry-pick, I just used patch -p1 < patch and commited only the changes that applies to z-p-c, the same operation was done in UnifySDK (see log in provious patchset) Origin: ver_1.7.0-unstable-23-g38f24ffb48 Bug-SiliconLabs: UIC-3273 Origin: s.s.com/projects/UIC/repos/uic/pull-requests/2855 Relate-to: SiliconLabsSoftware#44 Forwarded: https://github.com/rzr/UnifySDK/tree/z-wave/core/zpc/main Forwarded: SiliconLabsSoftware#143 Signed-off-by: Philippe Coval <[email protected]>
Origin: ver_1.7.0-unstable-24-geddc303adc Forwarded: SiliconLabsSoftware#143 Signed-off-by: Philippe Coval <[email protected]>
Signed-off-by: Philippe Coval <[email protected]>
Merge in UIC/uic from feature/UIC-3434-data-model-Schedule-Entry-CC to feature/UIC-3271-Schedule-Entry-Lock-CC
Merge in UIC/uic from feature/UIC-3435-Base-Skeleton-Code-Schedule-Entry-Lock-CC to feature/UIC-3271-Schedule-Entry-Lock-CC
Merge in UIC/uic from feature/UIC-3438-dotdot-mapper-Setup-Schedule-Entry-Lock-CC to feature/UIC-3271-Schedule-Entry-Lock-CC
Merge in UIC/uic from feature/UIC-3436-Attribute-resolver-rules-ScheduleEntryLock-CC to feature/UIC-3271-Schedule-Entry-Lock-CC
Merge in UIC/uic from feature/UIC-3494-dotdot-command-handlers-in-ZPC-ScheduleEntryLock-CC to feature/UIC-3271-Schedule-Entry-Lock-CC
Merge in UIC/uic from feature/UIC-3437-Report-callback-Schedule-Entry-Lock-CC to feature/UIC-3271-Schedule-Entry-Lock-CC
Merge in UIC/uic from feature/UIC-3439-Unit-Test-Schedule-Entry-Lock-CC to feature/UIC-3271-Schedule-Entry-Lock-CC
25e4765
to
de5870b
Compare
Hi @rzr, how do you want me to test this PR? I've able to install and run zpc on WSL2, Ubuntu 22.04.5LTS but have to disable some python3 packages for doc generation. |
Dont we have features implemented in sample apps ? if not I know that ZWA is providing EDE tool (to be used along CTT for certification, let's investigate about it: https://z-wavealliance.org/certification-overview/zwa-certification-tutorial/ https://github.com/Z-Wave-Alliance/ede/issues/6 )
ok i was running on debian 12 , let try to support 22.04 |
Change
Checklist