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

fix(config): correct parameter 5 size for Zooz ZEN34 #6546

Merged
merged 1 commit into from
Dec 8, 2023
Merged

fix(config): correct parameter 5 size for Zooz ZEN34 #6546

merged 1 commit into from
Dec 8, 2023

Conversation

The00Dustin
Copy link
Contributor

@The00Dustin The00Dustin commented Dec 6, 2023 •
edited
Loading

I have tested this change by replacing this file via the Z-Wave JS UI store section and restarting.

@The00Dustin
fix(config): Correct parameter 5 size for Zooz ZEN34
a7555b4 
I have tested this change by replacing this file via the Z-Wave JS UI store section and restarting.
@zwave-js-assistant zwave-js-assistant bot added the config ⚙ Configuration issues or updates label Dec 6, 2023
@The00Dustin The00Dustin changed the title fix(config): Correct parameter 5 size for Zooz ZEN34 fix(config): correct parameter 5 size for Zooz ZEN34 Dec 6, 2023
@AlCalzone AlCalzone merged commit 00b09b1 into zwave-js:master Dec 8, 2023
15 checks passed
AlCalzone added a commit that referenced this pull request Dec 9, 2023
@AlCalzone
chore: release v12.4.1
9549a04 
### Bugfixes
* Handle more cases of unexpected Serial API restarts (#6551)

### Config file changes
* Add wakeup instructions for Nexia ZSENS930 (#6545)
* Correct parameter 5 size for Zooz ZEN34 (#6546)
@The00Dustin The00Dustin deleted the Zen34Param5 branch March 11, 2024 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@AlCalzone AlCalzone AlCalzone approved these changes

Assignees
No one assigned
Labels
config ⚙ Configuration issues or updates
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@The00Dustin @AlCalzone